ConfigServer Community Forum

Also, I see from one of your other posts on the forum that you changed the location of some of MailScanner's configuration files (spam.whitelist.rules and spam.blacklist.rules). If you changed this, perhaps you have also changed something else which has broken the MailScanner upgrade, or perhaps the...

What version did you upgrade MailScanner from? Had it not been upgraded in a while? Check in your MailScanner Configuration for the value of "Spam List Definitions". It should be "%etc-dir%/spam.lists.conf". If that's correct, check the value of "%etc-dir%" (near the to...

Hi Joe, Ham is email that is not spam, in other words legitimate mail, whether personal or business. If you go into MailWatch and mark an email as Ham, you are telling SpamAssassin that the mail is not a spam. Normally you would only do this if SpamAssassin/MailScanner marked the mail as spam and yo...

You can't use cPanel's clamavconnector with MailScanner. It will break MailScanner. I don't know why you're getting that error in cPanel, but since you can't use cPanel's clamav with MailScanner it doesn't matter, unless of course you want to uninstall MailScanner so you can use cPanel clamav.

Are you still seeing this segmentation fault problem? I notice that you (I think it is you) posted to the MailScanner mailing list as well.

It shouldn't come back if you comment out the Rule2XSBody plugin in /etc/mail/spamassassin/v320.pre.

This type of issue might also be fixed by running one or both of the following: /usr/mscpanel/mscheck.pl and/or the appropriate one of the following two: /usr/mscpanel/msswitch.pl in # (if you are running incoming only scanning) or /usr/mscpanel/msswitch.pl inout # (if you are running both in and ou...

We have seen this on one server, it seemed there was a problem with the compiled SpamAssassin rules. These are located in: /var/lib/spamassassin/compiled/3.002004/ We removed that directory and commented out the following plugin in /etc/mail/spamassassin/v320.pre: loadplugin Mail::SpamAssassin::Plug...

Bayes should be enabled by default - where do you see that it is disabled? Do you have the MS WHM front-end with MailWatch? If so, are you seeing any bayes scores in the spam reports? To ensure that your spamassassin rules are updated regularly, follow the steps in this FAQ: http://www.configserver....

Excessnet, there shouldn't really be any connection between exim configuration errors and mail delivery problems, and your spamassassin/mailwatch fix, but if everything is now working for you that's great.