Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tell HN: Gmail rate limiting emails from AWS SES

news.ycombinator.com

Post reply on HN
Print view View original

31–40 of 92 posts

Re: Tell HN: Gmail rate limiting emails from AWS SES

#31

Post by ctas »

Do you have a custom return-path configured? Using a custom return path might help, because it ties your reputation primarily to your domain.

ESPs check multiple factors. Both IP and domain reputation play a role. They will check your return path / envelope sender domain reputation and your IP. Your domain will start with it's own reputation, but can be boosted with a good IP reputation. But if your domain had bad sending behaviour in the past, that might be an issue.

Source: I'm running a transactional mail service that solely works with shared IPs: https://www.markix.com.

Re: Tell HN: Gmail rate limiting emails from AWS SES

#32

Post by [deleted] »

nostrebored wrote: post #20
alyandon wrote: post #8

Earlier quoted context omitted.

I finally started sending anything from AWS SES straight to trash because the spam on their platform is persistent and they are non-responsive to spam reports. I was getting 30+ fraudulent/spam emails a day in just one inbox alone.

That's untrue. I can tell you that spam reports and bounces are monitored, and customers do have to go through validation of their workflows if they breach thresholds. I had to help multiple customers who had access to SES shut off for valid use cases because they didn't handle events coming back from customers appropriately.

[deleted]

Re: Tell HN: Gmail rate limiting emails from AWS SES

#33

Post by jeffbee »

LeonM wrote: post #22
leetrout wrote: post #13

Earlier quoted context omitted.

Not entirely true. There is a reason Mailchimp owns a rather large block of IP addresses. https://ipinfo.io/AS14782

> Not entirely true OK you are right, Gmail may use IP-based rating, but it only does that if there isn't sufficient proof (in form of DKIM signatures) that the email is sent on behalf of the domain. If the email is DKIM aligned, then domain rating is used. I just didn't want to go that far into detail in my post. > There is a reason Mailchimp owns a rather large block of IP addresses. The reason is mostly for suppor…

I don't think this is accurate. Address reputation is an important signal regardless of DKIM.

Re: Tell HN: Gmail rate limiting emails from AWS SES

#34

Post by mschuster91 »

vbezhenar wrote: post #23
anamexis wrote: post #10

Earlier quoted context omitted.

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

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

Re: Tell HN: Gmail rate limiting emails from AWS SES

#35

Post by mprovost »

messutied wrote: post #29
kunwon1 wrote: post #14

Amazon SES is not a good choice for sending critical email notifications. Their 'global suppression list' [1] has caused no end of headaches for me and my clients. If you and I are both using SES to send to the same person, and my message results in a hard bounce, then your messages to that person will start to silently fail. [1] https://docs.aws.amazon.com/ses/latest/dg/sending-email-glob...

Would you happen to know of better alternatives for sending critical email notifications? We're just now working on moving away from Mailgun into SES. This thread is making me reconsider.

"Critical" and "email" don't generally go together.

Re: Tell HN: Gmail rate limiting emails from AWS SES

#36

Post by 0ct4via »

nostrebored wrote: post #20
alyandon wrote: post #8

Earlier quoted context omitted.

I finally started sending anything from AWS SES straight to trash because the spam on their platform is persistent and they are non-responsive to spam reports. I was getting 30+ fraudulent/spam emails a day in just one inbox alone.

That's untrue. I can tell you that spam reports and bounces are monitored, and customers do have to go through validation of their workflows if they breach thresholds. I had to help multiple customers who had access to SES shut off for valid use cases because they didn't handle events coming back from customers appropriately.

Your experience of customers not handling events appropriately - and then having SES access revoked - does not negate or disprove alyandon's experience of getting no responses to spam reports.

You may have had a different experience, but that doesn't make their (differing) experience "untrue."

Re: Tell HN: Gmail rate limiting emails from AWS SES

#38

Post by jeffbee »

baobabKoodaa wrote: post #7
jeroenhd wrote: post #4

Things like this are to be expected with shared IP addresses for mail services. This sounds like something Amazon should figure out more than anything. There's probably something going on with a customer or theirs (misconfiguration, spammer, vulnerability exploited) that's triggering spam detection rules. At least Google reports the issue back to you instead of silently dropping all of your email like many other mail…

Google also silently drops mail in some cases.

Which cases?

Re: Tell HN: Gmail rate limiting emails from AWS SES

#39

Post by 0ct4via »

gog wrote: post #27

[flagged]

What an insightful and intelligent comment, that contributes incredible wealth to the current discourse, and doesn't minimize the seriousness of cancer at all - not.

"Omit internet tropes" is pretty clear in the guidelines, and failing to make any kind of intelligent or reasoned argument adds nothing to the conversation here. Do better.

Re: Tell HN: Gmail rate limiting emails from AWS SES

#40

Post by alyandon »

nostrebored wrote: post #20
alyandon wrote: post #8

Earlier quoted context omitted.

I finally started sending anything from AWS SES straight to trash because the spam on their platform is persistent and they are non-responsive to spam reports. I was getting 30+ fraudulent/spam emails a day in just one inbox alone.

That's untrue. I can tell you that spam reports and bounces are monitored, and customers do have to go through validation of their workflows if they breach thresholds. I had to help multiple customers who had access to SES shut off for valid use cases because they didn't handle events coming back from customers appropriately.

  I can tell you that spam reports and bounces are monitored
If they are, I saw no evidence of that (except for the initial auto-response) based on the numerous spam reports I manually submitted with headers, dates/times and body content.

If you work for SES, you all aren't acting swiftly enough to shut down egregious spam operators using your platform that are making other people's lives miserable.

Post reply on HN