(Quote)

delivery problems, except for Sendinblue and Amazon SES. But note that that is just my experience.

https://aws.amazon.com/ses/faqs/#Spam_and_Viruses

@M66B: Could one conclude that the issue of IP reputation is potentially more of an issue in practice with Amazon SES than it is with mxroute.io?

Check under "health" in the Amazon SES dashboard and you'll see the current "health" and if you drill the metrics down you can see the limits. They have a system wi

(Quote)

I don't have a firm opinion on what Amazon SES should do about those (rogue?) lists. It would be a constant battle for them, perhaps not worth the effort, especially if they don't charge more. :-D

disabling your account for a single complaint. Amazon allows a small percentage of bounces and complaints, which is fair because the world is not perfect.

If you use a dedicated SES IP you are responsible for it's reputation. If you use the SES pool amazon are.

Perhaps I misunderstood the (somewhat fragmented) discussion above. In any case, assuming you're right, this could also be viewed as a potential disadvantage of Amazon SES.

(Quote)

run my own mailserver for years, then moved to amazon workmail and then to office 365... why? Because I don't have the time to make a mailserver sing. It was a similar journey for SMTP... relay'd my

Okay, so this may be a disadvantage of Amazon SES: (very?/too?) heavy vetting of emails, and the consequent need to explain the situation to them.

(Quote)

on your way to be viewed as a possible shill for Amazon. People expect openly stated representatives of a brand to talk about it when it's mentioned, they don't expect a neutral third party to contin

(Quote)

@M66B no one is doing that, you're trying to build a narrative that others are doing it so that you can play some weird "hero" role. It's really awkward honestly. Especially when you

(Quote)

(Quote)

(Quote)