3 ms·

What are some other options in this space? What I need: - Focus on transactional email. - Support for inbound emails, sent to us via POST webhook. - Good de

What are some other options in this space? What I need: - Focus on transactional email. - Support for inbound emails, sent to us via POST webhook. - Good developer documentation and overall good product obviously. - DKIM, SPF and DMARC support. - Decent UI to troubleshoot delivery problems, i.e. easy to inspect the status for any one email. - Happy to pay for it, price not a big factor. I've looked at Mailgun, but happy to hear other suggestions.

kevincox 4y ago
I run an email based service and while I send most email on my own I have been using the following providers for fall-back (for inbox providers that have very strict policies). - https://serversmtp.com/ https://serversmtp.com/ - https://aws.amazon.com/ses/ https://aws.amazon.com/ses/ I prefer SES for a number of reasons: - The price is about the best you will get. - You can DKIM sign messages yourself if you want (although IIRC they remove the ability to verify your domain with DKIM from the console recently. Hopefully they don't drop this support). - Pay as you go Pricing means that you don't pay for unused quota. - Regional service may be more complicated but in theory you should be able to tolerate localized issues. The main downside is that you need to verify in each region which is very annoying.
slices 4y ago
just transitioned a client off mailgun due to repeated deliverability issues caused by other mailgun customers on a shared IP. The client doesn't have enough email volume to justify a dedicated IP, so there didn't seem to be anything else we could do while sticking with mailgun. wouldn't you know it, we transferred them to postmark...
rbut 4y ago
I now use Postal Server for all my SaaS, which is self-hosted via docker, and has all those those features. The good thing is your maintain the IP reputation yourself and your not paying exorbitant prices when sending large volumes of transactional emails (really it's just the cost of the server you install it on). https://github.com/postalserver/postal https://github.com/postalserver/postal

kevincox 4y ago

I run an email based service and while I send most email on my own I have been using the following providers for fall-back (for inbox providers that have very strict policies). - https://serversmtp.com/ https://serversmtp.com/ - https://aws.amazon.com/ses/ https://aws.amazon.com/ses/ I prefer SES for a number of reasons: - The price is about the best you will get. - You can DKIM sign messages yourself if you want (although IIRC they remove the ability to verify your domain with DKIM from the console recently. Hopefully they don't drop this support). - Pay as you go Pricing means that you don't pay for unused quota. - Regional service may be more complicated but in theory you should be able to tolerate localized issues. The main downside is that you need to verify in each region which is very annoying.

slices 4y ago

just transitioned a client off mailgun due to repeated deliverability issues caused by other mailgun customers on a shared IP. The client doesn't have enough email volume to justify a dedicated IP, so there didn't seem to be anything else we could do while sticking with mailgun. wouldn't you know it, we transferred them to postmark...

rbut 4y ago

I now use Postal Server for all my SaaS, which is self-hosted via docker, and has all those those features. The good thing is your maintain the IP reputation yourself and your not paying exorbitant prices when sending large volumes of transactional emails (really it's just the cost of the server you install it on). https://github.com/postalserver/postal https://github.com/postalserver/postal