Hi, as I suggested in this ticket http://trac.macports.org/projects/macports/ticket/11054 spamassassin installation needs 2 additional perl modules, so sa-update can work. Sa-update is needed to update spamassassin rules, and when I did the update my installation started working better (it catches a lot more spam). The 2 modules are p5-archive-tar and p5-lwp-authen-wsse. Gufo
Can somebody point me to setup instructions for spamassassin with Postfix when both are loaded by MacPorts? I have found a wide range of instructions, but most assume Debian or MacOSX server and they disagree wildly. I have spamassassin "installed" but not, apparently, hooked into Postfix.
I recommend installing amavisd and ClamAV to go along with this. If you Google this, you'll likely find a number of guides you can use for this setup. On Nov 27, 2006, at 7:50 PM, Russell Gold wrote:
Can somebody point me to setup instructions for spamassassin with Postfix when both are loaded by MacPorts? I have found a wide range of instructions, but most assume Debian or MacOSX server and they disagree wildly. I have spamassassin "installed" but not, apparently, hooked into Postfix. _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
On Nov 27, 2006, at 7:50 PM, Russell Gold wrote:
Can somebody point me to setup instructions for spamassassin with Postfix when both are loaded by MacPorts? I have found a wide range of instructions, but most assume Debian or MacOSX server and they disagree wildly. I have spamassassin "installed" but not, apparently, hooked into Postfix.
It depends a lot on how much traffic your box gets and what kind of setup you want. If you already want/need procmail (ie, you've set mailbox_commaind to /usr/bin/procmail in postfix's main.cf), you can just add something like this to your /etc/procmailrc: DROPPRIVS=yes :0fw: spamassassin.lock * < 256000 | /opt/local/bin/spamassassin You can make things a little more efficient by using spamc/spamd, or by setting up a postfix content filter (or a sendmail-compatible milter) to avoid the overhead of fork()/exec()ing procmail and perl for every incoming mail. See http://wiki.apache.org/spamassassin/IntegratedInMta -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
participants (4)
-
Daniel J. Luke
-
gaudente＠gmail.com
-
Joe Auty
-
Russell Gold