Received: from alcserv1.psfc.mit.edu (alcserv1.psfc.mit.edu [198.125.178.44])
by pacific-carrier-annex.mit.edu (8.12.4/8.9.2) with ESMTP id i022RqfS005467
for <[EMAIL PROTECTED]>; Thu, 1 Jan 2004 21:27:52 -0500 (EST)
Received: from [198.125.176.141] (ppp1.psfc.mit.edu [198.125.176.141])
by alcserv1.psfc.mit.edu (8.12.10/8.12.10) with ESMTP id i022Rnu7007032
(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT)
for <[EMAIL PROTECTED]>; Thu, 1 Jan 2004 21:27:51 -0500
Mime-Version: 1.0
X-Sender: [EMAIL PROTECTED] (Unverified)
Message-Id: <[EMAIL PROTECTED]>
Date: Thu, 1 Jan 2004 21:27:44 -0500
To: [EMAIL PROTECTED]
From: Mark London <[EMAIL PROTECTED]>
Subject: london, you look cute.
Content-Type: text/plain; charset="us-ascii"
X-Spam-Level: 0 ()
X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang)
Theo Van Dinter wrote:
On Wed, Dec 31, 2003 at 08:03:19AM -0800, Regis Wilson wrote:
It seems incredibly easy to me to write an eval routine that extracts the email address of the To: field, extracts the part before the "@", and then finds that substring in the subject.
Yup. already have a rule for that. The version that is currently in place is the only one that didn't false positive itself out of existence. Although I didn't try the full email address in the subject, wonder how that would do ...
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
