This issue is still present in Thunderbird 16. Using port 3268 works here so that was a nice workaround.
This issue is still present in Thunderbird 16. Using port 3268 works here so that was a nice workaround.