At 11:30 AM 10/9/2006, you wrote:
spamc is a small executable that hands off the message to spamd for
processing.
Ahh ok.
You can run it from the command line the same way you do with
spamassassin.
spamc < inputfile > outputfile
You also might want to check the process that is running to see
exactly what settings it is using.
ps -ef | grep spamd
For macs, the -ef doesn't work. ps aux is I believe the equivilant:
root 57 0.0 2.7 43692 14196 ?? Ss 10:35AM 0:06.62
/opt/local/bin/perl -T -w /opt/local/bin/spamd
root 290 0.0 3.5 44548 18376 ?? S 10:36AM 0:19.29
spamd
child
root 291 0.0 3.0 43308 15772 ?? S 10:36AM 0:00.85
spamd
child
root 675 0.0 0.0 8780 8 p0 R+ 11:53AM 0:00.00
grep spamd
Ok, it appears spamc definitely isn't using network tests.
Just ran a message through spamc and spamassassin:
spamc:
X-Spam-Level: *
X-Spam-Status: No, score=1.6 required=5.0 tests=EXTRA_MPART_TYPE,INFO_TLD,
UPPERCASE_25_50 autolearn=no version=3.1.6
spamassasin:
X-Spam-Level: *************
X-Spam-Status: Yes, score=13.3 required=5.0 tests=DNS_FROM_RFC_WHOIS,
EXTRA_MPART_TYPE,INFO_TLD,UPPERCASE_25_50,URIBL_AB_SURBL,
URIBL_JP_SURBL,URIBL_OB_SURBL,URIBL_WS_SURBL autolearn=no
version=3.1.6
I called both spamc and spamassassin with the full path.
Evan
