Re: [Mailman-Users] DMARC issues
On 11/04/14 03:19, Mark Sapiro wrote: I'm not sure why you can't upgrade if you can patch the code, but in any case, I can't point you at a single patch to do it my way because there are several. You could do it by applying all of the following patches in order. Thank you very much, Mark! -- Pozdrav / Regards, Siniša Burina -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] DMARC issues
Hello! I believe there's no need to elaborate on the problems recently introduced by Yahoo, changing their DMARC DNS record and rendering many mailman lists unusable for Yahoo mail users. I see the solution to this problem in changing the From: field to mailing list's address, but keeping the poster's name or address in the description part of the same field. For example: From: List Name on behalf of Poster Name l...@add.re.ss or From: Poster Name via List Name l...@add.re.ss or From: Poster Name l...@add.re.ss or From: Poster Name [pos...@add.re.ss] l...@add.re.ss I'm using Mailman 2.1.13, and can not upgrade to 2.1.16 on a live system. I was forced to turn on anonymous_list as the urgent remedy, byt the full anonymization is not really how it should be. Could someone please help me achieve this using the above version, by some changes in the code? Thank you! -- Pozdrav / Regards, Siniša Burina -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] DMARC issues
On 10/04/14 16:25, Joseph Brennan wrote: They're breaking RFC 822 / 5322. The From: field specifies the author(s) of the message, that is, the mailbox(es) of the person(s) or system(s) responsible for the writing of the message. [...] In all cases, the From: field SHOULD NOT contain any mailbox that does not belong to the author(s) of the message. I don't think we should compound that by changing the From line. Well, anonymous_list option does that too, completely hiding the original poster's information. The approach I proposed would do the same, only in slightly subtler manner. :) -- Pozdrav / Regards, Siniša Burina -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] DMARC issues
On 10/04/14 17:18, Lindsay Haisley wrote: This is the first I've heard of this issue, but it doesn't surprise me at all. Basically, Yahoo insists that their own mail servers are the only ones that can originate the message with @yahoo.com domain in the From header. Not Return-Path, Not the envelope sender, but exactly the From header in the message itself. If this practice gets adopted by more organizations, I don't know how else could this problem be solved. -- Pozdrav / Regards, Siniša Burina -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] DMARC issues
On 10/04/14 19:57, Stephen J. Turnbull wrote: Or just bounce them with a message stating that Yahoo no longer permits its users to post to mailing lists, so please use a different posting address. I realize that most sites can't do that, but mine can (and will if I get any complaints about this policy -- my subscribers are sympathetic). And that's exactly what I'm going to do. :) -- Pozdrav / Regards, Siniša Burina -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
