Closed
Bug 156382
Opened 23 years ago
Closed 23 years ago
won't let me (re)assign port number for SSL IMAP (incoming server)
Categories
(SeaMonkey :: MailNews: Account Configuration, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 128390
People
(Reporter: tkearns, Assigned: racham)
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530
BuildID: 2002053012
My IMAP service provider lets me connect securely on any port to their
imaps.proxy.fastmail.fm server. This is so that I can use a secure connection
even though my network environment blocks outside access through port 993.
However, if I select SSL for my incoming server and change the port number to
143, then when I click OK, it reverts back to port 993 (without asking/warning me).
If this is not a bug, then what is the point of making the port field editable?
This only happens when I change it to 143 while SSL is selected. Otherwise the
values will stick. This is not much use if your network environment only allows
you out on 143 (and you want a secure connection). In this case, the only
limitation is the browser.
Reproducible: Always
Steps to Reproduce:
1.select SSL for incoming IMAP server
2.change to port 143
3.click OK
4.revisit settings to see if the port is still what you set it as.
Actual Results: Mozilla refused to change it to port 143 (with SSL selected)
Expected Results: Mozilla should keep the port number I set - or warn me that
it's going to ingore it.
Comment 1•23 years ago
|
||
This has nothing to do with the browser.
Assignee: new-network-bugs → racham
Component: Networking → Account Manager
Product: Browser → MailNews
QA Contact: benc → nbaca
Comment 2•23 years ago
|
||
*** This bug has been marked as a duplicate of 128390 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•