主页 / server / 问题 / 1061686
Accepted
philolegein
Asked: 2021-04-27 21:06:26 +0800 CST

我是否需要调整我的 DMARC 设置（最终交付时 SPF 对齐失败）？

  • 772

我已经收到了我的第一份（有史以来！）DMARC 取证报告，我不确定这是否意味着我应该设置不同的东西，或者这是否是所需的行为，或者它是否不受欢迎但没有什么可做的。

实际报告说

Feedback-Type: auth-failure
User-Agent: szn-mime/2.0.46
Version: 1
Original-Mail-From: [email protected]
Original-Rcpt-To: [email protected]
Source-Ip: 2a00:1450:4864:20::348
Reported-Domain: cwrichardson.com
Authentication-Results: email.seznam.cz 1;
    spf_align=fail;
    dkim_align=pass
Delivery-Result: delivered

查看返回的标头，我猜在我发送电子邮件的位置 (@skolaseiferta.cz) 和收件人的实际电子邮件地址 (@seznam.cz) 之间发生了一些内部转发/别名。谷歌中间有一堆东西，看起来一切（SPF、DKIM、DMARC）都在通过。我有模糊的回忆，我在某个地方读过，有时谷歌在不更新标题的情况下转发，这会导致问题。也许这就是这里发生的事情，但我的核心问题是，这种失败（SPF 对齐；但传递的消息）是否表明我配置错误，如果是，我应该改变什么？

这是取证报告中报告的最终标题：

Received: from mail-wm1-x348.google.com (mail-wm1-x348.google.com [2a00:1450:4864:20::348])
    by email-smtpd17.ko.seznam.cz (Seznam SMTPD 1.3.125) with ESMTP;
    Wed, 21 Apr 2021 21:28:04 +0200 (CEST)  
Received: by mail-wm1-x348.google.com with SMTP id j128-20020a1c55860000b02901384b712094so754950wmb.2
       for <[email protected]>; Wed, 21 Apr 2021 12:28:04 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
       d=1e100.net; s=20161025;
       h=x-gm-message-state:dkim-filter:dkim-signature:from:message-id
        :mime-version:subject:date:in-reply-to:cc:to:references:delivered-to;
       bh=z9XlWb3jRfloYwjMKz59BkGnJPKn5q9UeC0Yjl3uFpU=;
       b=OmOkt9uiFimeL2nbIAnz89lXQh6/L47XxRfQcpkktf1KCjK1csYPs/I5UxzzgBxXDL
        QbkfBy3W6l6txQfM+E821xvBU63wXirBdbN8Gxo3Ldw6dQvZ+6uzatuCkEeFVHL6KO6H
        E1O27CVqbz6bhqvaDKEgZRItL6bSAO3OhprafiZk6Yhqr170cAKArDzfTyFgvXX4FGfI
        MFr/1BqM3VQnEyPRBRTiF5i4h1ZxRhnSUvcDH900v+7RN4AZ7+XLAcWjGfHBmWWHea6J
        GV14l7zl22LLRRGIhSaxP+L8qzSG6GM+NRFRJIA8OEfTHkpTXTI1q1aMzLRWIefkMFK/
        C9iQ==
X-Gm-Message-State: AOAM531OlI1F9zTh1HsZoHNZWRw2CRCcaLXZmaWuT10mdobzsf1XdbXR
    jVsZvqhPh/16vPkDdJdHwZdNzDTJ7CYTnntl2W3Ylv1iWfO45ExY/3J5H2S8LMTc9m/Vg1HzH9N
    unIJoFt2ngq8JpN5PRnXe3TbNIRVN5ypsMMYp9rWdDmXRlI/X3Q==
X-Received: by 2002:a5d:47c1:: with SMTP id o1mr27285827wrc.216.1619033282566;
       Wed, 21 Apr 2021 12:28:02 -0700 (PDT)
X-Google-Smtp-Source: ABdhPJxghHJgfoFCadI4rf70xN3TaKsadvCo5viffMf7GjVOMzjZImFo2jdnWEOn8V+OIxc8YVlx
X-Received: by 2002:a5d:47c1:: with SMTP id o1mr27285733wrc.216.1619033281236;
       Wed, 21 Apr 2021 12:28:01 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1619033281; cv=none;
       d=google.com; s=arc-20160816;
       b=i9HgJPQWyJQaj9eHYTRTLX30VfCcgk3coymQyyGzs3jKpMtoTGTSkTJoakmG4kpamB
        HBf9tf6FdxKZK1EPYUhu2HoIB99JSwU5/hm7+LjM9izktRYp12apYf37Q1XqUqWXXJkx
        iUUEVpjE33D6TmhklEOw6HZaSK+GI+AYESoUkIWuqJLG95+5gt2Ckq21Xs3zGw57m5vE
        pkusUkEKxR/8UOrFag6U4OLMr6ydy/oUNtQhUiAr2imI2qYUbMCoGpwDiIm4NI6n7Wtx
        WSTvKGZymXugiv51qBlmtL0u5U3dNTVTtJSKr2Vo4oDIQBIZaw1hm2oudeLPOvmdwSP0
        YfGQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
       h=references:to:cc:in-reply-to:date:subject:mime-version:message-id
        :from:dkim-signature:dkim-filter;
       bh=z9XlWb3jRfloYwjMKz59BkGnJPKn5q9UeC0Yjl3uFpU=;
       b=R3Rk9Xazyo8BwHtxFEETi3RxVnAMqd8aFzNgQYVSQ7eTSEFbkxquX3YWP5blsnu7el
        GinyOV6vxvBuRJpZOgx+7+zgT4os0xGP7naNBG8kyMBuFjvTTvt/g592KmZj0RurQezb
        lspa6TLQ+x1wpysKvlg7Dy0VKFhfAkww8vXDNNbaJuC/YlBFNGab+x2B2FLtrITIxR6B
        OyOpCsX2MvbXtuRikXRgzkvm5DWVqyt6XFH/a3kw9PvbzR23eEmX/OMZe/g+W9ZW8O7D
        /hbimfG2OjKsOAFOCX1yeUUlV0M2hdphi3yI3zSOgoqpTgQfieaHCm9LtkuYAmBBoFH7
        nuDw==
