[EMAIL PROTECTED] wrote:
What is involved in setting up spamassassin to run on a remote machine?
After installing it on hostA (mailserver) and hostB, I get onto hostA and tweak my procmailrc to have
:0fw: $HOME/spamassassin.lock | $SPAMHOME/bin/spamc -d hostB.FQDN
... (if spam, then filter)
What does a command line test tell you?
cat your.testmsg | /your/path/bin/spamc -d yourhost.com
And on hostB, I start it up with
$SPAMHOME/bin/spamd -d --syslog-socket=inet -r /var/tmp/spamdnew.pid \ --allowed-ips=<ip of hostA,ip of hostB>
It would tell you there is no spamd listening, you have spamc making a tcp connection to spamd on another host that is listening to a socket.
You need -i ip.address in your spamd startup.
http://spamassassin.apache.org/full/3.0.x/dist/doc/spamd.html
DAve
But I don't even see anything in syslog on hostB.
TIA
=-=-=-=-=-=-=-=-=-=- generated by /dev/dave -=-=-=-=-=-=-=-=-=-=-=-= David Stern University of Maryland Institute for Advanced Computer Studies
-- Dave Goodrich Systems Administrator http://www.tls.net Get rid of Unwanted Emails...get TLS Spam Blocker!
