Re: Can't configure spamd correctly

2004-12-07 Thread Info
Well, some progress

1) The problem with spamd was that, running as vscan it couldn't read
/etc/mail/spamassassin. My own dumb fault, corrected this and the log
now looks a lot healthier.

2) Amavisd-new seems to call perl-spamassassing directly, and keeps
child processes running at the ready. So spamd was never being used, and
wouldn't benefit me if it were.

Conclusion: Don't use spamd.

Thanks for the help

Paul Hilton

On Mon, 2004-12-06 at 15:04, Theo Van Dinter wrote:
> On Mon, Dec 06, 2004 at 02:57:02PM -0500, Info wrote:
> > Why is spamd running with a home directory under /tmp ?
> 
> The debug output you've shown is the initial temp message that gets sent
> through spamd to "prime the pump", so to speak.
> 
> > Dec  6 14:12:13 Pangloss spamd[23172]: debug: ignore: test message to
> > precompile patterns and load modules
> 
> :)



Re: Can't configure spamd correctly

2004-12-07 Thread Info
Jack,

Thanks for the suggestion, I may indeed do that, but at the moment
spamd isn't generating any messages after its startup. (unless I telnet
to it)

I start spamd with a script that came with the rpm package from SuSE in
/etc/init.d, the options are specified in the file /etc/sysconfig/spamd,
and I currently have SPAMD_ARGS="-d -a -L -D -x -u vscan", and
/etc/init.d/spamd does:
startproc -p /var/run/spamd.pid $SPAMD_BIN $SPAMD_ARGS

Paul Hilton

On Tue, 2004-12-07 at 10:01, Jack L. Stone wrote:
> At 09:51 AM 12.7.2004 -0500, Info wrote:
> >Theo,
> >
> >Thanks for the reply, and there may be some truth in that, but I'm not
> >convinced that it is ever working correctly.
> >
> >There have been NO spamd debug messages in the log since then, despite
> >emails being scanned. 
> >
> >There is never any message saying it actually found the Bayes data. I am
> >not convinced that spamd has ever found it, or that it is ever actually
> >being used.
> >
> >If I telnet to port 783 I do get spamd debug messages.
> >
> >Paul Hilton
> >
> >
> 
> You could isolate the spamd-only messages by adding a syslog switch:
> 
> Like so:
> /usr/local/bin/spamd --syslog=local1 -u spamd -x -d -r
> /var/run/spamd/spamd.pid
> 
> HTH.
> 
> 
> Happy trails,
> Jack L. Stone
> 
> System Admin
> Sage-american



Re: Can't configure spamd correctly

2004-12-07 Thread Jack L. Stone
At 09:51 AM 12.7.2004 -0500, Info wrote:
>Theo,
>
>Thanks for the reply, and there may be some truth in that, but I'm not
>convinced that it is ever working correctly.
>
>There have been NO spamd debug messages in the log since then, despite
>emails being scanned. 
>
>There is never any message saying it actually found the Bayes data. I am
>not convinced that spamd has ever found it, or that it is ever actually
>being used.
>
>If I telnet to port 783 I do get spamd debug messages.
>
>Paul Hilton
>
>

You could isolate the spamd-only messages by adding a syslog switch:

Like so:
/usr/local/bin/spamd --syslog=local1 -u spamd -x -d -r
/var/run/spamd/spamd.pid

HTH.


Happy trails,
Jack L. Stone

System Admin
Sage-american


Re: Can't configure spamd correctly

2004-12-07 Thread Info
Theo,

Thanks for the reply, and there may be some truth in that, but I'm not
convinced that it is ever working correctly.

There have been NO spamd debug messages in the log since then, despite
emails being scanned. 

There is never any message saying it actually found the Bayes data. I am
not convinced that spamd has ever found it, or that it is ever actually
being used.

If I telnet to port 783 I do get spamd debug messages.

Paul Hilton


On Mon, 2004-12-06 at 15:04, Theo Van Dinter wrote:
> On Mon, Dec 06, 2004 at 02:57:02PM -0500, Info wrote:
> > Why is spamd running with a home directory under /tmp ?
> 
> The debug output you've shown is the initial temp message that gets sent
> through spamd to "prime the pump", so to speak.
> 
> > Dec  6 14:12:13 Pangloss spamd[23172]: debug: ignore: test message to
> > precompile patterns and load modules
> 
> :)



Re: Can't configure spamd correctly

2004-12-06 Thread Theo Van Dinter
On Mon, Dec 06, 2004 at 02:57:02PM -0500, Info wrote:
> Why is spamd running with a home directory under /tmp ?

The debug output you've shown is the initial temp message that gets sent
through spamd to "prime the pump", so to speak.

> Dec  6 14:12:13 Pangloss spamd[23172]: debug: ignore: test message to
> precompile patterns and load modules

:)

-- 
Randomly Generated Tagline:
You mean, I'm on my own?  I've never been on my own.  Oh no!  On 
 own!  On own!  I need help.  Oh, God help me!  Help me, God!
 
-- Homer Simpson
   Homer Badman


pgpfkWQMQcYtV.pgp
Description: PGP signature


Can't configure spamd correctly

2004-12-06 Thread Info
Hello

Why is spamd running with a home directory under /tmp ?

I have spamassassin working as a mail filter under Amavis and Postfix
and SuSE.

I am trying to use spamd to speed things up.

I have two problems

