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: Mon, 02 Jan 2023 16:15:46 +0000 [thread overview]
Message-ID: <bug-29713-14326-ZrgI29631b@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 #34 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Frank Ch. Eigler from comment #33)
> (In reply to Mark Wielaard from comment #31)
> > Frank your domain, elastic.org, seems to be configured to sign (empty) list
> > headers
> > (Sender:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-
> > Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-
> > Owner:List-Archive) on all your messages. How would you like us to handle
> > that?
>
> This must be the default for the exim MTA in use here. It goes to show how
> fragile this sort of forwarding is - not sure you or I can do anything about
> it.
This is somewhat disappointing since this seems against the spec. These headers
shouldn't be included by default if they aren't set on the original outgoing
message. Is there a page we can point people to that explains why these
defaults are wrong and how to properly setup the exim MTA to do dkim signing?
If I understand Ian's comment #6 these misconfigured dkim defaults are not
common and we could just ignore them. People will just get periodically
unsubscribed till they fix their dkim setup to not include empty Sender or
List-* headers.
But it would be nice to apply From rewriting to help such misconfigurations.
There is a recipy for Exim to do that in comment #6. I don't know if that can
easily translate to postfix.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-01-02 16:15 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 [this message]
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
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-ZrgI29631b@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).