Bug 344342 - stuck with fetching mail from exchange
Summary: stuck with fetching mail from exchange
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR grave
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-19 10:12 UTC by alexander sergeyev
Modified: 2018-02-01 09:45 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description alexander sergeyev 2015-02-19 10:12:09 UTC
There is the same problem while working with exchange server. Sometimes it fetches all headers from exchange but finally it stuck. There is a logs pertaining this problem in .xsession-errors:

akonadi_imap_resource_4(725) RetrieveItemsTask::onExpungeDone: Expunge failed:  "Expunge failed, server replied: A000006 NO The currently selected folder is READ-ONLY. " 
akonadi_imap_resource_4(725) RetrieveItemsTask::onFinalSelectDone: Server bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known problem with Courier IMAP. 
akonadi_imap_resource_4(725)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
akonadi_imap_resource_4(725) RetrieveItemsTask::onFinalSelectDone: Server bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known problem with Courier IMAP. 
akonadi_imap_resource_4(725) RetrieveItemsTask::onFinalSelectDone: Server bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known problem with Courier IMAP. 

When I start to view email it stuck again with these logs:

request for item 853 "21769" failed: "Unable to retrieve item from resource: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." 
ItemRetrieverException :  Unable to retrieve item from resource: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
posting retrieval request for item 853  there are  1  queues and  0  items in mine 
request for item 853 still pending - waiting 
processing retrieval request for item 853  parts: ("RFC822")  of resource: "akonadi_imap_resource_4" 
continuing 
request for item 853 "21769" failed: "Unable to retrieve item from resource: <html>Job canceled.</html>" 
ItemRetrieverException :  Unable to retrieve item from resource: <html>Job canceled.</html>
akonadi_imap_resource_4(725) BatchFetcher::onUidSearchDone: Search job failed:  "Connection to server lost." 
posting retrieval request for item 853  there are  1  queues and  0  items in mine 
request for item 853 still pending - waiting 
processing retrieval request for item 853  parts: ("RFC822")  of resource: "akonadi_imap_resource_4" 
[885:914:0219/123702:ERROR:channel.cc(258)] RawChannel read error (connection broken)
[885:914:0219/123738:ERROR:channel.cc(258)] RawChannel read error (connection broken)

(may be some logs messed up with some other logs)

Version is 4.14.5 (not listed)

Reproducible: Always




64bit Archlinux with CK-kernel
Comment 1 Denis Kurz 2017-06-23 19:59:56 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-02-01 09:45:28 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.