(In reply to matteo sisti sette from comment #0)
> Actual results:
> "looked up gmail.com" (or whatever is the mail server domain) appears on
> the status bar and stays there for a while. Then it disappears.
> Mail is not checked, and no error message is shown.
> This happens systematically, 100% of the times.
> Then I click "get mail" again, and it ALWAYS works the second time.
This phenomenon can occur if IPv6 relevant problem exists in your environment.
- first DNS lookup(IPv6 address resolution) takes very long
=> timeout, Tb is unable to login.
- upon second DNS lookup by Tb, IPv6 address resolution is alrweady done by
first request, then second DNS look up ends within a shor period.
This started to occur from Tb 3, because defaullt of network.dns.disableIPv6 was changef rom true to false by Tb 3.
What happens if network.dns.disableIPv6=true is set?
(restart Tb after setting change to avoid needless problems)
(In reply to matteo sisti sette from comment #0)
> Actual results:
> "looked up gmail.com" (or whatever is the mail server domain) appears on
> the status bar and stays there for a while. Then it disappears.
> Mail is not checked, and no error message is shown.
> This happens systematically, 100% of the times.
> Then I click "get mail" again, and it ALWAYS works the second time.
This phenomenon can occur if IPv6 relevant problem exists in your environment. dns.disableIPv6 was changef rom true to false by Tb 3.
- first DNS lookup(IPv6 address resolution) takes very long
=> timeout, Tb is unable to login.
- upon second DNS lookup by Tb, IPv6 address resolution is alrweady done by
first request, then second DNS look up ends within a shor period.
This started to occur from Tb 3, because defaullt of network.
What happens if network. dns.disableIPv6 =true is set?
(restart Tb after setting change to avoid needless problems)