Scan outgoing messages for spam and reject based on defined Apache SpamAssassin™ score

Hello

1. [EDIT] The default score is 5.0 and is the most common score utilized.

2. The message is rejected at SMTP time, so the customer is aware the message is not accepted.

3. This option is intended for email forwarders so ensure email that's forwarded to external mail servers such as Google are scanned by SpamAssassin before leaving the cPanel server.

Thank you.

 

No bounce message is sent because the sending itself will fail at SMTP time with an error message indicating the reason for the failure.

Thank you.

 

Hello,

I'll clarify the previous statement as our documentation has since changed.

You do not have to multiply any values when configuring the SpamAssassin scores in cPanel and WHM. The default option when a user enables SpamAssassin is 5.0, so you can base your score adjustments on that. If you want to block messages more aggressively, then you would set the value lower such as 4.0 or 3.5. If you want to make SpamAssassin less aggressive, then change it to a value such as 6.0 or 7.5.

The only instance where you need to have familiarly with the scoring system is if you are viewing your Exim logs or a message header. SpamAssassin multiples the score values you enter in cPanel/WHM by 10, and that's the value you will see in logs and message headers. Sometimes a user will look in their message header, and see an entry such as:

Code:

X-Spam-Score: 40

That user might question why the message was not marked as SPAM if a SPAM threshold value of 5.0 was configured in cPanel or WHM. This happens because values you enter in cPanel/WHM are multiplied by 10. Thus, entering 5.0 for "Scan outgoing messages for spam and reject based on defined Apache SpamAssassin™ score" in "WHM >> Exim Configuration Manager" results in the following entry in /etc/exim.conf.localopts:

Code:

acl_outgoing_spam_scan_over_int=50

Thank you.