You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by qu...@apache.org on 2004/04/30 10:46:18 UTC

svn commit: rev 10449 - incubator/spamassassin/trunk/rules

Author: quinlan
Date: Fri Apr 30 01:46:16 2004
New Revision: 10449

Modified:
   incubator/spamassassin/trunk/rules/70_testing.cf
Log:
this hurts so bad


Modified: incubator/spamassassin/trunk/rules/70_testing.cf
==============================================================================
--- incubator/spamassassin/trunk/rules/70_testing.cf	(original)
+++ incubator/spamassassin/trunk/rules/70_testing.cf	Fri Apr 30 01:46:16 2004
@@ -31,12 +31,6 @@
 # will be pretty safe.  (lower rule as a baseline to see if we miss much)
 header T_FROM_DELPHI		From:addr =~ /\d[^\@]+\d[^\@]+\@delphi\.com/i
 
-# great Yahoo! forgery rule, but is it going to be stable?
-# hmm.  good question :(
-header __YAHOO_MSGID		Message-ID =~ /\@yahoo\.com>/i
-header __YAHOO_BEGINNING	Message-ID =~ /<\S+(?:\.\S+|\.\S+\.\S+\.\S+)\@/
-meta T_FORGED_YAHOO_MSGID	(__YAHOO_MSGID && !__YAHOO_BEGINNING)
-
 # more portable replacement for RCVD_NUMERIC_HELO that doesn't rely on
 # Received headers using "helo=" prefix.  exclude squirrelmail, which
 # records a perfectly-ok rcvd header for the HTTP step in this fmt