Bug 122499 - Remote IMAP servers continue to be used despite offline mode
Summary: Remote IMAP servers continue to be used despite offline mode
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Unmaintained
Component: IMAP (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 117492 125402 134148 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-02-22 17:35 UTC by Isaac Wilcox
Modified: 2015-04-12 10:17 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Isaac Wilcox 2006-02-22 17:35:35 UTC
Version:            (using KDE KDE 3.5.1)
Installed from:    Debian testing/unstable Packages

Hi,

Clicking File->Go offline doesn't actually disconnect active IMAP server connections.  After "going offline" you can see from the output of "netstat -4pa" that the connection is still very much open:
  tcp        0      0 myhostname:52301              my.imap.server:imaps ESTABLISHED 21343/kmail

In fact, if your currently selected folder is an IMAP folder at the point you click "go offline", you can click on other messages summary lines around the current one, and the content of the message will be loaded just fine over the network (you can watch the traffic using ethereal and see it's not locally cached or anything).  If you select another folder this'll cease to work (you'll get the "KMail is currently in offline mode" page).

This is not only totally contrary to what offline mode claims to do, but also potentially a minor security risk, because you might be going offline to prevent yourself from downloading sensitive mail over an insecure network, or something.

Cheers,

Zak
Comment 1 Isaac Wilcox 2006-02-22 18:36:21 UTC
Other ways this manifests itself...

If you're logically and physically online and connected to a remote IMAP folder and you go both logically (File->Go Offline) and physically offline (say, by pulling your network cable out), you still eventually get a message like:
  The connection to the server My IMAP Server was unexpectedly closed or timed out. It will be re-established automatically if possible.

You shouldn't get that message, because you're logically offline, but because the connection is never really closed and because there's some kind of hook that says "pop up this dialog if we detect connection death", you still do get the message.

Also, if the current folder was an IMAP folder when you went offline (in both senses), you can still click on the messages.  Each time you do, you get a pop up a message saying "Unknown host: my.imap.server".  It'd be better if the message summary pane explicitly changed to the "KMail is offline..." message upon going logically offline, making it impossible to click on the messages; alternatively, it'd be good enough to continue to show the message summaries but upon clicking on one, load a page into the message content pane saying "This message is stored on a remote server, and you're offline.  To read this message, go online (File->Go Online)."

I'm pretty sure I've also managed to get a longer error dialog while logically (and physically) offline, saying:
  Unknown Host
  An unknown host error indicates that the server with the requested name, my.imap.server, could not be located on the Internet.
  ...
but I can't remember how.
Comment 2 Florian Jostock 2006-07-15 14:38:40 UTC
I am using Kde 3.5.2 and I have the same problem: When disconnecting from Network, for example when hibernating, I use "dcop kmail KMailIface stopNetworkJobs".

When switching Network on I use "dcop kmail KMailIface resumeNetworkJobs; dcop kmail KMailIface checkMail", but the Mail from my IMAP-Account (using disconnected IMAP!) cannot be checked. 

If I cancel the Mail-Checking by clicking the red cross in the lower right corner of kontact (unfortunaly, there isnt an dcop-Command for this), and then check the Account again, then new Mail will arrive. 

If I dont, I will get an timeout-Error.
Comment 3 Ismail Onur Filiz 2006-07-18 19:35:08 UTC
*** Bug 117492 has been marked as a duplicate of this bug. ***
Comment 4 Wolfgang Wieser 2007-02-11 20:13:17 UTC
This but was opened 2006-02-22 and one year later it's still "UNCONFIRMED". 
I can indeed confirm it in KMail-1.9.5/KDE-3.5.5. 

Could someone PLEASE look into that. It's REALLY annoying when you have a 
dialup line. PLEASE!!!

Comment 5 Cyrill Helg 2007-02-12 00:27:23 UTC
*** This bug has been confirmed by popular vote. ***
Comment 6 Cyrill Helg 2007-02-12 00:28:39 UTC
At least we could confirm it now by popular vote. I hope it gets fixed in kde 4 at least.
Comment 7 Wolfgang Wieser 2008-01-19 19:52:43 UTC
It's been nearly 2 years now and nothing happened. 

It's a shame. Seems KMail urgently needs more developers. 
Comment 8 Lloeki 2008-03-10 11:02:26 UTC
absolutely. together with
http://bugs.kde.org/show_bug.cgi?id=82684 (from 2004-09-24!)
those are the bugs forcing me to use dIMAP with kmail.
Comment 9 Juha Tuomala 2009-07-16 21:02:37 UTC
Duplicate bug #125402 Kmail checks mail on startup although in offline mode
Duplicate bug #134148 Working offline does not close the connection 
Related bug   #114319 Encrypted emails sent during 'offline' are not encrypted
Related bug   #152743 when offline/online modes are irrelevant 
Related bug   #122503 Link in "KMail is currently offline" page fails to 
                      update menus, statusbar and message summary pane
Related bug   #90691  Online/offline status indicator should be "link"
Comment 10 Christophe Marin 2009-07-23 00:01:31 UTC
*** Bug 134148 has been marked as a duplicate of this bug. ***
Comment 11 Christophe Marin 2009-07-23 00:01:48 UTC
*** Bug 125402 has been marked as a duplicate of this bug. ***
Comment 12 Laurent Montel 2015-04-12 10:17:45 UTC
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.