Other

Figure. Outgoing messages section.

These options allow you to define what Antispam processing will be performed on outgoing messages.

Choose from the options listed:

Field	Description
Process with full Antispam and refuse	Use this option to have all messages processed and any that are identified as spam will be refused.
Process with full Antispam	Use this option to have all messages processed but then forwarded no matter what the result. Messages identified as spam will be marked according to your settings and sent.
Process with Antispam Live! only	Use this option to have all messages analyzed in real time based on characteristic mass distribution patterns to adjust the Spam score of a message.
Do not process with Antispam	Use this option to bypass Antispam processing. You should only use this if you trust all users on your system. Example: Processing Mailing list as External Delivery In case that you want to disable the Antispam filter for mailing lists, you have to enable the external delivery for all mailing lists on the server. Mailing lists will be processed as outbound. tool --filter="(u_type='1')" set account @ m_deliverexternally 1 The Antispam settings is set to "not process with Antispam (outgoing messages)". Now if you send email to mailing list, then mailing list will be not processed by Antispam.

Figure. Other section.

Field	Description
Process unknown accounts	This option tells IceWarp Server what to do when a message comes in for an undefined account (for example a message that is going to be forwarded to a defined account via rules). Check the box to have these messages processed by the Antispam engine.
Antispam mode	Choose from one of the following: User: The email address is added to the recipient's whitelist. This mode is best for ISP's whose customer base within a domain are unrelated. Domain: The email address is added to the whitelist of the recipient's domain. This mode is best for ISP's that host multiple "company" domains, where all domain users are related somehow. System: The email address is added to the whitelist for the whole IceWarp Server installation. This mode is best for company installations of IceWarp Server. Note: Setting the Antispam mode to Domain or System can make the blacklist and whitelist records appear confusing as they have specific user accounts specified as owners of records. This can cause some confusion if another user is questioning why a message did, or did not, get through. For example: When you change the mode from User to Domain, all whitelist/blacklist entries of individual users will apply to the whole domain. Vice versa, when changing the mode to User, whitelist/blacklist entries will apply only to their owners. This setting has influence on a database "level" that is used for address whitelisting when the Auto whitelist trusted email recipients to database box is checked. For more information about whitelisting, auto-whitelisting and whitelist clearing, refer toWhitelist.
Local users mode	Select one of the three options defining how you wish to process messages from other users on the same server (but maybe in different domains). Do not quarantine / whitelist / blacklist local users: Users from domains on this server will not be challenged. Use this if you trust all users in all domains. Quarantine / whitelist / blacklist all local users: All users will be challenged. Use this if you host any domain(s) of un-trusted, unrelated users. Quarantine / whitelist / blacklist local users from other domains: Local users will be challenged if they are from a different domain on the server. Use this if you host domains of trusted and un-trusted users (e.g. corporate domains).

Field

Description

Process unknown accounts

This option tells IceWarp Server what to do when a message comes in for an undefined account (for example a message that is going to be forwarded to a defined account via rules).

Check the box to have these messages processed by the Antispam engine.

Antispam mode

Choose from one of the following:

User: The email address is added to the recipient's whitelist.

This mode is best for ISP's whose customer base within a domain are unrelated.
Domain: The email address is added to the whitelist of the recipient's domain.

This mode is best for ISP's that host multiple "company" domains, where all domain users are related somehow.
System: The email address is added to the whitelist for the whole IceWarp Server installation.

This mode is best for company installations of IceWarp Server.

Note: Setting the Antispam mode to Domain or System can make the blacklist and whitelist records appear confusing as they have specific user accounts specified as owners of records. This can cause some confusion if another user is questioning why a message did, or did not, get through.

For example: When you change the mode from User to Domain, all whitelist/blacklist entries of individual users will apply to the whole domain. Vice versa, when changing the mode to User, whitelist/blacklist entries will apply only to their owners.

This setting has influence on a database "level" that is used for address whitelisting when the Auto whitelist trusted email recipients to database box is checked.

For more information about whitelisting, auto-whitelisting and whitelist clearing, refer toWhitelist.

Local users mode

Select one of the three options defining how you wish to process messages from other users on the same server (but maybe in different domains).

Do not quarantine / whitelist / blacklist local users: Users from domains on this server will not be challenged. Use this if you trust all users in all domains.
Quarantine / whitelist / blacklist all local users: All users will be challenged. Use this if you host any domain(s) of un-trusted, unrelated users.
Quarantine / whitelist / blacklist local users from other domains: Local users will be challenged if they are from a different domain on the server. Use this if you host domains of trusted and un-trusted users (e.g. corporate domains).

Figure. Advanced tab.

Field	Description
Thread pooling	Specify here the maximum number of threads to use when processing messages with the Antispam engine. Tip: This can be useful for reducing (or increasing) server load.
Maximum message size to process with Antispam	Specify a maximum size of message to be processed with the Antispam engine.
Antispam engine bypass file	Click the B button to open the Bypass file, listing any users, accounts or domains from which messages will not undergo Antispam processing. The Bypass dialog opens. For more information about this dialog, refer to Bypassing Rules / Filters.

Note: You can get comprehensive spamassassin rule statistics by specifying a file name in the settings file. Do this under the spamassassinrulestats entry in the format:
spamassassinrulestats="<filename>"
You can use date/time variables here if you want to create daily/hourly files etc.
spamassassinrulestats="yyyymmddhhnnss.txt"

The contents of the files will allow you to see which rules have been used and how many times and also you can analyze which rules have not been hit, allowing you to delete them to speed up processing and save processing power of your server. A simple example from a statistics file is shown below:

SpamAssassin statistics 2007-08-15

00:00

Genuine: 649

SpamQuarantine: 0

SpamMarked: 416

SpamRefused: 205

SpamAssassin: 481

Rules: 1293

TotalHits: 13588

NoHits: 1039

Rules with hits:

__FRAUD_DBI (1.00) 29

.... list of rules

Total: 254, Hits: 13588

Rules with no hits:

DRUGS_DEPR_EREC (1.00) # Refers to both an

erectile and an antidepressant ... list of rules

Total: 1039