Bug 320837 - once an account goes offline, it never comes back to online again
Summary: once an account goes offline, it never comes back to online again
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: POP3 Resource (show other bugs)
Version: 4.10
Platform: Other Linux
: NOR grave
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-06 22:13 UTC by miklos
Modified: 2017-01-07 23:20 UTC (History)
3 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description miklos 2013-06-06 22:13:44 UTC 
I had to unplug the network cable once, and kmail gave a notification about the network going offline. All my pop3 accounts are listed as offline since then, and I couldn't convince kmail/akonadi to bring them online again. I tried to force updating them (this only worked for imap), the restart button in the configure dialog, and pkill akonadi, but all were useless.

I've been using kmail since the kde2-era, and had absolutely no problems with it. I've been using kmail2 for a week (4.10 is supposed to be the 4th major release of it !?!), and now I already migrated to icedove (which is worse than kmail1 btw). Thank you very much for replacing a neat email client with a complete clusterfuck <sarcastic clap>

Reproducible: Always
Comment 1 Denis Kurz 2016-09-24 20:37:28 UTC 
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 miklos 2016-09-25 09:56:13 UTC 
As I've written in the report, I migrated to Thunderbird after a week of frustration with Kmail2. I have no desire to migrate back.
Comment 3 Denis Kurz 2017-01-07 23:20:32 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.