https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7890
--- Comment #4 from [email protected] <[email protected]> --- (In reply to Loren Wilton from comment #3) > > 2. Pass any file being moved /out/ of such a directory to (some > > equivalent of) sa-learn as ham. > Would you really want to do this? You said the problem (if that is the > correct word) was that spam messages were being repeatedly re-learned. That and the other things: the reaction is /delayed/ -- until the next time sa-learn cron-job runs. 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. > 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. > Personally I'd suggest having both spam and ham folders, and learning from Maintaining an explicit "ham" folder is too much burden on the users. The best I could think of is treating INBOX itself as ham, but only for messages older than N days -- on the assumption, that a user NOT labeling a message as spam within N days is a good evidence of it being ham. But that's a different topic altogether. > All that said, you are hopefully either running per-user bayes [...] Per-user Bayes here is simply, what Thunderbird comes with. But this is yet another topic... -- You are receiving this mail because: You are the assignee for the bug.
