https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7890
RW <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #5 from RW <[email protected]> --- (In reply to [email protected] from comment #4) > (In reply to Loren Wilton from comment #3) > That and the other things: the reaction is /delayed/ -- until the next time > sa-learn cron-job runs. There's nothing to stop you running it more often - particularly if you make it more efficent. > And yes, I could implement such a directory-watching daemon myself. But I > don't want /another/ daemon -- it should be part of spamd, in my opinion. > Both logically, and from the resource-consuming point of view: spamd is > already running, and it has all of the Bayes code in it. I don't think that's ideal as it means giving spamd read access to the mail store - something it wouldn't otherwise need. Dovecot has a plugin that largely does what you want. It can also be done using "IMAP Sieve" which allows sieve-like scripts to be handle IMAP events. I don't know whether Cyrus has equivalent functionality, I suspect it does. > > But assuming it is, I'd expect that removing it from a spam folder should > > only > > mean that it has been sufficiently learned, not that it has become ham. > > > Messages could be removed from the folder by a cron job, or after they have > > been learned. > > They could be. That delay will still be there, though. It would become so cheap you could run it once a second if you like. -- You are receiving this mail because: You are the assignee for the bug.
