talkswithwind: (tech)
talkswithwind ([personal profile] talkswithwind) wrote in [site community profile] dw_maintenance 2016-04-18 01:34 pm (UTC)

My deepest sympathies on email deliverability problems. That kind of thing falls into my Dayjob responsibilities, so I know those feels.

I noticed that doesn't have a DMARC entry yet. This is Yet Another Thing to say to mailers, "no, really, I'm me". It works along with SPF and DKIM, which are already set up.

Last month, Amazon SES added support to customize the MAIL FROM: address in the SMTP conversation. This is a big thing for SES customers, as it makes DMARC much easier to set up. Create an SPF record in the '' domain, set it up right with -all at the end, and deliverability would increase a bit. Better yet for troubleshooting, gmail will put a helpful additional header in messages saying how well incoming email passes DMARC, SPF, and DKIM

dmarc=pass (p=NONE dis=NONE)

Pretty handy.

One caveat I know from bitter experience. Setting a policy to enforcing will break mail-forwards. People who have gmail addresses but forward email off of gmail will generate bounces like, "Mail administrators at $domain have administratively prevented this email from delivering," which will break things. Great for platforms where nonrepudiation is more important than deliverabiity, not so great for platforms where deliverability is paramount.

Post a comment in response:

Anonymous( )Anonymous This account has disabled anonymous posting.
OpenID( )OpenID You can comment on this post while signed in with an account from many other sites, once you have confirmed your email address. Sign in using OpenID.
Account name:
If you don't have an account you can create one now.
HTML doesn't work in the subject.


If you are unable to use this captcha for any reason, please contact us by email at

Notice: This account is set to log the IP addresses of everyone who comments.
Links will be displayed as unclickable URLs to help prevent spam.