Navigation:  Security Menu > Spam Filter > Spam Filter > White List (automatic)

Automatic White Listing

Use personal contacts, white list and black list files

Click this option to allow each user's personal contacts, white list and black list files to be used as Spam Filter white and black lists. For each incoming message, MDaemon will search the recipient account's contacts, white list, and black list for the sender of the message. If the sender is found then the message will be white or black listed automatically. If you do not wish to apply automatic white and black listing to every MDaemon user then you can disable it for individual users by clearing the Spam Filter uses personal contacts, white list, and black list files option on the Options screen of the Account Editor.

Note: Keeping your contacts updated and synchronized with WorldClient, the Windows Address Book, and other MAPI mail clients that use the Windows Address Book can be easily done using ComAgent.

...only whitelist addresses that authenticate using SIDF or DKIM

When this option is enabled, MDaemon will not white list the message unless the sender was authenticated via the Sender ID Framework (SIDF) or DomainKeys Identified Mail (DKIM). This option helps to avoid white listing messages with spoofed addresses.

Automatically update white listed contacts

When this option is enabled, MDaemon will automatically add any non-local email addresses to which you send mail to your personal white list folder. When used in conjunction with "Use personal contacts, white list and black list files" above, the number of Spam Filter false positives can be drastically reduced.

If you do not wish to apply automatic white list updating to every MDaemon user then you can disable it for individual users by clearing the "Update white listed contacts with mail recipients" check box on the Options screen of the Account Editor.

Remove contacts which are missing name or phone data

Click this button if you wish to remove every contact that contains only an email address from every user's default Contacts folder. If a contact doesn't have at least a name or phone data it will be removed. The option is primarily to help those who have been using MDaemon's automatic white listing option prior to version 11 purge contacts that were added purely as a function of the white list feature. In previous versions of MDaemon the addresses were added to the main contacts instead of to a dedicated white list folder. This could result in users having many entries in their contacts that they would rather not have there.

Forwarding to whitelist@ updates whitelist contacts

When this option is enabled, accounts using the "Spam Filter uses personal contacts, white list, and black list files" on the Account Editor's Options screen can forward messages to whitelist@<domain> and have MDaemon add the sender of the original message to the account's white list. The white listed address is taken from the forwarded message's From header.

Messages forwarded to whitelist@<domain> must be forwarded as attachments of the type message/rfc822, and they must be received by MDaemon via SMTP from a session that is authenticated. Forwarded messages not meeting these requirements will not be processed.

You can change the address MDaemon uses by editing the following key in the CFILTER.INI file:

[SpamFilter]

WhiteListAddress=MyWhiteListAddress@

Note: the last character must be "@".

Forwarding to blacklist@ updates blacklist contacts

When this option is enabled, accounts using the "Spam Filter uses personal contacts, white list, and black list files" on the Account Editor's Options screen can forward messages to blacklist@<domain> and have MDaemon add the sender of the original message to the account's black list. The black listed address is taken from the forwarded message's From header.

Messages forwarded to blacklist@<domain> must be forwarded as attachments of the type message/rfc822, and they must be received by MDaemon via SMTP from a session that is authenticated. Forwarded messages not meeting these requirements will not be processed.

Update Bayesian engine with copies of white listed messages

Check this box to cause qualified messages to be copied automatically into the Bayesian non-spam learning folder (designated on the Bayesian screen). This helps to automate the process of providing the Bayesian engine with samples of non-spam messages. Regularly providing the Bayesian engine with new examples of non-spam to learn from will increase its reliability over time and help to reduce the number of false positives (i.e. messages that are erroneously classified as spam).

To qualify for this feature, an incoming message must be addressed to a local user and the sender must be someone in his address book file. If the message is outgoing, then it must be the recipient who is in the address book. If you do not want any outgoing messages to qualify, then use Notepad to edit the following setting in the MDaemon.ini file:

[SpamFilter]

UpdateHamFolderOutbound=No (default = Yes)

When a message qualifies, it is copied into the Bayesian non-spam learning folder even if Bayesian scheduled learning is disabled on the Bayesian screen. Thus, when scheduled learning is later enabled, or when learning is manually activated, a set of non-spam messages will be ready for analysis. Not every message that qualifies, however, is copied into the learning folder. When the feature is activated, MDaemon will copy qualified messages until a designated number is reached. Subsequently it will copy single messages at designated intervals. By default, the first 200 qualifying messages will be copied and then every tenth qualifying message after that. The initial number copied is equal to the number designated in the option, "Non-spam samples needed before Bayesian scoring is possible" located on the Bayesian Auto-learning screen. Changing that setting will also change this value. If you wish to change the interval by which subsequent messages are copied, you can do so by editing the following setting in the MDaemon.ini file:

[SpamFilter]

HamSkipCount=10 (default = 10)

Finally, once a designated total number of messages has been copied, the entire process will be begin again — 200 will be copied and then every tenth (or an alternate value if you have changed these settings). By default, the process will be restarted after 500 qualifying messages have been copied. You can change this value by editing the following setting in the MDaemon.ini file:

[SpamFilter]

HamMaxCount=500 (default = 500)