Add a sender exception in SpamExperts only for a defined legitimate need. Verify the real sender and investigate repeated false positives before trusting an entire domain.
01 Create a narrow exception
- Find a recent affected message and check its original sender details and classification.
- Open Incoming - Protection Settings > Sender Allow list. Choose the intended email or domain scope. An Admin tab entry can affect all domains belonging to that administrator.
- Choose Add Allow list sender. At domain scope, select the domain where shown and the local-part of the intended recipient address.
- Choose the sender flag for the address you have verified: the SMTP envelope sender, the visible message From address, or both. Enter the specific approved sender in Address; do not widen the exception to a whole domain unless required.
- Save, record the reason and review date, then ask for a new harmless message. Confirm its classification and delivery in the logs and destination mailbox.
02 Choose the correct scope
An exception for one employee should not automatically apply to every recipient in the company. Check whether a broader existing rule already covers the sender. Remove obsolete entries when a supplier or application changes.
Common questions
Does allowing a display name help?
Use the actual address or supported matching field. A display name is easily copied and is not a reliable identity boundary.
Will an allow entry guarantee delivery?
No. Other security checks, recipient validity and destination delivery can still matter. Confirm the specific classification and outcome.
Should I allow my own domain to prevent false positives?
Do not use broad self-domain trust as a substitute for correct authentication and routing. It can make spoofed mail harder to distinguish. Investigate the failing sender path.
If a legitimate partner's mail fails authentication, ask the partner to fix the sending configuration. A temporary narrow exception may support business continuity, but it should have an owner and expiry review. Share the relevant message evidence with us when the correct exception scope is unclear.