> It is now possible (thanks to Tony Meyer) to have a single > instance of sb_imapfilter deal with multiple IMAP accounts. > That's great. > > However, it seems to me that there is something lacking in > what you can specify in the config file. The way things are > implemented (and I don't see how it can be done differently > currently) is that for each of the accounts, all mail folders > in the imap:filter_folders configuration variale are > filtered. But it may well be that the different accounts use > different sets of folders.
Ah - didn't think of that. It's a good point - and it negates most of the use of being able to filter multiple accounts, unless you have a very simple (or matching) setup (e.g. filter "Inbox", move to "Unsure" and "Spam"). > In my case it's even worse. I use two sb_imapfilter setups > with different filter_folders, but also with different cutoff values. > > Has anybody given these kinds of problems any thought? Maybe it would be better if you could give imapfilter a list of configuration files. It could then cycle through them (e.g. load config, do filter/train, unload config, move to next file). That way you'd only need one imapfilter instance running, but it could handle any set of different options. It'd load them over the top of the config files found in the normal process (BAYESCUSTOMIZE, bayescustomize.ini, .spambayesrc etc), so options global to all servers could still be easily set. Actually, I guess you wouldn't have to explicitly give a list of configuration files. Imapfilter could look for a (e.g.) server_name.ini automatically, and load that if found. Does this sound useful? Anyone have a better idea? =Tony.Meyer _______________________________________________ spambayes-dev mailing list spambayes-dev@python.org http://mail.python.org/mailman/listinfo/spambayes-dev
