Document information

Reason why Xeams Ignores Whitelisted Email Addresses. 

This latest version of Xeams, by default, will only add a negative score for whitelisted email addresses and domains if DMARC passes. This is done by design to prevent forgeries. Consider an example of where a user whitelists store-news@amazon.com. This is a widespread address that is often forged. Older versions of Xeams would accept any email matching this value, even if SPF, DKIM, and DMARC failed.

The current version of Xeams applies a negative score only to a whitelisted filter when DMARC is aligned, which eliminates forged messages.

Ignoring DMARC

Most senders these days are DMARC-aligned - meaning they either have an aligned SPF or DKIM. A non-aligned DMARC usually means a configuration problem on the sender's end. In the rare cases where DMARC is not aligned, but you will want to accept emails from that sender, you can check the Skip DMARC alignment box when creating a sender filter, as shown below.

Needless to say, when this box is checked, Xeams will accept messages even if they are forged.

Ignoring DMARC Globally

By default, Xeams will skip DMARC alignment only when the box mentioned above is checked. To change this default setting, add the following line to the server.properties file.

ignore.dmarc.alignment.in.sender.filter=true

Add a comment to this document

Do you have a helpful tip related to this document that you'd like to share with other users?

Your Name

Email

Hide my email address

Captcha

Your Tip

Submit Tip