New MailScanner Front-End (MSFE) v4.0


  • Installation no longer attempts to recreate mailscanner database or update the MailScanner configuration settings if the mailscanner MySQL database already exists
  • Added whitelisting to virus.scanning.rules for mails released from quarantine (i.e. sent locally and from the postmaster@hostname address)
  • Moved to a simpler installer script using the license server
  • Timeout version checks incase version server is unavailable
  • Added check for incorrect ClamAV (or clamavconnector) installation which causes MailScanner to be disabled
  • Improved support for remote MySQL database servers

Ouch, that hurt!

Our apologies if you’ve been trying to contact us today. We had a main hard drive failure on our configserver/waytotheweb server which took us down for a while.Many thanks to our server provider Coreix for their very prompt work in getting us back up with a new disk.I then had the fun of running our own restore service on our own server ;)Well, we’re back up and running now 😀

New csf v2.60

Changes and additional OS support:

  • Added log file locations to csf.conf
  • openSUSE v10 compatible (generic)
  • Debian v3.1 (sarge) compatible (generic)
  • Unbuntu v6.06 LTS compatible (generic)
  • Added installation check for the LWP (libwww-perl) perl module
  • Ran spell checker against the readme.txt file

New MSFE v3.9


  • Fixed problem with installer where wasn’t being copied on installation
  • Added new IP licensing scheme. You will need to email your order details and servers main IP address to to be able to upgrade MSFE in future releases
  • Updated post-upgrade message to reflect the new route to the MSFE WHM UI
  • Added link to MSFE changelog if an upgrade is available

For this version, you can download the update from – if you don’t have a download account, please email and request one, and be sure to include the name under which you originally ordered and your servers IP address for future updates. Future versions will then be available for upgrade from within WHM.

MailScanner: Problems for Liquidweb clients

We have found that some clients hosted by Liquidweb are seeing the message “MailScanner Status: Disabled” at the top of their MailScanner front-end after a cPanel upgrade.The problem has been caused by Liquidweb’s installation of clamav rpms that modify the exim configuration each time cPanel is upgraded, thus breaking MailScanner. We have been uninstalling these rpms as part of our mailscanner install for several months now but it appears that Liquidweb has re-installed those rpms and the problem has arisen again since a recent cPanel upgrade.Fix instructions follow.If you would like us to perform the fix for you, then please log a ticket on our helpdesk with access details. There will be a $30 (half hour) charge for performing this service.Here is how to fix it:1. Remove /etc/exim.conf.local to start with a clean copy.

/bin/mv -fv /etc/exim.conf.local /etc/exim.conf.local.old/scripts/buildeximconf

2. Remove all installs and rpms of clamav and reinstall clamav.

killall clamdrpm -e clamav-db clamd clamav clamav-devel/bin/rm -Rfv /usr/bin/clam*/bin/rm -Rfv /usr/sbin/clam*/bin/rm -Rfv /usr/lib/libclam*/bin/rm -Rfv /usr/share/clam*/bin/rm -Rfv /usr/include/clam*/bin/rm -Rfv /usr/bin/freshclam*/bin/rm -Rfv /usr/etc/clamav*/bin/rm -Rfv /usr/local/bin/clam*/bin/rm -Rfv /usr/local/sbin/clam*/bin/rm -Rfv /usr/local/lib/libclam*/bin/rm -Rfv /usr/local/share/clam*/bin/rm -Rfv /usr/local/include/clam*/bin/rm -Rfv /usr/local/bin/freshclam*/bin/rm -Rfv /usr/local/etc/clamav*useradd clamavgroupadd clamavcd /root/rpmswget -xzf clamav-*cd clamav-*./configure –disable-zlib-vcheckmakemake installreplace “Example” “#Example” — /usr/local/etc/freshclam.confreplace “Example” “#Example” — /usr/local/etc/clamd.conffreshclamcd ../bin/rm -Rf clamav-*cd /root/rpms/touch /var/log/clam-update.logchown clamav:clamav /var/log/clam-update.log/scripts/perlinstaller –force Mail::ClamAV

3. Upgrade MailScanner (per instructions on website – to add correct configuration to exim.conf.local. Should be able to select option 2 (quick perl module check). You will need to do ths at the command line since you are probably already running the latest version of MailScanner.4. Re-add the dictionary attack ACL, log_selector, etc. to exim.conf.local via WHM exim configuration editor, if desired.

New csf v2.57


  • New feature: WHM UI mod_security v1 display last X entries in the audit_log
  • New feature: WHM UI mod_security v1 edit files or directories in /usr/local/apache/conf/ that are prefixed with modsec or mod_sec
  • Tweaked the pre-configured Firewall Security Level settings