https://bugs.kde.org/show_bug.cgi?id=327894
cluebat <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #15 from cluebat <[email protected]> --- 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. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Kdepim-bugs mailing list [email protected] https://mail.kde.org/mailman/listinfo/kdepim-bugs
