I followed the various posts to install the ART packages (clamav, qmail-scanner, spamassassin 3.1). And everything seems to be working great!

However, I tried to modify the $sa_quarantine_site variable in qmail-scanner; because, ideally, I would like to have several levels of filtering. But setting the additional variables doesn't seem to have any effect.

In further investigating, I'm not sure that qmail-scanner is even calling spamassassin as one of its scanners. Is it possible to have qmail-scanner do a preliminary scan for all users (to reject or quarantine really "spammy" stuff)... and also have the user configurable aspect in Plesk remain intact?

Yes, you can run both, they are compatible with each other in that regard. If you look at the log in /var/spool/qmailscan/qmail-queue.log it will tell you what its doing to each message, and the debug output from the daemons can be included by using the debug variable. If SA isnt being run, try running qmail-scanner-reconfigure

Scott,

Do you happen to know which patches are compiled into the psa qmail package? I need a version of qmail that is compatible with Plesk and contains the "QMAILQUEUE" patch. I want to be able to try out various scanners other than the Perl qmail-scanner (like qsheff or simscan).

Is the atomic qmail compiled to be compatible with Plesk?

I have a pretty good idea of what they are yes, but I dont have a list or anything like that. Adding in the qmailqueue patch wont help on a PSA box, unless you also replace xinetd with tcpserver. The PG version of qmail does use tcpserver, and has the qmailqueue patch applied. However I wouldn't say its exactly compatible with PSA. Everything is in the right place, but its missing some things on the authentication side that would probably break it on a plesk box.

That being said, I originally did develop this for PSA integration, and there is a very old version of this in the atomic-unstable channel that is more or less compatible with PSA 7.0. You might be able to update this to do what you want:

http://3es.atomicrocketturtle.com/atomi ... t/9/SRPMS/

I abandoned the design because of the tcpserver requirement, and eventually went with what is in PG today.

Thanks again Scott! You definitely know your s*&%.

It sounds like it might be easier (and safer) to just create a dedicated PG box, and use that to screen all the emails before passing them over to the Plesk machines.

Yeah that was my reasoning too, I wanted to make it maintainable and largely PG has been. Generally you set the box up, configure a few things, and then forget about it. I've had some running for over a year without so much as a reboot.

Tuning is where the maintenance comes in, so one thing you might to look into is storing the settings (including bayes and awl) in mysql, which you could tie into a web interface for controlling SA. Ive got one already in the squirrelmail rpm.