我正在使用 Sparkpost 作为 ESP 来预热辅助域。几个月来，我们一直将此 Sparkpost IP 用于我们的主域，没有出现任何问题。我一直在跟踪辅助域预热的交付能力，Google 显示SPF 通过
此外，有问题的电子邮件标题显示 SPF = Pass
Delivered-To: [email protected]
Received: by 2002:a05:6a10:bd06:b0:52e:9040:15a4 with SMTP id vu6csp442968pxb;
Tue, 9 Jan 2024 08:41:58 -0800 (PST)
X-Google-Smtp-Source: AGHT+IGRcchb3ovyiw/5xuYm3ptNWuD3xyaiboPymYSIYFqSSbpv0/J5Nk8ZzMncijMzCtW8sUm5
X-Received: by 2002:a05:6a20:7d98:b0:199:fa37:8447 with SMTP id v24-20020a056a207d9800b00199fa378447mr1318364pzj.13.1704818518456;
Tue, 09 Jan 2024 08:41:58 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1704818518; cv=none;
d=google.com; s=arc-20160816;
b=tXlFIFSbnuj8ZDpPdSB/D+JUdPADFCR9RqVdUTWWK2JZ7f3qfYWXLSYN7n/TiE368a
0uuLqf8C5B62OcIgcRl0R+m3RQCLrUa8apqPC8WmVwjE+ra4Y0MyW9eZEZBaRY13tBwK
HKx3xajWmt1CiniDQYymmj8+l/Uqz6MBcQmCMDBSlDEZy9u/3x+Fdt7qB3/R6ESXKA2f
kRYcMHuOZ/LUw9SSFKadTXj0bAjd+94ubLyAnBBWtRCweFIVonYAu8gREkfeMfZaU9Ha
tgzK6kO3jp/4TWYksK0JhQy5P3ZU++pyg+RwRBlRW+p6jKza+OWl2FfZjUrTvAg4GjmN
mUJA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
h=from:subject:mime-version:date:message-id:to:dkim-signature;
bh=ifMpQw6f1DKTqKjzS14PabOjSlquCfd6h2oLubLHC7k=;
fh=h14NezYAwyCh2DizMKVSwOlIhcGGyNuwZjGVcUJxnms=;
b=DFLRIUpGZ/Mi6C8XEDvI1YFaUPZIFq2i1UOXmDqKToQzRQ8VH1u50aj8AqnJ6toNau
6zo6KkEu+Y7ft3nfR3VRjbnQjWpqBPpJwAEppUpSTeOEYxNVXr6idfPInUaZ9sSu+Mc7
IjVVxTH9wXrbovp9j8SDvqpcq/7lcMkFrZD9XeZSq30/UjmnQNirH3aQ1YojmmYSnJ5e
Tb4KfpGu4IHvx3/eaxnBUicNIqORTWOkLE7sHJDfd7cGmcMMpAr2ijVqBZwIyf7y8O2Y
JQzqO0RTp3d9A1mHixDeLuGwBkRkod1RNe8DAFNonfLk4eLdQIy12zEEScbhzvECdb+C
6PYw==
ARC-Authentication-Results: i=1; mx.google.com;
dkim=pass [email protected] header.s=scph1223 header.b=l94eYBOq;
spf=pass (google.com: domain of [email protected] designates 156.70.150.33 as permitted sender) smtp.mailfrom="[email protected]";
dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=masterworks-offerings.com
Return-Path: <[email protected]>
Received: from mta-70-150-33.sparkpostmail.com (mta-70-150-33.sparkpostmail.com. [156.70.150.33])
by mx.google.com with ESMTPS id u22-20020a63f656000000b005cddb4051ffsi1667474pgj.25.2024.01.09.08.41.58
for <[email protected]>
(version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
Tue, 09 Jan 2024 08:41:58 -0800 (PST)
Received-SPF: pass (google.com: domain of [email protected] designates 156.70.150.33 as permitted sender) client-ip=156.70.150.33;
Authentication-Results: mx.google.com;
dkim=pass [email protected] header.s=scph1223 header.b=l94eYBOq;
spf=pass (google.com: domain of [email protected] designates 156.70.150.33 as permitted sender) smtp.mailfrom="[email protected]";
dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=masterworks-offerings.com
X-MSFBL: mxFOaiVyP8wgxeRuZCQPIuoOwf1rPY4boEqCJ7zuYCw=|eyJjdXN0b21lcl9pZCI 6IjM0NTgwNiIsInN1YmFjY291bnRfaWQiOiIwIiwidGVuYW50X2lkIjoic3BjIiw iciI6ImV0dUBtYXN0ZXJ3b3Jrcy5jb20iLCJtZXNzYWdlX2lkIjoiNjU5ODU1Nzc 5ZDY1YzliZjFjOWIifQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=masterworks-offerings.com; s=scph1223; t=1704818517; [email protected]; bh=ifMpQw6f1DKTqKjzS14PabOjSlquCfd6h2oLubLHC7k=; h=To:Message-ID:Date:Content-Type:Subject:From:From:To:Cc:Subject; b=l94eYBOqtXnkPb8t9tnY9E0qtIrRv1KikdCfaMQLYtEWBqaP4kaD4HkSoLwmEm2kI
eVyU5cH7MFbaOgJt88W7gSxVDIQDDxPOFujLLXHuRXVCG2iEPRiVfNiIAwbVu/YxSv
4xUvgYGZH7/C6Feu9WNckRLtCRNBAiYLwRNlRAVI=
To: [email protected]
Message-ID: <xxxxx>
Date: Tue, 09 Jan 2024 16:41:57 +0000
Content-Type: multipart/alternative; boundary="_----TSvzDTxPUpPzesYOhQax7g===_10/B9-32230-5577D956"
MIME-Version: 1.0
Subject: Test
From: email <[email protected]>
--_----TSvzDTxPUpPzesYOhQax7g===_10/B9-32230-5577D956
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="UTF-8"
但是，Postmaster 报告称 SPF 成功率为 0%，这可能会降低我们的二级域名声誉。有没有其他人遇到过这个问题并找到了可能的解决方案？感谢您的时间
答案1
Postmaster 可能会显示DMARC相关SPF结果失败，这是由于SPF您的电子邮件的对齐问题。因为在域SPF上检查了Return-Path，即b.masterworks.com，而FROM域是masterworks-offerings.com。
DMARC需要SPF域和FROM域之间的对齐，才能通过DMARC检查（在SPF）。此外，即使您将组织域更改为与 FROM 域匹配，由于是Return-Path从子域发送的，因此由于策略记录中的对齐标记设置为严格（ ），DMARC因此身份验证将在对齐时失败。这要求两个域完全匹配。SPFSPFDMARCaspf=s
要修复此对齐问题：更改标题中的组织域Return-Path并删除aspf标签，以便它采用默认值r（放宽）。