From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: Netdev <netdev@vger.kernel.org>,
v9fs-developer@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [GIT PULL] 9p update for 5.10-rc7 (restore splice ops)
Date: Thu, 3 Dec 2020 11:56:57 -0800 [thread overview]
Message-ID: <CAHk-=wigRSokT5YLRGH5Jyun1CwgYHR_1RMcoHjUyz7NJ8wG_g@mail.gmail.com> (raw)
In-Reply-To: <20201203103315.GA3298@nautica>
On Thu, Dec 3, 2020 at 2:33 AM Dominique Martinet
<asmadeus@codewreck.org> wrote:
>
>
> Hi Linus,
>
> Someone just reported splice got disabled in 5.10-rc1, here's a couple
> of patches to turn it back on using generic helpers.
Pulled.
> (Thanks for letting me know my mails got flagged as spam last time, I've
> taken the time to setup dkim/dmarc which brings its share of problems
> with some mailing lists but hopefully will help here)
It looks good here, but I would suggest you edit your DKIM configuration a bit.
In particular, you have "List-ID" in your set of header files that
DKIM hashes, and that means that any mailing list that then adds that
header will destroy your DKIM hash.
So you seem to make it almost intentionally hard for your DKIM to be
valid when you send emails to a list.
I'd suggest you keep the DKIM hash to just the basic fields that your
MUA will fill in, ie things like
Date:From:To:Cc:Subject:References:In-Reply-To:Message-ID
because if somebody messes with *those*, then I think they are doing
something wrong - in ways that adding a "List-ID" as it goes through a
mailing list is not.
(But I'm not a DKIM expert, just a spam hater).
Linus
next parent reply other threads:[~2020-12-03 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201203103315.GA3298@nautica>
2020-12-03 19:56 ` Linus Torvalds [this message]
2020-12-03 22:14 ` [GIT PULL] 9p update for 5.10-rc7 (restore splice ops) Dominique Martinet
2020-12-03 22:34 ` Linus Torvalds
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-=wigRSokT5YLRGH5Jyun1CwgYHR_1RMcoHjUyz7NJ8wG_g@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=asmadeus@codewreck.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).