Sorry, I wasn't on dmarc-discuss for some reason, looking at the archive: A. Schulze via dmarc-discuss:
> > I like to point to that open topic without any answer I hoped to get > from Google > > simple setup: > gmail user send with RFC5322.From *@googlemail.com via google using a > smartphone. > the user authenticate as *@gmail.com for submission. > dkim signing domain: header.d=gmail.com > spf: gmail.com > dmarc policy for googlemail.com: quarantine > result: dmarc fail. > - should gmail users no longer use RFC5322.From *@googlemail.com? > googlemail.com is definitely "old" and unnecessary, but it shouldn't be broken. > - should gmail users using RFC5322.From *@googlemail.com also > authenticate the submission as *@googlemail.com? > We've been making changes in this area for other things and may have broken this, and given the state of change, I don't know if it's still broken or not. Also, creating a googlemail.com account is complicated, so it's not easy for me to test myself. If it doesn't work for login @gmail.com send from @googlemail.com, but does for login @googemail.com send from @googlemail.com. I was able to test and show that login @googlemail.com and send from @gmail.com for my gmail.com account works fine. If you can reproduce an issue, please email me with the actual account information and headers, so I can try to find logs. Brandon > - or is it simply an issue that such messages are not handled > correctly at google? > Any clarification is welcome. > Thanks! > > > Hello, > > > > last days I wrote to a address <user at gmail.com> > > The answer was quarantained as the dmarc check failed. > > > > This ist the reply I receved: > > > > Authentication-Results: mail.example.org; dmarc=fail > > header.from=googlemail.com > > Authentication-Results: mail.example.org; > > dkim=pass (2048-bit key; unprotected) header.d=gmail.com > > header.i=@gmail.com header.b=gG3f0joi > > Authentication-Results: mail.example.org; spf=pass > > smtp.mailfrom=<firstname.lastname at gmail.com> > > smtp.helo=mail-wi0-x234.google.com > > ... > > Received: from [...] (users.submission.client. [public.ip]) > > by smtp.googlemail.com with ESMTPSA id > > e8sm15252097wiz.0.2015.08.16.23.40.46 > > for <$me> > > (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 > bits=128/128); > > Sun, 16 Aug 2015 23:40:46 -0700 (PDT) > > Sender: User <firstname.lastname at gmail.com> > > From: User <firstname.middlename.lastname at googlemail.com> > > X-Google-Original-From: User <firstname.middlename.lastname at > gmail.com> > > Message-ID: <55D181EE.80000 at gmail.com> > > User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) > > Gecko/20100101 Icedove/31.7.0 > > To: ... $me > > ... > > > > So Sender and X-Google-Original-From are "@gmail.com", but From is > > "@googlemail.com" > > No idea if the user did something wrong or only hit a common pitfall. > > Looks like this user may mix two similar addresses with different > > domainparts while using them as RFC5322.From or SMTP-Auth Username. > > > > Maybe the google people could clarify? > > > > Thanks, > > Andreas On Sat, May 7, 2016 at 2:16 AM, A. Schulze via dmarc-discuss < dmarc-discuss@dmarc.org> wrote: > > > Am 29.04.2016 um 11:15 schrieb A. Schulze via dmarc-discuss: > >> I like to point to that open topic without any answer I hoped to get from >> Google >> > > nobody could clarify? > > Andreas > _______________________________________________ > dmarc-discuss mailing list > dmarc-discuss@dmarc.org > http://www.dmarc.org/mailman/listinfo/dmarc-discuss > > NOTE: Participating in this list means you agree to the DMARC Note Well > terms (http://www.dmarc.org/note_well.html) >
_______________________________________________ dmarc-discuss mailing list dmarc-discuss@dmarc.org http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html)
