Live data from Hacker News

Show HN: Posthorn, self-hosted mail gateway

github.com

61–68 of 68 posts

Re: Show HN: Posthorn, self-hosted mail gateway

#61
post #60

Earlier quoted context omitted.

Security is the main worry when hosting email servers, not just of the email service, but also in preventing attacks via email. Antivirus integration is available with Postal. May be it is a good idea to chain multiple antivirus solutions. Instead of just expecting that Google or Microsoft would prevent malicious email, Postal may enable better control and transparency.

No, this isn't a worry. Where are you sourcing this? "not just the email service, but also preventing attacks via email".. is saying the same thing, in a rather GPT style.

Hey, disagree with me, if you will. Please don't say what I am saying is GPT style. Very insulting.

Re: Show HN: Posthorn, self-hosted mail gateway

#67

Does the SMTP relay handle DMARC aggregate reports, or do you still need something like parsedmarc set up alongside it? That's always the loose end when I put these together.

No, Posthorn is outbound only. DMARC aggregate reports come back as inbound mail to whatever address you put in your rua tag and Posthorn has no inbox or IMAP to receive them.

Parsedmarc is still the right tool if you want to self host reporting, otherwise you should look into solving this with your provider. Explicitly trying to avoid dealing with all the operational costs of running a mail server, just trying to enable email capabilities in apps that need it so it's beyond the scope of what I built here.

Re: Show HN: Posthorn, self-hosted mail gateway

#68

Compare that to the simplicity of https://github.com/marius/postfix-sendgrid and https://github.com/marius/postfix-mailgun

Yeah, those are similar but narrower scope tools. They do one thing, sit behind a firewall, listen on port 25 and forward SMTP submissions to sendgrid/mailgun's endpoint using an API key.

Posthorn adds an HTTP form endpoint (which is safe to expose to the internet), a JSON API with Bearer auth and idempotency, and a provider abstraction so you can use a broad range of providers via config.

If you just need to forward SMTP requests behind a firewall to a single provider, those are far simpler solutions and Posthorn is overkill. The moment you need anything outside of that, I couldn't find a solution that worked and that's the gap I built Posthorn to fill.

Happy to take any feedback on my approach, either here or in GitHub issues.

Post reply on HN