From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: v9fs-developer@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] 9p update for 5.10-rc7 (restore splice ops)
Date: Thu, 3 Dec 2020 14:34:36 -0800 [thread overview]
Message-ID: <CAHk-=wjh2=Afx3Eb18RW_APaBKMppmpCpAfFd+n_4DttWJeFow@mail.gmail.com> (raw)
In-Reply-To: <20201203221456.GA20620@nautica>
On Thu, Dec 3, 2020 at 2:15 PM Dominique Martinet
<asmadeus@codewreck.org> wrote:
>
> The problems I had with dkim are all lists that add footers so really
> not much to do about header filtering
Yeah, that's obviously always going to be a problem with DKIM.
But I think all the kernel mailing lists are good now - at least
partly because I used to complain about it.
The one thing that vger still does - or at least did not that long ago
- is to change whitespace in headers. But that is perfectly acceptable
SMTP behavior, and it's a problem only when somebody is using
"c=strict/strict" in their DKIM setup. And honestly, that's a
completely invalid DKIM setting, I don't understand how the DKIM
people ever thought it was ok (probably some company politics or other
because some vendor was too incompetent to implement the proper
relaxed hashing).
Linus
prev parent reply other threads:[~2020-12-03 22:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201203103315.GA3298@nautica>
2020-12-03 19:56 ` [GIT PULL] 9p update for 5.10-rc7 (restore splice ops) Linus Torvalds
2020-12-03 22:14 ` Dominique Martinet
2020-12-03 22:34 ` Linus Torvalds [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHk-=wjh2=Afx3Eb18RW_APaBKMppmpCpAfFd+n_4DttWJeFow@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=asmadeus@codewreck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=v9fs-developer@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).