Skip to content

Comment on Tell HN: Gmail rate limiting emails from AWS SESparent

Comments

Using SES is buying email delivery from a company who is in that business.

Disagree here. The sendgrid, mailchimp, postmark of the world are in the business of sending emails. They have their dedicated IPs and handle deliverability, anti spam, and whatnot with email providers like Gmail.

SES is an email sending infrastructure tool. That's not the same.

IMO equating SES with an email company is like saying home depot is a contractor because they sell hammers and lumber. It gives you the tools to be able to build stuff but it's not the same as a construction company.

SES, like Mailchimp, Sendgrid, and Postmark, has dedicated IPs as a paid add-on.

SES is not in the business of ensuring deliverability for your email. Dedicated ips is another hammer that they sell.

If Amazon can't make it work, might just use good old postfix I guess.

My anecdotal evidence is that simple postfix setup with IP from a reputable hoster which is not blacklisted works perfectly. And it's actually pretty simple to configure postfix for sending mail (now configuring postfix + dovecot + auth + spam filtering is another story).

If Amazon can't make it work, might just use good old postfix I guess.

AWS blocks TCP25 outbound by default [1].

[1] https://repost.aws/knowledge-center/ec2-port-25-throttle

My anecdotal evidence is that simple postfix setup with IP from a reputable hoster which is not blacklisted works perfectly.

And my anecdotal evidence is that it does not work perfectly: https://www.attejuvonen.fi/dont-send-email-from-your-own-ser...

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.