public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: Mark Wielaard <mark@klomp.org>
Cc: <maxim.kuvyrkov@linaro.org>,
	Iain Sandoe <idsandoe@googlemail.com>, <gcc-patches@gcc.gnu.org>,
	Jeff Law <jeffreyalaw@gmail.com>
Subject: Re: gcc-patches From rewriting mailman settings (Was: [Linaro-TCWG-CI] gcc patch #75674: FAIL: 68 regressions)
Date: Thu, 14 Sep 2023 09:00:39 +0200	[thread overview]
Message-ID: <87a5tp6xyg.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <8C44A2FD-0DF8-4395-9137-D95652A18573@googlemail.com>

Hi Mark!

On 2023-09-13T17:02:05+0100, Iain Sandoe <idsandoe@googlemail.com> wrote:
>> On 12 Sep 2023, at 16:00, Mark Wielaard <mark@klomp.org> wrote:
>> Adding Jeff to CC who is the official gcc-patches mailinglist admin.
>>
>> On Tue, 2023-09-12 at 11:08 +0400, Maxim Kuvyrkov wrote:
>>> Normally, notifications from Linaro TCWG precommit CI are sent only to
>>> patch author and patch submitter.  In this case the sender was rewritten
>>> to "Benjamin Priour via Gcc-patches <gcc-patches@gcc.gnu.org>",
>>> which was detected by Patchwork [1] as patch submitter.
>>
>> BTW. Really looking forward to your talk at Cauldron about this!

(Yes!)

>>> Is "From:" re-write on gcc-patches@ mailing list a side-effect of [2]?
>>> I see that some, but not all messages to gcc-patches@ have their
>>> "From:" re-written.
>>>
>>> Also, do you know if re-write of "From:" on gcc-patches@ is expected?
>>
>> Yes, it is expected for emails that come from domains with a dmarc
>> policy. That is because the current settings of the gcc-patches
>> mailinglist might slightly alter the message or headers in a way that
>> invalidates the DKIM signature. Without From rewriting those messages
>> would be bounced by recipients that check the dmarc policy/dkim
>> signature.
>>
>> As you noticed the glibc hackers have recently worked together with the
>> sourceware overseers to upgrade mailman and alter the postfix and the
>> libc-alpha mailinglist setting so it doesn't require From rewriting
>> anymore (the message and header aren't altered anymore to invalidate
>> the DKIM signatures).
>>
>> We (Jeff or anyone else with mailman admin privs) could use the same
>> settings for gcc-patches. The settings that need to be set are in that
>> bug:
>>
>> - 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
>>
>> The only visible change (apart from no more From rewriting) is that
>> HTML multi-parts aren't scrubbed anymore (that would be a message
>> altering issue). The html part is still scrubbed from the
>> inbox.sourceware.org archive, so b4 works just fine. But I don't know
>> what patchwork.sourceware.org does with HTML attachements. Of course
>> people really shouldn't sent HTML attachments to gcc-patches, so maybe
>> this is no real problem.
>>
>> Let me know if you want Jeff (or me or one of the other overseers) make
>> the above changes to the gcc-patches mailman settings.
>
> yes, please!

Yes, please!  For all mailing lists, globally.


Grüße
 Thomas
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955

  reply	other threads:[~2023-09-14  7:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11 22:58 [Linaro-TCWG-CI] gcc patch #75674: FAIL: 68 regressions ci_notify
2023-09-12  7:08 ` Maxim Kuvyrkov
2023-09-12 15:00   ` gcc-patches From rewriting mailman settings (Was: [Linaro-TCWG-CI] gcc patch #75674: FAIL: 68 regressions) Mark Wielaard
2023-09-13 16:02     ` Iain Sandoe
2023-09-14  7:00       ` Thomas Schwinge [this message]
2023-09-14 18:18         ` Mark Wielaard
2023-09-14  9:07     ` Richard Biener
2023-09-14 18:44       ` Mark Wielaard
2023-09-17 20:04     ` Mark Wielaard
2023-09-19  8:36       ` Mark Wielaard
2023-10-03 22:17         ` Gerald Pfeifer
2023-10-04  7:38           ` Mark Wielaard
2023-09-30 20:44       ` gcc-patches From rewriting mailman settings 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=87a5tp6xyg.fsf@euler.schwinge.homeip.net \
    --to=thomas@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=idsandoe@googlemail.com \
    --cc=jeffreyalaw@gmail.com \
    --cc=mark@klomp.org \
    --cc=maxim.kuvyrkov@linaro.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).