Bug 313399

Summary:	IMAP source hangs when server has IPv6 address but connection fails
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Erwin Van de Velde <erwin.vandevelde>
Component:	IMAP resource	Assignee:	Christian Mollekopf <chrigi_1>
Status:	RESOLVED WORKSFORME
Severity:	major	CC:	kdepim-bugs, mollekopf, vkrause
Priority:	NOR	Keywords:	triaged
Version:	4.9
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Erwin Van de Velde 2013-01-17 10:07:33 UTC

I have an IPv6 connection through a tunnel and since my mail server supports IPv6, normally all IMAP traffic is sent over IPv6. However, when the IPv6 connection fails (e.g. route failure somewhere along the route), the IMAP resource hangs indefinitely, unable to abort or whatsoever. Other applications like e.g. firefox gracefully fall back to IPv4 connectivity (which was still working) and in my opinion the IMAP resource should do the same.


Reproducible: Always

Steps to Reproduce:
1. Use IMAP resource with a server with both an IPv4 and IPv6 address
2. Make sure your host has IPv4 and IPv6 configured
3. Simulate route failure along the route (e.g. drop IPv6 traffic on the firewall)
Actual Results:  
IMAP resource hangs completely

Expected Results:  
The IMAP resource should fall back on IPv4 connectivity.

Comment 1 Kevin Ottens 2013-11-16 07:29:41 UTC

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

Comment 2 Christian Mollekopf 2013-12-03 17:10:59 UTC

Can you check if this is still the case with >= 4.11.3 and perhaps debug where it hangs?

Comment 3 Andrew Crouthamel 2018-09-25 03:54:54 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 03:35:23 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!