【问题标题】:Gmail shows "via" even if the domain is authenticated with Mailchimp and has valid SPF and DKIM records即使域通过 Mailchimp 进行身份验证并且具有有效的 SPF 和 DKIM 记录,Gmail 也会显示“通过”
【发布时间】:2017-12-21 08:02:41
【问题描述】:

我正在使用 Mailchimp 发送时事通讯,Gmail 显示邮件是通过 mail5.mcsignup.com 发送的,即使我添加了 Mailchimp 的 SPF 和 DKIM 记录并且域在 Mailchimp 中进行了身份验证。

Outlook 还显示电子邮件是“代表”发送的。

我用 mxtoolbox.com 测试了 SPF,用 dkimcore.org 测试了 DKIM,它们是有效的。

看起来 SPF 和 DKIM 在 gmail 标头中传递。以下是 Gmail 的标题:

   *ARC-Authentication-Results: i=1; mx.google.com;
           dkim=pass header.i=@mail5.mcsignup.com header.b=G93ARUrl;
           dkim=pass header.i=@mandrillapp.com header.b=i0uux1aP;
          spf=pass (google.com: domain of bounce-md_9656357.596bc38e.v1-
    43028f7e330f4128b36015188bc1fb10@mandrillapp.com designates 205.201.136.19 as 
    permitted sender) smtp.mailfrom=bounce-md_9656357.596bc38e.v1-
    43028f7e330f4128b36015188bc1fb10@mandrillapp.com
    Return-Path: <bounce-md_9656357.596bc38e.v1-
    43028f7e330f4128b36015188bc1fb10@mandrillapp.com>
    Received: from mail5.mcsignup.com (mail5.mcsignup.com. [205.201.136.19])
            by mx.google.com with ESMTPS id 
   d10si3015324yba.575.2017.07.16.12.50.38
            for <EMAIL@gmail.com>
            (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
           Sun, 16 Jul 2017 12:50:38 -0700 (PDT)
    Received-SPF: pass (google.com: domain of bounce-md_9656357.596bc38e.v1-
    43028f7e330f4128b36015188bc1fb10@mandrillapp.com designates 205.201.136.19 as 
    permitted sender) client-ip=205.201.136.19;
    Authentication-Results: mx.google.com;
           dkim=pass header.i=@mail5.mcsignup.com header.b=G93ARUrl;
           dkim=pass header.i=@mandrillapp.com header.b=i0uux1aP;
           spf=pass (google.com: domain of bounce-md_9656357.596bc38e.v1-
    43028f7e330f4128b36015188bc1fb10@mandrillapp.com designates 205.201.136.19 as 
    permitted sender) smtp.mailfrom=bounce-md_9656357.596bc38e.v1-        
    43028f7e330f4128b36015188bc1fb10@mandrillapp.com
    DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=mandrill; 
    d=mail5.mcsignup.com; h=From:Sender:Subject:To:Message-Id:Date:MIME-
    Version:Content-Type; i=contact@mail5.mcsignup.com; 
    bh=fnyV42cJxlWmSMb63R6R/rVuLTzDaUFDaGqL0N4WaMA=; 
   b=G93ARUrloP6yy40uMAHkv9TNXH/7GDjg4ozK0rk7oeKQ40lWaWzkB8UTgsMyHTSNLNneWdcTWlCO       
     INNBCc55gqlISw08WRn52e+7gQWx8vllJv77RiJiX58wFJYsTbrLQA086QQ/8EYEKo9Mtgqzxg4/
       2CFWJPCv3XKRgg6Nnmg=
    Received: from pmta07.mandrill.prod.suw01.rsglab.com (127.0.0.1) by 
    mail5.mcsignup.com id hdf1os174e0q for <EMAIL@gmail.com>; Sun, 16 Jul 2017 
    19:50:38 +0000 (envelope-from <bounce-md_9656357.596bc38e.v1-
    43028f7e330f4128b36015188bc1fb10@mandrillapp.com>)
    DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mandrillapp.com;
      i=@mandrillapp.com; q=dns/txt; s=mandrill; t=1500234638; h=From :
      Sender : Subject : To : Message-Id : Date : MIME-Version : Content-Type
      : From : Subject : Date : X-Mandrill-User : List-Unsubscribe;
      bh=fnyV42cJxlWmSMb63R6R/rVuLTzDaUFDaGqL0N4WaMA=;
      b=i0uux1aPb7yxSqpYdr5e45hKJHeAb1ow5k4xE9K7/NxlKt4JW9xvSS3AazIojjleDpLqfC 
    4gESZATfoj6eAXRSqoq2+o6Jxfwi7tvEdTf4IjdonTl3QioXSHJj/joagC8nKJ3HQIaPIh+I 
    xycoNL7i/nXzcQqlslsYW9z1G+/Hs=
    From: MY COMPANY <contact@mydomain.com>
    Sender: MY COMPANY <contact@mail5.mcsignup.com>
    Subject: MY SUBJECT
    Return-Path: <bounce-md_9656357.596bc38e.v1-
    43028f7e330f4128b36015188bc1fb10@mandrillapp.com>
    X-Accounttype: ff
    X-Auto-Response-Suppress: OOF, AutoReply
    Auto-Submitted: auto-generated
    Form-Sub: v=1;ip4=MY IP
    To: "EMAIL@gmail.com" <EMAIL@gmail.com>
    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=9656357.43028f7e330f4128b36015188bc1fb10
    X-Mandrill-User: md_9656357
    Message-Id: 
    <9656357.20170716195038.596bc38e18bbf4.75410701@mail5.mcsignup.com>
    Date: Sun, 16 Jul 2017 19:50:38 +0000
    MIME-Version: 1.0*

我也在该域上使用 cloudflare。

我错过了什么吗?有关如何删除“通过”和“代表”的任何建议?

【问题讨论】:

    标签: email gmail mailchimp spf dkim


    【解决方案1】:

    这就是 Outlook 显示“代表”的原因:

    From: MY COMPANY <contact@mydomain.com>
    Sender: MY COMPANY <contact@mail5.mcsignup.com>
    

    如果有Sender 标头和From 标头,则这表示“秘书方案”,其中消息由一个帐户(通常是邮件列表,但最初是秘书)发送但实际上是来自其他人(比如公司 CEO,他不知道如何使用电子邮件……)

    当 Outlook 看到发件人标头时,会将其显示为 From $from on behalf of $sender

    邮件列表通常会设置一个Sender 标头,实际上应该根据 RFC,以便 SIDF 等安全系统可以针对发件人而不是发件人进行验证(尽管 DMARC 不这样做,这是另一个问题)。

    【讨论】:

      【解决方案2】:

      发送电子邮件时包含多个域。

      1. HEADER FROM 是您在用户名之后看到的域(在 abc@example.com 中,example.comHEADER FROM 域)
      2. MAIL FROM 是用于发送电子邮件的域。您将在 Return-Path 下的标题部分看到。在标题中,您提到MAIL FROM 域是mandrillapp.com

      所以基本上在发送电子邮件时,您的电子邮件服务提供商使用mandrillapp.com 作为您的发送域。要解决此问题,您只需使用您的域更改返回路径。您可以使用域中无关紧要的任何子域。您仍然可以在HEADER FROM 中使用根域。

      按照本文进行更改。 https://mandrill.zendesk.com/hc/en-us/articles/360039293113-How-to-Customize-the-Return-Path-Address

      【讨论】:

        猜你喜欢
        • 1970-01-01
        • 2020-09-28
        • 2012-06-11
        • 2020-12-02
        • 1970-01-01
        • 2022-06-30
        • 1970-01-01
        • 2014-05-30
        • 2018-12-22
        相关资源
        最近更新 更多