# Reliably send small amount of mail from possibly blacklisted cloud IPs

So you boot a new cloud server. Only to discover that its IP is blacklisted by misbehavior of the previous owner. How to make sure your mail gets delivered for a modest price?

Context: I provide my customers each with their own cloud server. They use it to send on average 20 mails per day to their customers, using their own domain name. I have a couple of hundred customers/servers and I plan to have many more ;)

I have looked into Sendgrid, Mandril, Amazon SES, Mailjet, Mailgun but they are all focused on large marketing campaigns, not the occasional mail senders like my customers are. For example, with SendGrid I could create (by API) a "subuser" for each of my customers, but if my customer wants to get rid of the pesky "via sendgrid" header in Gmail/Outlook (and they want that), they are required to pay $20/month/domain. That seems quite expensive for sending < 100 mail. Plus it is a complicated procedure, which would be required for each of hundreds of domains. So what I want is a basic SMTP relay service, that will somewhat reliably deliver my small volumes of mail for a modest price. It should support segmentation, ie if one customer somehow sends spam, he should be blocked but it shouldn't affect my other customers. Bonus points for not having my customers go through complicated domain verification procedures (ie. not DKIM). How did you handle this issue? TIA! • If you don't want the pesky "via sendgrid" stuff then you have to go through the complicated verification procedures (which take all of two minutes). – Michael Hampton Feb 4 '15 at 14:00 • Plus (in my situation)$18K/month for a couple of hundred domains, who only send a few mail each. Plus I would have to code an interface for my customers, instruct my support staff, write documentation, which all together takes 2-3 weeks of extra work. – Willem Feb 4 '15 at 14:15
• Plus the verification requires DNS modifications at the sending domain level, which unfortunately a rather large portion of my non-tech customers are unable to comprehend, even if their life depends on it. – Willem Feb 4 '15 at 14:23
• At Mailjet you can setup as many domain / subaccounts as needed and only pay for the volume of emails you actually send. – arnaud.breton Feb 5 '15 at 9:03
• @arnaud.breton, tnx! However I cannot get Mailjet to do transparent verification. Even if I get Mailjet to send the verification mail to my customers' address, my customer would require /my/ Mailjet credentials to proceed. Have also sent elaboration to your support desk. – Willem Feb 5 '15 at 22:08

If you don't want to use SES or the like (which is what I'd recommend, even for small volumes), then another alternative is to stand up your own mail relay outside the cloud provider, on a non-blacklisted IP and have your servers relay through that. I've had good luck with Linode - I've never landed on a blacklisted IP there.

If you do this, make sure that you require authentication so that you're not an open relay.

• Thanks! This sounds like a good option, however I would still prefer a SaaS solution. Will run some more tests with SES though. Cheers! – Willem Feb 4 '15 at 14:17
• I was thinking the same exact thing but you beat me to it :) – MonkeyZeus Feb 4 '15 at 14:41

So, I did extensive testing with all of the SMTP relay providers (ESPs) above.

So to sum up the requirements:

1. ESP has multi-tenant features, such as subaccounts and containing misbehaviour within a subaccount.
2. My customer (end-user with own domain) shouldn't be bothered with manual domain or address verification procedures to enable the delivery of mail.
3. My customer, if he desires so, should be able to eliminate the via tag from Gmail/Outlook for a modest amount.

Strangely enough, only SendGrid and Mandrill will deliver without verification of the sender domain.

Both support multitenancy (Although Mandrill has a strange quirk where each subaccount requires the master API key for SMTP authentication. There is a hackish workaround though.)

Both enable the elimination of the via tag, however SendGrid will charge $20 per month per domain to do that. Mandrill will do it for free. All in all, Mandrill is quite cheaper. Given 100K mails, • Mandrill will charge$17.60
• SendGrid will charge \$79.95

I have not tested the quality of delivery thoroughly yet, although some samples with Mandrill showed a delay of 1m30s for delivery to Gmail (for just a single mail). The latter indicates that Google is throttling Mandrill.

• For Mandrill, I had to generate unique API keys, and then associate each of them with a subaccount in a custom rule. Nasty but it's functional... – Michael Hampton Feb 5 '15 at 22:48