[edgesrazor]

Thanks! This is a great walk-through for those using a solution with only 1 or a few IP addresses associated with little chance of that IP changing. Do you have any experience for those using services such as Amazon SES or Google Apps?

Setting up the PTR records for reverse DNS lookups are very tricky since Amazon and Google are always rotating the IP addresses for their mail servers. We've been fighting with this in our application for a little while now (using Python, not Ruby).

We're getting about 90% of our emails through, but some are getting denied for no reason whatsoever. The worst part is, they are server-side denials, so the emails aren't even going into the spam folders of the users.

Also, I second adding the DMARC section. DMARC is extremely simple, and it's very easy to implement gradually.

[igor_a]

I haven't worked with external emails providers. For now we are sending around 100-150k emails/day and we are using postfix as MTA.

Regarding server side rejects - again reading postfix logs can save you from such things. As an example recently we started seeing that we can't deliver a lot of emails to orange.fr, and the worst - if send just one email it always was accepted but when we sent bulk newsletter we had a lot of rejections - the reason was quite simple we've got rejected because of high frequency so we just had to throttle postfix on per domain basis.

[edgesrazor]

I think I might have to set up postfix and do some experimenting. One of the strangest things I've seen is that some domains are rejecting emails with links to our site in them, but will accept them if the links are removed (plain text or HTML).

I swear, someone could make a good living handling this for companies looking to handle transactional email internally.