From: Daniel Vetter <daniel@ffwll.ch>
To: Sean Paul <sean@poorly.run>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
Dave Airlie <airlied@linux.ie>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: drm-misc: Change seanpaul's email address
Date: Thu, 16 Aug 2018 18:30:39 +0200 [thread overview]
Message-ID: <CAKMK7uGpT428FnT_7zwbDovLNHk8GMuOzf9gW9wiBkyiOLSw3w@mail.gmail.com> (raw)
In-Reply-To: <20180816155538.GR164269@art_vandelay>
On Thu, Aug 16, 2018 at 5:55 PM, Sean Paul <sean@poorly.run> wrote:
> On Thu, Aug 16, 2018 at 09:32:48AM +0200, Daniel Vetter wrote:
>> On Wed, Aug 15, 2018 at 11:35:29AM -0400, Sean Paul wrote:
>> > Since chromium.org is now enforcing DMARC, my mails are going to
>> > people's spam folders. While this development might be desirable
>> > for people I communicate with, it's undesirable for me :-)
>> >
>> > Cc: Dave Airlie <airlied@linux.ie>
>> > Cc: Gustavo Padovan <gustavo@padovan.org>
>> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>> > Signed-off-by: Sean Paul <sean@poorly.run>
>> > ---
>> > MAINTAINERS | 2 +-
>> > 1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/MAINTAINERS b/MAINTAINERS
>> > index 93f189f0d60d..5eaa1c91d4a4 100644
>> > --- a/MAINTAINERS
>> > +++ b/MAINTAINERS
>> > @@ -4662,7 +4662,7 @@ F: include/linux/vga*
>> > DRM DRIVERS AND MISC GPU PATCHES
>> > M: Gustavo Padovan <gustavo@padovan.org>
>> > M: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>> > -M: Sean Paul <seanpaul@chromium.org>
>> > +M: Sean Paul <sean@poorly.run>
>>
>> Glorious domain :-)
>>
>> Aside: ffwll.ch has been running with dkim since a while, seems to work
>> correctly. You just need non-strict dkim enforcement, which at least for
>> gapps is the default.
>>
>> But even then Linus' gmail inbox throws my mails away every once in a
>> while, so email clearly doesn't work.
>
> My (completely incorrect, i'm sure) understanding is that DKIM is fine, but
> DMARC is the problem.
>
> It seems Mailman was altering some (or all) of my messages which caused DMARC
> to fail. At the very least the "Prevent duplicate messages" setting in mailman
> strips users cc from the headers. So if any one of the recipients has this
> setting enabled, the headers are munged, DMARC fails, and emails go to spam.
Hm tbh I didn't know about DMARC yet. Sounds like it just tells the
recipient how your domain would like SPF/DKIM failures to be handled.
One of these (if configured correctly) should survive mailing lists. I
did crawl dri-devel a bit, and there's mails that passed through with
full dmarc enforcement. So it's not impossible.
But hey in practice it doesn't even work for gmail->gmail when the
moon howling is too bad :-)
-Daniel
>
>>
>> </rant>
>>
>> Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> Thanks, pushed to -misc-next-fixes
>
> Sean
>
>> > W: https://01.org/linuxgraphics/gfx-docs/maintainer-tools/drm-misc.html
>> > S: Maintained
>> > T: git git://anongit.freedesktop.org/drm/drm-misc
>> > --
>> > Sean Paul, Software Engineer, Google / Chromium OS
>> >
>> > _______________________________________________
>> > dri-devel mailing list
>> > dri-devel@lists.freedesktop.org
>> > https://lists.freedesktop.org/mailman/listinfo/dri-devel
>>
>> --
>> Daniel Vetter
>> Software Engineer, Intel Corporation
>> http://blog.ffwll.ch
>
> --
> Sean Paul, Software Engineer, Google / Chromium OS
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2018-08-16 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 15:35 [PATCH] MAINTAINERS: drm-misc: Change seanpaul's email address Sean Paul
2018-08-16 7:32 ` Daniel Vetter
2018-08-16 15:55 ` Sean Paul
2018-08-16 16:30 ` Daniel Vetter [this message]
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=CAKMK7uGpT428FnT_7zwbDovLNHk8GMuOzf9gW9wiBkyiOLSw3w@mail.gmail.com \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sean@poorly.run \
/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).