From: Eric Blake <eblake@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Andrew Baumann <Andrew.Baumann@microsoft.com>
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 [thread overview]
Message-ID: <fb207ad9-0659-19c6-19cc-15fb8abd43c2@redhat.com> (raw)
In-Reply-To: <20170328210014-mutt-send-email-mst@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1585 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2017-03-28 18:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 17:35 [Qemu-devel] qemu-devel mailing list vs DMARC and microsoft.com's p=reject policy Peter Maydell
2017-03-28 17:53 ` Andrew Baumann
2017-03-28 17:58 ` Peter Maydell
2017-03-28 18:38 ` Eric Blake
2017-03-28 18:28 ` Michael S. Tsirkin
2017-03-28 18:41 ` Eric Blake [this message]
2017-03-29 6:46 ` Markus Armbruster
2017-03-29 10:44 ` Thomas Huth
2017-03-29 11:18 ` Markus Armbruster
2017-03-29 13:47 ` Michael S. Tsirkin
2017-03-29 10:34 ` Stefan Hajnoczi
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=fb207ad9-0659-19c6-19cc-15fb8abd43c2@redhat.com \
--to=eblake@redhat.com \
--cc=Andrew.Baumann@microsoft.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).