EmailArchitect Email Server > Anti-Spam Protection

Starting from version 5.2, Anti-Spam module is introduced. This module can effectively blocked 99.9% of junk email. Unlike RBLs service, Anti-Spam service uses customized rules and built-in functions to check message content.

Behind of Realtime Black List

The Realtime Black List (RBL) lists most IP addresses which were complaint as spreading spam. All incoming mail is checked by RBLs service first. The mail passes RBLs validation will be checked by Anti-Spam service.

Two Anti-Spam Levels

There are two anti-spam levels in Anti-Spam service. User can choose either low or high level rules to check email content.

Three Actions

Once a message is detected as junk email, administrator and user can choose from the follow options to process the junk email:

A. Using "Challenge Response" technology to verify the sender e-mail address;
B. Manullay approved by specific user;
C. Move the junk email to Junk* folder or add "*SPAM*" keyword in the email subject.

Junk* Folder

All user has a specific mailbox named "Junk*". By default, every junk email will be delivered to this folder such that user can still view the emails. Email in this folder will be removed by system automatically.

Never Blocked Addresses

The Anti-Spam never checks the email sent from the following email addresses.

1. From the address which is on personal contact list or global contact list.
2. From the authenticated user.
3. From the address on trusted list.
4. From the auto-white list.

Since the anti-spam service never checks the email from authenticated user, local user must set the user authentication in e-mail client.

Auto-White List

EmailArchitect Anti-Spam module maintains a list of recent recipients' addresses sent by authenticated user. All the addresses on the list are recognized as trusted address by Anti-Spam module, and email sent from the trusted address will never be marked as Junk email. Note that once you receive a spam, don't reply it, otherwise its sender address will be added to your auto-white list.

Error Adjustment by SPF and A & MX Record

Please possess the knowledge of Sender Policy Framework(SPF) from the following url:
http://spf.pobox.com/
http://www.microsoft.com/mscorp/safety/technologies/senderid/default.mspx

Although SPF is a good solution to prevent faked email sender, many domains have not yet set the SPF record to support this. As such, checking the MX/A record is very important to those domains.

e.g.

The email sender is: xxx@adminsystem.com and this email is from IP address: 210.17.235.64. By querying the dns server of adminsystem.com, mail.adminsystem.com is the MX record of adminsystem.com and the IP address of "mail.adminsystem.com" is "210.17.235.64". There is enough information to validate this email, and Anti-Spam service will not mark this email as junk even the email matches the junk rules.

Download the trial version   << Prev Topic: Anti-Virus Protection   Next Topic: Filters & Message Approval >>