Version: anoncvs head from 27.07.2004 (using KDE Devel) Installed from: Compiled sources Compiler: gcc 3.3.4 OS: Linux Hi, I am testting around with the dIMAP stuff in KMail and I found an annoying problem which also stands in the contrst to the name "disconnected IMAP". The TCP socket between client (kmail; kontact) and the server is kept open between scheduled new mail checks. From the name I would say that the socket is opened just before the check and closed directly afterwards. For me its a real problem when the ISP makes his 24 hour forced disconnect of my DSL line and kmail stands with error dialog about a lost server connection afterwards. So no more mail checking. Thomas
Maybe this also causes another problem with locking of IMAP folders. Because the folder INBOX is locked all the time, You cant really check the INBOX with another client (e.g. Your mobile). So the socket IMHO should be closed between the synchorisations.
"Disconnected imap" means you can work without an internet connection. But when you do have an internet connection, you might want to check mail often (e.g. every 2 minutes). In that case, if the slave was disconnected every time, it would take a very long time for every mailcheck, since it would have to reconnect (with SSL it can take a long time). IIRC that's the reason the slave isn't disconnected after a mailcheck.
Yes, and because of this offline capabilities the user would naturally use this IMAP connection for non relieble network links. I think of ISDN/Modem dial-up lines, connnections over mobiles etc. For this the closeing of the IMAP socket is really needed to get the dial-up line down or be better prepared for a connection lost. So my suggestion would be to make an "close connection after sync" option and make shure that the time between two sync has a reasonable value. This could be, for example, a minimum of 5-10 minutes. Also I would make a connection loss less interupting of the users work. So no modal error message, but a status line messages which could say "Sync failed X times because of network prblems". And checking mails more often doesn't really make sense ;-).
Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.