http://bugzilla.spamassassin.org/show_bug.cgi?id=4347
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
------- Additional Comments From [EMAIL PROTECTED] 2005-05-20 20:53 -------
the issue is larger than report_safe. perhaps I didn't make that as clear as I
could have.
we need to go through all the default config options and make sure they
appropriately check values and
return errors on failure. it's not a blocking issue really, but in some places
we're more lax than I think
we should be.
a quick run through shows: allow_user_rules, score, possible the
whitelist/blacklist stuff,
rewrite_header, trusted_networks, internal_networks, bayes_ignore_header,
report_safe_copy_headers,
redirector_pattern, version_tag, loadplugin, replace_rules,
spamcop_from_address,
spamcop_to_address, uridnsbl, urirhsbl, urirhssub, uridnsbl_skip_domain.
they all, in some form, avoid returning errors. either we ignore lines with
blank parameters, or we don't
check values before pushing onto arrays, etc.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
