suppression
When someone sends a complaint to your compliance desk there are a range of things you want to do, but one thing you always want to do is ensure that the recipient doesn’t receive any more unwanted email from your customer. Or, at least, not from your network. There are usually several different ways you can make sure that happens. There are big hammers a compliance desk can use in egregious cases – if the customer is immediately terminated, or has their ability to send mail suspended then there won’t be any more unwanted email to anyone, including the person who has reported unwanted mail. More normally, though, you’ll want to stop all mail from your customer to just the person reporting them immediately, at least while you look at the customers statistics and investigate further. If the report includes a copy of the offending email then there’ll be an
This is a bit of a random post, with a bit of a random data point, but it surprised me and I thought those who send via SES might want to know. Because I am not entirely sure that it’s well known.On the Amazon SES FAQ page, they answer the question, “Can my email deliverability affected by bounces or complaints that are caused by other Amazon SES users?”The answer is basically, “mumble mumble, no not really, but.” (They don’t really address the potential for shared IP reputation issues; and I’m not sure I want to pick at that scab here. Maybe in a followup post.)The interesting bit is this, though:An exception to this rule occurs when a recipient’s email address generates a hard bounce. When a recipient’s email address generates a hard bounce, Amazon SES adds that address to a global suppression list. If you try to send an email…