*UPDATE: Clarified 'wrong' wrt the various protocols.
*UPDATE: Clarified 'wrong' wrt the various protocols.
Its a messy state of affairs to have to workaround issues that dont match your particular models, but its often necessary to have things work at all.
Do note that mailing lists and the way they send mail predate DMARC, DKIM and SPF by far, why don't they better account for this extremely prevalent model of email usage. Why is it that mailing lists that are "broken".
I'd meant 'broken' with respect to DKIM, SPF et al (and have updated the post to reflect that).
So I don't view lists as somehow a techie habit - quite the opposite, in fact. They work for politics because the technical 'barrier to entry' is very low. You don't need to know anything more about computers than how to send and receive email in a client of your choice. Given that in most political groups you're dealing with students, pensioners and everyone in between, this is a distinct evolutionary advantage.
I have no idea how the total volume of list-mail breaks down between tech stuff and muggle concerns. But in any situation where you have to communicate between people of different generations with wildly different technical expertise, lists are an ideal lowest-common-denominator.
Until, that is, Yahoo or whoever cut their users off, and muggins here has to explain to uncomprehending people why their messages aren't appearing.
Guess it's going to be a long week for me. sigh
As well as every other mailing list in recent memory. (Including the LKML. I just checked.)
Whether it's "right" or "wrong" might be an argument that someone will find worth having, but I don't think it can be argued that this isn't common practice.
I appreciate where Yahoo's heart is, but this wasn't really well thought out on their part.
Yes, which many mailing lists do.
> In that case, it's the mailing list doing it wrong
Is it? Not having the actual originator as the "From:" seems to be "doing it wrong".
Personally, I've almost never wanted to privately reply to a mailing list posts (and I'm under the impression that doing so in most contexts is vaguely rude), but redundant CCs in reply-all chains are ugly, so I prefer munging Reply-To.
As for redundant Ccs: That is what Mail-Followup-To is there for, see also:
http://cr.yp.to/proto/replyto.html
edit: Oh, and also, in particular, he completely ignores the fact that Reply-To munging deletes existing Reply-To headers, and thus breaks things in a way that even the best MUA cannot possibly work around - the original Reply-To isn't there anymore, so it cannot possibly offer you an option to reply to the original Reply-To or to the munged Reply-To.
Because the envelope from headers are very likely changed to the mailing list, the SPF pass doesn't help with DMARC. And since the mailing lists very likely alter the messages (to put footers), the messages probably don't pass DKIM either.