Followup to Amazon SES

The nice folks at Amazon contacted me about my post yesterday and pointed out that they are not allowing just anyone to mail through their system. They have a multi step process for qualifying senders.
The first step, as described by their website is:

New users are placed in the Amazon SES sandbox, where they can test and evaluate the service in a restricted mode. As a sandbox user, you have full access to the Amazon SES API; however, the following restrictions are in effect:

  • Emails can be sent only to and from verified email addresses.
  • You can send a maximum of 200 messages per day.
  • You can send a maximum of one message per second.

To lift these restrictions and use Amazon SES in production, we recommend that you request production access at your earliest opportunity.

Production access requires filling out a form with very basic information about your mailing program.  Screening customers is a bit of an art form and only time will tell if Amazon got it right.

Related Posts

Amazon announces SES email service

Last month Amazon announced a cloud based email service: Amazon SES. Amazon SES is an API based email service priced at a very low rate.
The SES product rounds out Amazon’s cloud hosting offerings. The Amazon cloud hosting service is great for webhosting but pretty bad for mail. A lot of ISPs refused to accept email from Amazon cloud IPs. But now cloud hosted customers, and others, can use the SES system to send mail.
It remains to be seen how the SES program works. They are using shared IPs for all customers. This means shared IP based reputation. As one of the major targets is transactional mail, something that normally has a very high engagement factor, it’s likely there will be a lot of good reputation on the SES IPs.
On the flip side, Amazon has set a very low price point and is allowing anyone to use their API. This is going to make it very attractive to some bad actors. These are the same folks who are attempting to compromise ESPs and sneak their mail through enforcement.
A lot of the delivery through the Amazon SES IPs is going to rely on enforcement. They seem to be putting a lot of stock in their content filtering being able to stop spam from getting through. That may or may not be enough; a lot of spammers are actually really good at avoiding content filters.
The good news is that Amazon seems to have considered a lot of these issues. They are providing a SPF record for the SES IPs, and have a way to accept DKIM signed email. They also have an experienced delivery person working there which will work in their favor.
It will be interesting to see if this works. I believe the success or failure will lie with Amazon. I know, I know, normally I say that a sender is responsible for their own reputation. But in a shared environment, it is the overall reputation of the senders that is the key to delivery. Amazon can drive that overall reputation by what customers they allow to send mail through the system. It will be interesting to see what happens in 6 – 12 months when they’ve had some time to build up a customer base.

Read More