Spamassassin doesn't check some mails

[enginaar]

Hello,

There are some spam mails came which have not been checked by spamassassin. I'm using spamassassin for 2 or 3 years for my domain, didn't change anything lately but it doesn't check some mails. Here is an example header of a fugitive mail.

Return-Path: <[email protected]>
Envelope-to: engin@*****.com
Delivery-date: Thu, 12 Aug 2010 07:48:28 +0300
Received: from host100.ilce.druknet.bt ([202.144.143.100]) by name.server34.com with esmtp (Exim 4.67) (envelope-from <[email protected]>) id 1OjPhj-0005F9-4T; Thu, 12 Aug 2010 07:48:28 +0300
Received: from qmail7.arcamax.com (qmail7.arcamax.com [216.174.43.147]) by mx1.biz.mail.yahoo.com with ESMTP id j4sp19940421iaj.975.2010.08.11.67.63.54; Thu, 12 Aug 2010 10:16:03 +0530
Received: from bm2.arcamax.com (216.174.43.139) by qmail7.arcamax.com (PowerMTA(TM) v3.5r15) id hq6d3t4vcdtn for <engin@****.com>; Thu, 12 Aug 2010 10:16:03 +0530 (envelope-from <[email protected]>)
Received: (bminject v3.2); Thu, 12 Aug 2010 10:16:03 +0530
Date: Thu, 12 Aug 2010 10:16:03 +0530
Message-ID: <[email protected]>
From: "Trinidad Harrell" <[email protected]>
To: <engin@****.com>
Subject: Suspicious part has been quarantined : Hey engin
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_0012_01CB3A24.468499C0"
X-MimeOLE: Produced By Microsoft MimeOLE V6.1.7600.16543
Precedence: bulk
List-Unsubscribe: <mailto:[email protected]>

 

[PvanEs]

Did you found the problem already? I have the same problem here since a couple of days. All the spam I get is not checked by spamassassin.

 

[enginaar]

No. no solutions yet.

 

[nobaloney]

Someone will have to study SpamAssassin or ask on the SpamAssassin mailing list; SpamAssassin configuration seems a bit more complex than I can easily understand (I've tried), but I'd guess it's a problem with something about those emails meaning they skip getting checked.

Jeff

 

[fre0n]

hmmm search comes in handy afterall. I'm trying some solution out and it looks like it's working. Earlier i got several skipped mails without the x-spam headers in it every hour or zo. Right now every mail gets x-spam headers so it's promising for over a few hours now. Hopefully it remains stable.

 

[daveyw]

hmmm search comes in handy afterall. I'm trying some solution out and it looks like it's working. Earlier i got several skipped mails without the x-spam headers in it every hour or zo. Right now every mail gets x-spam headers so it's promising for over a few hours now. Hopefully it remains stable.

Glad to hear that you found probably the solution. But: Whats the fix/solution for the other peoples who's having this issue?

 

[fre0n]

Now i should say, next time use the search But here it goes. This thing helps out to get all incomming mail x-spam scanned and give it proper scoring.

http://www.directadmin.com/forum/showthread.php?t=27489

 

[nobaloney]

Did you make changes anywhere besides exim.conf? Did you have to make any changes to SpamAssassin installation?

Did you use exactly what was posted or something else? I might want to stick this into the new exim.conf if it's easy enough.

Jeff

 

[PvanEs]

I think I found the problem. Spamasassin checkes the mail when it is less then 100kB, the spam mails where around 150-200kB. I changed the setting {<{$message_size}{100k}} \ to 200k in /etc/exim.conf. Hope this solved it!

 

[fre0n]

Did you make changes anywhere besides exim.conf? Did you have to make any changes to SpamAssassin installation?

Did you use exactly what was posted or something else? I might want to stick this into the new exim.conf if it's easy enough.

Jeff

the problem also occured on less than 100k messages at first. After the small fix, where i followed the workaround but then with my own 'secret' phrase/word instead of the test123, all messages get correctly tagged. It involved only the exim.conf and the /etc/mail/spamassassin/local.cf file (for introducing the new tag)

 

[nobaloney]

So in other words I can't implement this in exim.conf because I don't control spamassassin.

Or does the test123 tag already exist, in the SpamAssassin configuration, in which case I can.

I'm not available to look at a DirectAdmin configuration right now so I'd appreciate it if someone could check for me.

Thanks.

Jeff

 

[daveyw]

Jeff, The tag 'test123' must also be added manually to the local.cf.
So I guess its not possible to implement this in the new exim.conf

 

[nobaloney]

Not by me.

What happens if test123 is implemented in the SpamAssassin code but note in the local.cf file? Perhaps once SpamBlocker 3 hits final release (unfortunately I've been quite busy all week so it may be another week before it's ready) we can always ask DirectAdmin, to, if they make it the standard, make the change automatically in SpamAssassin.

As you may realize SpamAssassin is still optional code both in exim.conf and in DirectAdmin.

Jeff

 

[daveyw]

That should be wonderfull, if DirectAdmin will help with this. Maybe they can build something with "DA-SA" (DirectAdmin SpamAssassin) and that it will be added also in exim.conf ?

I've added also one X-header, and it seems to work good. I got less spam then before the change.