DMARC bouncing of yahoo and hotmail users

Hi,
I've started noticing bounces to yahoo and hotmail users with this rejection message:
Unfortunately, messages from (xxx) on behalf of (yahoo.com.br) could not be delivered due to domain owner policy restrictions. (in reply to end of DATA command))
In researching this problem I found this thread:
http://osgeo-org.1560.x6.nabble.com/OSGeo-1454-mailman-Mass-bouncing-of-yaho...
From the thread it seems to indicate that Mailman v2.1.19 would have a
workaround for the issue.
First, does anyone know if the updates in Mailman do indeed address the issue?
Second, my server is running Ubuntu linux with Mailman v2.1.16 and I'm not able to update to a new version via the apt-get command since this version of Ubuntu has v2.1.16 as the "latest". Is it safe for me to update Mailman via a tarball and not mess up the packaged installation?
thanks Ricardo

On 4/13/16 11:22 AM, Ricardo Kleemann wrote:
I've started noticing bounces to yahoo and hotmail users with this rejection message:
Unfortunately, messages from (xxx) on behalf of (yahoo.com.br) could not be delivered due to domain owner policy restrictions. (in reply to end of DATA command))
Yahoo recently started applying DMARC p=reject to more domains. See https://mail.python.org/pipermail/mailman-users/2016-April/080678.html.
In researching this problem I found this thread:
http://osgeo-org.1560.x6.nabble.com/OSGeo-1454-mailman-Mass-bouncing-of-yaho...
From the thread it seems to indicate that Mailman v2.1.19 would have a
workaround for the issue.
First, does anyone know if the updates in Mailman do indeed address the issue?
There have been workarounds for this issue since 2.1.16, but they didn't get serious until 2.1.18 and have seen continuous tweaking since then.
See the FAQ articles at http://wiki.list.org/DEV/DMARC and http://wiki.list.org/x/17891458
Second, my server is running Ubuntu linux with Mailman v2.1.16 and I'm not able to update to a new version via the apt-get command since this version of Ubuntu has v2.1.16 as the "latest". Is it safe for me to update Mailman via a tarball and not mess up the packaged installation?
See the FAQ at http://wiki.list.org/x/17891606.

Mark Sapiro writes:
There have been workarounds for this issue since 2.1.16, but they didn't get serious until 2.1.18 and have seen continuous tweaking since then.
In other words, Mark is too modest. Get 2.1.latest (.20, I think?), 'cause Maintainer Markie kicks a--!
Technically, he's right, they're tweaks, but as a user experience life is truly better. If you need to upgrade, get the latest.
participants (3)
-
Mark Sapiro
-
Ricardo Kleemann
-
Stephen J. Turnbull