public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/29713] Please make libc-alpha mailing list compatible with “git am”
Date: Sun, 27 Aug 2023 21:08:28 +0000	[thread overview]
Message-ID: <bug-29713-14326-nDl3nmRWHm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29713-14326@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29713

--- Comment #42 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Mark Wielaard from comment #41)
> (In reply to Mark Wielaard from comment #40)
> > Note that c8s seems to have been updated to mailman 2.1.30
> > https://gitlab.com/redhat/centos-stream/rpms/mailman/-/commits/stream-
> > mailman-2.1-rhel-8.9.0
> > https://bugzilla.redhat.com/show_bug.cgi?id=2140631
> 
> Package available at
> https://kojihub.stream.centos.org/koji/buildinfo?buildID=35377

I went through the diff and it contains the patch we use in
mailman-2.1.29-12.sourceware.el8.3.x86_64 It also contains a simpler way to
prevent dropping CCs:

+# The process which avoids sending a list copy of a message to a member who
+# is also directly addressed in To: or Cc: can drop the address from Cc: to
+# avoid growing a long Cc: list in long threads.  This can be undesirable as
+# it can break DKIM signatures and possibly cause confusion.  To avoid changes
+# to Cc: headers, set the list's drop_cc to No.
+DEFAULT_DROP_CC = Yes

We should set that to No.

There is also a new dmarc_moderation_addresses:

+            ('dmarc_moderation_addresses', mm_cfg.EmailListEx, (10, WIDTH), 1,
+             _("""List of addresses (or regexps) whose posts should always
apply
+             <a href="?VARHELP=privacy/sender/dmarc_moderation_action"
+             >dmarc_moderation_action</a> 
+             regardless of any domain specific DMARC Policy."""),
+
+             _("""Postings from any of these addresses will automatically
+             apply any DMARC action mitigation.  This can be utilized to
+             automatically wrap or munge postings from known addresses or
+             domains that might have policies rejecting external mail From:
+             themselves.

We could use this for addresses that add any list headers to their own DKIM
signatures.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2023-08-27 21:08 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21 11:35 [Bug Infrastructure/29713] New: " fweimer at redhat dot com
2022-10-21 13:05 ` [Bug Infrastructure/29713] " fche at redhat dot com
2022-10-21 13:28 ` mark at klomp dot org
2022-10-21 13:30 ` fche at redhat dot com
2022-10-21 14:13 ` fweimer at redhat dot com
2022-10-21 14:52 ` fche at redhat dot com
2022-10-21 14:56 ` iank at fsf dot org
2022-10-21 15:05 ` iank at fsf dot org
2022-10-21 15:19 ` cgf at sourceware dot org
2022-10-21 15:26 ` iank at fsf dot org
2022-10-21 15:47 ` cgf at sourceware dot org
2022-10-25  7:34 ` fweimer at redhat dot com
2022-10-26 14:55 ` fche at redhat dot com
2022-10-30 22:08 ` mark at klomp dot org
2022-10-31  4:37 ` iank at fsf dot org
2022-10-31  4:39 ` iank at fsf dot org
2022-10-31 10:45 ` fche at redhat dot com
2022-10-31 21:47 ` mark at klomp dot org
2022-10-31 22:03 ` mark at klomp dot org
2022-10-31 22:44 ` joseph at codesourcery dot com
2022-11-01 10:04 ` mark at klomp dot org
2022-11-04 14:48 ` mark at klomp dot org
2022-11-04 19:58 ` iank at fsf dot org
2022-11-05  0:17 ` mark at klomp dot org
2022-11-05  0:32 ` fche at redhat dot com
2022-11-05 16:26 ` iank at fsf dot org
2022-11-05 19:22 ` mark at klomp dot org
2022-11-06 16:23 ` fche at redhat dot com
2022-11-07  9:07 ` fweimer at redhat dot com
2022-11-07 11:24 ` mark at klomp dot org
2022-11-07 12:05 ` fweimer at redhat dot com
2022-12-31 15:58 ` mark at klomp dot org
2023-01-01 13:59 ` fweimer at redhat dot com
2023-01-02 15:29 ` fche at redhat dot com
2023-01-02 16:15 ` mark at klomp dot org
2023-01-02 16:36 ` fche at redhat dot com
2023-01-02 17:06 ` fweimer at redhat dot com
2023-01-05 22:05 ` mark at klomp dot org
2023-01-05 22:48 ` iank at fsf dot org
2023-01-09  9:07 ` fweimer at redhat dot com
2023-08-11 18:41 ` mark at klomp dot org
2023-08-25 10:43 ` mark at klomp dot org
2023-08-27 21:08 ` mark at klomp dot org [this message]
2023-08-27 21:28 ` mark at klomp dot org
2023-09-01 12:23 ` mark at klomp dot org
2023-09-06 18:41 ` mark at klomp dot org
2023-10-11 11:40 ` mark at klomp dot org
2023-10-11 11:41 ` fweimer at redhat dot com

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=bug-29713-14326-nDl3nmRWHm@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.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).