From: "Mickaël Salaün" <mic@digikod.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Brauner <brauner@kernel.org>, Tom Rix <trix@redhat.com>,
lkml <linux-kernel@vger.kernel.org>,
LSM List <linux-security-module@vger.kernel.org>
Subject: Re: [GIT PULL] Landlock fixes for v5.18
Date: Wed, 23 Mar 2022 10:45:22 +0100 [thread overview]
Message-ID: <2c6c684b-1380-d65e-78d2-b8ab7239ea4a@digikod.net> (raw)
In-Reply-To: <CAADWXX_06uyx5KLE-6pv6pqQJ5qH4EqYiYK7rGK3zMyEZjW4dw@mail.gmail.com>
On 21/03/2022 18:37, Linus Torvalds wrote:
> On Mon, Mar 21, 2022 at 4:58 AM Mickaël Salaün <mic@digikod.net> wrote:
>>
>> Please pull these Landlock updates for v5.18-rc1 .
>
> Mickaël, both your pull requests (this and the 'trusted_for(2)' one)
> were marked as spam for me.
>
> The reason seems to be that you're using a SMTP host that doesn't
> actually do modern anti-spam measures (no DKIM), and while it does do
> SPF, gmail really dislikes it.
>
> There doesn't seem anything in particular standing out in the email
> itself, so I suspect your hosting provider (seems to be infomaniak.ch)
> ends up either being in a block of IP addresses that is also being
> used for spam, or it's just allowing a lot of spam itself.
>
> Some people think that gmail is being way too restrictive about these
> kinds of things, but since I hate spam with a passion, I end up siding
> with rather strict spam measures.. Honestly, if an email provider
> doesn't do DKIM in this day and age, it's not a very good email
> provider imho.
Thanks, it should be good now. Is there anything else you want me to do?
Regards,
Mickaël
next prev parent reply other threads:[~2022-03-23 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 11:59 Mickaël Salaün
2022-03-21 17:37 ` Linus Torvalds
2022-03-23 9:45 ` Mickaël Salaün [this message]
2022-03-27 22:22 ` pr-tracker-bot
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=2c6c684b-1380-d65e-78d2-b8ab7239ea4a@digikod.net \
--to=mic@digikod.net \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=trix@redhat.com \
/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
all inboxes | Powered by JetHome®