An issue that recently hit us: if you're going to be testing mail, then use the SES test addresses. Don't use your own or fake addresses. If SES get x% bounces

An issue that recently hit us: if you're going to be testing mail, then use the SES test addresses. Don't use your own or fake addresses. If SES get x% bounces on any outbound address, it will cut off your SES access across the board, and it doesn't come back on quickly. We had a test address that was purposefully undeliverable. A test script sent out thousands of mails when it shouldn't have, and those undeliverable mails got treated as bounces. So, we got our SES cut off for two days, despite our clearly test/undeliverable mail being the cause. Regular AWS support can't do anything, only a special email unlock team can (they protect the 'deliverability' of AWS mail), and they're not exactly responsive. http://docs.aws.amazon.com/ses/latest/DeveloperGuide/mailbox-simulator.html http://docs.aws.amazon.com/ses/latest/DeveloperGuide/mailbox...