Bug 324443 - REGRESSION: localhost: Cannot fetch item in offline mode
Summary: REGRESSION: localhost: Cannot fetch item in offline mode
Status: CONFIRMED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 5.2.3
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-03 08:05 UTC by Timo Weingärtner
Modified: 2016-10-12 09:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Timo Weingärtner 2013-09-03 08:05:36 UTC
I use a local IMAP server for my mail for many reasons, one of them being the ability to read my mail when I'm offline. Since the last upgrade kmail refuses reading mails for no reason (ip r g ::1 shows a valid route). Preferring "Fake Net" in the solid configuration does not help.

The non-alternatives are using a Maildir resource (no support for folder structure) and disconnected mode (why duplicate all the data?). 

Reproducible: Always

Steps to Reproduce:
1. create an IMAP account for localhost
2. disconnect non-lo interfaces
3. find out that you can still use the IMAP server with other clients but not with kmail


Expected Results:  
ability to read and manipulate mail
Comment 1 Denis Kurz 2016-09-24 17:53:31 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 2 Timo Weingärtner 2016-10-02 09:33:25 UTC
This bug is still present in KMail 5.2.3. When disconnecting all NM connections KMail shows:
---8<---8<---
Offline

KMail is currently in offline mode. Click here to go online . . .
---8<---8<---
but clicking "here" doesn't help.

Relying on NM to tell if a server is reachable is a heuristic and the heuristic is wrong.
A better heuristic might be to run "ip route get $SERVER" which might incur a DNS timeout if a hostname is used.
Comment 3 Denis Kurz 2016-10-12 09:15:29 UTC
Thanks for your assistance, Timo. I reset it to confirmed