When you launch 5.0 for the first time and get mail, you get an assertion failure since we don't have a summary file for the inbox. Seems like this ought to be a legal and non-surprising thing, at some level.
POP or IMAP?
I've seen it on IMAP. Can't speak for POP.
This bug was filed on pop in particular. But it also happens for imap. If (without having any summary files), you select the server (and not the folder) and then hit get new mail, we asssert because we try to open the db and we have no summary file.
I think we really need to create an inbox folder if one doesn't exist at startup, at least for imap, for reasons other than this bug. I'm going to go see exactly how 4.5 does this.
But David, I think this bug is just as much because we don't have a .msf file as it is because we don't have a folder. So that won't fix the problem will it? People seeing this bug can see it after they just migrated a profile for pop. So your inbox is there. But you hit get new mail before loading the inbox and building a .msf and you assert. Although I agree for imap, we should create the folder right away. I just wonder if that will fix all our problems.
Yes, but I would create an msf file when I created the folder :-)
Status: ASSIGNED → RESOLVED
Last Resolved: 20 years ago
Resolution: --- → FIXED
Summary: Assertion failure when you open an MSF file which doesn't exist → Assertion failure when you open an IMAP MSF file which doesn't exist
fixed by always creating imap inbox.
David does this fix pop too? That's where this bug originally came from....
No, it only fixes IMAP. Phil filed it on IMAP. I thought you meant there was a separate bug filed on POP. I changed the summary to reflect the IMAP nature of what I fixed...
The POP bug is http://bugzilla.mozilla.org/show_bug.cgi?id=14114
Passed by retest on the 10-08-12-M11 commercial build on all the Win98, WinNT, Mac and Linux platforms for the IMAP account: There is no assertion failure anymore even there's no summary file for the inbox.
You need to log in before you can comment on or make changes to this bug.