MailScanner and spamd/spamc
mailscanner at ecs.soton.ac.uk
Fri Jun 27 21:03:37 IST 2003
Using spamc/spamd will work slower than the way MailScanner already does it.
SpamAssassin is essentially a function library, all written in Perl. The
"spamc/spamd" system is just a front-end for it. MailScanner doesn't use
any front-end, it calls the library directly which is by far the fastest
way to do it. Using spamc/spamd would merely add extra code in the way that
achieves nothing except slowing everything down.
At 20:53 27/06/2003, you wrote:
>We tried using SpamAssassin with MailScanner and we found that it made mail
>processing really slow. So I would like to try the spamd/spamc
>approach. Can anyone give me some tips on how to make this work. The
>SpamAssassin documentation says,
>"Simply copy the two executables to where you want them. Then, configure
>your system to run spamd in the backgroup, and where your mailer invokes
>'spamassassin' instead invoke 'spamc'. ".
>When I used SpamAssassin with MailScanner, I had to set "Use SpamAssassin"
>to "yes" in the MailScanner.conf file. If I want to use spamc, what do I
>do? What do they mean by, "where your mailer invokes 'spamassassin'
>instead invoke 'spamc'. "?
Professional Support Services at www.MailScanner.biz
MailScanner thanks transtec Computers for their support
More information about the MailScanner