Bug 222287

Summary:	IMAP resource gets disconnected for inactivity in reading
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Dennis Schridde <heri+kde>
Component:	IMAP resource	Assignee:	Christian Mollekopf <chrigi_1>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	laurent.rineau, vkrause
Priority:	NOR	Keywords:	triaged
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Dennis Schridde 2010-01-11 21:54:33 UTC

Version:           4.4_rc1 / 4.3.90 (using Devel)
Compiler:          gcc 4.4.2 Gentoo 4.4.2 p1.0
OS:                Linux
Installed from:    Compiled sources

When doing a synchronization of my IMAP data it will usually happen after a while, that:
* dovecot logs something like: Disconnected for inactivity in reading our output bytes=37634/8595795
* akonadiconsole shows: There is currently no connection to the imap server. (translated from german)

It also happens very often that the imap resource just hangs and does seemingly nothing, while it should actually fetch lots of emails. iftop and nethogs show no or almost no traffic during that time. akonadiconsole/debugger shows just some "FETCH" lines (telling from my mind) every few minutes.

Comment 1 Kevin Ottens 2010-01-25 17:59:17 UTC

This one is really providing not enough information to be useful to me. I need more precise steps on how to make it stuck like that, etc.

Comment 2 Kevin Ottens 2013-11-16 07:31:05 UTC

The IMAP resource has a new maintainer, reassigning to him.

Comment 3 Andrew Crouthamel 2018-09-25 03:56:51 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 set the bug status 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 Andrew Crouthamel 2018-10-27 02:10:07 UTC

Dear Bug Submitter,

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!