score=0/spamc errors

[Laramie Combs]

I have never seen a score of exactly 0 from spamassassin.

Mailscanner should not have to connect to spamd for its scanning - it just
uses the spamassassin program for scanning and scoring.

Spamd probably got started running with your upgrade to the SA 2.55.

Are you seeing other mail messages getting scores from MailScanner?

-Laramie Combs
Network Analyst
Appalachian State


----- Original Message -----
From: "Matthew Bowman" <mbowman at UDCOM.COM>
To: <MAILSCANNER at JISCMAIL.AC.UK>
Sent: Tuesday, July 08, 2003 4:56 PM
Subject: score=0/spamc errors


> Hi
>
> I have had a client call me today about a problem whereby an e-mail
> doesn't get scored..
>
> In the headers it says SCORE=0 but I cannot find any trace of this in the
> maillog.
>
> However I do see the mail be routed as follows:
>
> Jul  8 12:42:21 smithers sendmail[21543]: h68GgK621543:
> from=<1zbygm6VcbmPdijo463wtpZP7mIjEe at 5948.bounce.e-i1.com>, size=1568,
> class=0, nrcpts=1,
> msgid=<1zbygdxMTSdGUZafvxunkgQGyd9a5V at 1zbygQk9GFQ3HMNSikhaXTD3lQwNsI>,
> proto=SMTP, daemon=MTA, relay=b7.e-i1.com [63.251.54.87]
> Jul  8 12:42:21 smithers sendmail[21543]: h68GgK621543:
> to=<garyl at gormanrupp.com>, delay=00:00:01, mailer=smtp, pri=31568,
> stat=queued
> Jul  8 12:42:22 smithers sendmail[21551]: h68GgK621543:
> to=<garyl at gormanrupp.com>, delay=00:00:02, xdelay=00:00:00, mailer=smtp,
> pri=121568, relay=grcmail1.gormanrupp.com. [63.173.204.4], dsn=2.0.0,
> stat=Sent (Message accepted for delivery)
>
> No indication of Spam Checking...
>
> Maillog has also reported this
>
> Jul  8 16:54:53 smithers spamc[1410]: connect() to spamd at 127.0.0.1
> failed, retrying (1/3): Connection refused
> Jul  8 16:54:54 smithers spamc[1410]: connect() to spamd at 127.0.0.1
> failed, retrying (2/3): Connection refused
> Jul  8 16:54:55 smithers spamc[1410]: connect() to spamd at 127.0.0.1
> failed, retrying (3/3): Connection refused
> Jul  8 16:54:56 smithers spamc[1410]: connection attempt to spamd aborted
> after 3 retries
>
> Are these linked? or seperate issues?
>
> Problems started to happen after the upgrade to MS 4.22-4 and SA 2.55
>
> Any help would be appreciated
>
> Thank you
>
> Matthew Bowman
> UDCom
>