Occasionally you may see email receipts being routed to spam when you are sending them to yourselves. This may happen if you are using the same domain to receive the email as you are using to send it.
For example:
Sending domain -> receipts@tedtech.com
Recipient -> ted@tedtech.com
If this does happen, it's worth getting in touch with us to confirm but this doesn't indicate a problem delivering to your customers.
This tends to happen because your email system (hosting the email ted@tedtech.com) isn't expecting to receive an email from an external source, claiming to be internal. For example: Office 365 applies additional "Composite Authentication" (compauth) checks on internal domains.
When Office 365 hosts your work domain (e.g. tedtech.com) , it may detect emails that claim to be from an internal domain but are sent from an external IP address. By default, Office 365 flags this as possible spoofing, resulting in a compauth=fail status. This means that while the email may pass DMARC checks on other systems (which trust DKIM validation), your own Office 365 setup applies stricter rules because it sees the email arriving externally from an internal domain, potentially flagging it as suspicious.
This explains why the same email might pass DMARC on all systems except your own Office 365 environment, where it may end up in quarantine or spam.
One solution is to adjust the "mail-from" domain to also be your own domain (e.g tedtech.com) . This would resolve the issue of Office 365 quarantining your emails, but it would not affect delivery to your external customers. However, this approach would require you to set up dedicated email addresses for bounce and complaint notifications. Additionally, if your Office 365 mail server were to go down, we wouldn't be able to send Digital Receipts. This approach will also affect bounce reporting in the reporting dashboard.
Alternatively, you could consider setting up an Inbound Connector in Office 365 or bypassing the spam filtering rules specifically for these emails.
Please note that our email provider (AWS SES) verifies the status of your mail server to ensure it can receive bounces and complaints before sending any emails. If your mail server is down, we would not be able to deliver Digital Receipts.
Retailer's email receipts with their own sender address ending up in Spam/Quarantine List
