I dont want to automatically delete the spam coming to my inbox but at the same time I dont want to wade through it to find the ham. Also when I check my mail on a mobil device downloading all those spam Subject: headers takes a while.
I found a great howto on using procmail to route the spam to an IMAP folder so it can be viewed later.

Note that the part about installing safecat is irrelevant if you have procmail >= 3.14.

http://www.chrisbeach.co.uk/view/tech/m ... nder_plesk

The procmail script could even be modified to trigger on a certain spam level.

here is the .procmailrc code without safecat:

Better yet...
I have the spam forward to another address using

instead of

you can do this with qmail-scanner too, based on score, your options are:

Tag/Release
Reject at the SMTP layer or Delete
move to a quarantine folder

So I tag/quarantine at 4, and delete at 7

Can I still use the PSA version of SA when using qmail-scanner to do this?
I mean, do I have to use the qmail-scanner SA to markup the spam for qmail-scanner to filter the messages? Or can qmail-scanner filter based on the markup done by PSA's SA? I want my users to be able to use Plesk to manage their spam settings.

Short version... uhhh no. Theres no way to control qmail-scanner from psa-spamassassin, and vice versa. At least not without coding something (which someone should do already... come on peeps pony up and help me out here!)

In order of what happens on the system it works like this:

1) mail hits smtpd
2) smptd hands off to qmail-scanner
3) qmail-scanner calls antivirus scanners, then spamassassin
4) qmail-scanner calls qmail-queue
5) qmail-queue dumps to queue, qmail-local reads queue
6) qmail-local reads users .qmail for delivery instructions

At this point, if you dont have psa-spamassassin, the .qmail file just dumps to the user's Mailbox. If you do, then the .qmail file has a line to call spamc, and spamassassin would be run again, with settings of the user. Thats why I say they arent "compatible", they really are its just you're using spamassassin twice when you do it. At this point messages are already marked as spam or ham, so you could just do your filtering here. Step 3 is where qmail-scanner implements its filtering rules (tag/quarantine/delete/reject).

SWSoft?

Are you listening?

Haha, come on I know I'm not the only one out here that can code.