I was wondering - the current implimentation of the clamav plugin calls 'clamscan'. Is there any particular reason why the clamd daemon isn't being used? I wrote my own plugin (clamav_clamd) that uses the Clamd module on CPAN to access the clamd daemon. So far it works great, but I haven't done any benchmarks. Its only been running for about 20 minutes now - no firey death yet.
Now to spamassassin, whenever I enable to built-in spamassassin plugin I get tons of files in my tmp folder. So, rather than figure out what is wrong I decided to do what I thought is right - use the Mail::Spamassassin module directly. Since I'm planning on running under PPerl I'm hoping that loading up the Spamassassin module doesn't waiste much resources (haven't benchmarked this either). Any comments? Should I not be doing this - any particular reason why the current plugin isn't doing this?
For a while there Rasjid Wilcox had been working on an all-in-one check_delivery plugin. Any reason why this isn't included in the qpsmtpd distribution by default? Seems to be a common enough request by qpsmtpd users.
Thanks for any advice and help,
Aran
PS: Before mentioned plugins available if anyone wants 'em.
#!/bin/sh QMAILDUID=`id -u smtpd` NOFILESGID=`id -g smtpd` exec /usr/local/bin/softlimit -m 25000000 \ /usr/local/bin/tcpserver -c 10 -v -R -p \ -u $QMAILDUID -g $NOFILESGID `head -1 config/IP` smtp \ ./qpsmtpd 2>&1
