Is Amazon SES a reputable place to send mail from

On the first installment of our Wednesday question series, I chose a question from twitter.

Can you advise is Amazon SES is a reputable place to send email from? @inkpixelspaper

This is a great question. In many cases the reputation of a provider doesn’t affect delivery, but as with almost everything in email there are exceptions and cases where a poor provider reputation may affect delivery of mail from all their customers. In almost all of the cases, though, the underlying issue is the provider not requiring good behaviour from their customers.
A common scenario is a provider (either ISP or ESP) not having the time, resources or desire to handle an abuse desk. Complaints about spam don’t get handled and ISPs and filtering companies just start blocking more and more of the IP space. More and more customers, even the ones who are sending wanted, opt-in mail find their delivery starting to suffer. Customers that have good polices start moving elsewhere. At the same time, customers that have been tossed off other providers start migrating to that provider.
This scenario is more common with shared IP addresses, where a few bad apple customers can cause problems for everyone on that IP address. But I have also seen it happen with providers who offer dedicated IP addresses, particularly if those providers move problem customers around in order to avoid blocks or filters.
What does this mean in terms of Amazon SES? It means that their reputation is dependent on how good their policies are and how well they manage their outgoing mail streams and their customers.
AmazonSES does not, apparently, have any IPs currently listed on the SBL. Senderscores for their IP addresses range from 100 down to the mid-60’s. Senderbase shows most of the IPs have a generally good reputation. This tells me if you’re sending to domains that feed into senderscore and senderbase, then you’re probably not going to have delivery problems based on Amazon’s reputation.
On a more personal note, though, we are getting quite a bit of spam from AmazonSES customers. Despite repeated complaints, Amazon appears not to be taking any action against those customers. In fact, Amazon isn’t even telling customers not to send to people who complain.
We don’t block by IP address for a number of reasons, but if we did block by IP, the AmazonSES range sends us enough spam and little enough real mail that it would probably be blocked here. This tells me that if you’re sending to small and medium sized business domains or personal domains you may have delivery problems based on Amazon’s reputation.
Ultimately, though, the public sources of information indicate that using AmazonSES may not hurt your email delivery. But, as with everything in email, TEST TEST TEST. There’s no setup fee, so set it up and see how it works for you. Test sends to your business domain, set up accounts at gmail, yahoo, hotmail and aol to test delivery to those places.
Also, know that a provider’s reputation is not static. Personnel changes, policy changes, and customer changes can all affect a provider’s reputation. A little sloppiness with handling abuse complaints or letting a customer or two slide in the short term won’t really affect delivery for other customers. Letting those things slide over the long term can hurt delivery for even good customers. Don’t assume that because a provider is good or bad today that they’ll still be good or bad in a year.
 
===
Have a question you want answered? tweet them to @wise_laura or send them to laura-questions@wordtothewise.com

Related Posts

Hunting the Human Representative

