https://bugs.kde.org/show_bug.cgi?id=327894
--- Comment #17 from Christian Mollekopf <mollek...@kolabsys.com> --- (In reply to comment #15) > I have a problem with exact same symptoms (messages sent to trash appear > seconds later as ghosts, have to delete from separate MUA) but have not done > quite as deep an investigation. In my case the server is Dovecot and > multiple simultaneous connections from different clients works perfectly > fine. I'm not sure any other client uses more than one session to the same > server at a time except for bulk download. > > The use of a separate thread for IDLE makes no sense to me, it sounds like > whomever set that up didn't quite get the concept. The intended way to use > IMAP IDLE, and the way basically everything else that works does it, is you > connect, refresh mail, perform whatever user actions have been queued, then > call IDLE and you stop. Whenever the connection closes, that means something > changes so you repeat the process starting at connect, refresh everything, > do queued user-initiated actions, call IDLE, wait. ad naseum. That doesn't resemble anything in RFC 2177. AFAIU IDLE works like this: * the client opens a connection * the client sends IDLE command * the server can now send unsolicited responses for for arriving mail etc. * the client stops the command using DONE We're doing this in a separate session, which should work. Ideally we would be reconnecting every 29mins to keep the server from closing the connection, but currently we simply wait for the server to close the connection and then reopen a new one. Anyways, this probably has nothing to do with the bug at hand. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs