> -----Original Message-----
> From: Piotr Zalewa [mailto:[EMAIL PROTECTED]
> Sent: Monday, 31 March 2008 2:26 p.m.
> To: SpamAssassin
> Subject: RE: Failed to check the emails
> 
> Thanks Michael.
> 
> I've run the
> spamassassin -D --lint > spamassassin_lint 2>&
> 
> I can't find anything suspicious there - but I'm not the master
either.
> I think it's rather qmail-scanner configuration problem ... I'll paste
> here parts which I think are important ... If it's not helpful I can
> attach the file (to priv as I think).
> 
> dbg: logger: adding facilities: all
> dbg: logger: logging level is DBG
> dbg: generic: SpamAssassin version 3.2.1
> dbg: config: score set 0 chosen.
> dbg: util: running in taint mode? no
> dbg: dns: is Net::DNS::Resolver available? yes
> dbg: dns: Net::DNS version: 0.59
> [...]
> dbg: bayes: no dbs present, cannot tie DB
> R/O: /root/.spamassassin/bayes_toks
> [...]
> dbg: dns: is_dns_available() last checked 1206925264 seconds ago;
> re-checking
> dbg: dns: is DNS available? 0
> [...]
> dbg: check: is spam? score=4.205 required=4
> dbg: check:
>
tests=MISSING_DATE,MISSING_HEADERS,MISSING_SUBJECT,NO_RECEIVED,NO_RELAYS
> dbg: check:
>
subtests=__HAS_MSGID,__MISSING_REF,__MSGID_OK_DIGITS,__MSGID_OK_HOST,__M
SO
> E_MID_WRONG_CASE,__NONEMPTY_BODY,__SANE_MSGID,__UNUSABLE_MSGID
> 
> As I said - emails sent normally from other servers are being checked
> for spam
> 
> Piotr
> 
> On Mon, 2008-03-31 at 13:02 +1300, Michael Hutchinson wrote:
> > > -----Original Message-----
> > > From: Jason Haar [mailto:[EMAIL PROTECTED]
> > > Piotr Zalewa wrote:
> > > > But some are coming not being checked ...
> > > > X-Spam-Status: No, hits=? required=?
> > It sounds like a config issue. It would pay to do a "spamassassin -D
> > --lint". This will produce a lot of output, but it is worth reading
and
> > understanding all of the information, to be able to parse it for
errors.
> > Cheers,
> > Mike
> >
> >

>From what you posted, S.A looks OK, except it couldn't tie your Bayes
database. That's mostly a temp issue, if it recurs without resovling
itself then it's an issue.

However, I think you're right about the fact that it's a config error
somewhere else. I use Simscan myself, and haven't touched qmail-scanner
before. I do have a config file where I can turn Spam and AV checking on
or off for a particular domain, but it is Simscan specific. Besides,
that sort of feature should still not leave you with a S.A header in the
email. You might want to check the sanity of the receiving end's qmail
config. Especially the control files.

Have you attempted to track the email through your system by grepping
through the logs? 

I do this for tracking mails, and normally wind up using "tail -f
<logfile>" and leave it running while I do testing... If you're too busy
a domain, that wont work for you.

It'd be interesting to see if you're getting some kind of failure when
S.A is being called. 

X-Spam-Status: No, hits=? required=?
^^ this isn't normal, S.A should know what it's required hits score is,
no matter what it's doing. Can it read/write the file that sets this
option?

I can only hazard a guess with no more information:
Perhaps your system is running S.A in per-domain or per-user mode? There
could be a problem that there is no configuration file to read when it's
receiving mail from the other system you're talking about, or the config
file for that domain exists but S.A doesn't have permissions to deal
with it.

U could post your "spamassassin -D --lint" to me if you like... I'm not
guaranteeing expert analysis tho :)

Is qmail-scanner keeping a log on your system? And are you able to see
your email traverse from the other domain to the mail server in
question, in the log files? (/var/log). If so, perhaps post some log
entries or try to see what's going on when that email is being scanned.

Cheers,
Mike

Reply via email to