From: Eric Blake <eblake@redhat.com>
To: Andrew Baumann <Andrew.Baumann@microsoft.com>,
Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] qemu-devel mailing list vs DMARC and microsoft.com's p=reject policy
Date: Tue, 28 Mar 2017 13:38:04 -0500 [thread overview]
Message-ID: <c538920e-f270-4ba1-df38-2b0b43fafb8b@redhat.com> (raw)
In-Reply-To: <DM2PR21MB006077BF2F5F3DDA94E83ABD9E320@DM2PR21MB0060.namprd21.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]
On 03/28/2017 12:53 PM, Andrew Baumann via Qemu-devel wrote:
>> (3) I could set dmarc_moderation_action to Munge From, which means that
>> those senders who have a p=reject policy will get their mails
>> rewritten to have a From="Whoever (via the list) <qemu-devel@...>"
>> and their actual email in the Reply-to:
>> * if anybody's mail client doesn't honour Reply-to: then what they
>> think is a personal reply will go to the list by accident
That's my favorite of the options (and these days, reply-to works a lot
better than it used to even 10 year ago)...
>>
>> For the moment I have picked option (3), but I'm open to argument
>> that we should pick something else.
>
> Option 3 is a fine one from my perspective (I could also live with 2). This email will hopefully help you test whether it's effective.
and it appears to have worked; Andrew's mail purported to be from the
list, but had a correct 'Reply-to', and my mailer (thunderbird) appears
to do the right thing for reply-to-all.
--
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:38 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 [this message]
2017-03-28 18:28 ` Michael S. Tsirkin
2017-03-28 18:41 ` Eric Blake
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=c538920e-f270-4ba1-df38-2b0b43fafb8b@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).