From: Matthew Wilcox <willy@infradead.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Jann Horn <jannh@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, bcrl@kvack.org
Subject: Re: Emails from kvack.org going into spam
Date: Fri, 16 Oct 2020 14:57:33 +0100 [thread overview]
Message-ID: <20201016135733.GF20115@casper.infradead.org> (raw)
In-Reply-To: <20201016135451.GB36674@ziepe.ca>
On Fri, Oct 16, 2020 at 10:54:51AM -0300, Jason Gunthorpe wrote:
> Does anyone know who is the admin for kvack.org?
That's Ben. Adding cc.
> I was cleaning my GMail spam mail box and saw lots of messages from
> Jann Horn in the spam filter. Since he is not a spammer I investigated
> what is going on.
>
> I see it is because GMail is flagging all of Jann's messages as having
> a DKIM failure and Jann's employeer domain 'google.com' is enforcing a
> DMARC policy:
>
> Authentication-Results: mx.google.com;
> dkim=neutral (body hash did not verify) header.i=@google.com header.s=20161025 header.b=UzPVodG7;
> spf=pass (google.com: domain of owner-linux-mm@kvack.org designates 205.233.56.17 as permitted sender) smtp.mailfrom=owner-linux-mm@kvack.org;
> dmarc=fail (p=REJECT sp=REJECT dis=QUARANTINE) header.from=google.com
>
> Selecting a message from Jann that went through LKML and kvack:
>
> https://lore.kernel.org/lkml/20201015000041.1734214-1-jannh@google.com/raw
> https://lore.kernel.org/linux-mm/20201015000041.1734214-1-jannh@google.com/raw
>
> And checking the DKIM:
>
> $ opendkim-testmsg < raw.lkml
> $ opendkim-testmsg < raw.mm
> opendkim-testmsg: dkim_eom(): Bad signature
>
> Confirms that Jann sent the message correctly, but kvack is breaking
> the signature while vger is not. The DMARC policy on Jann's email is
> causing receivers to junk his email as spam. I expect I'm not the only
> one.
>
> I see that kvack is modifying the message in transit. Notably it
> changed the transfer encoding from
> Content-Transfer-Encoding: 8bit
> to
> Content-Transfer-Encoding: quoted-printable
>
> And mangled the body accordingly. Changing the
> Content-Transfer-Encoding definitely breaks the signature.
>
> This seems to be a fairly big problem - it is extra hard for people to
> contribute. Setting up a text based email flow is already hard, but
> having to also somehow obtain an email address that doesn't use DMARC
> is becoming an increasingly tough bar to clear.
>
> eg what will people even do if/when Google decides to enable DMARC on
> gmail.com as well?
>
> Is it possible that this list software can be reconfigured to match
> the vger lists that do seem to work OK?
>
> Is moving the list to vger an option?
>
> Thanks,
> Jason
>
next prev parent reply other threads:[~2020-10-16 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 13:54 Emails from kvack.org going into spam Jason Gunthorpe
2020-10-16 13:57 ` Matthew Wilcox [this message]
2020-10-16 14:13 ` Benjamin LaHaise
2020-10-16 15:10 ` Jason Gunthorpe
2020-10-16 15:17 ` Jann Horn
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=20201016135733.GF20115@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bcrl@kvack.org \
--cc=jannh@google.com \
--cc=jgg@ziepe.ca \
--cc=linux-mm@kvack.org \
/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).