From: Mark Wielaard <mark@klomp.org>
To: newlib@sourceware.org, binutils@sourceware.org,
gdb-patches@sourceware.org, elfutils-devel@sourceware.org,
libabigail@sourceware.org
Subject: Updating mailman settings to avoid From rewriting
Date: Tue, 3 Oct 2023 00:12:40 +0200 [thread overview]
Message-ID: <20231002221240.GA29354@gnu.wildebeest.org> (raw)
Hi,
Currently the newlib, binutils, gdb-patches, elfutils-devel and
libabigail mailinglists rewrite the From header when a message is from
a (strict) dmarc domain. This is to avoid breaking the dmarc policy
and get bounces from such messages.
However this breaks applying patches posted to the list with git am
since the Author of the patch now looks like it has the mailing-list
email address. This also breaks some tools that use
patchwork.sourceware.org to run CI buildbot jobs (git pw however seems
to get it right, as does using b4 against inbox.sourceware.org).
glibc and gcc have been experimenting with new mailman settings to not
require From rewriting. Those settings make sure no (essential) Header
are changes, and no changes to the body of the message are made that
could invalidate any dkim signatures. These are the same settings used
by the FSF tech-team for lists.gnu.org. [*]
At the Cauldron it seemed this was working well and it was pointed out
that some CI bots can get the author of patches wrong for these lists
that use patchwork. Also people seemed to appreciate the change so
they could more easily apply all patches as is from the mailinglist.
So I am proposing we apply the following settings for these lists:
- subject_prefix (general): (empty)
- from_is_list (general): No
- anonymous_list (general): No
- first_strip_reply_to (general): No
- reply_goes_to_list (general): Poster
- reply_to_address (general): (empty)
- include_sender_header (general): No
- drop_cc (general): No
- msg_header (nondigest): (empty)
- msg_footer (nondigest): (empty)
- scrub_nondigest (nondigest): No
- dmarc_moderation_action (privacy): Accept
- filter_content (contentfilter): No
Please let me know if there are any objections or concerns.
Also the newlib and gdb-patches mailinglists don't have an admin at
the moment. Could someone volunteer to act as list admin for these?
Cheers,
Mark
[*] https://sourceware.org/bugzilla/show_bug.cgi?id=29713
next reply other threads:[~2023-10-02 22:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 22:12 Mark Wielaard [this message]
2023-10-07 0:14 ` Mark Wielaard
2023-10-07 3:55 ` Thiago Jung Bauermann
2023-10-07 12:20 ` Benson Muite
2023-10-08 21:12 ` Mark Wielaard
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=20231002221240.GA29354@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=binutils@sourceware.org \
--cc=elfutils-devel@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=libabigail@sourceware.org \
--cc=newlib@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).