Closed Bug 45922 Opened 24 years ago Closed 24 years ago

Migration: Migration ignorse default secure news and imap ports

Categories

(MailNews Core :: Profile Migration, defect, P3)

x86
All

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: huang, Assigned: sspitzer)

References

Details

(Whiteboard: [nsbeta3-] relnote-user)

Attachments

(2 files)

Used 07-19-11-M17 commercial build for all the platforms

News Migration: Migration ignore default secure news port 563

1) Setup a 4.x profile with default secure news port 563
(ex: news://secnews/netscape.champions with the SSL checked and port 563 setup)
2) Migrate this profile and try to see those secnews/newsgroups got migrated.
3) Actual Results: Migration ignore default secure news port 563 -- From the 
Folder Pane, users can see the secnews got migrated, but no newsgroups list 
under this secure news server until I go to Account setting to change the port 
number from 119 to 563.

Expected results: users should see the newsgroups list under this secure news 
server and allow to access without changing the port number from the account 
settings.
Change QA Contact to me since I will take this bug for verify.
QA Contact: gbush → huang
Ccing Scott since Seth is in sabbatical.
Change platforms to all since problem is occurring to all the platforms.
Changing the serverity to major since without this fix, users cannot access 
migrated secure news successfully.
Severity: normal → major
OS: Windows NT → All
If you correct the port number manually and then see all of the newsgroups, does 
the read/unread number of the newsgroups show correctly from 4.x?
Keywords: nsbeta3, relnote2
*** Bug 47554 has been marked as a duplicate of this bug. ***
Keywords: mail2
- per mail triage
Whiteboard: [nsbeta3-]
Are you sure that this will be nsbeta3-?
If without this fix, users will misunderstand that the secure news is broken!!
i agree....the fix is trivial too.....clearing to see if we can renominate or at
least make it a mail6....
Whiteboard: [nsbeta3-]
mailtriage marking [nsbeta3-] and mail6
Keywords: mail6
Whiteboard: [nsbeta3-]
*** Bug 53500 has been marked as a duplicate of this bug. ***
*** Bug 53500 has been marked as a duplicate of this bug. ***
Keywords: relnote3, relnoteRTM
sorry for the extra email. Removing mail2 keyword.
Keywords: mail2
Sorry for the extra email. Removing mail6 keyword.
Keywords: mail6
Whiteboard: [nsbeta3-] → [nsbeta3-] relnote-user
nominating for 6.5
Keywords: mail3
QA Contact: huang → laurel
I just noticed that the same problem exists for secure imap servers.  updating 
summary. (secure imap servers that use the default port migrate over to port 
143.)

as soon as racham lands his fix for 48092, I can land my fix for this.

(it stinks that I didn't fix this for 6.0)
Status: NEW → ASSIGNED
Summary: News Migration: Migration ignore default secure news port 563 → Migration: Migration ignorse default secure news and imap ports
that fix is incorrect, I'm working on a correct one.
here is the proper fix.

now secure imap and secure news servers get migrated over with the proper ports
and isSecure set properly.

mscott, sr=?
sr=mscott
fixed.

I'm lame for not fixing this for 6.0.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
QA Contact: laurel → stephend
Okay, this is FIXED, users no longer have to check the secure news port or SSL
to see their newsgroups, but we aren't displaying the proper subscribed groups
until we restart the app after migration.  I've filed a new bug covering this in
bug 63223.  So, marking this FIXED on Windows 2000, 2000121804, Mac 2000121808
and Linux 2000121808.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: