- Newest
- Most votes
- Most comments
Typically when you see DKIM passing and SPF failing, it's the result of email forwarding. DNS information suggests that 93.188.3.35 is an outgoing mail server from another organization.
DMARC leverages both SPF and DKIM, so as long as either passes, DMARC passes too. It is well known that email forwarding breaks SPF, so DKIM is there to cover that scenario.
The short answer is that you can't control whether your recipients choose to forward their email, nor can you control how forwarding email servers attempt to deliver the message in a DMARC-compatible fashion, so you can't solve this scenario.
answered 4 years ago
Hello. If you haven't already done so, please review Complying with DMARC using Amazon SES which may help identify the issue.
answered 4 years ago
Relevant content
asked 4 years ago
asked 2 years ago
asked 2 years ago
asked 2 years ago

Hello. Thanks for the answer, but I already checked it and did how it says.