E-mail Antispam
Alle berichten worden door DMA nagekeken en voorzien van een spam score. De hoogste spam score is 10.00 en berichten die deze score krijgen worden met een spam melding geweigerd. Berichten met een score tussen 3.50 en 10.00 worden gemarkeerd met [SPAM] in het onderwerp veld van het bericht, u kunt hierop een eigen wizard instellen waardoor deze berichten bij ontvangst naar uw spam mapje gaan.
Het is tevens mogelijk om gemarkeerde spam naar een spam map op de server te sturen en het is mogelijk om ook gemarkeerde spam te weigeren voor ontvangst. Om inzichtelijk te maken waarom een bericht als SPAM is gemarkeerd is wordt in de header van het bericht de SPAM REASONS gegeven.
Hieronder een lijst met de gebruikte codes:
Spam Reasons, Body, Sender
| Code | Reason |
| P | HTML and text parts do not match |
| E | External images in content |
| N | No text part |
| I | Embedded image in content |
| B | No body and no subject |
| R | No intermediary server |
| S | Message contains a script |
| F | Spam scored via a filter |
| K | Spam scored via blacklist keyword |
| X | Message cannot get to quarantine from any reason (e.g. anti-spam database is not accessible). |
Charset Reasons
| Code | Reason |
| F | Charset not allowed |
| M | Missing charset information |
Bypass Reasons
| Code | Reason |
| B | Bypassed because of an entry in the bypass file. This could be sender, recipient, local sender, trusted session, etc. |
| G | Sender exists in GroupWare address books. |
| H | Whitelist and blacklist are skipped if the remote side tells us the sender is local, but the session is not authenticated nor comes from a trusted IP. The email is then processed as usually – other rules are applied. |
| K | Words found in whitelist keywords. |
| L | License is invalid. |
| M | Spam processing was bypassed because the access mode was set for specific accounts, and this account is not one of them. |
| O | Message is outgoing. |
| Q | Local domain senders whitelisted. |
| R | Sender is listed as a contact in the recipient’s IM roster. |
| S | Message exceeds size threshold for checking. |
| T | Sender is trusted – the session was authenticated or the sender’s IP is set in trusted IPs. |
| U | If the Spam folder or quarantine reports are enabled, senders of all SMTP connections from localhost or from another “friendly” servers in load balanced scenario are compared with the sender specified in the settings of spam/quarantine reports. If match is found, connection is whitelisted and bypass reason U is set. |
| W | Sender is on whitelist, or a rule was used to ACCEPT the message. |
| X | Message could not be quarantined for some reasons, e.g. quarantine is not active. |
| J | Recipient’s access mode does not allow to quarantine. |
| Z | Local users mode is set |
IceWarp Anti-Spam LIVE Reasons – identified as LIVE
| Code | Reason |
| Y | This message is flagged as highly likely spam by the IceWarp Anti-Spam LIVE servers. |
| H | This message is flagged as highly likely to be a bulk mail. |
| N | This message is considered genuine. |
Intrusion Prevention Reason Codes
| Code | Explanation |
| C | Tarpitting invoked via Content Filters |
| I | IP blocked for exceeding connections in one minute |
| M | IP blocked for delivering oversized message |
| R | IP blocked for exceeding RSET command count |
| D | IP blocked for being listed on DNSBL |
| A | The account that this message was sent to was a “tarpit” account so the sending IP is tarpitted |
| P | IP block for exceeding unknown User delivery count |
| Y | IP blocked for Relaying |
| S | IP blocked for exceeding Spam score in a message |
| U | Ip blocked Manually via Console |
| L | IP blocked for too many failed login attempts |