1) I don't think that Amavis is actually using spamd
2) Spamd is not configuring correctly.



I am using spamassassin v2.64, amavis-new v20030616p5-23, perl
v5.8.1-81, postfix v2.0.14-41, SuSE v9.0

My /etc/sysconfig/spamd has:
SPAMD_ARGS="-d -a -L -D -x -u vscan"

My /usr/share/spamassassin is the default

My /etc/mail/spamassassin has only local.cf which has:
required_hits   5.0
rewrite_subject 1
subject_tag [spam]
report_safe 1
use_terse_report0
use_bayes   1
bayes_path  /var/spool/amavis/.spamassassin/bayes
bayes_file_mode 0666
auto_learn  1
skip_rbl_checks 1
ok_languagesall
ok_locales  all

The user vscan has a home directory of /var/spool/amavis

When I start spamd my /var/log/mail log gets:
Dec  6 14:12:12 Pangloss spamd[23172]: debug: daemonized.
Dec  6 14:12:13 Pangloss spamd[23172]: debug: Preloading modules with
HOME=/tmp/spamd-23172-init
Dec  6 14:12:13 Pangloss spamd[23172]: debug: ignore: test message to
precompile patterns and load modules
Dec  6 14:12:13 Pangloss spamd[23172]: debug: using
"/usr/share/spamassassin" for default rules dir
Dec  6 14:12:13 Pangloss spamd[23172]: debug: using
"/etc/mail/spamassassin" for site rules dir
Dec  6 14:12:15 Pangloss spamd[23172]: debug: bayes: no dbs present,
cannot scan: /tmp/spamd-23172-init/.spamassassin/bayes_toks
Dec  6 14:12:15 Pangloss spamd[23172]: debug: Score set 0 chosen.
Dec  6 14:12:15 Pangloss spamd[23172]: debug: Initialising learner
Dec  6 14:12:15 Pangloss spamd[23172]: debug: bayes: no dbs present,
cannot scan: /tmp/spamd-23172-init/.spamassassin/bayes_toks
Dec  6 14:12:15 Pangloss spamd[23172]: debug: running header regexp
tests; score so far=0
Dec  6 14:12:15 Pangloss spamd[23172]: debug: running body-text per-line
regexp tests; score so far=1.879
Dec  6 14:12:16 Pangloss spamd[23172]: debug: running raw-body-text
per-line regexp tests; score so far=1.879
Dec  6 14:12:16 Pangloss spamd[23172]: debug: running uri tests; score
so far=1.879
Dec  6 14:12:16 Pangloss spamd[23172]: debug: uri tests: Done uriRE
Dec  6 14:12:16 Pangloss spamd[23172]: debug: running full-text regexp
tests; score so far=1.879
Dec  6 14:12:16 Pangloss spamd[23172]: debug: all '*From' addrs:
[EMAIL PROTECTED]
Dec  6 14:12:16 Pangloss spamd[23172]: debug: all '*To' addrs:
Dec  6 14:12:16 Pangloss spamd[23172]: debug: running meta tests; score
so far=1.879
Dec  6 14:12:16 Pangloss spamd[23172]: debug: lock: 23172 created
/tmp/spamd-23172-init/.spamassassin/auto-whitelist.lock.Pangloss.acculin.com.23172
Dec  6 14:12:16 Pangloss spamd[23172]: debug: lock: 23172 trying to get
lock on /tmp/spamd-23172-init/.spamassassin/auto-whitelist with 0
retries
Dec  6 14:12:16 Pangloss spamd[23172]: debug: lock: 23172 link to
/tmp/spamd-23172-init/.spamassassin/auto-whitelist.lock: link ok
Dec  6 14:12:16 Pangloss spamd[23172]: debug: Tie-ing to DB file R/W in
/tmp/spamd-23172-init/.spamassassin/auto-whitelist
Dec  6 14:12:16 Pangloss spamd[23172]: debug: auto-whitelist (db-based):
[EMAIL PROTECTED]|ip=none scores 0/0
Dec  6 14:12:16 Pangloss spamd[23172]: debug: AWL active, pre-score:
1.879, mean: undef, originating-ip: undef
Dec  6 14:12:16 Pangloss spamd[23172]: debug: Post AWL score: 1.879
Dec  6 14:12:16 Pangloss spamd[23172]: debug: DB addr list: untie-ing
and unlocking.
Dec  6 14:12:16 Pangloss spamd[23172]: debug: DB addr list: file locked,
breaking lock.
Dec  6 14:12:16 Pangloss spamd[23172]: debug: unlock: 23172 unlink
/tmp/spamd-23172-init/.spamassassin/auto-whitelist.lock
Dec  6 14:12:16 Pangloss spamd[23172]: debug: is spam? score=1.879
required=5 tests=DATE_MISSING,NO_REAL_NAME
Dec  6 14:12:16 Pangloss spamd[23172]: server started on port 783/tcp
(running version 2.64)
Dec  6 14:12:16 Pangloss spamd[23172]: server pid: 23172
Dec  6 14:12:16 Pangloss spamd[23172]: logmsg: server started on port
783/tcp (running version 2.64)
Dec  6 14:12:16 Pangloss spamd[23172]: server started on port 783/tcp
(running version 2.64)

And reports no extra messages from spamd when an incoming message is
filtered, although amavis.log does show a spam score.

I have tried putting -H /var/spool/amavis into SPAMD_ARGS, makes no
difference.


Thanks for any help,
Paul Hilton