From: "Serge E. Hallyn" <serge@hallyn.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Serge E. Hallyn" <serge@hallyn.com>,
linux-security-module@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ryan Foster <foster.ryan.r@gmail.com>,
Christian Brauner <brauner@kernel.org>
Subject: Re: [GIT PULL] capabilities update for v6.19
Date: Thu, 4 Dec 2025 22:43:01 -0600 [thread overview]
Message-ID: <aTJi1TunpnTguOtm@mail.hallyn.com> (raw)
In-Reply-To: <CAADWXX_rO42NznU6c+rjqzaUuTLMp_DXSf_mn8rVDCe+1AMUTQ@mail.gmail.com>
On Thu, Dec 04, 2025 at 05:20:18PM -0800, Linus Torvalds wrote:
> On Thu, Dec 4, 2025 at 4:27 PM Serge E. Hallyn <serge@hallyn.com> wrote:
> >
> > This contains the capabilities changes for 6.19.
>
> This email was in my spam folder.
>
> The reason appears to be due to it being marked as "DMARC: FAIL".
>
> I think it's simply because your mail domain doesn't have a dmarc
> policy at all, and gmail has been getting more strict about having
> both dkim and dmarc set up.
>
> Anyway, I obviously found the email, but I thought I'd mention it,
> because while I check my spam folder fairly religiously, it's still
> mostly a pretty quick scan for possible emails. There's no guarantee I
> always notice...
>
> Linus
Thanks! I set up SPF years ago, but guess I will have to figure out
DKIM.
The odd thing is, when I send emails to my own gmail account I don't see
any complaints about DKIM or DMARC, only:
ARC-Authentication-Results: i=1; mx.google.com;
spf=pass (google.com: domain of serge@hallyn.com designates 178.63.66.53 as permitted sender) smtp.mailfrom=serge@hallyn.com
But I'll fix it.
thanks,
-serge
next prev parent reply other threads:[~2025-12-05 4:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 0:27 [GIT PULL] capabilities update for v6.19 Serge E. Hallyn
2025-12-05 1:20 ` Linus Torvalds
2025-12-05 4:43 ` Serge E. Hallyn [this message]
2025-12-05 16:57 ` Linus Torvalds
2025-12-05 4:15 ` 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=aTJi1TunpnTguOtm@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=brauner@kernel.org \
--cc=foster.ryan.r@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=torvalds@linux-foundation.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).