Show HN: Listmonk – Fast self-hosted newsletter and mailing list manager
1–10 of 52 posts
Re: Show HN: Listmonk – Fast self-hosted newsletter and mailing list manager
#2What 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
#3Re: Show HN: Listmonk – Fast self-hosted newsletter and mailing list manager
#4Does the AGPL licence mean that every email (the recipient being a 'network user') needs a 'sent with listmonk, source code is here' footer?
Re: Show HN: Listmonk – Fast self-hosted newsletter and mailing list manager
#5Projects 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?
PS: Postal SMTP is awesome.
Re: Show HN: Listmonk – Fast self-hosted newsletter and mailing list manager
#6Does the AGPL licence mean that every email (the recipient being a 'network user') needs a 'sent with listmonk, source code is here' footer?
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
#7Projects 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
#8This looks like the free/open-source version to Sendy based on more modern tech like Golang/Docker/etc I've been hoping for, congrats on your alpha release!
Re: Show HN: Listmonk – Fast self-hosted newsletter and mailing list manager
#9Projects 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?
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.