I am currently switching from thunderbird from Kmail. (I was a long time user of thunderbird). Unfortunately, by setting up one of my mail account (which is a basic IMAP/SMTP server), I miss some folders in one account, including the Inbox folder. Everything is fine on my others account. The data/folders are still available in the web interface. I am aware that the SMTP server part is not functional/unreachable (when I am not on the right wifi network), but it should not cause any problem for the mail retrieval (I never had such problem with stock Android mail app neither Thunderbird). So it is a kmail specific problem (I just say it for diagnostic purposes, nothing is meant to be provocative). The problem is very important : I mean by that I don't have the Inbox folder (so neither do I have the mail), they are not in any other account folder, neither they are the local folder. I double-triple checked the configuration, it is fine. There is nothing relevant in the Version of Kmail: 4.14.10. Reproducible: Always Steps to Reproduce: 1. Setting up the account 2. Check the mails (until some folder are created) 3.notice the bug Actual Results: Some folder are created in the concerned account, but not all of them. Not all the mail are downloaded either. Expected Results: All folders in the web interface and other softwares should be there. Nothing more relevant to add. The konsole does not provide anything relevant. Maybe just says that akonadi can't find birthday information, that's it. Neither does gdb (there is no crash, segfaults or anything else). Don't hesitate to ask questions. I didn't find anything relevant in google, neither in kde bug. Please notify me if I am wrong.
I also want to add that trying to remove the configuration and start all over changed nothing. I have the same problem in the same account.
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.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 oportunity 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.
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 more recent), please open a new one unless it already exists. Thank you for all your input.