http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5710
Summary: config size sanity warnings.
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Platform: Other
OS/Version: other
Status: NEW
Severity: minor
Priority: P5
Component: spamassassin
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
As discussed over on sa-users I propose some basic sanity checks.
While these are currently intended to help novices realize that sa-blacklist is
detrimental to SA's health, I think implementing this as a general-purpose
feature is helpful in letting users know their configuration is "too large".
So I propose the following options, which cause the parser to generate warnings
only. The idea is to trigger warnings when the config is "probably absurd unless
you've got large hardware"
1) warn_conffile_maxsize (speced in KB, default 1024)
generates a warning if any single config file exceeds this size. Conf files
could be large, but 1MB is probably uncalled for.. 3.2.3 as shipped has 1 .cf
over 100k. My config has 7 over 100k when you count all the SARE stuff, but
neither has any over 200k
Others that might be useful:
2) warn_whiteblack_maxentries (speced in entries, default 8192)
generates a warning if the entries in whitelist_* or blacklist_* exceeds this
count. Anyone with more than 8k black/whitelists is probably doing a LOT wrong
on their system, not even considering the performance issues..
3) warn_conf_maxrerules (speced in regex-based rules, default 32768)
generates a warning if the number of body, rawbody, uri, full and header
rules exceeds this count.
A crude grep shows SA 3.2.3 shipped with 1495 such rules (might be overstated, I
just grepped for "body ", etc..). My test box has a very large SARE contingent,
and that adds 3057 more rules for a total of 4552. Others might be larger, but
32k is probably absurd. meta rules are lightweight generally speaking, so
shouldn't be counted here, IMO..
Takers on these 3 options? A lot of folks liked the first one.. what about the
other two? (when it comes to it, please specify the scope of any votes ie: 1-3)
+1 or: 1) +1 2) 0 3) -1 )
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
