Paul 'Baloo' Johnson <[EMAIL PROTECTED]> writes: > Would it be possible for spamassassin to be run at a level where > all inbound mail gets run through it and spam forwarded to the local > postmaster?
What I did was set up my firewall to forward to an internal relay on port 2025. The daemon on that port runs spamassassin on each message, then forwards the (possibly munged) message to port 25. If you don't have a firewall, you could make the spamassassin daemon listen on port 25 and set up your real mail server to listen on some other port. I took this approach because my postfix config is fairly complex, with multiple mail delivery agents. It was easier to get the spam check out of the way before it hit postfix. The SpamAssassin package comes with a spamproxyd that does this for you. However, that daemon is not very tolerant of exceptional conditions so I don't recommend using it. I found this out when 1 hours' worth of mail went into the bitbucket due to a full disk on my mail server; fortunately it was only an hour. I just wrote a replacement that does better error checking, which seems much more robust. Also keep in mind that SpamAssassin slows things down. If your mail server is having trouble keeping up now, it won't keep up at all if SpamAssassin has to vet each message. -- Dave Carrigan ([EMAIL PROTECTED]) | Yow! Impudent.. Yet possessing UNIX-Apache-Perl-Linux-Firewalls-LDAP-C-DNS | a certain ALUMINUM SILICATE Seattle, WA, USA | overbite....Needs REDDY-WHIP!! http://www.rudedog.org/ | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
