Closed
Bug 17285
Opened 25 years ago
Closed 25 years ago
[DOGFOOD] handle migration of nntp servers on non-standard ports (!= 119)
Categories
(MailNews Core :: Backend, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
M11
People
(Reporter: sspitzer, Assigned: sspitzer)
References
Details
(Whiteboard: Verified Win32 & Linux, can't verify MAC)
this is the nntp version of bug 17212
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M11
Assignee | ||
Comment 1•25 years ago
|
||
fix coming as soon as the tree opens...
Assignee | ||
Updated•25 years ago
|
Summary: handle migration of nntp servers on non-standard ports (!= 119) → [DOGFOOD] handle migration of nntp servers on non-standard ports (!= 119)
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 2•25 years ago
|
||
fixed.
Assignee | ||
Comment 3•25 years ago
|
||
marking fixed.
Pref mail.server.server1.port migrates properly with the irregular port number.
Note: this pref doesn't display if server is standard port.
OK using 1999-11-02-10m11 commerical build NT 4.0
OK using 1999-11-01-08m11 commercial build linux 6.0
migration not working on mac (ref bug #16305)
port pref migrates properly using 1999-11-04-08m11 commercial build Mac OS 8.5.1
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•