Date: Mon, 03 Feb 2025 19:00:28 -0500
From: Zeffie via Bug reports for the GNU Bourne Again SHell
<bug-bash@gnu.org>
Message-ID: <875b2e87e5d847a4aa04ba2b31bec...@zeffie.com>
| To whom it may concern,
That is most probably not anyone on this list - you'd need to contact
the list maintainers at gnu.org (and no, I have no idea how).
| I wanted to bring to your attention that the bash-bug mailing list
| messages are being marked as spam by our spam filtering.
Spam and DKIM have almost nothing to do with each other, filtering for
spam based upon DKIM is dumb.
| The debug headers indicate an "Invalid DKIM signature" which appears
| to be causing the posts to be flagged.
That's because the From header is being changed by the list to work
around some other "spam protection" mechanism that lots of people seem
to believe in (some kind of check that the addr on the From header
matches the SMTP source of the message - which it almost never does
for mailing list messages).
| This is particularly concerning because it may lead to legitimate
| technical discussions and patches being overlooked or misclassified by
| recipients.
Only by people foolish enough to use DKIM for spam filtering.
| I suspect that the DKIM configuration for the mailing list
What makes you believe there is one? Most messages on the list don't
carry DKIM header fields, as most users don't believe they have enough
usefulness to bother. If you want forgery protection (which is what
it pretends to offer) send signed messages.
One day the world is going to realise that spam is a social (and perhaps
legal) issue, and not a technical one - there is no possible technical
solution that can stop spam, certainly not at the recipient (at the sender
detecting large numbers of messages being sent is a good clue in many
cases, mailing list sites excepted - but the sending site rarely has any
incentive to bother.)
| might need to be reviewed or updated to ensure that the signatures
| validate correctly according to current standards.
If the list went back to leaving the From field alone, which I would
certainly prefer, DKIM would no longer fail (though there's still no
good reason for anyone to use it) but even more people get messages
rejected or classified as spam in that case.
| I would appreciate it if someone with the appropriate authority could
| investigate this matter
You'd have to ask such a person, who most probably doesn't have a lot
of interest in bash bugs, and so isn't on this list.
kre
