On 2020-01-24 at 16:07 +0100, Renaud Allard via mailop wrote: > In this day and age, mailing lists have no excuse for not rewriting > the original envelope sender to one of their own (mailop does it > correctly). > Forwards between uncontrolled servers are also a very bad idea for > multiple reasons that are way outside the scope of this topic.
I disagree. If I receive that was sent by "Renaud Allard", I would expect the From to be Renaud Allard, and be able to search for all the messages from your company (or family) by searching for "@allard.it", just like I could search if there is any message from "@microsoft.com" to test for their (active) presence on this list. The "right" way they should be, according to the spirit of the RFC, going back to RFC 680 would be to keep the user in the From header (the person who wished this message to be sent) and place the mailing list at the Sender header (the person who sends the message). It should be the task of the MUA to then display the Sender field as applicable. SenderID actually got it right. Yet, given that many MUA ignored that field, DMARC chose to use only the From header, breaking the meaning of From header for everyone, since information is lost in the process. Cheers _______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
