linux-kernel - Re: [GIT PULL] regulator updates for v4.14

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20170904171919.73kxhfmmwl2l52kd@sirena.org.uk>
Date:   Mon, 4 Sep 2017 18:19:19 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     lkml <linux-kernel@...r.kernel.org>,
        Liam Girdwood <lgirdwood@...il.com>
Subject: Re: [GIT PULL] regulator updates for v4.14

On Mon, Sep 04, 2017 at 10:04:02AM -0700, Linus Torvalds wrote:

>  google either hates you personally, or your sirena.org.uk domain, or
> something else about how you write your pull emails.

> Both your regulator and your SPI pull request were marked as spam.

> It's not obvious why that would be. They both have passing SPF and
> DKIM, and neither of them looks all that different from any other pull
> request I get.

> So it's probably personal.

> What the hell did you do to piss off gmail?

I've got no real idea, I'm trying a little experiment on this one to see
if it makes it happier but at this point I'm fairly sure either they're
just being overly aggressive with personal mail hosting or they don't
like the fact that I'm sending with my kernel.org address and the
envelope sender ends up as being that of my mail infrastructure.

They *didn't* do their frequent thing of deferring the mail at SMTP time
so it's probably not the machine the mails go through on their way out,
looks like it's some form of content based filtering.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)