>From the messages I've seen recently on this subject, I don't think I'm the
only person who can't get the spamc/spamd combination working.  I'm using SA
v2.11 on a Mandrake 8.1 system with perl 5.6.1.  (Well, now I'm running
2.20.  See below.)

If I run spamd from a terminal window as root like so:

    spamd -D -L

I can feed it spam via spamc to my heart's content and it all works as
expected.  (In fact, I fed it about 23,000 saved spams earlier.  It
identified 19,000 as spam and 4,000 as not.  But that, as they say, is
another story.)

Confident that I wasn't screwing up too badly, I modified the distributed
RH/Mandrake start script so it invoked spamd like

    daemon spamd -d -c -a -D -L 
                                      
(I just added the -D and -L flags.)  I then fed it a single message I had
saved that SA had already marked as spam like so:

    spamassassin -d < spam.txt | spamc | less

The message came out with no SA markings.  Furthermore, where the manually
started spamd ripped through the messages like a hot knife through butter,
it took about 30 seconds before less showed me the message.

I took a look in /var/log/syslog.  It showed a whole raft of debug messages
when it started:

    May 16 20:00:19 localhost spamd: debug: ignore: test message to precompile 
patterns and load modules
    May 16 20:00:19 localhost spamd: debug: using "/usr/share/spamassassin" for 
default rules dir
    May 16 20:00:19 localhost spamd: debug: using "/etc/mail/spamassassin" for site 
rules dir
    May 16 20:00:19 localhost spamd: debug: running header regexp tests; score so far=0
    May 16 20:00:19 localhost spamd: debug: running body-text per-line regexp tests; 
score so far=4.8
    May 16 20:00:19 localhost spamd: debug: running raw-body-text per-line regexp 
tests; score so far=4.8
    May 16 20:00:19 localhost spamd: debug: running full-text regexp tests; score so 
far=4.8
    May 16 20:00:19 localhost spamd: debug: local tests only, ignoring Razor
    May 16 20:00:19 localhost spamd: debug: is DNS available? 0
    May 16 20:00:19 localhost spamd: debug: checking RBL orbs.dorkslayers.com., set 
relay
    May 16 20:00:19 localhost spamd: debug: checking RBL inputs.orbz.org., set relay
    May 16 20:00:19 localhost spamd: debug: checking RBL relays.osirusoft.com., set 
relay
    May 16 20:00:19 localhost spamd: debug: checking RBL relays.ordb.org., set relay
    May 16 20:00:19 localhost spamd: debug: checking RBL ipwhois.rfc-ignorant.org., 
set rfci
    May 16 20:00:19 localhost spamd: debug: checking RBL relays.visi.com., set relay
    May 16 20:00:19 localhost spamd: debug: checking RBL results in set relay for 
127.0.0.6
    May 16 20:00:19 localhost spamd: debug: checking RBL results in set relay for 
127.0.0.4
    May 16 20:00:19 localhost spamd: debug: 19357 Trying to get lock on 
/root/.spamassassin/auto-whitelist pass 0
    May 16 20:00:19 localhost spamd: debug: Tie-ing to DB file R/W in 
/root/.spamassassin/auto-whitelist
    May 16 20:00:19 localhost spamd[19358]: server started on port 783 
    May 16 20:00:19 localhost spamd: debug: auto-whitelist (db-based): 
[EMAIL PROTECTED] scores 2/14.2
    May 16 20:00:19 localhost spamd: debug: AWL active, pre-score: 7.1, mean: 7.1
    May 16 20:00:19 localhost spamd: debug: Post AWL score: 7.1
    May 16 20:00:19 localhost spamd: debug: add_score: New count: 3, new totscore: 21.3
    May 16 20:00:19 localhost spamd: debug: DB addr list: untie-ing and destroying 
lockfile.
    May 16 20:00:19 localhost spamd: debug: DB addr list: file locked, breaking lock.
    May 16 20:00:19 localhost spamd: debug: is spam? score=7.1 required=5
    May 16 20:00:19 localhost spamd: spamd startup succeeded

After that, all it gave me was a single line for each invocation of spamc:

    May 16 20:00:40 localhost spamd[19358]: connection from localhost.localdomain [ 
127.0.0.1 ] at port 33642 

I tried once more, this time modifying the spamd command line like so:

    daemon spamd -d -D -L 

That worked.  (Ran fast, qualified the message as spam.)

One more try, this time getting rid of -L.  It ran slower (about six seconds
to display), but did mark the message as spam.

Upgrading to 2.20 didn't help with the -a problem, so for now I'm running
spamd with the "-d -c -L" set of flags.

Thx,

-- 
Skip Montanaro ([EMAIL PROTECTED] - http://www.mojam.com/)
"Excellant Written and Communications Skills required" - seen on chi.jobs

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to