已发送的电子邮件通过SPF和DKIM，但在Gmail收到时，DMARC失败

Gmail将我的电子邮件标记为垃圾邮件。消息通过SPF和DKIM，但未通过DMARC。有什么方法可以让我的邮件通过DMARC吗？

我最近在Flywheel注册了WordPress托管，该托管使用Mandrill进行交易电子邮件。我的网站有几种表单，它们在提交时发送电子邮件通知。

我附加了示例消息的原始来源：

Delivered-To: xxxxx@seesawsf.com
Received: by 10.36.109.5 with SMTP id m5csp1332570itc;
        Sun, 1 Feb 2015 23:03:34 -0800 (PST)
X-Received: by 10.236.2.6 with SMTP id 6mr7036797yhe.179.1422860614601;
        Sun, 01 Feb 2015 23:03:34 -0800 (PST)
Return-Path: <bounce-md_30068542.54cf2145.v1-57b0f565d61f4314ae4398e41d1cf6f7@mandrillapp.com>
Received: from mail128-15.atl41.mandrillapp.com (mail128-15.atl41.mandrillapp.com. [198.2.128.15])
        by mx.google.com with ESMTPS id g67si3643342yhd.195.2015.02.01.23.03.34
        for <xxxxx@seesawsf.com>
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Sun, 01 Feb 2015 23:03:34 -0800 (PST)
Received-SPF: pass (google.com: domain of bounce-md_30068542.54cf2145.v1-57b0f565d61f4314ae4398e41d1cf6f7@mandrillapp.com designates 198.2.128.15 as permitted sender) client-ip=198.2.128.15;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of bounce-md_30068542.54cf2145.v1-57b0f565d61f4314ae4398e41d1cf6f7@mandrillapp.com designates 198.2.128.15 as permitted sender) smtp.mail=bounce-md_30068542.54cf2145.v1-57b0f565d61f4314ae4398e41d1cf6f7@mandrillapp.com;
       dkim=pass header.i=@mail128-15.atl41.mandrillapp.com;
       dmarc=fail (p=QUARANTINE dis=QUARANTINE) header.from=seesawsf.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=mandrill; d=mail128-15.atl41.mandrillapp.com;
 h=From:Sender:Subject:To:Message-Id:Date:MIME-Version:Content-Type; i=info@mail128-15.atl41.mandrillapp.com;
 bh=Jt6YNkQAh5eG3xb1p6nYqPNm8rQ=;
 b=HwSrIhBVCHMWd2/PMVTb49MJ/nrtEXVsIbV5wIzMyVNPiaCzmI5t5JkPM+E00Ug6CziUbTgUGM2o
   M/2W3jq43+EYjXGmVatW1Q3GcnErPc14WQr3b0FtCJFeTxVKR3wublilVvWyA9oRtTqsgyWc0Mlj
   0LrqrPb6UXTPre52Fog=
DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=mandrill; d=mail128-15.atl41.mandrillapp.com;
 b=qx6ydLL6hfTwC7h8XIW5C6jwtBHZ2R/5g8cCE60yXMxhLbH+fD5fc4kLXYNR6Ok5qlwvMKkG/aU5
   2/AQkTHLHxsq7fmVBpDFnxI1R2T1vBkYZ6StFnkhQp1tHUTfGrj+5j5K8+msc+qiIktNRSeL12JD
   egxGpd+2goJerCPfGsQ=;
Received: from pmta04.atl01.mandrillapp.com (127.0.0.1) by mail128-15.atl41.mandrillapp.com id hpsgkc1mqukr for <xxxxx@seesawsf.com>; Mon, 2 Feb 2015 07:03:34 +0000 (envelope-from <bounce-md_30068542.54cf2145.v1-57b0f565d61f4314ae4398e41d1cf6f7@mandrillapp.com>)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mandrillapp.com; 
 i=@mandrillapp.com; q=dns/txt; s=mandrill; t=1422860613; h=From : 
 Sender : Subject : To : Message-Id : Date : MIME-Version : Content-Type 
 : From : Subject : Date : X-Mandrill-User : List-Unsubscribe; 
 bh=3BX+Ypp8U/OwrT6jZiEJ7HZzbu5vXIAOTBSMt9pdT/c=; 
 b=D4qNdklkpV8zM74TZFQ8CkUy8N3zJesDWFWnNN6qAZ4eqW3WTCjg0W7Sooks5h+IiqC55Z
 2DbpzSC1GuNMDFbmxzUTeWXyA1QU/TpDrpHnd9D9qDLiflNTmWcrwKlT6U8Bp00d+itgq9bv
 ZhmZZ2+vY3fe3rFHv26UKwvdusFmg=
