From: Willy Tarreau <w@1wt.eu>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: users@linux.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: PSA: final vger mailing list migration: Thu, Dec 14, 11AM PST (1900 UTC)
Date: Thu, 14 Dec 2023 07:11:00 +0100 [thread overview]
Message-ID: <20231214061100.GC18223@1wt.eu> (raw)
In-Reply-To: <20231213-gregarious-vole-of-luxury-42f22c@meerkat>
On Wed, Dec 13, 2023 at 10:19:19AM -0500, Konstantin Ryabitsev wrote:
> On Wed, Dec 13, 2023 at 06:20:55AM +0100, Willy Tarreau wrote:
> > On Tue, Dec 12, 2023 at 04:36:28PM -0500, Konstantin Ryabitsev wrote:
> > (...)
> > > # Questions, comments?
> > >
> > > If you have any questions or concerns, please reply to this message.
> >
> > Thanks for this update. I'm having a no-delay rule on my SMTP server
> > for a few well-known friendly senders whom I don't want to inflict
> > the SMTP banner delay. Vger is on it the list. Which host will send
> > messages now ? subspace.kernel.org or any other ?
>
> You can check the output of:
>
> dig -t txt _listspf.kernel.org
>
> On our end, we use postwhite for similar purposes, which allows us to just add
> domains and have it automatically generate the list of exceptions via
> published spf records:
>
> https://github.com/stevejenkins/postwhite
Looks like what I needed, perfect, thanks Konstantin!
Willy
next prev parent reply other threads:[~2023-12-14 6:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 21:36 PSA: final vger mailing list migration: Thu, Dec 14, 11AM PST (1900 UTC) Konstantin Ryabitsev
2023-12-13 5:20 ` Willy Tarreau
2023-12-13 15:19 ` Konstantin Ryabitsev
2023-12-14 6:11 ` Willy Tarreau [this message]
2023-12-14 22:08 ` Konstantin Ryabitsev
2023-12-14 23:05 ` Konstantin Ryabitsev
2023-12-15 16:32 ` Greg KH
2023-12-15 18:03 ` Konstantin Ryabitsev
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=20231214061100.GC18223@1wt.eu \
--to=w@1wt.eu \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=users@linux.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.