Yes, the learn client does not try to keep up with what it has done, or not done, before - that is handled by the server (the Bayes engine).
I believe there is no reasonable way for the client to achieve this, anyway - it cannot reliably modify your maildir in such a way that it can be assured of finding things again, since your email software might discard whatever the learn client put there for the "memory" of what it processed. And a maildir is not the only kind of input it recognizes, so it could be quite unmanageable to try to implement as many ways of 'remembering' as there are ways of giving it things to process. So I would say the better solution is to adjust the way you run your learning, so that it will discard, or move elsewhere, the items it has processed. Perhaps put things you want learned into a place that no other process touches, run the learn on that, then move that stuff to another place if you want to keep it around for a while. >>> LuKreme <krem...@kreme.com> 05/06/09 4:23 PM >>> On 6-May-2009, at 07:13, RW wrote: > On Wed, 6 May 2009 01:43:08 -0600 > <lbut...@covisp.net> wrote: > >> The trouble appears to me to be that sa-learn has no concept of >> whether or not it has learned a message or not. > > It does, they are stored in the bayes_seen file if you are using > db storage. It odes int aht it doesn't relearn then, but it doesn't in terms of processing them. Lemme explain. If I have a maildir with 109 messages, 9 of which are new, running sa- learn might take X minutes. If I have a maildir with 9 messages, all of which are new, sa-learn takes much less than X minutes. If I have a maildir with 2893 messages, 9 of which are new, it will take much much more than X minutes.
