Closed Bug 17397 Opened 25 years ago Closed 25 years ago

[DOGFOOD] Need to set port when migrating POP servers w/non-default port

Categories

(MailNews Core :: Backend, defect, P3)

Product:
MailNews Core
Component:
Backend
Platform:
x86
All
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: sspitzer, Assigned: sspitzer)

References

Details

(Whiteboard: Verified Win32 & Linux, can't verify MAC)

just like, #17212, but for pop. fixing coming as soon as the tree opens.
QA Contact: lchiang → laurel
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
marking m11, as that is when it got fixed.
mail.server.server1.port pref set correctly on migration for POP server having irregular port number. OK using 1999-11-01-08m11 commercial build linux 6.0 OK using 1999-11-02-10m11 commercial build NT 4.0 migration not working currently on Mac (ref bug #16305)
Whiteboard: Verified Win32 & Linux, can't verify MAC
Status: RESOLVED → VERIFIED
Can't verify on Mac using the edit server name trick (mail server name field won't allow a colon":" for appending port), so will assume it's okay on mac. port pref migrated fine for news server, so will assume it would do so for mail. Marking verified.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.