ARC-Authentication-Results: i=1; mx.google.com;
      dkim=pass [email protected] header.s=default header.b=rKVHfdcx;
      spf=pass (google.com: domain of [email protected] designates 54.93.189.174 as permitted sender) [email protected];
      dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=cwrichardson.com
Return-Path: <[email protected]>
Received: from mercury.mirovoysales.com (mercury.mirovoysales.com. [54.93.189.174])
       by mx.google.com with ESMTP id r5si462898wrl.256.2021.04.21.12.28.00;
       Wed, 21 Apr 2021 12:28:01 -0700 (PDT)
Received-SPF: pass (google.com: domain of [email protected] designates 54.93.189.174 as permitted sender) client-ip=54.93.189.174;
Authentication-Results: mx.google.com;
      dkim=pass [email protected] header.s=default header.b=rKVHfdcx;
      spf=pass (google.com: domain of [email protected] designates 54.93.189.174 as permitted sender) [email protected];
      dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=cwrichardson.com
Received: from localhost (unknown [127.0.0.1])
    by mercury.mirovoysales.com (Postfix) with ESMTP id EF3C88004B;
    Wed, 21 Apr 2021 19:27:59 +0000 (UTC)
X-Virus-Scanned: amavisd-new at example.com
Received: from mercury.mirovoysales.com ([127.0.0.1])
    by localhost (ip-10-0-200-85.eu-central-1.compute.internal [127.0.0.1]) (amavisd-new, port 10024)
    with ESMTP id wQKPlvH_4S8m; Wed, 21 Apr 2021 19:27:57 +0000 (UTC)
Received: from [192.168.1.2] (213.121.broadband6.iol.cz [88.101.121.213])
    (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
    (No client certificate requested)
    by mercury.mirovoysales.com (Postfix) with ESMTPSA id 3A67080037;
    Wed, 21 Apr 2021 19:27:57 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mercury.mirovoysales.com 3A67080037
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cwrichardson.com;
    s=default; t=1619033277;
    bh=z9XlWb3jRfloYwjMKz59BkGnJPKn5q9UeC0Yjl3uFpU=;
    h=From:Subject:Date:In-Reply-To:Cc:To:References:From;
    b=rKVHfdcxSd1ZhsD1G1X5jvil3lpme2V8tNU+3D0PgdBklG/uYMEdRFVOjr6vqkp9y
     GhZa5D1MVyG1Zd/OZ8v7OZ6x2YZsObnWz92Q5B+X1H5lvbD7/1K9AuNAVmMMmWdlMl
     EY7thbBBQyT1f7j4TvHJTwuJx2JZszR1BjlGoEiY=
From: Christopher Richardson <[email protected]>
Message-Id: <[email protected]>
Content-Type: multipart/alternative;
    boundary="Apple-Mail=_4FC50147-75FE-4FDF-B8EC-F651F9EF7F63"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Subject: =?utf-8?B?UmU6IMWha29sYSB2IHDFmcOtcm9kxJs=?=
Date: Wed, 21 Apr 2021 21:27:56 +0200
In-Reply-To: <[email protected]>
Cc: Sarah Richardson <[email protected]>,
[email protected]
To: [email protected]
References: <CAOSANHi3e3EPsdvvBU5sh_r3T5h+m8+4Mmwsek=ZxHj3rmEaZQ@mail.gmail.com>
<[email protected]>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Delivered-To: [email protected]: Wed, 21 Apr 2021 21:28:10 +0200 (CEST)
Reporting-MTA: dns; email.seznam.cz

Final-Recipient: rfc822; [email protected]
Status: 2.0.0
Diagnostic-Code: x-uknown;
Action: x-unknown
Original-Recipient: rfc822; [email protected]
email email-server dmarc

1 个回答

  1. Best Answer

    要实现 DMARC 合规性，必须对齐 SPF 或 DKIM 。所以我不明白你为什么收到这份取证报告——据我了解 DMARC 系统，这条消息是合规的，因为 DKIM 通过了对齐测试据我所知，这条消息是符合 DMARC 的——通常你不会得到取证报告，但有一个设置要求报告，即使任何机制失败（感谢@anx 提供此信息 - 对我来说是新的！）。该报告还在最后一行告诉您消息已送达 - 因此这里没有拒绝或隔离。

    转发是 DMARC 的一个已知问题，因为标头中的发件人地址可能不匹配。通常，如果邮件网关检测到不符合 DMARC 的邮件并且由于标头中的特定提示而“看起来已转发”，则网关可以让该邮件通过 - 即使 SPF和DKIM 失败 -请参阅 DMARC Policy Overrides。

    • 3

相关问题