Email SPF+DKIM+DMARC=已通过，但邮件以垃圾邮件结尾
试图发送电子邮件，但由于某种原因，它们最终被放入垃圾邮件文件夹。所以我们调整了Dkim和Dmarc，现在所有的记录都显示在Gmail中通过了，但仍然标记为垃圾邮件 还通过dkimvalidator进行了测试，结果显示所有记录都通过并显示Email SPF+DKIM+DMARC=已通过，但邮件以垃圾邮件结尾,email,gmail,spf,dkim,dmarc,Email,Gmail,Spf,Dkim,Dmarc,试图发送电子邮件，但由于某种原因，它们最终被放入垃圾邮件文件夹。所以我们调整了Dkim和Dmarc，现在所有的记录都显示在Gmail中通过了，但仍然标记为垃圾邮件 还通过dkimvalidator进行了测试，结果显示所有记录都通过并显示 SpamAssassin Score: -0.1 Message is NOT marked as spam 现在，电子邮件的分类如下所示 此帖子的发送IP已更改为123.456.789.12 发送域已更改为somedomain.net 发送电子邮件地址已更改
SpamAssassin Score: -0.1
Message is NOT marked as spam
Original Message
Message ID <3164f55daebbc258d0a4846eda47142b@somedomain.net>
Created at: Fri, Mar 15, 2019 at 3:06 PM (Delivered after 1 second)
From: support@somedomain.net
To: someuser@gmail.com
Subject: Are you getting our emails?
SPF: PASS with IP 123.456.789.12Learn more
DKIM: 'PASS' with domain somedomain.netLearn more
DMARC: 'PASS' Learn more
Delivered-To: someuser@gmail.com
Received: by 2002:a05:6504:1158:0:0:0:0 with SMTP id r24csp952466ltn;
Fri, 15 Mar 2019 12:06:09 -0700 (PDT)
X-Google-Smtp-Source: APXvYqwbxqRfiq2UKjVTB57wP4g1MW2NvFWKdyYY9P4PITERpXVsMmcdriTP6Fp9rsf+DU2Ky1nQ
X-Received: by 2002:a1c:230e:: with SMTP id j14mr3316801wmj.9.1552676769338;
Fri, 15 Mar 2019 12:06:09 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1552676769; cv=none;
d=google.com; s=arc-20160816;
b=kI1D5Zd50f7UIVNtLYscVA3w9dhrAzg3YfuSMJWIIag6Le+YNqzYUpTxlQ11pK0Jvd
9bQ8KztlKnEwTWvC90bUrX7FvNTdKTEeatTQao5I5z77QxBG8q96cYYnbmzHVzsKxcS6
eBJYwO7gabkTsJzdGHYeYR9pYHPANr5vhtkpGYn4OSEAvrTokXHnI7Lma5MlI+QcJFhO
eGb6omkWY05TGfZZYMJ9ny/8WBhG6W3mpuT+x3Z0mv9IWnuxhhnDWgYGb+qEK/cUkCjl
CLHaxq+uRh8MXnjzoChWHXc4elm8yKo9CS3qqAppMThxQ3X/2kp9SVg+EPKut9R3OtG0
D+ng==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
h=message-id:user-agent:subject:to:from:date
:content-transfer-encoding:mime-version:dkim-signature;
bh=GrxIPJ9zPlbqzf38J/MOr7Lt7eP6CUv0wQxJqM2McmE=;
b=QgXB7YGir4NdgYnbt+2pORQCK5bMsOT+mHtSghj+CrTIORIqW04ie/3v8iWpMop2uc
ZYby4O/YD5TohP7VnYT1/lHGcQO8BCK+BCqXJaJb1JyzoRFyAM2aVMfJonRphm3VSfzH
JCGAAQjW3hTRsANmiU4Toh5IgXVgLvz2ZFSbOjY+xEopHJar1XXg9kN9N+A8kZMJWIIk
dVXrhwSDV/1Z0/8ObepuXI+KZNRpyKItMjMMDDyh1Py7cQl1MJXnoTzr53aCeDw3nWWg
yUDRjq3kDUK2Rm0X/O43DGHQvAHvk7gge4UaE5rDFjtBphLVYO0Zadto3bQAFwAMouR9
H9Qg==
ARC-Authentication-Results: i=1; mx.google.com;
dkim=pass header.i=@esomedomain.net header.s=mail header.b="cLQsKmq/";
spf=pass (google.com: domain of support@somedomain.net designates 123.456.789.12 as permitted sender) smtp.mailfrom=support@somedomain.net;
dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=somedomain.net
Return-Path: <support@somedomain.net>
Received: from ms101.somedomain.net (vmi247326.someotherotherdomain.net. [123.456.789.12])
by mx.google.com with ESMTPS id k4si945224wmi.131.2019.03.15.12.06.09
for <someuser@gmail.com>
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Fri, 15 Mar 2019 12:06:09 -0700 (PDT)
Received-SPF: pass (google.com: domain of support@somedomain.net designates 123.456.789.12 as permitted sender) client-ip=123.456.789.12;
Authentication-Results: mx.google.com;
dkim=pass header.i=@somedomain.net header.s=mail header.b="cLQsKmq/";
spf=pass (google.com: domain of support@somedomain.net designates 123.456.789.12 as permitted sender) smtp.mailfrom=support@somedomain.net;
dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=somedomain.net
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=somedomain.net; s=mail; h=Message-ID:Subject:To:From:Date: Content-Transfer-Encoding:Content-Type:MIME-Version:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
bh=GrxIPJ9zPlbqzf38J/MOr7Lt7eP6CUv0wQxJqM2McmE=; b=cLQsKmq/CfXyv0nzG9Fwi6cs4 Ei3zkeoZTgWBvLZfF303+EVPnwUdqgKKlXfLntlfW+8lp54rm3S/dI9p640dC6IIoGJrdkYwWUw+0 J0K6U9rSTs1yUJ8mM6kWdYURmUQ7eAMvbqFtCIXhcXPBBlKDgvFGCpwz5GnSark8zkU7c=;
Received: from localhost ([127.0.0.1] helo=ms101.somedomain.net) by vmi247326.someotherdomain.net with esmtp (Exim 4.91) (envelope-from <support@somedomain.net>) id 1h4s9g-0001pt-Nb for someuser@gmail.com; Fri, 15 Mar 2019 15:06:08 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Date: Fri, 15 Mar 2019 15:06:08 -0400
From: suppor@somedomain.net
To: someuser@gmail.com
Subject: Are you getting our emails?
User-Agent: Roundcube Webmail/1.4-rc1
Message-ID: <3164f55daebbc258d0a4846eda47142b@somedomain.net>
X-Sender: support@somedomain.net
非常感谢您的帮助 不久前我在G套件支持部门工作，花了很多时间在Gmail上 有些事情要记住 1尝试使用~all而不是？all设置您的SPF。我仍然可以在返回路径中看到您的域，您可能需要将其编辑掉 2您的DKIM需要添加到返回路径中列出的域中。如果返回路径是domaina.com，则DKIM需要来自domaina.com 3 DMARC在发送电子邮件时并没有多大帮助，它主要用于防止针对您的域的入站欺骗，尽管如此，拥有它仍然很好 4尝试从不同的服务器发送电子邮件，有时特定的服务器有相当坏的声誉，导致电子邮件被标记为垃圾邮件-tester.com工具有助于了解您的电子邮件有多垃圾邮件 5.尽量不要向从未收到你消息的人发送营销电子邮件。如果你真的这么做了，使用Mailchimp这样的专门服务，也可以帮助运送，避免BCC 除此之外，这是一个很难回答的问题，你可以把一切都做好，但是有0保证你的电子邮件永远不会被标记为垃圾邮件，不幸的是，它一半在你的控制之下，另一半是别人从你的域、你的服务器、你的内容、你的实际用户名、包括的链接报告的内容，请记住，你的声誉因服务器而异，因此，如果电子邮件在Gmail中以垃圾邮件形式发送，并不一定意味着它会在hotmail中以垃圾邮件形式发送。有时，使用完全不同的域/服务器/服务会有所帮助，但如果声誉已经受到污染，那么只有将电子邮件标记为“非垃圾邮件”最终才会有助于邮件的传递，我知道，这种情况发生时会很糟糕
干杯 回答得好。还有一个因素是gmail postmaster工具严重损坏。托管提供商声称这是一个RoundCube配置错误，毫无意义，但至少我们有人在修复。