Bug 345558

Summary:	INBOX is empty, all other subfolders of same account have all mails present
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Martin Riethmayer <ripper>
Component:	IMAP resource	Assignee:	Christian Mollekopf <chrigi_1>
Status:	RESOLVED UNMAINTAINED
Severity:	major	CC:	aheinecke, kde.kfoar, kdepim-bugs, montel, vkrause
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	imap log

Description Martin Riethmayer 2015-03-26 18:58:53 UTC

I have set up three e-mail accounts with Kontact / KMail on openSUSE 13.2, KDE 4.14.6

On two accounts (all IMAP, one is freenet.de, one is a self-hosted Kolab server, one is my works E-Mail) everything is working as expected. On the work-account however, I'm not seeing any mails in the inbox. I'm getting all sub-folders and e-mails in those subfolders (including archives with more than 5K mails in each).

Thunderbird is displaying all mails in all accounts. I just found out that the context menu on the working two INBOX-es seem to be very much like a sub-folder (e.g. have an entry for folder properties) while the non-working-INBOX does not. Does this mean the IMAP server config must be changed?

The server is "courier imapd 4.3.0"

Reproducible: Always

Steps to Reproduce:
1. Select the INBOX folder of the imap-Server in question, look for new mails

Actual Results:  
No messages are displayed

Expected Results:  
The messages in the INBOX should be displayed

See also https://forum.kde.org/viewtopic.php?f=215&t=125228

The xsession-errors file is always empty.

Comment 1 Martin Riethmayer 2015-03-26 18:59:19 UTC

Created attachment 91756 [details]
imap log

Comment 2 Ovidiu-Florin BOGDAN 2015-04-09 19:44:31 UTC

I'm also experiencing this. I've taught it to be an issue with the fact that KMail translates the INBOX name. I have KDE in Romanian.

Comment 3 Martin Riethmayer 2015-04-10 20:25:17 UTC

While my INBOX of the non-working folder is also translated (to german), the same is true for the two working Inboxes. So I don't think it's an issue of the translation itself. I'm still suspecting the server imap software (mainly because of the comment of einar in the above linked forums thread)

Comment 4 Andre Heinecke 2015-06-26 12:28:21 UTC

Happened for me too, for me the reason was that Serverside Subscriptons were enabled and the INBOX not subscribed. After subscribing to the inbox (Account settings -> Advanced -> Serverside Subscription) the contents were shown.

Can you check if your INBOX is subscribed?

Comment 5 Martin Riethmayer 2015-07-02 21:40:07 UTC

Unfortunately, this is not the case for me. All folders are subscribed locally and server side, but the INBOX does not show up.

Comment 6 Martin Riethmayer 2015-07-02 21:41:12 UTC

sorry, that should read "but the mails from the INBOX do not show up." Editing is not possible, is it?

Comment 7 Ovidiu-Florin BOGDAN 2015-08-24 07:22:10 UTC

(In reply to Andre Heinecke from comment #4)
> Happened for me too, for me the reason was that Serverside Subscriptons were
> enabled and the INBOX not subscribed. After subscribing to the inbox
> (Account settings -> Advanced -> Serverside Subscription) the contents were
> shown.
> 
> Can you check if your INBOX is subscribed?

This also fixed it for me.
Martin, do you still experience this?

Comment 8 Martin Riethmayer 2015-09-02 05:17:07 UTC

Both local and server side subscriptions are turned on for all folders / subfolders but still my INBOX doesn't show any mails. 

The INBOX should have a couple of unread mails, btw, but not even the number of unread mails is shown. In subfolders, both the correct number of unread mails and the mails themselves are shown.

Comment 9 Denis Kurz 2017-06-23 20:16:32 UTC

This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.

Comment 10 Denis Kurz 2018-02-01 09:53:04 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.