You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2011/09/07 05:46:05 UTC

[Bug 4691] fast_body, fast_rawbody, and tmethod support

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

Adam Katz <an...@khopis.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |antispam@khopis.com

--- Comment #32 from Adam Katz <an...@khopis.com> 2011-09-07 03:46:05 UTC ---
Is this patch still feasible?

I'd like to resurrect this idea in a slightly different manner:  default
limits.  Something like this (assuming "string 0:0" removes any scope from the
query):

  default_tmethod  string 0:512000

  body    TEST_WHOLE_MSG  /\btest\b/
  tmethod TEST_WHOLE_MSG  string 0:0
  body    TEST_FROM_END   /\bsincerely,/i
  tmethod TEST_FROM_END   string -100:100

With uri, body, rawbody, etc. limited to just the first 500kB (the default
max_size for spamc), we should theoretically then be able to increase the
default max_size considerably without much overhead.  Any rule (such as the two
defined above) that wants to re-scopes itself can do so explicitly.

This should significantly reduce scan time, especially if a script regularly
drills into the timing logs and reduces the scope of the more
resource-intensive rules (incrementally until it affects the hit stats).

-- 
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.