infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-16849) please disable munging on all Apache Impala project email lists
Date Sat, 11 Aug 2018 02:27:00 GMT

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

Chris Lambertus updated INFRA-16849:
------------------------------------
    Status: Waiting for user  (was: Waiting for Infra)

This is a complex issue, and you may not be able to strike a happy medium. Here's the scoop:

There are three flags in ezmlm which apply to this: 

  - T: do not add a trailer to the email (typically used for unsubscribe information) 
  - t: opposite, add the trailer

  - F: do not add a prefix to the subject line of [listname]
  - f: opposite, add the prefix

  - x: results in the following non-standard actions:
     - Drop any messages containing Precedence: bulk
     - Remove many non-text MIME parts from messages (see mimeremove).
     - Limit posts to 2 bytes <= msg body size <= 1000000

  - X: means
    - Do not reject bulk senders, limit size, nor remove parts

When ezmlm adds things like footers or changes the subject prefix or removes a mime component,
it causes DMARC to break because ezmlm has modified the message, and it no longer matches
the original sender's DKIM signature. Places like Yahoo reject the message due to their draconian
DMARC policy. 

You can see the policy via https://mxtoolbox.com/dmarc.aspx and enter yahoo.com. p=reject
means messages which fail are dropped.

In order to help resolve this issue, the ASF applies a spec-compliant .INVALID to the domain
name of the original sender when "munging" options are enabled, which means the message won't
fail a DKIM check due to the nonexistence of the .INVALID domain.

The problem you have identified is that some providers flag invalid domains as spam, so by
applying .INVALID to the From: address domain of the sender, we trigger anti-spam rules.

The only way around this is to completely turn off message "munging," which means to disable
the options which add the unsubscribe footer, add the subject prefix, and remove mime components.
Once we've turned off those options, ezmlm will no longer append .INVALID to the sender's
domain name.

Note that we can also manage the .INVALID addition manually by adding or removing a 'dmarc'
control file from the list configuration directory.

What you are asking us to do is to remove all of the unsubscribe footers, prefix changes,
and mime removal from all of the impala lists, which will also remove the .INVALID added to
the From: addresses. Many of your lists have a variety of options, some munged, others not.
With your confirmation, I will remove all ezmlm options which add or modify messages, which
will disable the .INVALID suffix.

Thanks for your patience while I looked into this further. 




> please disable munging on all Apache Impala project email lists
> ---------------------------------------------------------------
>
>                 Key: INFRA-16849
>                 URL: https://issues.apache.org/jira/browse/INFRA-16849
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Mailing Lists
>            Reporter: Michael Brown
>            Assignee: Chris Lambertus
>            Priority: Major
>
> Pursuant to https://blogs.apache.org/infra/entry/dmarc_filtering_on_lists_that please
disable munging on all Apache Impala email lists.
> bq. Apache projects that prefer to avoid munging may file a Jira ticket with infrastructure
to ask that their lists be set to "ezmlm-make -+ -TXF" options.
> Thanks.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message