DMARC is perfectly compatible with mailing lists as long as they don't forge emails. If they set headers like List-Unsubscribe and sent them along, it wouldn't be an issue. Amusing that the Linux kernel depends so much on email security but they're against preventing spoofing.
Conversation
Replying to
what are you talking about? the vger.kernel.org lists I'm on send mails with valid SPF/DKIM/DMARC from the original sender, and they don't append footers or subject prefixes or anything like that.
1
can you please be more specific and say which list(s) you're talking about?
1
(er, of course the SPF is from the list, not from the original sender.)
1
Replying to
I'm not talking about the current status of the vger.kernel.org but rather the fact that they spent years fighting it, banned users from providers using DMARC and still rant about it being so awful. I don't understand why they opposed it so much and still do even now.
1
Replying to
do you have concrete pointers on when LKML became DKIM-compatible? from what I can tell from looking at lore.kernel.org, even back in 2007 there was no footer on LKML mail anymore?
1
Replying to
Essentially, I don't understand why they are talking about DMARC being horrible in 2019, 2018, 2017, 2016 and 2015. I can link you to the threads I'm talking about. They seem really opposed to the concept of it and they apparently banned .com over them adding DMARC reject.
mailarchive.ietf.org/arch/msg/ietf/ is an example in December 2016. I don't see anything about it in 2020. I can't recall ever having problems but I was using Gmail which doesn't have a reject policy.
Early post in 2015: lkml.org/lkml/2015/9/4/
More recent 2018: lkml.org/lkml/2018/8/15
1
It's possible they fixed this in 2018 and were just still angry about it in 2019?