2010515 - account hub: port input green validation checkmarks - confusing, and wrong - can't autodetect port

Status: RESOLVED WONTFIX

(Thunderbird :: Account Manager, defect)

Description

[Vlad Lucaci, Thunderbird QA (:vlucaci)]

Attachment: Screenshot 2026-01-15 at 10.48.33.png

Affected versions

• 149.0a1(20260114100257)
• 148.0b1(20260113151928)

Affected platforms

• macOS 15.5
• macOS 26
• Windows 11
• Windows 10
• Ubuntu 24
• Ubuntu 25

Steps to reproduce

1. Add a new account via Accounts Hub.
2. Input a valid email address(IMAP or POP3)
3. Click on Manual Configuration.

Expected result

• The Port is correctly detected as 993(imap) with a green checkmark.

Actual result

• The Port is detected as 143 with a green checkmark.

Notes

• The user can get past this screen with this incorrect information (port 143 and Connection Security as SSL\TLS) but at the end of the configuration, the Continue button will remain greyed out.
• This issue is not present in 140.6.0esr (The 993 port with SSL\TLS connection security is correctly detected)

Comment 1

[Vlad Lucaci, Thunderbird QA (:vlucaci)]

Closing this issue as invalid after discussing with Martin. Port number information cannot be pulled from the first screen.

Comment 2

[Magnus Melin [:mkmelin]]

Certainly confusing with checkmarks for the dropdown. Apparently it means it's valid, but that doesn't make much sense as a dropdown can not have invalid values, and in this case even blank IS valid, as that will be used for autodetect.

Re-using the bug for that.

Comment 3

[Martin Giger [:freaktechnik]]

(In reply to Magnus Melin [:mkmelin] from comment #2)

Certainly confusing with checkmarks for the dropdown. Apparently it means it's valid, but that doesn't make much sense as a dropdown can not have invalid values, and in this case even blank IS valid, as that will be used for autodetect.

Re-using the bug for that.

It's not a dropdown, it's a number input field. The field is also currently required, so you can't leave it empty. As far as I understand, guess config will still try the autodetect ports anyway, but currently there's no explicit autodetect for the port. These are things we're re-visiting with the manual config overhaul.

Comment 4

[Magnus Melin [:mkmelin]]

Ah, indeed.

But how could you then autodetect port?
This used to work in the old wizard

Comment 5

[Martin Giger [:freaktechnik]]

We will rework this logic in bug 1931015.