Bug 380454 - Akonadi IMAP resource neglects to reconnect failed control socket while IDLE connection remains live
Summary: Akonadi IMAP resource neglects to reconnect failed control socket while IDLE ...
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 5.5.1
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-02 07:51 UTC by Matt Whitlock
Modified: 2022-12-06 05:20 UTC (History)
3 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 Matt Whitlock 2017-06-02 07:51:05 UTC
Akonadi IMAP typically maintains two socket connections to the IMAP server: one that executes the "IDLE" command and another for all other commands. If the second connection dies while the IDLE connection remains live, then Akonadi is unable to send any commands to the server, including fetching new messages, fetching updated message flags, updating message flags, and expunging messages. This state persists indefinitely until and unless the IDLE connection dies too, at which time Akonadi then initiates a new connection.

There should be no need to maintain two simultaneous connections in the first place, as the IDLE command can be aborted. Using a single connection both for idling and for other commands would almost certainly fix this bug "for free."
Comment 1 Justin Zobel 2022-11-06 09:24:42 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Matt Whitlock 2022-11-06 12:53:41 UTC
I don't use Akonadi anymore. I switched to a mail client designed for IMAP (Trojitá).
Comment 3 Bug Janitor Service 2022-11-21 05:13:28 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2022-12-06 05:20:12 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!