From: seesaw registration <xxxxx@seesawsf.com>
Sender: seesaw registration <info@mail128-15.atl41.mandrillapp.com>
Subject: [removed]
Return-Path: <bounce-md_30068542.54cf2145.v1-57b0f565d61f4314ae4398e41d1cf6f7@mandrillapp.com>
X-Sg-User: flywheelxxxxx
X-Sg-Opt: PWD=/www
X-Php-Originating-Script: 0:class-phpmailer.php
X-Priority: 3
X-Mailer: PHPMailer 5.2.7 (https://github.com/PHPMailer/PHPMailer/)
To: <xxxxx@seesawsf.com>
Message-Id: <410d02299d22f05ab4d859c2a733e836@seesawsf.flywheelsites.com>
Received: from [162.243.115.105] by mandrillapp.com id 57b0f565d61f4314ae4398e41d1cf6f7; Mon, 02 Feb 2015 07:03:33 +0000
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=30068542.57b0f565d61f4314ae4398e41d1cf6f7
X-Mandrill-User: md_30068542
Date: Mon, 02 Feb 2015 07:03:33 +0000
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="_av-S0IDuFcF1O5aP8YpCVA_Kg"

--_av-S0IDuFcF1O5aP8YpCVA_Kg
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

[ removed message content ]

--_av-S0IDuFcF1O5aP8YpCVA_Kg
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

[ removed message content ]

--_av-S0IDuFcF1O5aP8YpCVA_Kg--

您需要为您的域添加Mandrill DKIM记录。SPF和DKIM通过了，但是它基于对mandrillapp.com进行身份验证的消息，而不是您的域（即，正在使用Return-Path域进行消息身份验证）。为了进行域身份验证并通过DMARC对齐检查，“发件人”域需要SPF和DKIM。以下是有关要添加的DKIM记录的信息：http : //help.mandrill.com/entries/22030056-How-do-I-add-DNS-records-for-my-sending-domains-

完成此操作后，Mandrill帐户所有者（在您的情况下为Flywheel）将需要/想要验证Mandrill中的那些记录，以便Mandrill知道两者均有效并且可以开始为您的域签名消息（可以在帐户中完成此操作）或通过Mandrill API）。

许多主要的电子邮件提供商，例如Google，Yahoo，Hotmail，AOL等，都采用了基于域的消息身份验证，报告和一致性（DMARC）。可以在这里了解到，它的目的是通过大多数邮件服务器已经使用的机制SPF和标准化的电子邮件身份验证DKIM。

添加DMARC策略记录与添加SPF和DKIM记录非常相似：您将TXT使用Google 在此处列出的标签将记录添加到域的DNS表中。他们提供的示例是：

v=DMARC1; p=none; rua=mailto:postmaster@your_domain.com

检查您域的DNS记录，我发现DMARC尚未添加记录：

v=spf1 +a +mx include:_spf.google.com include:servers.mcsv.net include:spf.mandrillapp.com -all

有关如何TXT为Mandrill和普通DNS提供商添加记录的详细信息，请参见此处。

此问题是由返回路径和标头From：之间不一致引起的。

返回路径：mandrillapp.com

来自：@ seesawsf.com

• SPF和DKIM使用RFC5321.MailFrom（通常为Return-Path ：）检查域。
• DMARC使用RFC5322.MailFrom（标头来自：）检查域

参考：https : //space.dmarcian.com/how-can-spfdkim-pass-and-yet-dmarc-fail/

如果域不同，则尽管通过了SPF和DKIM，但DAMRC无法验证发送方事件，并且验证将失败。

在这种情况下，SPF和DKIM会对mandrillapp.com进行身份验证，而不对seesawsf.com进行身份验证。

解决方法是，将Retrun-Path和Header From设为同一域，否则DMARC将失败。