SA Bugzilla – Bug 6059
turn off AWL by default in 3.3.0
Last modified: 2009-03-29 15:13:11 UTC
at this stage I don't think it's worth having on by default, given the problems it causes for disk load and out-of-control bloated db files eating lots of disk space and memory, vs the marginal gains in accuracy it provides. let's set it off by default.
+1 Until an expiry scheme can be implemented, the AWL is not production ready. ie: bug 3082 needs to be completed
I agree with both of you
I don't mind turning it off by default. To make it useful requires use of SQL, correct trusted_networks settings, absence of blanco whitelisting of own domain, and an occasional ditching of records with count of 1, so it should be enabled only by a conscious decision of administrator aware of issues. Btw, someone recently reported that a /16 network mask (two octets) for an IP address in AWL is unfortunate for him, as his /24 netblock happens to fall under /16 of some ISP (which does not own the complete /16 address range). Narrowing the range to /24 (three octets) may need to be considered, and likewise choosing and implemting a suitable mask (/48?) for IPv6 addresses. I'll still want to use it though: coupled with auto_whitelist_distinguish_signed enabled it can be quite effective with domains like gmail.com and yahoo.
: 421...; svn commit -m "bug 6059: disable AWL by default" Sending rules/v310.pre Transmitting file data . Committed revision 759790.