User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:188.8.131.52) Gecko/20110303 Thunderbird/3.1.9 For a new account, there is a display of what TBird decides is the suggested or appropriate server settings. On return of discovered settings, I notice a few things: Mostly this is related to the width of the columns of server names and domain names. They are too narrow, so account names like pop...secureserver.net don't get displayed in full [their right ends truncated off]. Fix is probably accounting for long domain names and or missing cross checks and workings. Reproducible: Always
The redesigned account wizard (bug 549045) has changed that reporting format and does no longer use a table for displaying the identified configuration. Instead, it's a single label now, have a look at attachment 517569 [details]. It might still apply to the Manual Setup, which still has a fixed width for the form fields but allows scrolling therein when modifying the host name. That's shown in attachment 517570 [details].
Ludo, do you have any really long server-name entry in the ISPDB to verify? Judging from the account with the longest names I've access to, the redesigned account wizard shouldn't have problems to accommodate some 40-50 characters per server name in the reporting page. When going to Manual Config, 25-30 characters should be possible in those entries, then you have to scroll (and that's manual mode anyway, thus you'd inspect and modify the full entry). So, from my point of view this is "works for me" on trunk after bug 549045.
(In reply to comment #2) > Ludo, do you have any really long server-name entry in the ISPDB to verify? > No but based on https://live.mozillamessaging.com/autoconfig/v1.1/ I would try one of the Japanese domains. rainbow.mail.plala.or.jp symphony.mail.plala.or.jp are probably the longuest we have. Another trick would be to find a very long google/hosted name.
I tried firstname.lastname@example.org email@example.com and stopped the automated process by clicking manual. I don't see the problem described by this bug. But I did notice in server field that "server name" started with a period, for example ".rainbow.mail.plala.or.jp"
WFM based on comment 4