David, thanks for the message and for the huge, sensitive work that goes behind this. This problem was not ICANN's making nor ICANN's choice yet of course demands from ICANN a response that is not easy at all. The changes you are implementing are very sensitive. It is important for the community to note and comment on all changes and indications of trouble they/we notice as they may signal needs to adjust the changes you are describing, or to attend to specific users' issues. Everybody should be aware that this is very finicky and that the best responses to trouble are objective, civil reports with well documented information such as platform (hardware, operating system, email client or browser, etc.), full email headers, and copies of the system messages received. Wishing everybody good luck! Alejandro Pisanty - - - - - - - - - - - - - - - - - - - - - - - - - - - Dr. Alejandro Pisanty Facultad de Química UNAM Av. Universidad 3000, 04510 Mexico DF Mexico +52-1-5541444475 FROM ABROAD +525541444475 DESDE MÉXICO SMS +525541444475 Blog: http://pisanty.blogspot.com LinkedIn: http://www.linkedin.com/in/pisanty Unete al grupo UNAM en LinkedIn, http://www.linkedin.com/e/gis/22285/4A106C0C8614 Twitter: http://twitter.com/apisanty ---->> Unete a ISOC Mexico, http://www.isoc.org . . . . . . . . . . . . . . . . ________________________________________ Desde: at-large-bounces@atlarge-lists.icann.org [at-large-bounces@atlarge-lists.icann.org] en nombre de David Closson [david.closson@icann.org] Enviado el: viernes, 23 de octubre de 2015 14:18 Hasta: John R. Levine; Dev Anand Teelucksingh CC: Josh Jenkins; at-large@atlarge-lists.icann.org Asunto: Re: [At-Large] (no subject) Greetings all, ICANN IT Operations can indeed implement the DMARC “fix ups" for our mailman system. We were waiting to test a vendor provided backport (changes from a newer version) patch for our mailman system. We have completed testing as of this morning and plan schedule the change for this weekend. The change will be almost transparent with exception to senders from domains with strict reject DMARC policies. In this case, the “from:” will be replaced with the list address and we will insert a “reply-to:” header with the senders address. Our testing indicates this is working flawlessly with the vendor patch. The lac-discuss-en@atlarge-lists.icann.org and lac-discuss-es@atlarge-lists.icann.org cannot have this “fix up” enabled until the translation email parser is modified to look at the "reply-to” header when a DMARC sender “fix-up” is applied. The code change may take a few more weeks. -- David Closson Director of IT Operations, ICANN 12025 Waterfront Dr. Suite 300 Los Angeles, CA 90094 Office: +1-310-578-8670 Cell: +1-213-270-3866 -- -----Original Message----- From: "John R. Levine" <johnl@iecc.com> Date: Friday, October 23, 2015 at 11:54 AM To: Dev Anand Teelucksingh <devtee@gmail.com> Cc: "david.closson" <david.closson@icann.org>, "at-large@atlarge-lists.icann.org" <at-large@atlarge-lists.icann.org> Subject: Re: [At-Large] (no subject)
Perhaps the issue can be raised at a future At-Large Technology Taskforce call. I've added this issue to the https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_dis... page
Sorry, I'm overcommitted already and have no time. In the very short term, the only plausible way to work around DMARC damage is to upgrade to mailman 3.x and use some of their rewriting hacks. They make the lists work worse since you can't tell who each message is from, but at least they get deliivered.
In the longer run, this week the same people who brought us DMARC have an add-on called ARC that, assuming it works like it should, should mitigate much of the DMARC damage and let people resume running lists the way they always have.
Dev Anand
On Thu, Oct 22, 2015 at 2:26 PM, David Closson <david.closson@icann.org> wrote:
Thanks John.
We can discuss off-list if you would like.
Yes, I was attempting to avoid an email discussion regarding DMARC but we already have a upgrade planned to our mailman system since some DMARC support is a necessity moving forward.
-- David Closson Director of IT Operations, ICANN 12025 Waterfront Dr. Suite 300 Los Angeles, CA 90094 Office: +1-310-578-8670 Cell: +1-213-270-3866 --
-----Original Message----- From: "John R. Levine" <johnl@iecc.com> Date: Thursday, October 22, 2015 at 10:54 AM To: "david.closson" <david.closson@icann.org> Cc: Olivier MJ Crepin-Leblond <ocl@gih.com>, "at-large@atlarge-lists.icann.org" <at-large@atlarge-lists.icann.org> Subject: Re: [At-Large] (no subject)
We are working to provide a solution to this problem as quickly as possible. We will update Valentina Pavel (ICANN IT support case holder) who can in turn advise the Atlarge stakeholders.
It's actually called DMARC, and I can report there is some work in progress to fix it at the group that caused the DMARC problems in the first place.
R's, John
At-Large mailing list At-Large@atlarge-lists.icann.org https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge-2Dlists.icann.o...
At-Large Official Site: https://urldefense.proofpoint.com/v2/url?u=http-3A__atlarge.icann.org&d=BQIB...
At-Large mailing list At-Large@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/at-large At-Large Official Site: http://atlarge.icann.org