From: David Timber <dxdt@dev•snart.me>
To: Christian Brauner <brauner@kernel•org>
Cc: linux-kernel@vger•kernel.org, linux-fsdevel@vger•kernel.org,
git@vger•kernel.org
Subject: Re: [RFC PATCH] Introduce filesystem type tracking
Date: Fri, 20 Feb 2026 14:43:58 +0900 [thread overview]
Message-ID: <a676fa73-bb73-485b-9ace-36a841be2b15@dev.snart.me> (raw)
In-Reply-To: <20260219-kavaliersdelikt-ansatz-9bdd1aa77326@brauner>
> All these mails have a broken header and set In-Reply-To: to <>:
>
> In-Reply-To: <>
>
> So all of these messages share a single bogus parent with the empty
> message ID <> and then Neomutt groups them together which makes it look
> like a really old thread got new replies...
Sorry for off-topic
I run my own Postfix+Dovecot stack and for an added layer of security, I
enabled client cert verification for all MUA ports(submission and imap)
so that bots don't even have a chance at establishing a TLS session.
The downside of this would be lack of client support. I'd love to use
but unfortunately git-send-email cannot be configured to present a
client cert to the server. I just learned that git-send-email is only a
single 2k-line perl script, so I could submit the patch if anyone's
interested. Just a few lines for the script to pass the PEM paths to the
openssl lib.
next parent reply other threads:[~2026-02-20 5:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1211196126-7442-1-git-send-email-tspink@gmail.com>
[not found] ` <7b9198260805200606u6ebc2681o8af7a8eebc1cb96@mail.gmail.com>
[not found] ` <20080520134306.GA28946@ZenIV.linux.org.uk>
[not found] ` <20080520135732.GA30349@infradead.org>
[not found] ` <20260218-goldrausch-hochmoderne-2b96018fbe5b@brauner>
[not found] ` <aZakzr_QAY6a-dlB@infradead.org>
[not found] ` <20260219-galaxie-sensibel-b6d27e60d524@brauner>
[not found] ` <20260219-kavaliersdelikt-ansatz-9bdd1aa77326@brauner>
2026-02-20 5:43 ` David Timber [this message]
2026-02-20 7:52 ` [PATCH] send-mail: add client certificate options David Timber
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=a676fa73-bb73-485b-9ace-36a841be2b15@dev.snart.me \
--to=dxdt@dev$(echo .)snart.me \
--cc=brauner@kernel$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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