Recherches récentes
Pas de recherche récente

Craig Rodrigues
Adhésion le 16 oct. 2021
·
Dernière activité le 16 oct. 2021
Suivis
0
Abonnés
0
Activité totale
2
Votes
0
Abonnement
1
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par Craig Rodrigues
Craig Rodrigues a ajouté un commentaire,
@... I am working with a Zendesk setup, and following these instructions: https://support.zendesk.com/hc/en-us/articles/203663336-Adding-support-addresses-for-users-to-submit-tickets
we have it set up so that the support address is support@mydomain.com .
This works fine, and the e-mails generated by Zendesk have:
From: mysetup <support@mydomain.com>
Reply-To: mysetup <support@mydomain.com>
The e-mails are being sent out properly, but some of our customers are finding these e-mails in the SPAM folder.
I analyzed the e-mails in my customer's SPAM folder and see:
SPF: | PASS |
---|---|
DKIM: | 'PASS' with domain zendesk.com |
DMARC: | 'FAIL' |
DMARC is failing because DKIM/SPF is not aligned with the Reply-To: address.
When sending e-mails, is it possible to get Zendesk to sign the e-mails with DKIM/SPF for mydomain.com instead of zendesk.com?
When my customer's e-mail system sees SPF signed for one domain (zendesk.com), but From: and Reply-To: contains another domain (mydomain.com), then this fails DMARC and gets flagged as spam.
Afficher le commentaire · Publication le 09 sept. 2021 · Craig Rodrigues
0
Abonnés
1
vote
0
Commentaire