From: "Frank Ch. Eigler" <fche@elastic.org>
To: gcc@gcc.gnu.org
Cc: overseers@sourceware.org
Subject: Mailing list reconfiguration: VERP Sender: header affected
Date: Wed, 2 Jun 2021 10:52:57 -0400 [thread overview]
Message-ID: <YLebSQIdJlj0TIls@elastic.org> (raw)
Hi -
I made an experimental configuration change on sourceware/gcc.gnu.org
yesterday that had unforeseen effects on some mailing list
subscribers. We turned on VERP (variable envelope return paths) on
outgoing mail from mailman, in order to assist tracking mail delivery
problems. This changes the Sender: field that allows precise handling
of bounces, but interferes with filtering on that field.
If you use Sender:-based filtering for sorting your incoming email
stream, I suggest switching to observing List-Id: instead, or else
using a regexp/substring style of Sender: matching.
We're not sure we're keeping the new configuration yet. It's
performing well. With either of the two changes, you would be
immunized against change even if we return to the previous
configuration sometime. I'm sorry about the inconvenience!
- FChE
next reply other threads:[~2021-06-02 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 14:52 Frank Ch. Eigler [this message]
2021-06-03 11:29 ` Martin Liška
2021-06-12 6:00 ` Gerald Pfeifer
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=YLebSQIdJlj0TIls@elastic.org \
--to=fche@elastic.org \
--cc=gcc@gcc.gnu.org \
--cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).