Bug 119604

Summary:	Offline-ness should extend to local folders
Product:	[Unmaintained] kmail	Reporter:	Isaac Wilcox <iwilcox>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	bjoern, cfeck, tiposchi
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Isaac Wilcox 2006-01-06 02:42:37 UTC

Version:            (using KDE KDE 3.5.0)
Installed from:    Debian testing/unstable Packages

Hi,

I've just upgraded to 3.5, primarily to get offline support, which I've been looking forward to.  It works exactly as expected for my IMAP account, but sadly not for my local folders.  Now, obviously one can /generally/ assume that local folders are accessible without any network activity, so online/offline status doesn't really apply to them, but this isn't the case if the precommand sets up an SSH tunnel (which mine does) or does some other networky thing.  I should imagine this is quite common.

So, I think a tickbox should be added to the configuration dialog for local receiving accounts which, when ticked, causes their checking to be suspended just as for remote receiving accounts.  It's arguable that you might want to grey out this tickbox if there's no precommand, as without a precommand a local folder really must be local - but that might be making another assumption :)

A DCOP call to test online/offline status that could be used in the  precommand script would be a workaround (I had a quick look, but couldn't find one to query the status - only to set/reset), but I think this is really a problem with kmail and should ultimately be fixed there.

Cheers,

Zak

Comment 1 Isaac Wilcox 2006-01-06 02:51:37 UTC

Hmm.  S'pose I should add...the reason the continued local folder checking while offline is a Bad Thing is that the precommand fails and exits nonzero when I'm genuinely offline, and pops up a message every time it does so (once a minute, cos I like to keep in touch :) ).

Comment 2 Matt Douhan 2006-01-06 11:02:32 UTC

as the author of the code in question ( with a LOT of help from others ) I like your suggestions and I will definatly look into getting them into the KMail version that ships with KDE4. I cannot get it into 3.5 as that trunk is feature frozen AFAIK.

The workaround to have a dcop call to check online/offline status as a workaround is very trivial to add and I might be able to provide you with a tiny patch against 3.5.

I am expecting to have my development setup back up and running in 2-3 weeks time and then I will look into this.

Comment 3 Björn Ruberg 2009-12-24 16:35:10 UTC

What's happend to this in the last three years?

Comment 4 Salvo "LtWorf" Tomaselli 2013-10-30 12:53:55 UTC

Could this bug be triaged since that version of kmail doesn't exist anymore?

Comment 5 Christoph Feck 2013-11-01 10:12:56 UTC

Salvo, should this be moved to kmail2, or otherwise resolved?

Comment 6 Salvo "LtWorf" Tomaselli 2013-11-02 07:47:19 UTC

I think resolved, but I just opened a bug for a very related (but different) issue in kmail2.

Comment 7 Laurent Montel 2015-04-12 09:49:00 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.