Bug 286247 - No feedback when an IMAP server is unreachable
Summary: No feedback when an IMAP server is unreachable
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: UI (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-10 08:35 UTC by Will Stephenson
Modified: 2017-01-07 22:24 UTC (History)
2 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 Will Stephenson 2011-11-10 08:35:27 UTC
Online IMAP resource.

When the server is unreachable, KMail only shows the 'retrieving folder contents' widget forever, without reporting a failure to connect.  

This will be mistaken by the average user for Akonadi weirdness.

Expected behaviour:
Display a status message.
Hide the folder tree for the unreachable server.
Comment 1 Laurent Montel 2012-01-17 18:08:07 UTC
In 4.8 we draw in red broken resource in treeview is it enough ?
Comment 2 Gregor Petrin 2012-04-19 06:37:56 UTC
Firstly, the red broken resource in treeview does not always show (I think when a resource is stuck in 'connection established' mode). 

Secondly, I rely on my system tray to see new messages and there is no indication there that something is wrong.

And thirdly, there is a KMail notification called 'A resource is broken' which I have enabled but it does nothing, at least in my experience.

I'm not sure if I should open bug/wish reports for each of those, but more should definitely be done to alert users that their email is broken.
Comment 3 Denis Kurz 2016-09-24 18:14:46 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 4 Denis Kurz 2017-01-07 22:24:28 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.