Re:A serverless email server on AWS using S3 and SES
by dfsegoat on Friday April 30, 2021 @10:03AM
(#26993595)
Individual SES IP's have been [temporarily] blacklisted before. We hit this issue earlier this year with one spam filter/service, and you can find plenty of past examples in the SES forums.
e.g.
Re:A serverless email server on AWS using S3 and SES
by acdha on Friday April 30, 2021 @10:19AM
(#26993794)
Sorry, I should have said significant problems. If you send email on anything like a large-scale basis you’ll get on some kind of blacklist at some time – all you need is one user sending email to someone with a twitchy spam reporting reflex. What I was thinking about, though, is that it’s usually transient – e.g. out of hundreds of thousands of emails I’ve never had one bounce that way instead of being delayed, which is better then self-hosting on a long-time class B over a similar timeframe.
Are you thinking of EC2? SES has never had a problem with this in my experience.
Regarding verification, you can verify any email address where you can receive a link long enough to click on it. Domain validation is only needed if you want to send mail from arbitrary addresses without that step.