Closed Bug 350542 Opened 18 years ago Closed 18 years ago

Mail fails to select startup folder with global inbox

Categories

(SeaMonkey :: MailNews: Account Configuration, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ajschult784, Assigned: ajschult784)

References

()

Details

Attachments

(2 files)

With linux seamonkey build 2006-08-28-09-trunk, I get the message JS frame :: chrome://messenger/content/msgMail3PaneWindow.js :: EnsureFolderIndex :: line 1513" data: no]Exception in LoadStartFolder caused by no default account. We know about this at mail startup, even though there is a default account. The default account uses a global inbox and is set up to not check mail at startup. With this, mail attempts to select the top-level account folder, but because it uses a global index, the top-level folder is missing.
We already had rootMsgFolder, which is what we really want.
Attachment #235865 - Flags: review?(mnyromyr)
JFTR: I didn't actually do a regression window search, but I had some old builds lying around: The Windows nightly 2006-03-10-09 dumps TypeError: msgFolder has no properties on your testcase, Windows nightly 2006-03-22-09 dumps your error message, even though with a slightly different line number.
Attachment #235865 - Flags: review?(mnyromyr) → review+
Attachment #235865 - Flags: superreview?(neil)
Assignee: mail → ajschult
Comment on attachment 235865 [details] [diff] [review] just don't grab the serverURI Looks reasonable. Aside: I noticed we should be using startURI rather than startFolder or startFolderResource.
Attachment #235865 - Flags: superreview?(neil) → superreview+
Attached patch port fix to TBSplinter Review
Attachment #236362 - Flags: review?
Attachment #236362 - Flags: review? → review?(mscott)
Comment on attachment 236362 [details] [diff] [review] port fix to TB thanks a lot Andrew.
Attachment #236362 - Flags: review?(mscott) → review+
landed the TB fix too
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
This appears to have never been fixed on the 1.8 branch. The latest Tb 2 nightly (20070308) is still giving the errors. Scott, is it too late to land this on the branch?
-> bug 373856 for Tb 2.0
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: