Updating mailman settings to avoid From rewriting

Updating mailman settings to avoid From rewriting

[Mark Wielaard]

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

Re: Updating mailman settings to avoid From rewriting

[Mark Wielaard]

Hi,

On Tue, Oct 03, 2023 at 12:12:40AM +0200, Mark Wielaard wrote:
> 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.

The above settings are now active for the newlib, binutils,
gdb-patches, elfutils-devel and libabigail mailinglists.

> 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?

We still need admins/moderators for these two lists.

Cheers,

Mark

> [*] https://sourceware.org/bugzilla/show_bug.cgi?id=29713

Re: Updating mailman settings to avoid From rewriting

[Thiago Jung Bauermann]

Mark Wielaard <mark@klomp.org> writes:

> Hi,
>
> On Tue, Oct 03, 2023 at 12:12:40AM +0200, Mark Wielaard wrote:
>> 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.
>
> The above settings are now active for the newlib, binutils,
> gdb-patches, elfutils-devel and libabigail mailinglists.

Thank you!

>> 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?
>
> We still need admins/moderators for these two lists.

I'm not a maintainer or anything in GDB nor GNU, but if that isn't a
prerequisite and if other people are OK with it I'd be happy to be list
admin for gdb-patches.

-- 
Thiago

Re: Updating mailman settings to avoid From rewriting

[Benson Muite]

On 10/7/23 06:55, Thiago Jung Bauermann wrote:
> 
> Mark Wielaard <mark@klomp.org> writes:
> 
>> Hi,
>>
>> On Tue, Oct 03, 2023 at 12:12:40AM +0200, Mark Wielaard wrote:
>>> 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.
>>
>> The above settings are now active for the newlib, binutils,
>> gdb-patches, elfutils-devel and libabigail mailinglists.
> 
> Thank you!
> 
>>> 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?
>>
>> We still need admins/moderators for these two lists.
> 
> I'm not a maintainer or anything in GDB nor GNU, but if that isn't a
> prerequisite and if other people are OK with it I'd be happy to be list
> admin for gdb-patches.
> 
Would be happy to help with newlib

Re: Updating mailman settings to avoid From rewriting

[Mark Wielaard]

Hi,

On Sat, Oct 07, 2023 at 03:20:55PM +0300, Benson Muite wrote:
> On 10/7/23 06:55, Thiago Jung Bauermann wrote:
> > Mark Wielaard <mark@klomp.org> writes:
> >>> 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?
> >>
> >> We still need admins/moderators for these two lists.
> > 
> > I'm not a maintainer or anything in GDB nor GNU, but if that isn't a
> > prerequisite and if other people are OK with it I'd be happy to be list
> > admin for gdb-patches.
> > 
> Would be happy to help with newlib

That would be nice. Note that it can be a shared responsibility. And
it isn't really much work. Two or three times a month there is spam
(most is filtered out before it hits the list) or a message that is
too big gets caught in moderation. And you can block people from
posting to the list in an emergency (or when gdb or newlib has a code
of conduct committee, when they decide to give someone a
timeout). Although that last one luckily only happens once every
couple of years.

If none of the gdb or newlib maintainers objects I can add you and
sent you the list password. Please sent me your PGP key if you have
one so I can sent you the authentication details in private.

Cheers,

Mark