AWS SES Receive: It's Worse Than You Thought
AWS generally has great products, I use them almost exclusively, both professionally and privately, I am a what you could call a fanboy.
But now and then, they offer a service that is just utterly garbage, which becomes useless unless you write a lot around it. B2C services providfed by AWS often fall into this category.
One of this services is SES Receiving.
I migrated from a self-hosted solution to AWS-SES-Receiving a few weeks back. My main area of concern is the lack of SPAM filtering.
I gathered enough data to realize that this service is very faulty, under performing and creates more problems than it solves. It other words: it’s useless or one could even say: total garbage.
The bad stuff
This are limitation I was aware of before starting my migration and accepted them. But it would make the service so much more appealing if they where addressed.
No IMAP client
AWS has the WorkMail service, which comes with a Webapp and IMAP server and costs 4.00 USD/month/user. For 6.00 USD/month/user, you get a Google Workspace account account, which includes so much more than just EMail (Drive, Meet, …)
This isn’t a deal breaker for me, since I only wanted to provide forwards to personal emails.
No ability to forward messages
You have to send as a user from your domain, so no ability to forward an incoming message keeping the original external sender.
This is the main feature of my needs. I made peace with it, and rewrite the From field and providing a Reply-To.
No in-built alias management
Everybody needs aliases. Be it only
info. No way to do this in SES, unless you fiddle with the rules settings.
Not a deal breaker, since I was to handle externally all forwards.
The totally broken stuff
This is the part that made me cringe the most.
SES Receiving is absolutely worthless when it comes to SPAM filtering. Their functionality is totally useless, an important proportions of SPAM messages are still going through.
What is happening
On average, 30 to 50 messages are received a day. The total sample rate is of 840.
Out of the 840 messages, SES identified:
- Spam: 198
- Invalid SPF: 2
- Ham: 640
On manual analysis (just checking the Sender and Subject), from this 640, I identified:
- False Negative: 559
- Ham: 81
From the false negative, 33 where dropped with a simple MX check on the sender’s domain. Which leaves us with a delivery of 526 Spam messages to my end users.
87.3% of the messages claimed to be clean by SES are actually SPAM. This is an astonishing bad and shameful result.
How to improve this?
There are a few obvious “tricks”, which I started to implement:
- Check the sender’s MX. If it doesn’t exist, drop the message. This reduced the SPAM in only a minimalistic way.
- Use Postmarks’s Spamassassin API: It removed some SPAM, but not enough. Their rules seems top be a bit outdated.
- Run your own Spamassassin: which makes us going back to square one and hosting a solution on a server. Yes there is Fargate, or even Lambda Container, but you still need to build and manage it.
What AWS should do
AWS want’s to proclaim themselves as a leader in ML. Then show us how! Give us a decent and bullet proof SPAM filtering solution.
We should be able to see some kind of confidence level and decide ourselves what is spam or not. We should even be able to cut the STMP communication early if the level is too high, and never have to process an obvious SPAM messages.
And also, allow us to call an API to declare what is SPAM and what is HAM, like any Gmail Account allows us to do.
Almost 90% of the messages (yes that’s 9 out of 10) claiming to be clean are actually SPAM. This doesn’t check anybody’s level of expectation.
Until AWS put’s a lot of effort into SES, don’t use them for your E-Mail solution. Just give your money to Google.