User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.143 Safari/537.36 Steps to reproduce: Tried to connect to a dual stack IMAP server (has both ipv4 and ipv6 DNS entries), whilst there was a problem with IPv6 (but not IPv4) connectivity between the local machine and the mail server. For dual stack mail servers (which have both ipv4 and ipv6 address entries in DNS), but where there is broken ipv6 connectivity between the Thunderbird user and the mail server (e.g. routing blackhole, firewall misconfiguration etc.), the connection hangs. Actual results: Connection hung (busy icon), for > 5 minutes. Expected results: Rapid fall back to an IPv4 connection, as is implemented for HTTP in #621558 #684893 etc. resulting in the user being unaware of the ipv6 connectivity problem.
Bug 1059268 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.143 Safari/537.36 Steps to reproduce: Tried to connect to a dual stack IMAP server (has both ipv4 and ipv6 DNS entries), whilst there was a problem with IPv6 (but not IPv4) connectivity between the local machine and the mail server. For dual stack mail servers (which have both ipv4 and ipv6 address entries in DNS), but where there is broken ipv6 connectivity between the Thunderbird user and the mail server (e.g. routing blackhole, firewall misconfiguration etc.), the connection hangs. Actual results: Connection hung (busy icon), for > 5 minutes. Expected results: Rapid fall back to an IPv4 connection, as is implemented for HTTP in bug 621558, bug 684893 etc. resulting in the user being unaware of the ipv6 connectivity problem.