[imapfilter-devel] Imapfilter Exiting Infinite Loop Timeout?

[Paul]

On 05/19/2010 07:34 AM, Lefteris Chatzimparmpas wrote:
>
> This will logout from your "home" account after the copy, so it's not
> possible to timeout later on.  The next time that it will need to copy
> messages to a mailbox there, it will do a fresh login, and so on.
>
Yes! That looks like it is working perfectly - but leads me to another 
couple of questions.

   do_idle(airbred['INBOX'],home['personal/incoming'],airbred['delivered'])

See I am passing a mailbox - it possible to get from a mailbox  
(home['personal/incoming']) to be able to issue a logout at the account 
level - ifcore.logout(home._imap).  Ie, this gets to the function as 
"tomailbox", so is there something like tomailbox._account._imap?

I will be doing this for a number of accounts, by running several 
instances of imapfilter with different configs, and and so do_idle will 
be a "require".   Ideally I would want it to be mailbox agnostic (though 
I could just work around by using the same "home" account variable for 
each instance of imapfilter).

So my other question is about running multiple instances - I know this 
was prevented in earlier imapfilter versions to avoid locking issues.  
So if I have several imapfilters pulling emails from different accounts, 
and copying them to a single account but different folders, will I run 
into any issues do you think?  I am expecting that with different 
destination folders I will be avoiding any locking issues, but can you 
think of any other problems I might face?

(An imapfilter that supported threading would be totally cool :))

Many thanks,

Paul