Hacker News Reader

I don't know, it sounds like you've just implemented all of those things n+1 times.

And practically every web framework out there provides exactly this type of reusable functionality, not tied to a specific vendor.

I think a lot is hidden inside "which calls SES" versus "point it at your MTA, do a ton of configuration, then it may work."

Email is unfortunately a moving target. What worked before, gradually stops working as the big providers put up increasing obstacles to your own MTA doing a successful delivery.

I've heard Amazon SES also has delivery problems so take with a pinch of salt. But I would hope they generally try to maintain it.

I agree, but then I think then we're comparing using SES (or Mailgun/Sendgrid/Mandrill/whatever) versus maintaining your own MTA, which is orthogonal to the serverless vs non-serverless debate.

Reply on news.ycombinator.com