Configuration > Anti-Spam > global settings

Sylvain Viart
Added over 4 years ago

Trusted IPs/Networks

The syntax is standard CIDR notation, such as 192.168.1.0/24, one IP or network by line. IPv6 is also supported.

Messages sent by IP addresses listed in the "Trusted IPs/networks" box will still be scanned.

However, MailCleaner will forget the last Received header (the one from this host), and apply all anti-spam check the previous host. This is useful is you have a SMTP gateway in front of MailCleaner which is receiving the messages from the internet and then forwarding them to MailCleaner. That way, MailCleaner will be able to play the anti-spam check in the real external host, and not your internal, trusted system.

Of course, if there is no other Received header, meaning that the message was originally issued from the trusted host, then the message will be fully trusted.

Enable access to whitelists  : ☐
Ignore whitelist in tag mode : ☐

The whitelist and warnlist flag enable the whole white/warn listing in MailCleaner. Without this check enabled, nobody will be able to access and manage the white/warn lists.

If enabled, the whitelists must also be enabled in the domain configuration (subpanel filtering) to be effectively active.

We placed these protections because whitelisting is a very dangerous feature. Although it seems something quite common and natural, it is really badly used and thus very dangerous.

The fact is that the whitelist is based on information (sender address) that is trivial to forge and fake. This makes it very easy for a spammer to circumvent any filtering by correctly forging the sender address of their spam (which is more and more often the case).

This is why we strongly recommend users not to use whitelists.

Enable access to warnlists :

The warnlist is a mitigation of this risk. The principle here is the same as for the whitelist, but instead of letting the message go through (leading the user to believe the filter didn't detect the spam), it will put the message in quarantine and warn the recipient user that a message from this sender has been blocked. Then through a simple link, the user will be able to release and receive the message.

Although this is not the ultimate solution, it will help much when a spammer abuses someone's address book in order to bypass all filtering.