Bug 345280

Summary: KMail doesn't fetch any messages
Product: [Applications] kmail2 Reporter: rgpublic
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: kde.kfoar
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description rgpublic 2015-03-17 20:34:46 UTC 
After many months I thought I'd give the all-new KMail again a try and switch back from Thunderbird. I didn't quite work out though, because KMail doesn't fetch any messages from my company IMAP server. When I create an IMAP connection under settings everything is detected (TLS etc) and the icon turns green, but that's it. No folders. No error. No messages. Nothing. It works with other IMAP accounts, though. Back to Thunderbird, for now... :-(

Reproducible: Always

Steps to Reproduce:
1. Create IMAP connection to company mail server


Actual Results:  
No folders, no messages, vast gaping emptiness - almost like our universe ;-)

Expected Results:  
folders, messages, a usable KMail

If there is anything I might do to further debug this or help you out, just let me know.
Comment 1 rgpublic 2015-04-07 16:58:22 UTC 
I've found the solution here:

https://forum.kde.org/viewtopic.php?f=20&t=97403

This solved the problem for me. Nevertheless: I'd consider it a confusing bug that by default KMail isn't showing any folders whatsoever.
Comment 2 Ovidiu-Florin BOGDAN 2015-04-09 19:39:52 UTC 
Are you using a localised environment?
Comment 3 Denis Kurz 2016-09-24 18:06:07 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:37:37 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.