From: "Adam Sjøgren via info-gnus-english" <info-gnus-english@gnu.org>
To: info-gnus-english@gnu.org
Subject: Re: From and Reply-To mangling?!
Date: Sat, 28 Dec 2019 15:35:57 +0100 [thread overview]
Message-ID: <878smwo6uq.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87v9q1hwaa.fsf@gnu.org> (Amin Bandali's message of "Sat, 28 Dec 2019 00:08:29 -0500")
Amin writes:
> Adam Sjøgren via info-gnus-english <info-gnus-english@gnu.org> writes:
>
>> So this mailing list now changes the From: and adds Reply-To: ?!?
>>
>> Only for some users/posts. Hm.
>
> Could be due to changes made to a number of mailman settings (including
> from munging) for many GNU lists by the FSF sysadmins in late October?
> For instance: https://lists.gnu.org/r/bug-gnuzilla/2019-10/msg00006.html
Ah, it explains why only some messages are mangled: "if a strict DMARC
sender sends to the list, we alter the headers of that message". I've
got DMARC configured for my domain (koldfront.dk).
I think it would be great if the mailing list software stopped adding a
footer, so there is no need to mangle the headers.
I.e. what the linked email calls "the unmodified message fix".
Best regards,
Adam
--
"The Commodore 64. Under $600. You can't buy a Adam Sjøgren
better computer at twice the price." asjo@koldfront.dk
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2019-12-28 14:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-28 1:23 Adam Sjøgren via info-gnus-english
2019-12-28 5:08 ` Amin Bandali
2019-12-28 12:44 ` Lars Ingebrigtsen
2019-12-28 14:39 ` Michael Albinus
2019-12-28 14:54 ` Adam Sjøgren via info-gnus-english
2019-12-28 14:35 ` Adam Sjøgren via info-gnus-english [this message]
2019-12-29 2:38 ` 황병희
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=878smwo6uq.fsf@tullinup.koldfront.dk \
--to=info-gnus-english@gnu.org \
--cc=asjo@koldfront.dk \
/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 NNTP newsgroup(s).