Beginning from mid to late December, kmail has not been pulling email from openmailbox.org IMAP inbox, though it pulls from other folders. This is not an issue with other email clients. Reproducible: Always Steps to Reproduce: Create an account on openmailbox.org Configure a new IMAP account with KMail Send an email to the openmailbox email address Actual Results: Email does not appear in inbox Expected Results: Emails should be pulled from the server and appear on the local inbox
Same here! It works with old kmail-1 one. Fresh install (removed ~/.kde ~/.config ~/.local) and pretty much anything matching "akonadi|kmai|kde" in my $HOME
Browsing similar bugs, I should add the following points: - I did not use the migrator - I use courier/ssl on the server - The right-klick context-menu on inbox does not give me the "Update Folder" command, only "Update this folder and All its Subfolders"
Ok, the thing seems to be clearly well known from the 2011s. Comment 6 in bug 284172 [1] helped for me: Simply add "INBOX" to the top of of your courierimapsubscribed file on the courier server -- if you're lucky enough to run one. https://bugs.kde.org/show_bug.cgi?id=284172
On Thursday, February 12, 2015 11:01:35 AM Marcus Hardt wrote: > https://bugs.kde.org/show_bug.cgi?id=343825 > > Marcus Hardt <marcus.hardt@iwr.fzk.de> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |marcus.hardt@iwr.fzk.de > > --- Comment #1 from Marcus Hardt <marcus.hardt@iwr.fzk.de> --- > Same here! > It works with old kmail-1 one. > > Fresh install (removed ~/.kde ~/.config ~/.local) and pretty much anything > matching "akonadi|kmai|kde" in my $HOME
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.
*** This bug has been marked as a duplicate of bug 284172 ***