45 days ago · Tech · hide · Fediverse post

When you’re launching a brand new SaaS application or service, you know it’s going to send emails. That means you’ve got to pick an email delivery service. Which API are you going to use to allow your new app to send transactional emails to the world? Luckily, the market is crowded with options: SendGrid, Mailchimp’s Mandrill, Amazon SES, Mailgun, Postmark, Mailersend – the list goes on. For most developers, dropping in an API key from one of these transactional providers is the path of least resistance. But what if you don't want to rely on a third-party vendor? What if you want -- or need -- to run your own email infrastructure?Historically, self-hosting transactional email meant cobbling together a traditional Unix email stack. You’d spin up Postfix or Exim on a VPS, build a custom API wrapper to hand messages off to the MTA, maybe configure queues, maybe configure your application to relay via SMTP. It’s doable, but it’s a heavy lift. I know. I’ve done it. I still crazily run my…

Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town