infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-14305) Mailing list is adding ".INVALID" to djones@ena.com From: header
Date Sun, 18 Jun 2017 08:36:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-14305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gavin updated INFRA-14305:
--------------------------
    Status: Waiting for Infra  (was: Waiting for user)

> Mailing list is adding ".INVALID" to djones@ena.com From: header
> ----------------------------------------------------------------
>
>                 Key: INFRA-14305
>                 URL: https://issues.apache.org/jira/browse/INFRA-14305
>             Project: Infrastructure
>          Issue Type: Project
>          Components: Mailing Lists
>            Reporter: Dave Jones
>            Assignee: Gavin
>            Priority: Minor
>
> When I send to an apache.org ezmlm list, my From: header is changing from djones@ena.com
to djones@ena.com.INVALID.  My email platfrom should have perfect SPF pass and alignment plus
DKIM signing and alignment.  These headers show this is true:
> Mailing-List: contact ruleqa-help@spamassassin.apache.org; run by ezmlm
> Precedence: bulk
> List-Help: <mailto:ruleqa-help@spamassassin.apache.org>
> List-Unsubscribe: <mailto:ruleqa-unsubscribe@spamassassin.apache.org>
> List-Post: <mailto:ruleqa@spamassassin.apache.org>
> List-Id: <ruleqa.spamassassin.apache.org>
> Reply-To: ruleqa@spamassassin.apache.org
> Delivered-To: mailing list ruleqa@spamassassin.apache.org
> Received: (qmail 9380 invoked by uid 99); 7 Jun 2017 20:26:14 -0000
> Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142)
> by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Jun 2017 20:26:14 +0000
> Received: from localhost (localhost [127.0.0.1])
>      by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with
ESMTP id BC5881A0266
>      for <ruleqa@spamassassin.apache.org>; Wed, 7 Jun 2017 20:26:13 +0000 (UTC)
> X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
> X-Spam-Flag: NO
> X-Spam-Score: -0.102
> X-Spam-Level:
> X-Spam-Status: No, score=-0.102 tagged_above=-999 required=6.31
>      tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
>      RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
>      autolearn=disabled
> Authentication-Results: spamd2-us-west.apache.org (amavisd-new);
>      dkim=pass (1024-bit key) header.d=ena.com
> Received: from mx1-lw-eu.apache.org ([10.40.0.8])
>      by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024)
>      with ESMTP id zQW2_9JXySyV for <ruleqa@spamassassin.apache.org>;
>      Wed, 7 Jun 2017 20:26:12 +0000 (UTC)
> Received: from smtp5i.ena.net (smtp5i.ena.net [96.5.1.13])
>      by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id
2071F5F2AE
>      for <ruleqa@spamassassin.apache.org>; Wed, 7 Jun 2017 20:26:12 +0000 (UTC)
> What is adding this ".INVALID" to my visible From: header?  It would have to be something
after SpamAssassin on spamd2-us-west.apache.org since it hits the DKIM_VALID_AU rule.  It
must be ezmlm doing this but why when this header shows DMARC should pass with good DKIM inbound:
> Authentication-Results: spamd2-us-west.apache.org (amavisd-new);
>      dkim=pass (1024-bit key) header.d=ena.com
> Thanks,
> Dave



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message