Re: This is driving me NUTS

2004-11-03 Thread Yang Xiao
Hi,
Thanks for the explaination, one last question, this might be better
suited for MIMEDefang, but since we are on the topic, how do I tell
MIMEDefang to bypass/ignore SpamAssassin?
I tried to delete the sa-mimedefang.cf file, but that didn't seem to
do anything.

Many thanks,

Yang


Re: This is driving me NUTS

2004-11-03 Thread Matt Kettler
At 10:52 PM 11/2/2004 -0500, Yang Xiao wrote:
I'm seeing different SpamAssassin spam scores being reported by
MIMEDefang and MailScanner on the same message.

NO. They are NOT the same message. MailScanner is seeing the message 
*after* mimedefang has modified it. This changes the message dramaticaly if 
it's been encapsulated, and causes none of the header rules to match.

You'll only get the same results by feeding both the SAME message without 
any modifications, and without any bayes learning going on in the meantime.

How can this be? I would rather use MailScanner + SpamAssassin than 
MIMEDefang.
Double scanning causes this problem. Pick one and only one way to call SA. 
Stop screwing around with two scanners at once. SA doesn't work that way.

Calling it twice will always screw up the scores for the second scanner, 
unless your first scanner only adds headers, and even that can change 
things if you're using bayes and don't have a bayes_ignore_header statement 
for it.

If you really want to test two at once, make sure mimedefang does not 
modify the message other than to add a header, and add a 
bayes_ignore_header for it to your local.cf so it doesn't bias the bayes 
scores.




Re: This is driving me NUTS

2004-11-03 Thread Yang Xiao
> For 2: can you be more specific about this? what kind of mismatch? Are you
> getting an X-spam-status with a different score than the body report? If
> so, make sure you're not scanning mail twice. (ie: make sure there's no SA
> calls in procmail if you're using mimedefang)

Hi,
Thanks, I found that I need to modify mimefefang-filter to prepend
Subject Header.
I'm seeing different SpamAssassin spam scores being reported by
MIMEDefang and MailScanner on the same message.

MiMEDefang:
X-Spam-Score: ** (6.309)

MailScanner:
X-Spam-Status: No, score=3.1 required=5.0 tests=ALL_TRUSTED,BILLION_DOLLARS,
 DEAR_SOMETHING,FROM_ENDS_IN_NUMS,NIGERIAN_BODY1,NIGERIAN_BODY2,
   RCVD_BY_IP autolearn=no version=3.0.1
X-Spam-Level: ***

How can this be? I would rather use MailScanner + SpamAssassin than MIMEDefang.
I also noticed that before adding MIMEDefang, Spams was sent as
attached txt and the body contained the SpamAssassin score breakdown,
how do I get that back?

Thanks,

Yang


Re: This is driving me NUTS

2004-11-03 Thread Matt Kettler
At 05:29 PM 11/2/2004 -0500, you wrote:
1. SpamAssassin noi longer Prepend Subject Line even though I told it
to in local.cf
2. Spam score mismatch in headers.
3. Spam gets delivered as it is but Spamassassin report was send as an
attachment instead of the other way around!
for 1 and 3: You are using mimedefang, any markup options you place in 
local.cf are irrelvant. Mimedefang does it's own markups, and it's 
mimedefang you need to configure, not SA.

For 2: can you be more specific about this? what kind of mismatch? Are you 
getting an X-spam-status with a different score than the body report? If 
so, make sure you're not scanning mail twice. (ie: make sure there's no SA 
calls in procmail if you're using mimedefang) 



This is driving me NUTS

2004-11-02 Thread Yang Xiao
Hi all,
I don't know what I did, but this is what's happening to me

1. SpamAssassin noi longer Prepend Subject Line even though I told it
to in local.cf
2. Spam score mismatch in headers.
3. Spam gets delivered as it is but Spamassassin report was send as an
attachment instead of the other way around!
Please help.

This is my setup
Fedora Core 2
SpamAssassin 3
Mimedefang 3.48
ClamAV 0.8

Many Thanks!
Yang


---Sample Mail Header

Received: from mail.domain.com (192.168.2.111 [192.168.2.111]) by
mail.ohpp.com with SMTP (Microsoft Exchange Internet Mail Service
Version 5.5.2657.72)
id VLSN5ZAB; Tue, 2 Nov 2004 17:18:09 -0500
Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.192])
by mail.domain.com (8.12.11/8.12.11) with ESMTP id iA2MJBU5021808
for <[EMAIL PROTECTED]>; Tue, 2 Nov 2004 17:19:13 -0500
Received: by wproxy.gmail.com with SMTP id 66so89085wri
for <[EMAIL PROTECTED]>; Tue, 02 Nov 2004 14:19:07 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=beta; d=gmail.com;

h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;

b=EFkIA1O6m6xKEFDXjFBPzrUROzzjTFvbnmXvPhQb+9qzLdDugN4g7dnGN+K2d10tX93Y+wwPC5goJ51JN9DL9sucPQ5hitkLZjzs4jqdzra8KHM/9blM5etbiu3k7wACwaDMKX9UVAsIuiBb5CsGlkQsrlnwPMFFw/1TLQ4J60k=
Received: by 10.54.50.22 with SMTP id x22mr134736wrx;
Tue, 02 Nov 2004 14:19:06 -0800 (PST)
Received: by 10.54.22.65 with HTTP; Tue, 2 Nov 2004 14:19:06 -0800 (PST)
Message-ID: <[EMAIL PROTECTED]>
Date: Tue, 2 Nov 2004 17:19:06 -0500
From: Yang Xiao <[EMAIL PROTECTED]>
Reply-To: Yang Xiao <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Fwd: Congratulations
In-Reply-To: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="--=_1099433954-21740-0"
References: <[EMAIL PROTECTED]>
X-Spam-Score: ** (6.309)
BILLION_DOLLARS,DEAR_SOMETHING,FROM_ENDS_IN_NUMS,NIGERIAN_BODY1,NIGERIAN_BODY2
X-Scanned-By: MIMEDefang 2.48 on 192.168.2.111
X-Virus-Scanned: ClamAV 0.80/569/Tue Nov  2 14:14:23 2004
clamav-milter version 0.80j
on mail.domain.com
X-Virus-Status: Clean
X-Spam-Status: No, score=3.1 required=5.0 tests=ALL_TRUSTED,BILLION_DOLLARS,
DEAR_SOMETHING,FROM_ENDS_IN_NUMS,NIGERIAN_BODY1,NIGERIAN_BODY2,
RCVD_BY_IP autolearn=no version=3.0.1
X-Spam-Level: ***
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on mail.domain.com

This is a multi-part message in MIME format...

=_1099433954-21740-0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

=_1099433954-21740-0
Content-Type: text/plain; name="SpamAssassinReport.txt"
Content-Disposition: inline; filename="SpamAssassinReport.txt"
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.415 (Entity 5.415)