DMARC issue

@Again​ I still don't get it. The post says "f you would like to use your "comcast.net" address to send email, it is recommended that you send these messages via our Xfinity Connect webmail platform", which is what I'm doing. The question I have is whether this is an issue with Xfinity/Comcast, or TripAdvisor? It would appear the cause is due to Xfinity/Comcast. But do I have any options or will I need to accept it? 

@user_jkkqcm​ 

You're sending emails to the address "sfwebform@tripadvisor.com" directly from our webmail?  Or are you sending to another email address @tripadvisor.com ?

I'm asking because I don't see any emails to sfwebform, so I wonder if they're doing something with the emails once they receive them, and that's causing the issue.  Can you tell me when you tried to send these messages, and when you received the bounce above?  Or can you try again and note the time when you attempt this?

Also, neither we nor Google are using Exim, which leads me to believe something else is attempting to route emails as comcast.net

Are you sure?  This line makes me think otherwise:  Remote-MTA: dns; smtp.google.com

@strega7​ Except I can't know the mailpath of messages after they leave our platform.  It's entirely possible that when forwarding to another gmail user that Gmail injects into their own SMTP servers instead of some internal routing.

Sorry if I wasn't clear, but that was directed at user_jkkqcm.  I know he said he was using comcast webmail, but that line made me think he was using gmail to send a message from ...@comcast.net.

@user_jkkqcm​ Could you DM me the account you're sending from?  That will help me better look at logs from our side.

Wow!  I did not get that at all from the earlier posts.  So what I think you are saying, is that YOU are not (directly) emailing AT ALL when this happens.  

Back when DMARC started rolling out, I had to convert the web contact form on my own website.  It used to send me emails as FROM the person contacting me.  To be SPF/DKIM/DMARC compliant, I had to change it to send emails FROM some email address within my own domain and with a Reply-To of the user contacting me.  Maybe ask tripadvisor if that they have done something like that?  Since they are DMARCing against comcast.net instead of their own domain, this makes me think that they haven't. 

@strega7​ In the base case I am not sending an email, I am submitting information into a form while I am logged in. And somehow this information is converted to another object (maybe), submitted into their system, and then a receipt email is issued back to me? But now the form information no longer shows up and no receipt email. I will share another case beyond the base care form, and that is the email address help@tripadvisorsupport.com which also seems to disappear my actual emails and that email address used to give me email receipt replies previously and it no longer does, and the email does not show up in their system. And again, my apologies for not fully explaining it so well. I did DM the employee with this additional information yesterday, too. 

That's interesting because you have two entirely different cases:  One case is tripadvisor's web page and infrastructure - and therefore their responsibility to get right.  But the other case is you sending an email - which means you have to get it right.  (By get it right, I mean not doing anything like using gmail to send email from something@comcast.net for example.)  Nothing occurs to me as a single thing that would cause (or fix) both of these issues.

For the webform case, it looks (TO ME) like tripadvisor's website is messed up.  It appears (TO ME) based on an error that you posted earlier that tripadvisor's web site is sending an email to sfwebform@tripadvisor.com and they're doing it via smtp.google.com, yet, the DMARC complaint is "Unauthenticated email from comcast.net..." That would be the same issue I fixed on my website a couple of years ago.  You used to be able to send email as "from" whoever you wanted to.  Not so much these days.  

@strega7​ Thanks for the thoughts. I can try again with them. I'm assuming most (or all) their IT support is offshore, so I may not get anywhere. I have one more trick up my sleeve in that I can change my TA account email default to a gmail account I have, separate from all this mess. But it still may not work. Who knows. Thx. 

@user_jkkqcm​ I realize this is not malicious, but sentiment/intent is not easily known within internet protocols.  That said, it does indeed sound like TripAdvisor is attempting to send an email as "comcast.net", and that is where DMARC is meant to protect the comcast.net domain.

Is this a form that any of us can login to see?  Do you have a contact at TripAdvisor?