Re: [Mailman-Developers] Author_is_list option in upcoming mailman 2.1.16

2013-09-14 Thread Franck Martin
When a list goes bad, usually the members are not blamed but the list admin, therefore making the list the system responsible of the writing of the message. Anyhow, it does not matter, this is a religious discussion. Please feel free to code and test your solution of encapsulating the message in

Re: [Mailman-Developers] Author_is_list option in upcoming mailman 2.1.16

2013-09-14 Thread Franck Martin
On Sep 14, 2013, at 5:16 PM, Stephen J. Turnbull wrote: > Franck Martin writes: > >> Unfortunately z= and especially l= are not used practically by >> senders because they create a risk. One could add an attachment >> containing malware to the message for instance. > > Indeed, we have to assum

Re: [Mailman-Developers] Author_is_list option in upcoming mailman 2.1.16

2013-09-14 Thread Stephen J. Turnbull
Franck Martin writes: > Unfortunately z= and especially l= are not used practically by > senders because they create a risk. One could add an attachment > containing malware to the message for instance. Indeed, we have to assume that the MUAs are broken in this respect. See Daniel Gillmor's po

Re: [Mailman-Developers] Author_is_list option in upcoming mailman 2.1.16

2013-09-14 Thread Franck Martin
On Sep 13, 2013, at 7:48 PM, Mark Sapiro wrote: > On 09/13/2013 12:18 PM, Franck Martin wrote: >> >> Mailman breaks DKIM as soon as you add a footer or tag in the subject line, >> which a lot of lists do (including this one). > > > Not necessarily. It depends on the DKIM signature and how mu

Re: [Mailman-Developers] Author_is_list option in upcoming mailman 2.1.16

2013-09-14 Thread Stephen J. Turnbull
Franck Martin writes: > One may argue that since the list is modifying the message, it is > now the new author of it, this proposal just make it more clearly. Nonsense. Here's what RFC 5322 says: The "From:" field specifies the author(s) of the message, that is, the mailbox(es) of the