linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Linus Torvalds <torvalds@linux-foundation.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 23:14:56 +0100	[thread overview]
Message-ID: <20201203221456.GA20620@nautica> (raw)
In-Reply-To: <CAHk-=wigRSokT5YLRGH5Jyun1CwgYHR_1RMcoHjUyz7NJ8wG_g@mail.gmail.com>

Linus Torvalds wrote on Thu, Dec 03, 2020:
> Pulled.

Thanks!

> > (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.

Hmm, good catch, but that one was on me just now -- I just resent the
mail as I got it through the v9fs list to reuse recipients instead of
the one I had sent before so I did send a bogus list-id, which happened
to get signed.
... looking at list archives it looks like majordomo took that to be a
spam and didn't forward the mail at all, that's a discrete way to sneak
a direct mail without any Cc!
I was about to add it to ignored headers for signing but I'll just have
to be careful about that now. Or figure how to make mutt drop it first.


The problems I had with dkim are all lists that add footers so really
not much to do about header filtering (normally lists would change the
from when they do that or change subject, but for some reason the two
I'm thinking of don't, one of the two even strips dkim headers so even
the body length flag (l=) isn't helping)
I haven't had problems with kernel lists which don't mess with key
headers, good job admins.


Anyway, it's a bit off topic -- good to know new mail didn't go to spam
at least :)
-- 
Dominique

  reply	other threads:[~2020-12-03 22:15 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 [this message]
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=20201203221456.GA20620@nautica \
    --to=asmadeus@codewreck.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).