Precisium has various levels of spam protection available.
You may choose the base level of spam filtering you'd like for your account by emailing email@example.com
The base spam filtering is based on blacklists, and prevents messages from known junk-sources from even getting to your mailbox.
(See Base spam protection below)
In addition to the base protection, you can configure rules on the server to handle spam in a custom manner.
These 'sieve' rules can be adjusted to perform actions on emails depending on the spam-score.
When messages arrive on the servers, they are scanned and marked with information describing how 'spammy' a particular message appears to be.
This is done by adding message 'headers' which you can detect in your sieve rules in order to take appropriate action such as filing into a 'Junk Email' folder or deleting.
For example, the X-Spam-Level header will contain a number of asterisks (*).
The more asterisks, the more likely it is to be spam. A reasonable action might be to auto-file messages with 5 or more *'s into a junk folder.
Most mail programs also allow you to filter or categorise email based on these headers, but the disadvantage of waiting for messages to get to your mail program is that you generally download more,
and if you have multiple devices, you'd need to configure your rules in each one. By using the server-side 'sieve' rules - the spam is detected and filtered in the same way for all your devices.
To configure your sieve settings, log in to your configpanel (configpanel.com) with your administrative username and go into the 'email' section of the menu.
Select 'filters and autoresponders', then select the appropriate mailbox in the 'sieve' column and create your rules.
Sieve rules can be quite complex - so if you'd prefer us to configure the basic filtering for you, phone us or email firstname.lastname@example.org.
Base spam protection
One of the most effective mechanisms for protecting your inbox is to use 'blacklists' of known spam-sources or virus-compromised machines.
We offer the following spam protection levels:
- None. No blacklists used.
Email must still pass an extremely basic technical 'dress code' to be received however.
- Basic. bl.spamcop.net, zen.spamhaus.org, combined.njabl.org, safe.dnsbl.sorbs.net, SPF
This provides reasonable protection with fairly low probabilities of falsely identifying genuine messages as spam.
- Standard. bl.spamcop.net, zen.spamhaus.org, safe.dnsbl.sorbs.net, combined.njabl.org, psbl.surriel.com, spamrats.com, SPF
You run some risk of false positivies, but usually this will be because the sender is using a system that is supporting spammers or has been compromised in some way.
Generally if you receive reports of mail to you being 'bounced' because of spam settings - the sender should first check with their own technical-support that their systems have been cleaned up.
If you have important email that is being blocked whilst on this level, but you don't wish to drop down to 'basic' protection -
you may request that we put in a special exception for certain senders.
- Aggressive. All the above blacklists and more,SPF - plus requires that the sending mailserver has a valid hostname.
This setting provides the cleanest mailbox, but runs a high risk of falsely identifying email as spam.
We suggest this only be used for mailboxes where you only wish to receive mail from systems that maintain the highest technical standards and anti-spam policies.
Note that on the 'basic' setting, you may still receive the occasional complaint from people trying to email you, that their message has bounced.
If this is because of a spamcop listing, then this situation will automatically resolve once their system has stopped being a source of spam.
Spamcop will not list a mailserver if there have been no spam reports against it within 24 hours.
It will also not list a server with only one report, and systems with only two reports will be listed for a maximum of 12 hrs after the most recently reported spam was sent.
For this reason it is a good choice for basic spam protection, and generally the occasional valid senders who mention that they are being blocked because of this, should be told to resend their message once their system administrator has cleaned up their mailserver.