From: Florian Weimer <fweimer@redhat.com>
To: overseers@sourceware.org
Subject: Re: Broken DMARC workaround for glibc mailing lists
Date: Mon, 01 May 2017 10:18:00 -0000 [thread overview]
Message-ID: <90c4c146-d703-c481-7065-839856769093@redhat.com> (raw)
In-Reply-To: <20170430053402.GA6286@ednor.casa.cgf.cx>
On 04/30/2017 07:34 AM, Christopher Faylor wrote:
> On Sat, Apr 29, 2017 at 10:32:42PM -0400, Christopher Faylor wrote:
>> On Fri, Apr 28, 2017 at 06:29:38PM +0200, Florian Weimer wrote:
>>> Hi,
>>>
>>> we have received a report that at least one of the glibc mailing lists
>>> lacks anti-DMARC header rewriting:
>>>
>>> https://sourceware.org/ml/libc-help/2017-04/msg00034.html
>>>
>>> I have seen the usual âviaâ From rewriting on other sourceware.org
>>> lists. I don't think we have much choice but to enable that for all the
>>> glibc lists, too.
>>
>> ? We don't arbitrarily turn on/off features like that for different
>> mailing lists. This feature is on for every mailing list.
>
> I found what should have been a minor misconfiguration in libc-help
> mailing list configuration. I don't know if it will help or not.
>
> I'll monitor the mailing list to see if this fixes it.
Thanks for investigating this.
Florian
next prev parent reply other threads:[~2017-05-01 10:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 16:29 Florian Weimer
2017-04-30 2:32 ` Christopher Faylor
2017-04-30 15:41 ` Christopher Faylor
[not found] ` <20170430053402.GA6286@ednor.casa.cgf.cx>
2017-05-01 10:18 ` Florian Weimer [this message]
2017-05-02 14:07 ` Christopher Faylor
2017-05-05 10:32 ` Florian Weimer
2017-05-08 5:34 ` Christopher Faylor
2017-05-08 6:15 ` Christopher Faylor
2017-05-08 6:44 ` Florian Weimer via overseers
2017-05-08 14:22 ` Christopher Faylor
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=90c4c146-d703-c481-7065-839856769093@redhat.com \
--to=fweimer@redhat.com \
--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).