14409 - [BLOCKER] Cannot open any existing IMAP msg from IMAP folder after migrate from 4.7 to 5.0

Status: VERIFIED FIXED

(MailNews Core :: Networking, defect, P3)

Description

[Karen Huang]

Use 9/20 build on WinNT/98 platform and using migration from 4.7:

1) After migration from 4.7 to 5.0
2) The IMAP folders displayed,
but the msgs didn't displayed even I select the INBOX, Sent, Draft...ect
existing folders which brought from 4.7
3) I got the follwoing msg: The current command didn't succeed. The mail server
responded: nMailbox does not exist.

Actual Results: Didn't display any existing folder's msg on thread pane and msg
body and I got the follwoing msg: The current command didn't succeed. The mail
server responded: nMailbox does not exist.

responded: nMailbox does not exist.

Expected Results: Should display each existing folder's msg on Thread Pane and
displayed in msg body.

Comment 1

[lchiang]

Others including pmock, sol, chriss are running into this.  They don't actually
need to migrate - just install today's build (9/20) and run mail.

Comment 2

[lchiang]

Karen - do you know how to do an IMAP log?  Perhaps, capture the log commands
and paste here as you select the Inbox.

Comment 3

[lchiang]

David - do these comments you made in the mail/news newsgroup apply to this bug?
"Because of the xpidl changes from yesterday, imap is broken in today's build. I
have a simple fix, which I'd like permission to check in. nsImapUrl::SetSpec was
not changed to take a const char *, so it never gets called."

Comment 4

[David :Bienvenu]

I fixed this at 9 this morning - I guess you didn't get respinned builds. This
was caused by the xpidl changes, and no one fixing nsImapUrl::SetSpec to take a
const char * instead of a char *. I thought Leaf was going to respin builds, but
evidently, he didn't.

Comment 5

[Scott MacGregor]

David B. could this be related to the imap problem that kept the tree closed
this morning? Maybe they didn't get the last release build that was respun with
the fix?

Comment 6

[David :Bienvenu]

yes, we overlapped there. Yes, I fixed this.

Comment 7

[lchiang]

cc: leaf.  Leaf - would like to confirm whether or not the the latest Win32
builds that we got from you today has the fix that David mentions.  Thanks!

(If so, great!  At this time, I can't say for sure that everyone who ran into
this problem that I noted were using the latest respun build).

Comment 8

[Daniel (Leaf) Nunes]

I haven't tried migrating, so i really have no idea. I was able to fetch imap
messages with the latest build however, on a clean profile creation.

Comment 9

[lchiang]

That's all that's needed.  I don't think this bug is particular to migrating
although David can surely correct me if I'm wrong!

Comment 10

[David :Bienvenu]

I'm 100% sure that was the problem I fixed (nMailbox does not exist is a
distinctive error). I'm also 100% sure it's fixed, so some people definitely
weren't running my fix. Yes, definitely nothing to do with migration.

Comment 11

[Karen Huang]

I used 9-20-13-M11 (latest build) for opening this bug, so I don't know whether
this build already include the fixed on Windows platform? But I will verify on
today's 9-21 build later.

Comment 12

[Karen Huang]

Passed by retest on the 9-22-09-M11 build. All the IMAP folders' msgs displayed.