Live data from Hacker News

Show HN: Listmonk – Fast self-hosted newsletter and mailing list manager

github.com

1–10 of 52 posts

Re: Show HN: Listmonk – Fast self-hosted newsletter and mailing list manager

#2
Projects like this seem like a great idea, but deliverability seems like a big concern that is hard to measure unless you have a reasonable amount of experience.

What are best practices for using/selecting an ESP if you were to use a project like this and want to ensure reasonable deliverability?

Re: Show HN: Listmonk – Fast self-hosted newsletter and mailing list manager

#5

Projects like this seem like a great idea, but deliverability seems like a big concern that is hard to measure unless you have a reasonable amount of experience. What are best practices for using/selecting an ESP if you were to use a project like this and want to ensure reasonable deliverability?

Author here. We've been using listmonk in production at our company (regulated financial business) to deliver e-mail updates including regulatory ones for over 6 months. We host our own SMTP instances using Postal[1] on EC2 instances and have never had any issues with deliverability. If it's legitimate e-mail, I don't think it's much of an issue.

PS: Postal SMTP is awesome.

[1] https://github.com/atech/postal

Re: Show HN: Listmonk – Fast self-hosted newsletter and mailing list manager

#6
post #3

Does the AGPL licence mean that every email (the recipient being a 'network user') needs a 'sent with listmonk, source code is here' footer?

Why would it? That's not part of the license.

Besides, that an email is produced by an AGPL software does not make it covered by the AGPL. That should be exactly the same legal situation as with open source text editors.

Re: Show HN: Listmonk – Fast self-hosted newsletter and mailing list manager

#7

Projects like this seem like a great idea, but deliverability seems like a big concern that is hard to measure unless you have a reasonable amount of experience. What are best practices for using/selecting an ESP if you were to use a project like this and want to ensure reasonable deliverability?

Deliverability is a non-issue if you hook tools like this and Sendy up to Amazon SES with DKIM and verified MAIL FROM settings. I've been doing it for years and never once had a deliverability issue. I've also sent directly from EC2 instances without issues but SES is so cheap and reliable I've stuck with it.

Re: Show HN: Listmonk – Fast self-hosted newsletter and mailing list manager

#9

Projects like this seem like a great idea, but deliverability seems like a big concern that is hard to measure unless you have a reasonable amount of experience. What are best practices for using/selecting an ESP if you were to use a project like this and want to ensure reasonable deliverability?

I wonder if orgs using gApps can use it as an SMTP relay as a possible solution. My team did this (except we used our Office365 as a relay) when one of our clients brought in a new firewall and found that password reset emails were being blocked coming out of AWS.

Now before you mention how this should be a solveable problem inn AWS, we’re already well underway testing with the client. The problem presented itself as a manifestation of inheriting the last guy’s infrastructure and working to...unfuck a lot of his questionable design choices.

Post reply on HN