Tuesday 26th July 2016 16:37
Our recommended Exim Configuration Editor Standard Options
settings in WHM version 11.40 and above (with MailScanner installed and
ACL Options: Leave cPanel's defaults or modify as desired. We recommend enabling the following:
* Dictionary attack protection
* Require HELO before MAIL
* Require remote (domain) HELO
* Require RFC-compliant HELO
You should leave "No reject rule by spam score" and "No ratelimiting
by spam score" as they are set by default. No SpamAssassin options
should be enabled at all.
Access Lists: Leave cPanel's defaults or modify as desired.
Domains and Ips: These settings should not affect MailScanner.
Filters: Disable the following:
* Attachments: Filter messages with dangerous attachments
* Apache SpamAssassin�: Global Subject Rewrite
* Apache SpamAssassin�: bounce spam score threshold - set to No bouncing by spam score
* SpamAssassinTM: X-Spam-Subject/Subject header prefix for spam emails - leave default
System Filter File = /etc/antivirus.empty
Mail: Enable the following:
* Log sender rates in the exim mainlog
* Reject mail for users over quota at SMTP time. (CPU Expensive)
* Sender Verification
The two options that say "Skip scanning messages for virii/malware or
spam when the scanner is unavailable" do not have any impact if you are
using MailScanner instead of cPanel's implementation of SpamAssassin.
We recommend disabling:
* Sender Verification Callouts
RBLs: We recommend enabling one or both of these RBLs in
order to block such emails at exim rather than have them processed by
MailScanner. If you enable this you should set "Spam List = " to a blank
field in the MailScanner Configuration. Enabling this in exim rather
than MailScanner should help reduce the resource usage by MailScanner.
Security: Leave as cPanel default or modify as desired.
SpamAssassinTM Options: All should be Off or Disabled.
Note: None of the SpamAssassin options in any of the sections should be enabled if you are running MailScanner.
Another note: If any of the above options are missing or there are
additional options, you are probably using an earlier or later version
of cPanel/WHM than the one referred to in this FAQ. We try to update
this FAQ when these options change but there may be a slight delay.