[prev in list] [next in list] [prev in thread] [next in thread] 

List:       spamassassin-devel
Subject:    [Bug 6780] New: Existing but empty From: and To:
From:       bugzilla-daemon () bugzilla ! spamassassin ! org
Date:       2012-03-31 13:14:09
Message-ID: bug-6780-26 () https ! issues ! apache ! org/SpamAssassin/
[Download RAW message or body]

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6780

             Bug #: 6780
           Summary: Existing but empty From: and To:
           Product: Spamassassin
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Rules
        AssignedTo: dev@spamassassin.apache.org
        ReportedBy: lemat@lemat.priv.pl
    Classification: Unclassified


in recent wave of spam I have seen existing but empty From: and To: headers. I
mean MISSING_HEADERS does not match since these headers exist. The closest rule
to match such spam is FH_FROMEML_NOTLD, but it is only for From: header.
Therefore I propose something like that:

header EMPTY_FROM         From =~ /^\s*$/
describe EMPTY_FROM       empty From:

header EMPTY_TO         To =~ /^\s*$/
describe EMPTY_TO       empty To:

or meta EMPTY_TO & EMPTY_FROM

-- 
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[prev in list] [next in list] [prev in thread] [next in thread]