Bug 341277 - RetrieveItemsTask::onFinalSelectDone: Server bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known problem with Courier IMAP.
Summary: RetrieveItemsTask::onFinalSelectDone: Server bug: Your IMAP Server delivered ...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.14.2
Platform: Debian unstable Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-26 08:10 UTC by Vladislav Vorobiev
Modified: 2018-01-31 16:54 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Vladislav Vorobiev 2014-11-26 08:10:59 UTC 
I have here 4:4.14.2-2 and still have this bug

posting retrieval request for item 86502  there are  1  queues and  0  items in mine 
request for item 86502 still pending - waiting 
processing retrieval request for item 86502  parts: ("RFC822")  of resource: "akonadi_imap_resource_11" 
akonadi_imap_resource_11(24819) RetrieveItemsTask::onFinalSelectDone: Server bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known problem with Courier IMAP. 
QDBusObjectPath Akonadi::Server::NotificationManager::subscribeV2(const QString&, bool) Akonadi::Server::NotificationManager(0x1a19910) "akonadi_newmailnotifier_agent_24852_ECGjdZ" true 
QDBusObjectPath Akonadi::Server::NotificationManager::subscribeV3(const QString&, bool, bool) Akonadi::Server::NotificationManager(0x1a19910) "akonadi_newmailnotifier_agent_24852_ECGjdZ" true false 
continuing 
request for item 86502 succeeded

It seems to be the same as here https://bugs.kde.org/show_bug.cgi?id=338186

Reproducible: Sometimes
Comment 1 Denis Kurz 2017-06-23 19:56:40 UTC 
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.
Comment 2 Denis Kurz 2018-01-31 16:54:16 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 more recent), please open a new one unless it already exists. Thank you for all your input.