Yesterday’s post was inspired by a number of questions I’ve fielded recently from people in the email industry. Some were clients, some were colleagues on mailing lists, but in most cases they’d found a delivery issue that they couldn’t solve and were looking for the elusive Human Representative of an ISP.
There was a time when having a contact inside an ISP was almost required to have good delivery. ISPs didn’t have very transparent systems and SMTP rejection messages weren’t very helpful to a sender. Only a very few ISPs even had postmaster pages, and the information there wasn’t always helpful.
More recently that’s changed. It’s no longer required to have a good relationship at the ISPs to get inbox delivery. I can point to a number of reasons this is the case.
ISPs have figured out that providing postmaster pages and more information in rejection messages lowers the cost of dealing with senders. As the economy has struggled ISPs have had to cut back on staff, much like every other business out there. Supporting senders turned into a money and personnel sink that they just couldn’t afford any longer.
Another big issue is the improvement in filters and processing power. Filters that relied on IP addresses and IP reputation did so for mostly technical reasons. IP addresses are the one thing that spammers couldn’t forge (mostly) and checking them could be done quickly so as not to bottleneck mail delivery. But modern fast processors allow more complex information analysis in short periods of time. Not only does this mean more granular filters, but filters can also be more dynamic. Filters block mail, but also self resolve in some set period of time. People don’t need to babysit the filters because if sender behaviour improves, then the filters automatically notice and fall off.
Then we have authentication and the protocols now being layered on top of that. This is a technology that is benefiting everyone, but has been strongly influenced by the ISPs and employees of the ISPs. This permits ISPs to filter on more than just IP reputation, but to include specific domain reputations as well.
Another factor in the removal of the human is that there are a lot of dishonest people out there. Some of those dishonest people send mail. Some of them even found contacts inside the ISPs. Yes, there are some bad people who lied and cheated their way into filtering exceptions. These people were bad enough and caused enough problems for the ISPs and the ISP employees who were lied to that systems started to have fewer and fewer places a human could override the automatic decisions.
All of this contributes to the fact that the Human Representative is becoming a more and more elusive target. In a way that’s good, though; it levels the playing field and doesn’t give con artists and scammers better access to the inbox than honest people. It means that smaller senders have a chance to get mail to the inbox, and it means that fewer people have to make judgement calls about the filters and what mail is worthy or not. All mail is subject to the same conditions.
The Human Representative is endangered. And I think this is a good thing for email.

Read More

Reputation is more complex than a single number

I checked our SenderScore earlier this month, as quite a few people mentioned that they’d seen SenderScore changes – likely due to changed algorithms  and new data sources.

It sure looks like something changed. Our SenderScore was, for a while, zero out of a hundred. That’s as bad as it’s possible to get. I didn’t get a screenshot of the zero score, but I grabbed this a couple of days later:

Are ReturnPath wrong? No. Given what I know about the traffic from our server (very low traffic, particularly to major consumer domains, and a negligible amount of unavoidable backscatter due to our forwarding role addresses for a non-profit to final recipients on AOL) that’s not an unreasonable rating. And I’m fairly sure that as they get their new algorithms dialed in, and get more history, it’ll get closer. (Though I’m a bit surprised that less than 60 mails a day is considered a moderate volume.)
But all our mail is delivered fine. I’ve seen none of my mail bounce. It’s very rare someone mentions that our mail has ended up in a bulk folder. I’ve received the replies I’ve expected from all the mail I’ve sent. Recipient ISPs don’t seem to see any problems with our mail stream.
A low reputation number doesn’t mean you actually have a problem, it’s just one data point. And a metric that’s geared to model one particular sort of sender (very high-volume senders, for example) isn’t going to be quite as useful in modeling very different senders. You need to understand where a particular measure is coming from, and use it in combination with all the other information you have rather than focusing solely on one particular number.
 

Read More

Setting expectations at the point of sale

In my consulting, I emphasize that senders must set recipient expectations correctly. Receiver sites spend a lot of time listening to their users and design filters to let wanted and expected mail through. Senders that treat recipients as partners in their success usually have much better email delivery than those senders that treat recipients as targets or marks.
Over the years I’ve heard just about every excuse as to why a particular client can’t set expectations well. One of the most common is that no one does it. My experience this weekend at a PetSmart indicates otherwise.
As I was checking out I showed my loyalty card to the cashier. He ran it through the machine and then started talking about the program.
Cashier: Did you give us your email address when you signed up for the program?
Me: I’m not sure, probably not. I get a lot of email already.
Cashier: Well, if you do give us an email address associated with the card every purchase will trigger coupons sent to your email address. These aren’t random, they’re based on your purchase. So if you purchase cat stuff we won’t send you coupons for horse supplies.
I have to admit, I was impressed. PetSmart has email address processes that I recommend to clients on a regular basis. No, they’re not a client so I can’t directly take credit. But whoever runs their email program knows recipients are an important part of email delivery. They’re investing time and training into making sure their floor staff communicate what the email address will be used for, what the emails will offer and how often they’ll arrive.
It’s certainly possible PetSmart has the occasional email delivery problem despite this, but I expect they’re as close to 100% inbox delivery as anyone else out there.

Read More