Kai Schaetzl wrote:
> 
> Jberliner wrote on Tue, 13 Jan 2009 17:16:20 -0800 (PST):
> 
>> spamassassin -D --lint
> 
> did you check if the same happens when you run those messages thru 
> "spamassassin -D" and thru spamc?
> 
> 

Yes, I had already sent the message(s) to spamassassin -D and got the same
results. 

I did not try passing them to spamc, though when I do now, it seems to
replicate the problem. 

#spamc -c < untagged-spam-msg
0.0/4.3

#spamc -r < untagged-spam-msg
(no output)

# spamc -y < untagged-spam-msg
(no output)

Note that when I pass hams to spamc, they seem to always trigger the rules. 

A couple of things about the non-tagged messages: they usually feature a
spoofed sender address identical to the recipient, but not always: so, e.g.
From: <m...@mydomain.com> To: m...@mydomain.com. And, in looking at the message
headers, a few things are consistently different about the bad messages. I
don't know if this is because SA or qmail-scanner rewrite the headers or
what...

- they are missing a "Date:" header
- The order of the last few header lines is somewhat different  
- and of course X-Spam-Report always returns the symbol _SUMMARY_ instead of
any tests processed. 
- the number of SA hits is always reported as 0.0, which should be a very
rare occurrence given the custom rules I've added to help troubleshoot.

Thanks for any further insights or suggestions. 

-- 
View this message in context: 
http://www.nabble.com/Spamd-skipping-tests-tp21448225p21463477.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.

Reply via email to