Re: [Qemu-devel] [PATCH] scripts: report on author emails that are mangled by the mailing list

["Daniel P. Berrangé" <berrange@redhat.com>]

On Thu, Aug 23, 2018 at 11:41:20AM +0100, Peter Maydell wrote:
> On 23 August 2018 at 11:25, Daniel P. Berrangé <berrange@redhat.com> wrote:
> > In some cases the Author: email address in patches submitted to the
> > list gets mangled such that it says
> >
> >     John Doe via Qemu-devel <qemu-devel@nongnu.org>
> >
> > This change is a result of workarounds for DMARC policies.
> 
> I do wonder if overall we'd be better off with the other
> workaround (don't change From lines in list emails, don't
> add "[Qemu-devel]" prefix to subject lines)... It would be
> a one-off annoyance to people who filter list mail on subject
> rather than other headers, but it would get rid of this annoying
> wart where a handful of senders end up with their mail with
> a from address that our patch management tools don't handle
> very well...

I kind of like seeing the qemu-devel prefix, since I don't tend to
pre-filter email into separate folders per list. I only do per-list
filtering (on headers) once at start of the day when reading the
overnight backlog. For rest of the day have a single inbox and tend
to rely on subject alone.

Of course the prefix isn't entirely reliable regardless, as if you
are CC'd on mails you'll probably see the copy delivered via the CC
long before you get the copy via the list.

AFAIK, the libvirt mailing list isn't mangling From lines, and it
also has a subject prefix added, so I wonder why it doesn't have
a need for the same workaround wrt DMARC ?  Or maybe it does need
it and we've never realized.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|