[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] qemu-devel mailing list vs DMARC and microsoft.com's p=
From: |
Eric Blake |
Subject: |
Re: [Qemu-devel] qemu-devel mailing list vs DMARC and microsoft.com's p=reject policy |
Date: |
Tue, 28 Mar 2017 13:41:36 -0500 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
On 03/28/2017 01:28 PM, Michael S. Tsirkin wrote:
>> (2) I could reconfigure mailman to try to not rewrite anything that
>> we think is likely to be signed (in particular not the body or the
>> subject)
>> * this means dropping the [qemu-devel] tag from the subject, which I'm
>> a bit reluctant to do (it seems likely at least some readers are
>> filtering on it, and personally I quite like it)
>> * if anybody DKIM-signs the Sender: header we're stuck anyway
>
> For the record I'd strongly prefer this option - I tag all list mail
> and so "qemu-devel" appears twice: in subject and as a tag.
> Also, if mail is copied to another list, qemu-devel will
> still appear as gmail de-duplicates email by msg id.
> I can remove tags I don't care about but can't remove
> subject prefixes.
I'm ambivalent - I like the prefixes, but don't mind if they are not
present (it's easy enough to filter on List-Sender: when the prefix is
not reliable). It's especially nice that the prefix lets me tell the
difference between mail sent to qemu-devel and qemu-block while still
dumping both lists into the same folder.
> Is there a way not to munge the name? It's currently rewritten to
> add "via qemu-devel" which confuses the clients which think
> it's part of the name, and can't be easily stripped away.
Not that I know of, but at least the munging only occurs for senders
with restrictive DMARC and not for ALL senders.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature