![]() So please don't do the 'oh some other company is involved so it's definitely their problem' bit. But Zendesk emails are consistently marked SPAM, even though SPF, DKIM, and DMARC are all passing on Yahoo's side, as the headers show. ![]() We use GMail connector precisely because we've had pristine SPF/DKIM/DMARC setup and rely on deliverability of it that way. We don't have any trouble reaching people directly via GMail on Yahoo and AOL. While I understand that - my point in sending the headers I did is that it probably is NOT due to GMail connector and possibly due to the way the emails are encoded, etc that are triggering Spam filters. Is it possible something in the way emails are getting composed is causing this? Yahoo even alerts that it has disabled links in the email (though helpfully provides a link to activate them and suggests clicking 'Not Spam'). But we never had this much trouble with our ticket emails getting seen before (thankfully we send SMS texts when a ticket is solved, so we often get a call asking if the problem is solved). I completely understand this is somewhat out of Zendesk's hands - despite everything passing, they still mark is as Spam. ![]() Received-SPF: pass (domain of designates X.X.X.X as permitted sender)Īuthentication-Results: 1. ĭmarc=pass(p=NONE) om= This is the header in a Zendesk email sent to my Yahoo test account. And it STILL goes directly to Yahoo's spam folder (AOL about the same). We use the GMail connector for outgoing emails and can confirm we have valid SPF, DKIM *AND* DMARC settings. It seems to have gotten much worse recently.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |