If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

IMAP folders get confused when "bad" folder name is encountered

RESOLVED EXPIRED

Status

Thunderbird
General
--
minor
RESOLVED EXPIRED
13 years ago
12 years ago

People

(Reporter: Jorg K (GMT+2), Assigned: Scott MacGregor)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
IMAP folders get confused when "bad" folder name is encountered.
I connected Thunderbird 1.0 to an Exchange server where I had several folders
containing a "/" in their names (which is an illegal character for an IMAP
folder). Thunderbird got quite confused with the folder hierarchy. Problem went
away when I renamed the IMAP folders (using MS Outlook).
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.