James Butler
2009-Apr-17 18:58 UTC
[Dovecot] For the record: Postfix+Spamassassin+ClamAV+Dovecot
Postfix 2.5.5 SpamAssassin 3.2.5 (under Perl 5.10.0) ClamAV 0.95.1 Dovecot 1.2.rc2 works fine on Fedora 10. Installed Dovecot and ClamAV from source and everything else using yum. I'm using the ClamAV plugin for Spamassassin: http://wiki.apache.org/spamassassin/ClamAVPlugin I'm calling Spamassassin with: /etc/postfix/main.cf: mailbox_command = /usr/bin/spamc -f -e /usr/local/libexec/dovecot/deliver Postfix hands off to Spamassassin, which processes ALL mail (not just attachments) through the ClamAV plugin before parsing for spam, and then hands the whole mess off to Dovecot for 'deliver' to handle. How simple is that? Since ClamAV scanns all mail, it might be too processor-intensive for really large mail systems, but it is working great for our 120+ user system with lots of spam coming in. If you're using Procmail or some other preprocessor that can hand off to a pipe, then you could skip the plugin and pipe messages over a certain size (i.e. >1024) to clamd, instead. Enjoy! James
Seth Mattinen
2009-Apr-17 19:29 UTC
[Dovecot] For the record: Postfix+Spamassassin+ClamAV+Dovecot
James Butler wrote:> Postfix 2.5.5 > SpamAssassin 3.2.5 (under Perl 5.10.0) > ClamAV 0.95.1 > Dovecot 1.2.rc2 > > works fine on Fedora 10. > > Installed Dovecot and ClamAV from source and everything else using yum. > > I'm using the ClamAV plugin for Spamassassin: > http://wiki.apache.org/spamassassin/ClamAVPlugin > > I'm calling Spamassassin with: > > /etc/postfix/main.cf: > mailbox_command = /usr/bin/spamc -f -e /usr/local/libexec/dovecot/deliver > > Postfix hands off to Spamassassin, which processes ALL mail (not just > attachments) through the ClamAV plugin before parsing for spam, and then > hands the whole mess off to Dovecot for 'deliver' to handle. > > How simple is that? > > Since ClamAV scanns all mail, it might be too processor-intensive for > really large mail systems, but it is working great for our 120+ user > system with lots of spam coming in. If you're using Procmail or some other > preprocessor that can hand off to a pipe, then you could skip the plugin > and pipe messages over a certain size (i.e. >1024) to clamd, instead. >SpamAssassin is more of a CPU hog than Clam is, although that depends if you're scanning large files or not. If my mail systems aren't falling over while running Clam and SA (although I don't use the plugin, I scan the stream with clamd before SA) the average system should be fine too. ~Seth
Egbert Jan van den Bussche
2009-Jun-01 08:41 UTC
[Dovecot] For the record: Postfix+Spamassassin+ClamAV+Dovecot
> -----Oorspronkelijk bericht----- > Van: dovecot-bounces+egbert=vandenbussche.nl at dovecot.org > [mailto:dovecot-bounces+egbert=vandenbussche.nl at dovecot.org] > Namens James Butler > Verzonden: vrijdag 17 april 2009 20:58 > Aan: Dovecot Mailing List > Onderwerp: [Dovecot] For the record: > Postfix+Spamassassin+ClamAV+Dovecot > > > Postfix 2.5.5 > SpamAssassin 3.2.5 (under Perl 5.10.0) > ClamAV 0.95.1 > Dovecot 1.2.rc2 > > works fine on Fedora 10. > > Installed Dovecot and ClamAV from source and everything else > using yum. > > I'm using the ClamAV plugin for Spamassassin: > http://wiki.apache.org/spamassassin/ClamAVPlugin > > I'm calling Spamassassin with: > > /etc/postfix/main.cf: > mailbox_command = /usr/bin/spamc -f -e > /usr/local/libexec/dovecot/deliver > > Postfix hands off to Spamassassin, which processes ALL mail (not just > attachments) through the ClamAV plugin before parsing for > spam, and then hands the whole mess off to Dovecot for > 'deliver' to handle. > > How simple is that? > > Since ClamAV scanns all mail, it might be too > processor-intensive for really large mail systems, but it is > working great for our 120+ user system with lots of spam > coming in. If you're using Procmail or some other > preprocessor that can hand off to a pipe, then you could skip > the plugin and pipe messages over a certain size (i.e. >1024) > to clamd, instead. > > Enjoy! > > JamesHi! Apologies for digging an old thread from the bin. I was wondering how this relates to Amavisd? Should I regard the proposed plugin solution as a 'poor mans' solution when one does not want to install amavis? Thanks! Egbert Jan (NL)