A new spam-scanning solution is being used for the Hosted Email platform. It provides high-level email security by dramatically reducing inbound email spam, phishing, and malware. It also helps prevent outbound spam and IP blacklisting. Our new, intelligent email security system uses open-source technology.
Manually marking an email as spam
Marking an email as spam reports various elements of the email like the sender, email headers, email contents, etc. to the email server. The spam filter will incorporate these elements and filter out future emails that are similar.
Reporting legitimate marketing emails as spam will be ineffective since they are considered a trusted sender. Unsubscribing from their mailing list will prevent future marketing emails.
Note: Marking an email as not spam will teach the spam filter which kinds of emails are considered safe.
- Mark the email as Spam.
- Press Accept to confirm the selected email as spam.
Important: If you confirm to share your data with our Spam partner, the pop-up will go away and you will not be prompted to make a selection going forward. Should you choose to decline, when you mark an email as Spam, the pop-up will appear each time.
Moving messages between the inbox/spam folders trains the new system, applying the changes to the respective user. This per-user system activates once trained through enough examples.
Scores over 9.00 are considered spam and are used for the default level. Users may make the spam detection more aggressive by setting their spam level settings to high or to very high, which are triggered at 8.50 or 8.00 scores, respectively.
Score values are found in the new X-User header. A negative score contributes to the message being viewed as ham. A positive score increases the chances the message is marked as spam.
The spam scanning system adds several headers to each message. The X-Spam-Status header contains the spam score for the message. The X-User header contains the score modification as a result of per-user training. X-Rspamd-Server, X-Rspamd-Queue-Id, and X-Stat-Signature are primarily for system use and can be helpful for OpenSRS support staff in diagnosing issues.