Ok, I've googled this, and perhaps I'm not searching with the right
words or my search is too vague..
Running spamassassin on a os/x box,
SA is called from my procmail:
:0fw: spamassassin.lock
| spamc -s 512000
(Perhaps I have more than one spamc and I'm calling the wrong one?)
Just received a piece of spam with the below headers:
X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on
www-espphotography-com.local
X-Spam-Level: **
X-Spam-Status: No, score=2.4 required=5.0 tests=HELO_DYNAMIC_HOME_NL,INFO_TLD,
UNPARSEABLE_RELAY autolearn=no version=3.1.6
(Partial, obviously).
Ran it through spamassassin on the command line:
-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on
www-espphotography-com.local
X-Spam-Level: ********************
X-Spam-Status: Yes, score=20.2 required=5.0 tests=HELO_DYNAMIC_HOME_NL,
INFO_TLD,RCVD_IN_SORBS_DUL,RCVD_IN_WHOIS_BOGONS,UNPARSEABLE_RELAY,
URIBL_AB_SURBL,URIBL_JP_SURBL,URIBL_OB_SURBL,URIBL_SBL,URIBL_SC_SURBL
autolearn=spam version=3.1.6
Any hints of what to look for as to why mail being received isn't
scoring all that well?
The crontab entry launched on startup is:
<http://www.espphotography.com:10000/cron/edit_cron.cgi?idx=11>/opt/local/bin/spamd
Any clues?
Thanks.
Evan
