-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Justin Mason wrote: > Also, any suggestions from outside the dev team? Anyone got good ideas > for new SpamAssassin features that would be good to pay someone to work on > for 3 months? If I look at the tools and scripts I built around SA (and which are far from perfect), I would like to see: * Show which whitelist_from(_*) rule hit on messages * Frequency reporting (à la nightly/mass checks) - currently I grep and filter this data out of the mail log file, which is error-prone * "Virtualize" all *.cf and *.pre parsing to allow full DB-based operations * Auto-maintenance for AWL (ie pruning "old" entries) * Make the internal status of spamd (counters, timings, ..) available eg through a CLI tool, through SNMP or through a database. * A solid, stable, full-featured web interface for configuration, operation and monitoring (yes, DB-based again ;) ). - -- Matthias -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFF2CmMxbHw2nyi/okRAjxsAJ96VNxALfLcRnH/QEf5UgmsVQ3mVgCg1LK6 AbCNGeHGGbOkt0nyTLlNER8= =Gs5o -----END PGP SIGNATURE-----
