Bug 326473

Summary: Kmail does not show contents of folders on IMAP server
Product: [Applications] kmail2 Reporter: envite
Component: foldersAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: grave CC: pavel, rafaelalcantaraperez
Priority: NOR    
Version: 4.10.5   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description envite 2013-10-23 01:16:53 UTC 
Kmail does this and receives this answer:
A000211 SELECT "INBOX/FOLDER"
A000211 NO Mailbox does not exist, or must be subscribed to.

Trying with another mail client against same server it works:
3 select "INBOX.FOLDER"
* FLAGS ($TODO \Draft \Answered \Flagged \Deleted \Seen \Recent)
* OK [PERMANENTFLAGS ($TODO \* \Draft \Answered \Flagged \Deleted \Seen)] Limited
* 9 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 366652616] Ok
* OK [MYRIGHTS "acdilrsw"] ACL
3 OK [READ-WRITE] Ok

So Kmail fails to properly open the folder, which is correct.

Reproducible: Always

Steps to Reproduce:
1. Use Kmail
2. Connect to an IMAP server
3. Click on any folder
Comment 1 envite 2013-10-25 17:42:53 UTC 
Fails also with dovecot 2.1.17
Comment 2 landgraf 2013-11-06 14:48:18 UTC 
Checked with Zimbra and Kmail 4.10.5 (kde-pimkmail-4.10.5-2pclos2013)

The bug is here.
Comment 3 landgraf 2013-11-06 15:47:22 UTC 
So It works for me now (Just resubscribe to the folders under the Aconadi UI).
Comment 4 envite 2013-11-06 21:22:25 UTC 
Resuscribing does not help. Kmail still uses the wrong format (slash instead of dot) for communicating to the IMAP server.
Comment 5 Denis Kurz 2016-09-24 18:13:29 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 6 Denis Kurz 2017-01-07 22:49:12 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.