(late reply) ... Actually unrelated. msg_received is protected by locks internally where it needs to be (actually i dont think it requires any locks). It is basically the mechanism where messages are passed between threads so is intended to be asynchronous. Z On 18 May 2001 16:33:31 +0200, michael lausch wrote: > > I'm currently (well for 2 weeks actually) experiencing UID > clashes for my IMAP INBOX. I traced all the e-msgport and mail-mt > calls and i found the following call scenario: > > Thread called functions > 21888 calls mail_msg_received -> timeout_timeout > 21887 calls mail_msg_received -> regen_list_regen > 21887 return mail_msg_received > > UID CLASHES IN 21888 HAPPENS HERE > > 21888 return mail_msg_received > 21911 calls mail_msg_received > 21911 return mail_msg_received > > i don't know if it's save for two threads to enter mail_msg_received > at the same time. but if it isn't this seems to tbe the reason > why. > > > > > _______________________________________________ > evolution maillist - [EMAIL PROTECTED] > http://lists.helixcode.com/mailman/listinfo/evolution _______________________________________________ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
