From: Christopher Faylor <cgf-use-the-mailinglist-please@gcc.gnu.org>
To: Michael Matz <matz@suse.de>
Cc: "Frank Ch. Eigler via Gcc" <gcc@gcc.gnu.org>,
Overseers mailing list <overseers@sourceware.org>,
Segher Boessenkool <segher@kernel.crashing.org>,
Mark Wielaard <mark@klomp.org>,
Alexander Monakov <amonakov@ispras.ru>,
Jonathan Wakely <jwakely.gcc@gmail.com>,
Florian Weimer <fw@deneb.enyo.de>,
"Maciej W. Rozycki" <macro@wdc.com>
Subject: Re: Not usable email content encoding
Date: Tue, 14 Apr 2020 17:06:00 -0400 [thread overview]
Message-ID: <20200414210600.GA5765@cgf.cx> (raw)
In-Reply-To: <alpine.LSU.2.21.2004132229540.11688@wotan.suse.de>
On Mon, Apr 13, 2020 at 10:53:06PM +0000, Michael Matz wrote:
>On Mon, 13 Apr 2020, Christopher Faylor wrote:
>>On Wed, Apr 08, 2020 at 04:15:27PM -0500, Segher Boessenkool wrote:
>>>On Wed, Apr 08, 2020 at 01:50:51PM +0000, Michael Matz wrote:
>>>>On Wed, 8 Apr 2020, Mark Wielaard wrote:
>>>>>Earlier versions of Mainman2 had some issues which might accidentally
>>>>>change some headers. But the latest fixes make this possible. It is
>>>>>how the FSF handles DMARC for various GNU mailinglists (by NOT
>>>>>modifying the headers and body and passing through the DKIM
>>>>>signatures):
>>>>>https://lists.gnu.org/archive/html/savannah-hackers-public/2019-06/msg00018.html
>>>>
>>>>Oh, that would be nice to have at sourceware.org. Please? :-)
>>>
>>>Yes, please please please, can we have this?
>>
>>In case it isn't obvious, we are already running the latest available
>>version of mailman 2.
>
>I think that means that dmarc_moderation_action: "Munge From" can
>simply be switched off then (at least I don't see which other headers
>e.g. gcc@ is rewriting that would cause DMARC to scream; and if there
>are any, then it would be better to disable those as well. Same with
>any potential body rewriting that might still happen).
It can't be switched off if we strip html attachments.
>I would offer help testing that this doesn't cause delivery issues, e.g.
>on some test email list, but it seems none of my domains is DMARC-infected
>:-/
Nevertheless, offers of help are appreciated (and rare). :-)
cgf
next prev parent reply other threads:[~2020-04-14 21:06 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 13:45 Martin Liška
2020-03-16 13:47 ` Richard Earnshaw
2020-03-16 13:52 ` Martin Liška
2020-03-16 13:51 ` Florian Weimer
2020-03-16 13:52 ` Frank Ch. Eigler
2020-03-16 13:54 ` Alexander Monakov
2020-03-16 14:11 ` Martin Liška
2020-03-16 14:18 ` Jonathan Wakely
2020-03-17 19:46 ` Segher Boessenkool
2020-03-17 19:51 ` Frank Ch. Eigler
2020-03-17 21:45 ` Segher Boessenkool
2020-03-18 10:38 ` Florian Weimer
2020-03-18 11:01 ` Frank Ch. Eigler
2020-03-18 11:39 ` Florian Weimer
2020-03-18 14:19 ` Michael Matz
2020-03-18 14:22 ` Frank Ch. Eigler
2020-03-18 15:15 ` Bernd Schmidt
2020-03-18 16:22 ` Frank Ch. Eigler
2020-03-18 16:42 ` Michael Matz
2020-03-18 17:36 ` Christopher Faylor
2020-03-18 21:52 ` Jim Wilson
2020-03-18 22:29 ` Jonathan Wakely
2020-03-18 22:34 ` Jonathan Wakely
2020-03-18 22:44 ` Frank Ch. Eigler
2020-03-19 3:30 ` Christopher Faylor
2020-03-19 3:32 ` Christopher Faylor
2020-03-18 22:45 ` Joseph Myers
2020-03-18 23:02 ` Jonathan Wakely
2020-03-19 13:05 ` Tom Tromey
2020-03-19 13:26 ` Florian Weimer
2020-03-19 13:41 ` Richard Biener
2020-03-19 13:58 ` Florian Weimer
2020-03-19 18:17 ` Segher Boessenkool
2020-04-23 0:54 ` Tamar Christina
2020-04-23 5:47 ` Florian Weimer
2020-04-23 7:34 ` Richard Biener
[not found] ` <CAH6eHdShSXwc4K7ar9HWgHu12tDQe-s2LifdvmVp8VytwYV-ew@mail.gmail.com>
2020-04-23 8:39 ` Jakub Jelinek
2020-04-23 15:32 ` Jeff Law
2020-04-23 9:55 ` Tamar Christina
2020-04-23 11:46 ` Segher Boessenkool
[not found] ` <CAH6eHdTHsZWO9vuycKm22dDbSGSfzcrKbzEpb6vNdb-zXCiKjQ@mail.gmail.com>
2020-04-23 12:30 ` Segher Boessenkool
2020-04-23 15:33 ` Jeff Law
2020-04-23 16:57 ` Frank Ch. Eigler
2020-04-23 20:32 ` Segher Boessenkool
2020-04-23 20:27 ` Segher Boessenkool
2020-04-23 21:14 ` Tom Tromey
2020-04-24 15:48 ` Thomas Koenig
2020-04-24 17:09 ` Segher Boessenkool
2020-05-01 15:51 ` Jeff Law
2020-05-02 12:50 ` Segher Boessenkool
2020-03-19 18:08 ` Segher Boessenkool
2020-03-18 22:33 ` Frank Ch. Eigler
2020-03-19 0:17 ` Segher Boessenkool
2020-03-19 0:32 ` Segher Boessenkool
2020-04-06 20:58 ` Maciej W. Rozycki
2020-04-06 21:09 ` Frank Ch. Eigler
2020-04-06 21:59 ` Maciej W. Rozycki
[not found] ` <CAH6eHdTqJEM90d9+nNWrAa_zZrQQha79oMbnbVsRt_2Zd90PdA@mail.gmail.com>
2020-04-07 9:53 ` Florian Weimer
2020-04-08 12:38 ` Mark Wielaard
2020-04-08 13:50 ` Michael Matz
2020-04-08 21:15 ` Segher Boessenkool
2020-04-13 19:47 ` Christopher Faylor
2020-04-13 22:53 ` Michael Matz
2020-04-14 21:06 ` Christopher Faylor [this message]
2020-04-14 21:38 ` Maciej W. Rozycki
2020-04-15 2:59 ` Christopher Faylor
2020-04-07 15:13 ` Michael Matz
2020-04-07 15:22 ` Frank Ch. Eigler
2020-04-07 15:56 ` Michael Matz
2020-04-07 16:09 ` Christopher Faylor
2020-04-07 17:08 ` Maciej W. Rozycki
2020-04-09 18:19 ` Florian Weimer
2020-04-07 16:08 ` Christopher Faylor
2020-04-07 16:58 ` Maciej W. Rozycki
2020-04-06 23:15 ` Segher Boessenkool
2020-03-21 22:29 ` Maciej W. Rozycki
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=20200414210600.GA5765@cgf.cx \
--to=cgf-use-the-mailinglist-please@gcc.gnu.org \
--cc=amonakov@ispras.ru \
--cc=fw@deneb.enyo.de \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=macro@wdc.com \
--cc=mark@klomp.org \
--cc=matz@suse.de \
--cc=overseers@sourceware.org \
--cc=segher@kernel.crashing.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).