Readit Newsandris9 commented on Bichon: A lightweight, high-performance Rust email archiver with WebUI github.com/rustmailer/bic... · Posted by u/rendx
It's slow, unreliable, very feature-limited, and extremely expensive for what it is.
Especially these days, you could vibe-code something an order of magnitude better within a day or two and not be locked into a single author's rat's nest of code.
At this point, almost all new EmailEngine customers are AI startups. These are teams that know how to use LLMs well, which makes it interesting that they still opt for EmailEngine despite the extremely expensive $83/month price tag.
andris9 commented on Bichon: A lightweight, high-performance Rust email archiver with WebUI github.com/rustmailer/bic... · Posted by u/rendx
It’s a great honor to be able to talk with Andris. A few months ago I learned that the author of EmailEngine not only created EmailEngine, but is also behind many foundational Node.js email libraries that are widely used. My own projects, RustMailer and Bichon, are built on the shoulders of many great Rust email libraries. EmailEngine is undoubtedly a success, and Andris has spent years quietly and diligently contributing to these core libraries. I have deep respect for you.
Thanks, and best of luck with Rustmailer! I believe there’s plenty of room for multiple solutions in this space.
andris9 commented on Bichon: A lightweight, high-performance Rust email archiver with WebUI github.com/rustmailer/bic... · Posted by u/rendx
Why?
EmailEngine author here. The commenter tried the EmailEngine trial back in 2024 and appears to have had a negative experience. Since then, he’s repeatedly criticized EmailEngine and related components like the ImapFlow IMAP library, often while promoting his own product.
andris9 commented on A Postmark backdoor that’s downloading emails koi.security/blog/postmar... · Posted by u/ghuntley
I came here to say this too. I’m really not sure he’d leave his very public personal email in there in purpose. I am not ashamed to say I still use my personal Gmail for testing in 2025.
By the way, this is not specific to MCP, could have happened to any package.
I maintain the Nodemailer library. Several years ago I used my personal email in a few usage examples. Developers still copy that old snippet, add their SMTP credentials and send test emails - which land in my inbox.
I once flew to the US for a week on ESTA to attend a few meetings (pre-COVID), but I mostly just did my regular developer work in the US office. By today’s standards, would I have been shackled for that?
I have two:
The first is a preventive maintenance and calibration tracker (https://pmcal.net) that was born out of my day job as an engineer in small business manufacturing.
The second is an AI engine for pulling structured data out of incoming email (either via IMAP on your email server or via SES). If you think of the engine that powers TripIt, they had to write about 10,000 different ingestors for each airline and hotel and travel booking site. With a structured output AI, the need to write specific ingestors goes away.
You can also get structured data out of mailboxes with my project EmailEngine. You can use an API request to fetch message contents, or you can configure EmailEngine to send a webhook for every new email in a structured JSON, for example, like this: https://emailengine.app/webhooks#messageNew
andris9 commented on Ask HN: How do you ensure you don't get locked from your email? · Posted by u/stankot
I renew my essential domain names in 10‑year increments. As long as I control the domain, I can spin up new mail hosting if any provider boots me. I’d lose the old messages stored on their servers, but the address itself keeps working.
Service discovery is handled via the port-forwarding model. A node can advertise a named endpoint (e.g. an Ollama instance), and another node can bind a local listener to that key. The mesh routes traffic end-to-end encrypted, so from the client’s perspective it behaves like a local port even though the service is remote.
For distributed inference, the main constraints are latency and hop count - extra hops add delay, which is fine for background work but relevant for interactive use. Everything runs in userspace, and outbound connections plus QUIC make it usable behind typical residential NATs.