Last modified: 2014-05-27 19:26:51 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T66818, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 64818 - Mitigate strict DMARC policy on the mailing lists
Mitigate strict DMARC policy on the mailing lists
Status: NEW
Product: Wikimedia
Classification: Unclassified
Mailing lists (Other open bugs)
wmf-deployment
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: upstream
Depends on: 64547
Blocks:
  Show dependency treegraph
 
Reported: 2014-05-04 10:32 UTC by Seb35
Modified: 2014-05-27 19:26 UTC (History)
8 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Seb35 2014-05-04 10:32:08 UTC
Try to become more DMARC-complient on the mailing lists to improve deliverability, particularly given Yahoo and AOL recently switched to a policy p=reject, preventing these users from sending emails to the mailing lists.

This bug is partly wontfix since this is linked to an upstream Mailman for a proper resolution, but could be partly mitigated by changing some configuration parameters, although there is no proper solution. I open this bug partly to isolate this mailing lists issue from other DMARC-related bugs (56414, 59731, 64795), and properly tracking the issue.

Two mitigations:

1/ http://www.spamresource.com/2014/04/run-email-discussion-list-heres-how-to.html is a way to mitigate the issue, although the main point is to change the From: header to a fixed address like wikitech-l@lists.wikimedia.org (quite disruptive for all users).

2/ http://www.ietf.org/mail-archive/web/ietf/current/msg87176.html proposes to rewrite Yahoo (+AOL) sending addresses from someone@yahoo.com to someone@yahoo.com.invalid to bypass DMARC.
Comment 1 Nemo 2014-05-04 18:55:10 UTC
(In reply to Seb35 from comment #0)
> This bug is partly wontfix since this is linked to an upstream Mailman for a
> proper resolution

Can you link or file it (on launchpad)?
Comment 2 Seb35 2014-05-04 20:32:46 UTC
Apart http://dmarc.org/faq.html#s_3 which is only theoretical, I found this announcement of some support for DMARC in Mailman 2.1.16 and 2.1.18 (released April 18, 2014): http://wiki.list.org/display/DEV/DMARC

If I understand correctly, the introduced config parameter from_is_list is now on a per-list basis; this one rewrite the From: header (RFC 5322) with "Sender via the list wikitech-l" <wikitech-l@lists.wikimedia.org>, or could wrap the message as a sub-part in a MIME message.
Comment 3 Nemo 2014-05-05 05:37:05 UTC
Reply-To is unaffected, which is good (we use reply_goes_to_list). https://bugs.launchpad.net/mailman/+bug/1313010

Probably better wait for https://bugs.launchpad.net/mailman/+bug/1315970 at least.
Comment 4 Andre Klapper 2014-05-06 16:18:04 UTC
I think we'll wait for upstream here, or rather on bug 64547 (Mailman 3). 
Hence setting low priority.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links