45922 - Migration: Migration ignorse default secure news and imap ports

Status: VERIFIED FIXED

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

Description

[Karen Huang]

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.

Comment 1

[Karen Huang]

Change QA Contact to me since I will take this bug for verify.

Comment 2

[Karen Huang]

Ccing Scott since Seth is in sabbatical.

Comment 3

[Karen Huang]

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.

Comment 4

[lchiang]

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?

Comment 5

[Karen Huang]

*** Bug 47554 has been marked as a duplicate of this bug. ***

Comment 6

[lchiang]

- per mail triage

Comment 7

[Karen Huang]

Are you sure that this will be nsbeta3-?
If without this fix, users will misunderstand that the secure news is broken!!

Comment 8

[Scott MacGregor]

i agree....the fix is trivial too.....clearing to see if we can renominate or at
least make it a mail6....

Comment 9

[scottputterman]

mailtriage marking [nsbeta3-] and mail6

Comment 10

[[e-mail] (gone - use [e-mail] instead)]

*** Bug 53500 has been marked as a duplicate of this bug. ***

Comment 11

[[e-mail] (gone - use [e-mail] instead)]

*** Bug 53500 has been marked as a duplicate of this bug. ***

Comment 12

[scottputterman]

sorry for the extra email. Removing mail2 keyword.

Comment 13

[scottputterman]

Sorry for the extra email. Removing mail6 keyword.

Comment 14

[laurel]

nominating for 6.5

Comment 15

[(not reading, please use [e-mail] instead)]

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)

Comment 16

[(not reading, please use [e-mail] instead)]

Attachment: fix, depends on racham's patch

Comment 17

[(not reading, please use [e-mail] instead)]

that fix is incorrect, I'm working on a correct one.

Comment 18

[(not reading, please use [e-mail] instead)]

Attachment: fix

Comment 19

[(not reading, please use [e-mail] instead)]

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=?

Comment 20

[Scott MacGregor]

sr=mscott

Comment 21

[(not reading, please use [e-mail] instead)]

fixed.

I'm lame for not fixing this for 6.0.

Comment 22

[[e-mail] (gone - use [e-mail] instead)]

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.