122814 - [Regression] Can't use non-standard port for SMTP server anymore

Status: VERIFIED DUPLICATE of bug 52330

(SeaMonkey :: MailNews: Account Configuration, defect)

Description

[Ben Bucksch (:BenB)]

Previous and expected result:
In 0.9.4.1, I could open prefs.js and in the pref for the SMTP server name add a
:<port> behind the hostname, e.g.
user_pref("mail.smtpserver.smtp1.hostname", "myserver:26");
I saw "myserver:26" as name in the Account Manager, could select that server for
a certain identity and that way send mail using the SMTP server on that port.
I think I could even have entered "myserver:26" as hostname using the Account
Manager, but I never tried this.

Relevance:
I needed that, because I need to run 2 SMTP servers on the same machine
(firewall), because of the ******* MAPS DUL.

Actual / current result:
Now, the name of the SMTP server is blank (I get a blank entry in the
list/dropdown boxes) and the identity shows 'Always use default server' as
selected SMTP server, although the server smtp1 (which is not the default) is
selected in the backend. If I ignore that and send nevertheless, I get a server
not reachable (although it is).
If I select the blank entry for the identity using the Account Manager, the
default SMTP serve is used or I get server not reachable again.
It's all very odd - I might be wrong with one or more details here.

Comment 1

[Gilles Durys]

This works in Netscape 6.2 (and 0.9.4.1 which is basically NS6.2) but not in
Mozilla.

*** This bug has been marked as a duplicate of 52330 ***

Comment 2

[Ben Bucksch (:BenB)]

tnx