Hello everyone,

I have observed an interesting case where calendar invites send by google to 
another third-party email service are being rejected on the way back (ie. when 
accepted) if the receiver of the invites is in DMARC reject.

I have also observed that in some cases there are two sets of response buttons 
present in the calendar invitation email. One set is the usual google response 
buttons found towards the bottom of the email, and the other set is out-of-band 
response buttons found towards the top of the email. I have shown some examples 
below.

Google buttons:

Out-of-band buttons:


When accepting the invitation using the google response buttons, the email is 
rejected and the responder receives a 5.7.1 DSN back due to the responder's 
domain having a DMARC reject policy. However, when accepting the invitation 
using the out-of-band buttons the email is sent through the correct servers, 
DMARC passes and the response is received successfully by Google. 

Those out-of-band buttons do not always exist. Some mail clients display them 
and some do not. Also, it depends if a desktop mail client is used or webmail. 
During my testing I found the following:

Google --> Office 365 domain that is in DMARC reject - working but office 365 
domain needs to reply using the out-of-band buttons

Google --> AOL - not working as AOL does not display out-of-band buttons

Google --> Yahoo - working but Yahoo needs to reply using the out-of-band 
buttons


My question 1: is using the out-of-band buttons the only workaround for the 
moment and if it is, what happens when those buttons are not available?

My question 2: is there any work done by google to resolve this?

Hey Brandon, can you give some insight on the above issue?

Regards,
Ivan Kovachev
 
_______________________________________________
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)

Reply via email to