It's not like it is hard. At least not harder than integrating to a third party email sender.
It's not like it is hard. At least not harder than integrating to a third party email sender.
- You need to make sure that your email servers IPs are not on black lists.
- That you use DKIM properly
- your multipart mime encoding is correct
- bouncing e-mails are handled...
- take care of scaling & operating the servers
- and so on....
You can spent ( and waste ) a lot of time on this... especially if you are new to email sending..
This alone is a huge, huge chore. Especially if you run a hosted service that allows some user-specified content in outbound email bodies. It's a lot cheaper for us to pay Mandrill to handle all of that for us, provide us excellent metrics and diagnostics, and let us know if one of our users is sending junk mail before it gets out of hand.
Blacklists suck. Not as much as spam sucks, though.
Yes, sending an email is easy enough. It's all the other stuff we have services like this for.
http://aws.amazon.com/ses/pricing/
"You can send 2,000 messages for free each day when you call Amazon SES from an Amazon EC2 instance directly or through AWS Elastic Beanstalk."
After using SES for close to two years, I'd suggest looking elsewhere if you really care about deliverability or stats/metrics. We switched to Mandrill a few months ago and have been very impressed. It's still a tiny, microscopic percentage of our budget, but we get so much more (open/click reporting, sub-accounts, rendered email body history, much better blacklist/whitelist management).
They get accurate data for clicks, but geolocation/browser stats for opens aren't 100%. They still track the rates, but it looks like they're coming from one of Google's proxies, so this is the best they can do for now.
My employer has been making more and more use of SES, and we've just started looking at automated processing of feedback notifications [1]. Did you find them lacking?
[1] http://docs.aws.amazon.com/ses/latest/DeveloperGuide/notific...