• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2366
  • Last Modified:

DMARC Fail when SPF & DKIM Pass

We have recently switched our DMARC policy from "none" to "quarantine".  We utilize MailChimp and have followed their instructions to add their server information to our SPF and DKIM records.  When we send out our test campaign, both SPF and DKIM pass but DMARC is failing.  As I understand it, this is because SPF and DKIM are passing based on the "mandrillapp.com" domain, but this doesn't match the domain in the From field (ourdomain.com).  Redacted message header from a test mailer is at the bottom.

Firstly, am I understanding the issue correctly?  Secondly, does somebody have a recommendation on what adjustment I can make so that these messages are not flagged?

It appears from this article (http://wiki.asrg.sp.am/wiki/Mitigating_DMARC_damage_to_third_party_mail) that I can take steps to obscure the from email address so that it is not suggesting that the message originates from myaddress@ourdomain.com.  Ideally, however we would prefer this to remain so that recipients can click reply directly.

Thanks in advance!

Received: from mail187-199.suw11.mandrillapp.com (mail187-199.suw11.mandrillapp.com [])
	by dmarctest.org (8.14.9/8.14.9/dmarctest.org.mc-1.2) with ESMTP id u7VEDZkZ002452
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <autoreply@dmarctest.org>; Wed, 31 Aug 2016 07:13:38 -0700 (PDT)
	(envelope-from bounce-md_9656357.57c6e60d.v1-xxxxx@mandrillapp.com)
DMARC-Filter: OpenDMARC Filter v1.3.0 dmarctest.org u7VEDZkZ002452
Authentication-Results: dmarctest.org/u7VEDZkZ002452; dmarc=fail header.from=ourdomain.com
Authentication-Results: dmarctest.org; spf=pass smtp.mailfrom=bounce-md_9656357.57c6e60d.v1-xxxxx@mandrillapp.com
DKIM-Filter: OpenDKIM Filter v2.9.2 dmarctest.org u7VEDZkZ002452
Authentication-Results: dmarctest.org; dkim=pass reason="1024-bit key"
	header.d=mail187-199.suw11.mandrillapp.com header.i=myaddress@mail187-199.suw11.mandrillapp.com
	header.b=ZScFeS87; dkim-adsp=none; dkim-atps=neutral
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=mandrill; d=mail187-199.suw11.mandrillapp.com;
 h=From:Sender:Subject:To:Message-Id:Date:MIME-Version:Content-Type; i=myaddress@mail187-199.suw11.mandrillapp.com;
Received: from pmta01.mandrill.prod.suw01.rsglab.com ( by mail187-199.suw11.mandrillapp.com id horj14174i4g for <autoreply@dmarctest.org>; Wed, 31 Aug 2016 14:13:34 +0000 (envelope-from <bounce-md_9656357.57c6e60d.v1-xxxxx@mandrillapp.com>)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mandrillapp.com; 
 i=@mandrillapp.com; q=dns/txt; s=mandrill; t=1472652813; h=From : 
 Sender : Subject : To : Message-Id : Date : MIME-Version : Content-Type 
 : From : Subject : Date : X-Mandrill-User : List-Unsubscribe; 
From: <myaddress@ourdomain.com>
Sender: <myaddress@mail187-199.suw11.mandrillapp.com>
Subject: MailChimp Template Test - "Mailer Subject"
X-Accounttype: ff
X-Auto-Response-Suppress: OOF, AutoReply
Auto-Submitted: auto-generated
To: <autoreply@dmarctest.org>
X-Report-Abuse: Please forward a copy of this message, including all headers, to abuse@mandrill.com
X-Report-Abuse: You can also report abuse here: http://mandrillapp.com/contact/abuse?id=9656357.xxxxx
X-Mandrill-User: md_9656357
Message-ID: <9656357.20160831141333.57c6e60de94781.11430196@mail187-199.suw11.mandrillapp.com>
Date: Wed, 31 Aug 2016 14:13:33 +0000
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="_av-Ps-Vnv22FE1bQqTaBly1nw"

Open in new window

Dan Carp
Dan Carp
  • 3
  • 3
2 Solutions
btanExec ConsultantCommented:
You understood the issue correctly, see also MailChimp explanation
For example, let’s say you send a MailChimp campaign with a From email address like firstname.lastname@yahoo.com. The campaign appears to be sent from a yahoo.com domain, but it’s actually sent from MailChimp’s servers. Yahoo’s strict DMARC policy doesn’t like this. Their DMARC policy tells your subscribers’ receiving servers to automatically reject anything that looks like it comes from yahoo.com, but comes from somewhere else instead.  

To improve deliverability, we encourage you to use a From email address at a domain owned by you or your organization, like firstname.lastname@mycompany.com. Not only will this help avoid delivery issues, it can help your subscribers recognize your brand.

For your case, you likely need to add a Mandrill DKIM record for your domain. The SPF and DKIM pass, but it is based on messages being authenticated for mandrillapp.com, not your domain (most cases, the Return-Path domain is being used for message authentication though not seen in the log).

In order to authenticate as your domain, and in turn pass the DMARC alignment check, you need both SPF and DKIM for the "from" domain. Here's information about the DKIM record to add: http://help.mandrill.com/entries/22030056-How-do-I-add-DNS-records-for-my-sending-domains-

Once you do that, the Mandrill account owner (in your case MailChimps), will need/want to validate those records in Mandrill, so that Mandrill knows both are valid and can start signing messages for your domain (this can be done within the account or via the Mandrill API).
btanExec ConsultantCommented:
Otherwise if the Adding of your "from" as per last shared into the SPF and DKIM is not possible, you may have to consider those which can like Yahoo and AOL, though it is not representative to your original "From" domain
For best results, we recommend you switch to a domain you own. However, if you use Yahoo or AOL Mail and can’t register your own domain, we can help you avoid delivery problems. We’ll automatically add send.mailchimpapp.com or mail.mailchimpapp.com to your Yahoo or AOL address to help ensure delivery. This process is currently only available for Yahoo and AOL addresses.
Dan CarpIT DirectorAuthor Commented:
Thank you very much for the response, btan - I really appreciate the confirmation.  We have already gone through MailChimp's steps for authenticating our domain (adding their information to our SPF and DKIM DNS records) which is why I thought it so odd that DMARC was still failing.

With your confirmation that I was taking the right steps, I started thinking it through further and decided to send a full campaign to a few test email addresses (as opposed to sending a test email from the template designer).  Sure enough, when sending a campaign, MailChimp does indeed authenticate ourdomain.com for SPF and DKIM and therefore DMARC passes as well.

So in the end, the issue is only with sending test emails during the template design stage.  I may troubleshoot this in the future, but for now I'm more than content knowing that our actual campaigns will go out successfully.  Thanks again!
Improved Protection from Phishing Attacks

WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!

btanExec ConsultantCommented:
Great to hear that. Thanks for sharing.
Rich RumbleSecurity SamuraiCommented:
You still have to publish a DMARC policy for that domain, which you're not right now
Dan CarpIT DirectorAuthor Commented:
Solved issue with further testing
Dan CarpIT DirectorAuthor Commented:
Sorry for any confusion, Rich - I was using ourdomain.com as a placeholder.  We do have a published DMARC policy for our actual domain.  Thanks for checking!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now