https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7397
Michael P <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Michael P <[email protected]> --- For the record, our version of sa-update deals with a lot of the outstanding enhancement requests, but is not yet production ready.. eg, help docs, pretty up the code etc, but has been proven to work for the last year in all our production environments. However, would be nice to get some comments, to be truthful sa-update tries to do too much. I would suggest discussion on whether it should be broken out into sa-setup and sa-update. While it may seem obvious, and probably did in the past, that an update should happen whether the new dataset of rules are on the local file system, (eg a developer testing or during initial setup or one server pulling updates for a cluster) vs doing an http 'pull' from a remote mirror, I would suggest that given the differences in behaviour that these two actions be separated. I think that decision should be made before updating the current sa-update code for 4.0 -- You are receiving this mail because: You are the assignee for the bug.
