Yes, there is no clear documentation for this setup. After piecing together
many snippets, it is now working very well for me.

Like someone else mentioned, I would suggest using qmail-scanner. This way,
all mail is scanned and tagged with the X-Spam-Status header before final
delivery. Qmail-scanner can be used to run clamav (this is what I do), maybe
with less cpu usage (if you are running it as a file access-run daemon).
Qmail-Scanner needs the qmail-queue patch for qmail, to allow an alternate
program (ie qmail-scanner) to run instead of qmail-queue.

See this to imagine the qmailqueue patch:
http://www.nrg4u.com/qmail/the-big-qmail-picture-103-p1.gif (this helped me
a lot. I am not sure where the original location for this was, somewhere
related to the qmail sites, oh well)

But, as you say you have clamav running, then you may be fine with using the
.qmail files to scan and filter the messages, ie without qmail-scanner. You
are using procmail, but I imagine something very similar to the following
setup could be created (as this guide uses maildrop for message filtering)

http://www.mail-archive.com/[EMAIL PROTECTED]/msg13511.html
Where is says [EMAIL PROTECTED] in the above document, use [EMAIL PROTECTED]
Also, I had to change a few things to fet this to work for me, like the
locations of the binaries, and the X-Spam-Status header name, etc.

This way the current virtual user enviroment variables are used to get
proper Maildir delivery information. Hope this helps.

Also, if you consider the qmail-scanner route, I found this to be very
helpful: (though I would not use their spamassassin configuration beyond
installation, as it is out of date)
Do note that I would use tcp.smtp to control who (in relation to ip
adressing) gets their smtp traffic scanned, where in the above document,
they enable scanning of all mail (by nature of how they set the QMAILQUEUE
environment variable) when you might want only inbound mail scanned (to save
resources). The tcp.smtp setup example is in the qmail-scanner

I am happy to help further, as I am interested in writing this procedure up,
as a HOWTO based on the various documents mentioned. I also had a long list
of questions that I ultimately answered.

So keep on this thread if you have more questions, so I can disect it later.

Good luck,

Alex Martin

----- Original Message ----- 
From: "Vpopmail List" <[EMAIL PROTECTED]>
Sent: Monday, September 22, 2003 12:14 PM
Subject: [vchkpw] Spamassassin + qmail + vpopmail + procmail + courier-imapd
+ squirrelmail + qmail-scanner + clamav

Hello list ..

I tried the gentoo list with this problem, but no luck ..

I have finally taken the shot at trying to get this working ..

What is working?

Qmail, vpopmail, courier-imapd, qmail-pop3d and squirrelmail, qmail-scanner,
clamav(minor problems)

this all works ...

what I am trying to involve now is
procmail and spamassassin

there really isn't much documentation to get this all working especially
under gentoo .. but I don't think there is much to configure with either of
these packages ..
.. so I was wondering if I'd get any help here ..

I think that vpopmail being involved is what is confusing me ..

most have the $HOME as /home/USER/.maildir

well with vpopmail I have it as ..

/var/vpopmail/domains/USER/Maildir/ and from there it is new, cur, etc ..

also I do not see this X-Spam file anywhere?

any help is appreciated ..

thanks ..

Reply via email to