Can be done with brute-force rule creation, EG:

  # ISKIMARO 66.55.160.0/19  (12/8/05) SBL11507
  header L_RCVD_SPAMMER161     Received =~ /\[66\.55\.1[678]\d\.\d{1,3}\]/
  describe L_RCVD_SPAMMER161   ISKIMARO Spamhaus
  score L_RCVD_SPAMMER161      1.5

Bit of a pain to maintain but does work.


The only SA feature I like more than "eval:helo_ip_mismatch()" is the meta system.  Thinking about this overnight, I have a whole new approach:


PROBLEM
SpamHaus is good but not perfect, most entries (old and new) can be blocked outright.


OLD SOLUTION
Create duplicate positive entries (IP/RBL) to catch most of what SpamHaus says should be positive.  Result: huge private list of spammers to build and maintain.


NEW SOLUTION
Create duplicate negative entries (IP/RBL) to uncatch some of what SpamHaus says should be postive.  Result: small private list of exceptions to build and maintain.  Something like:

__PublicSpamHaus
__AntiSpamHaus

meta    SpamHausCapture    __PublicSpamHaus && !__AntiSpamHaus


...basically, micro whitelisting.


Dan

Reply via email to