You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by "Richard J. Kieran" <rk...@rhnet.org> on 2004/04/05 04:48:01 UTC
Spams skipping SA
I just got back on the list, so if this has been covered, forgive me, then bring me up to date.
I have had a rash of spams in the last week or so that manage to avoid being scanned by Spamassassin. They follow this pattern: Subject is a number followed by one, maybe two words, like this: 78 how
ym. The body copy varies. Sometimes drugs, sometimes mortgages, etc.
Here's one:
Return-Path: <Be...@msn.com>
Received: from spamfilter.rhnet.org (204.168.249.20)
by mail.rhnet.org (FirstClass Mail Server v7.1) with ESMTP
(Sender: BessieHealy690@msn.com)
transient id 4934; Sat, 03 Apr 2004 00:02:04 -0500
Received: from cm218-253-164-160.hkcable.com.hk (cm218-253-164-160.hkcable.com.hk [218.253.164.160])
by spamfilter.rhnet.org (8.12.9/8.12.9) with SMTP id i3351juw013438;
Sat, 3 Apr 2004 00:02:00 -0500 (EST)
(envelope-from BessieHealy690@msn.com)
Date: Sat, 3 Apr 2004 00:02:00 -0500 (EST)
From: "Felix Alexandria" <Fe...@msn.com>
MIME-Version: 1.0
Subject: 78 how ym
Received: from sls-zs6g7.msn.com ([110.184.132.230]) by qk4-a5.msn.com with Microsoft SMTPSVC(7.0.2195.6824); Sat, 03 Apr 2004 13:55:58 +0600
Received: from sls-al7t7.msn.com ([176.56.96.36]) by zd2-h9.msn.com with Microsoft SMTPSVC(3.4.2195.6824); Sat, 03 Apr 2004 03:57:58 -0400
Received: from mail pickup service by sls-ny7p3.msn.com with Microsoft SMTPSVC; Sat, 03 Apr 2004 02:58:58 -0500
X-Message-Info: 46custodianayw
Message-ID: <VP...@msn.com>
X-Mailer: Atlas Mailer 2.0
Content-Class: urn:content-classes:message
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
X-OriginalArrivalTime: Sat, 03 Apr 2004 11:02:58 +0300 (UTC) FILETIME=[56X2D9N3:46E95192]
To: undisclosed-recipients:;
X-Scanned-By: MIMEDefang 2.38
OFFSHORE-DISCRETE Pharmacy...
*No-questions ever asked. We trust the judgement of our clients based on their needs. We guarantee complete privacy on all transactions.
Popular drugs of the MONTH: CIaLis. (35-hour time frame to act), Valium.(rleases stress on the spot, allowing more confidence)
We have a full-lineup, check all of our low prices & products.
http://msn.com.utdhosw.com/m004/index.php?id=m004
{ many, many linefeeds in here...}
No more of either, I wish to be taken0ff, thank-you.
http://ivy.utdhosw.com/byebye.html
wax indispose hunt bop sinew algeria colloquia personify vance asocial emitter streak patriarchy shakedown mettle earthmen aubrey blackbody
1
EndOfSpam-------------------
We are using SA 2.60 out of MIMEDefang on FreeBSD. It looks like it may well be MIMEDefang that's falling down on these, but I can't see why. Thanks.
Richard
Re: Spams skipping SA
Posted by Kris Deugau <kd...@webhart.net>.
"Richard J. Kieran" wrote:
[snip]
> X-Scanned-By: MIMEDefang 2.38
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> We are using SA 2.60 out of MIMEDefang on FreeBSD. It looks like it
> may well be MIMEDefang that's falling down on these, but I can't see
> why. Thanks.
Well, MD itself appears to be OK, otherwise you wouldn't get that header
added.
IIRC the default filter does NOT add any header info if the call to SA
returns a score less than your threshold (defined in the filter, not in
the SA config!).
On one system here, I use something like this: (Watch for linewrap)
if ($Features{"SpamAssassin"}) {
if (-s "./INPUTMSG" < 120*1024) {
# Do SA checks, add headers/modify subject if spam, etc
action_change_header("X-Spamscanned", "Yes: SpamAssassin
$Mail::SpamAssassin::VERSION (zeus.webhart.net)");
} else {
action_change_header("X-Spamscanned", "No: Messages larger than
120KB not spamscanned");
}
}
I check to see if the message is "too large". If not, run the SA check
and add an info header that just says "Yes, this message was
spamscanned". If it's too big, add an info header that says so.
You should probably direct any further questions about MD-SA integration
to the MIMEDefang list.
-kgd
--
"Sendmail administration is not black magic. There are legitimate
technical reasons why it requires the sacrificing of a live chicken."
- Unknown