http://bugzilla.spamassassin.org/show_bug.cgi?id=3033
------- Additional Comments From [EMAIL PROTECTED] 2004-02-12 10:02 -------
Subject: RE: enhancement: modify spamd to monitor changes to
/etc/mail/spamassassin and reload config
After following the discussion, and thinking this over a bit, I'm going
to -1 my
proposed enhancement. My motivation for having this feature was to lower the
support overhead ("did you restart spamd?") and to help overcome the
time/two
that I'd forgotten to restart spamd, but it looks like this sort of
automation
is difficult to achieve given current constraints.
Perhaps one 'fix' would be to move the things that are often modified the
most
(explicit whitelists/blacklists) into a database and provide tools to update
them.
Arguably some of the more
popular rulesets that are periodically updated (bigevil, and evilnums come
to mind) would be better suited to a database, and a single eval rule for
each that looks up url's and postal addresses in the database.
I don't know if this principal could be extended to the SA ruleset in
general. The closest analog that I know of is sendmail's access.db. I think,
but am not sure, that makemap for example, likely sends a signal to sendmail
telling it that one of the maps has been modified, because it doesn't
require
that the user manually restart sendmail when a new map has been created.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
