On Fri, 2 Oct 2020, Carlos E. R. wrote:
The absence of subject prefix breaks some filtering.
Yep, I am aware - people will have to adjust their filtering.
Sorry, but it is impossible.
There are the permanent filters that can filter on any header.
But there are the visual filtering, like the "Quick filter" in Thunderbird,
that can only filter on subject, sender, recipient, and body.
And there is of course the human usual filter. I look at all the messages in
my inbox, and by just looking at the header I decide to look inside or not.
Not having the visual clue to the list breaks usability. Dozens of lists and I
will not see in the inbox to which list, if any, does the post belong to. I
can also confuse personal mails with lists mails.
This is a huge breakage.
Yes, but this is what we (the whole mailing list world) get with
DKIM/DMARC, whose "designers" never thought about mailing lists. If the
mailing list server doesn't adhere to DKIM some subscribers won't receive
mail anymore as their MTAs reject them then (which they must if they
adhere to DMARC and the senders policy requests rejection). There are
basically only two possiblities:
a) don't rewrite or remove any headers that are included in the signature
(and Subject: is often included of course), and don't munge the body
b) remove all traces of DKIM, but that implies that you _have_ to rewrite
the From: header so that it looks like the mail originates from the
mailing list server, not from the person actually sending the mail
I'm on mailing lists that do either (a) or (b), and option (b) is much
worse than (a): all mails come from: list(a)server.org and the originator is
coded in the reply-to header, or in some additional x-foo: header that no
mail client shows by default.