Closed
Bug 216691
Opened 22 years ago
Closed 18 years ago
Mailbox does not exist error when syncing mail
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: amp68, Assigned: mscott)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
I have Thunderbird 0.1 installed on my laptop and whenever I sync my IMAP mail
for offline use, I end up getting an error stating "Mailbox does not exist." If
I then click on all the folders on my list, I eventually find the one that does
not exist, only to have it exist about 10 seconds later. I then end up having
another folder that does not exist completely different from the original one.
If I quit our of Thunderbird and go back in, all folders exist for a brief time
before the cycle starts all over again.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1•22 years ago
|
||
*** Bug 216692 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 2•22 years ago
|
||
Here's some more detail for you. At home I use MacOS X and it uses a folder
called Deleted Messages as the IMAP trash folder. When I told Thunderbird to
sync all folders except the Deleted Messages folder, all of the sudden, the
error went away. Go figure. Hope this helps in some way towards resolving the
issue.
Updated•22 years ago
|
QA Contact: asa
Comment 3•20 years ago
|
||
Reporter, can you please try reproduce this error on a newer build?
Updated•18 years ago
|
QA Contact: front-end
Reporter | ||
Comment 4•18 years ago
|
||
I forgot I even had this bug open all this time! I am running Thunderbird 2.0 now and have not seen this bug in years.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Comment 5•18 years ago
|
||
"Fixed by who knows what, or when" is "WORKSFORME", but thanks for letting us know it's not a problem any more.
Resolution: FIXED → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•