I've never used that method myself. However, if it works
then in theory you can turn on/off SA on a per-domain basis.
Here's how we are doing it: We use qmail-scanner along with
the QMAILQUEUE patch. Basically, qmail-scanner is configured to use
clamav and SA for scanning. Since qmail-scanner is called in place
of qmail-queue (done by setting the QMAILQUEUE environment variable
in tcpserver) it scans all incoming mail for viruses and spam. Plus,
we can use smtproutes to provide virus and spam filtering. (Just MX
their domain to us, use smtproutes to route to their real mail
esrver, and on the way through it gets scanned.)
To me, the best method is using qmail-scanner, but that has
the side effect that you can't toggle on/off spam and virus filtering
on a per-user or per-domain basis. As long as you can live with that
(I can) then I'd go with qmail-scanner. :)
Unless the network is lying to me again, John McGivern said:
> I wanted to confirm what was the best way to implement spam assassin with a
> qmail/vpopmail/qmailadmin setup.
> Somebody else had set this up a while ago - I think it is working but I'm not sure
> if it is affecting other mail deliveries.
> Basically I have spam assassin installed and I have a .qmail-default in every domain
> folder on my server. It looks like this:
> | /var/qmail/bin/preline -d /var/qmail/bin/bouncesaying "[message to bounce back if
> not SPAM]"
> | /home/vpopmail/bin/vdelivermail ' ' bounce-no-mailbox
> Does this look like it should work okay with spam assassin? I notice others
> .qmil-default files look a little different. This was set up to handle all spam on
> a domain basis.
> John McGivern
Jeremy Gault <[EMAIL PROTECTED]>
Network Administrator / MIS, WinWorld Corporation
(v) 4237-473-8084 // (f) 423-472-9465