Frequently, legit emails will get caught in greylist or quarantine where the Header From address shows the actual organization (for example, no_reply@standard.com) but the From address is something like 01020199df60110e-adad6878-1234-4d5f-9b1c-1d93aa94033a-000000@eu-west-1.amazonses.com.
Typically, when an email gets quarantined due to 'Sender Alignment' I would add their email domain to a whitelist that is attached to one of my Recipient Policies that bypasses SPF Sender Alignment.
However when the sender uses a service such as amazonses or sendgrid, where the header-from and the header don't match, whitelisting won't work since I assume the whitelist is using from (vs header from).
How can I ensure these emails get delivered successfully without opening up all of Amazon SES or sendgrid?
Is there a way to create an exception list for trusted DKIM domains? Or can you advise on a better way to handle this? I don't see any other posts about this topic so I suspect maybe my spam filtering strategy is not ideal.
How are you successfully filtering incoming emails from legitimate companies that are using bulk messaging services such as Sendgrid and AmazonSES? These services have so many IPs that can change.
We refuse allow list requests. 3rd parties should manage their email correctly in order to make their config is good and they do not end up on known deny lists.
Hello roci
Consider last 7.6.4 firmware to manage Header From as sender
(https://docs.fortinet.com/document/fortimail/7.6.4/release-notes/945544/whats-new)
7.6x also includes several enhancements to manage sender alignment in a more flexible manner than earlier versions
hope it helps
regards
/ Abel
User | Count |
---|---|
2647 | |
1405 | |
810 | |
690 | |
455 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.