我有安装了Wordpress的Ubuntu服务器。从服务器发送电子邮件时，我得到以下标头：
Received-Spf: neutral.
我确实在以下问题上设置了SPF记录：
v=spf1 mx a include:_spf.google.com include:spf.gigahost.dk ~all
A记录解析为我服务器的IP
46.101.199.65
当使用IP和电子邮件[email protected]对http://vamsoft.com/support/tools/spf-policy-tester进行测试时，它会通过。
知道Google为什么不将服务器发送的电子邮件标记为“通过”吗？
这是完整的标题。我已经用[email protected]替换了我的电子邮件。但是接收电子邮件是Google Apps帐户。
Delivered-To: [email protected]
Received: by 10.157.38.140 with SMTP id l12csp352662otb;
Tue, 5 Jul 2016 06:42:16 -0700 (PDT)
X-Received: by 10.28.50.131 with SMTP id y125mr17192051wmy.94.1467726136065;
Tue, 05 Jul 2016 06:42:16 -0700 (PDT)
Return-Path: <www-data@ubuntu-2gb-fra1-01-tpk>
Received: from ubuntu-2gb-fra1-01-tpk ([46.101.199.65])
by mx.google.com with ESMTP id f66si16033wme.56.2016.07.05.06.42.15
for <[email protected]>;
Tue, 05 Jul 2016 06:42:16 -0700 (PDT)
Received-SPF: neutral (google.com: 46.101.199.65 is neither permitted nor denied by best guess record for domain of www-data@ubuntu-2gb-fra1-01-tpk) client-ip=46.101.199.65;
Authentication-Results: mx.google.com;
spf=neutral (google.com: 46.101.199.65 is neither permitted nor denied by best guess record for domain of www-data@ubuntu-2gb-fra1-01-tpk) smtp.mailfrom=www-data@ubuntu-2gb-fra1-01-tpk
Received: by ubuntu-2gb-fra1-01-tpk (Postfix, from userid 33)
id AF06414471B; Tue, 5 Jul 2016 09:42:15 -0400 (EDT)
To: [email protected]
Subject: =?UTF-8?Q?Your_Kj=C3=B8tt_og_Blod_order_receipt_from_July_5,_2016?=
X-PHP-Originating-Script: 33:class-phpmailer.php
Date: Tue, 5 Jul 2016 13:42:15 +0000
From: =?UTF-8?Q?Kj=C3=B8tt_og_Blod?= <[email protected]>
Message-ID: <[email protected]>
X-Mailer: PHPMailer 5.2.14 (https://github.com/PHPMailer/PHPMailer)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
最佳答案
SPF检查中使用的是smtp.mailfrom地址。这就是所谓的信封发件人。而且由于ubuntu-2gb-fra1-01-tpk不是有效的域，因此它不能具有SPF记录，因此为中性结果。
因此，您将必须设置Wordpress安装以使用更好的信封发送器。我不是Wordpress专家，但似乎有几个过滤器/插件可让您更改邮件设置。
关于wordpress - 接收到的SPF:中性，我们在Stack Overflow上找到一个类似的问题：https://stackoverflow.com/questions/38205403/