On 7/25/18 1:48 PM, Jordan Brown wrote: > Hmm. It would take MUA changes to be fully effective, but a possibility > that comes to mind is to have mailing lists leave the original message > absolutely unmodified, but wrap it in a message that comes "from" the > mailing list. That way everything about the message is verifiably true. > > A list-aware MUA could more or less transparently unwrap such a > message. It would probably display some indication that the message > came through the ML - the name of the list, unsubscribe mechanism, > archive pointers, ML header or footer text, et cetera, and maybe > activate alternative "reply" options[*] - but would largely present the > message as "from" the original author, *via* the mailing list. > > Perhaps the wrapper message would look like today's munged ML messages - > From: Real Person <mailingl...@example.com> / Reply-To: Real Person > <realper...@example2.com> - but a list-aware MUA would largely hide that. > > Of course there are a million details and getting adoption would be hard. Yes, one set of solutions would involve defining standards of how to compose composite messages, with standards on how to display them. A major part of the current issue is that for anything more than a single part plain text you can't be sure how it will be handled.
Yes, you can't be absolutely positive that every MUA will work right, you at least have the defense that you did your best to be clear within the standard, and perhaps the standard could even be worked that existing non-conforming implementations are so bad that it is clear that the user needs a new MUA. -- Richard Damon ------------------------------------------------------ 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