Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20201203103315.GA3298@nautica> <CAHk-=wigRSokT5YLRGH5Jyun1CwgYHR_1RMcoHjUyz7NJ8wG_g@mail.gmail.com>
 <20201203221456.GA20620@nautica>
In-Reply-To: <20201203221456.GA20620@nautica>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu, 3 Dec 2020 14:34:36 -0800
Message-ID: <CAHk-=wjh2=Afx3Eb18RW_APaBKMppmpCpAfFd+n_4DttWJeFow@mail.gmail.com>
Subject: Re: [GIT PULL] 9p update for 5.10-rc7 (restore splice ops)
To:     Dominique Martinet <asmadeus@codewreck.org>
Cc:     v9fs-developer@lists.sourceforge.net,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

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