On Wed, 9 Mar 2005, Dave Goodrich wrote:
[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 host
At 01:31 PM 3/9/2005, [EMAIL PROTECTED] wrote:
$SPAMHOME/bin/spamd -d --syslog-socket=inet -r /var/tmp/spamdnew.pid \
--allowed-ips=
But I don't even see anything in syslog on hostB.
erm, that's not going to cause it to syslog to hostB... that's going to
cause spamd to allow hostB to run spamc
[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 do
[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)
And on
