Re: running spamd remotely

2005-03-09 Thread dave
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 hostB.FQDN
... (if spam, then filter)
What does a command line test tell you?
cat your.testmsg | /your/path/bin/spamc -d yourhost.com

Great idea. First, as mentioned below, I changed startup to add "-i"  ie
$SPAMHOME/bin/spamd -d --syslog-socket=inet -r /var/tmp/spamdnew.pid \
  --allowed-ips=HostA-ip,HostB-ip,127.0.0.1 -i HostB
then on HostA,
% cat /etc/motd | $SPAMHOME/bin/spamc -d hostB
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on
HostB.fqdn
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 required=4.0 tests=ALL_TRUSTED,MISSING_DATE,
MISSING_SUBJECT,NONLOCAL autolearn=unavailable version=3.0.2

(HostA had SA v.265 installed, HostB has SA v3.02)
and the above indeed spews spamd stuff to syslog on hostB

And on hostB, I start it up with
$SPAMHOME/bin/spamd -d --syslog-socket=inet -r /var/tmp/spamdnew.pid \
  --allowed-ips=
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.

Thanks a lot for your help!
 =-=-=-=-=-=-=-=-=-=-  generated by /dev/dave -=-=-=-=-=-=-=-=-=-=-=-=
 David SternUniversity of Maryland
   Institute for Advanced Computer Studies


Re: running spamd remotely

2005-03-09 Thread Matt Kettler
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 and connect.

If you want to redirect your syslog output, do that in syslog.conf.  



Re: running spamd remotely

2005-03-09 Thread Dave Goodrich
[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=
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 SternUniversity of Maryland
   Institute for Advanced Computer Studies


--
Dave Goodrich
Systems Administrator
http://www.tls.net
Get rid of Unwanted Emails...get TLS Spam Blocker!


Re: running spamd remotely

2005-03-09 Thread Daryl C. W. O'Shea
[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 hostB, I start it up with
$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.
TIA
I'm assuming when you say you "don't see anything", you mean you don't 
see anything about 'hostA' trying to connect.

Do you have a firewall running on the spamd host?  You'll need to open 
up tcp port 783 if you do.

Daryl


running spamd remotely

2005-03-09 Thread dave
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 hostB, I start it up with
$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.
TIA
 =-=-=-=-=-=-=-=-=-=-  generated by /dev/dave -=-=-=-=-=-=-=-=-=-=-=-=
 David SternUniversity of Maryland
   Institute for Advanced Computer Studies