User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031111 Debian/1.5-2.backports.org.1 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5) Gecko/20031007 I renamed some folders in my inbox, and the new names contained a semicolon ";". Although I was able to see the mails, drop mails into the folder, and see the from, subject etc, I was unable to view the mail, move it out of the folder, or reply to the mail. Renaming the folder, removing the semicolon removes the problem, giving me access to the mails in the folder again. Reproducible: Always Steps to Reproduce: 1.Rename a folder in your inbox, to contain a semicolon in the foldername 2. 3. Actual Results: What is described in the details box Expected Results: Let me read and reply to the mails

WORKSFORME on Thunderbird 0.7.3 Release build(Win-2K). Creation/renaming/move/delete folder has no problem and folder is accessible always. Reporter, your problem is posiibly Bug 65303. > new folder created with same name as previously renamed folder contains phantom mail - crashes when read Old Mozilla had problems on renaming of folder. - If previously used folder name is used on folder creation, old file information is used from garbage even after restart. But this has been slightly improved. Current Mozilla still has renaming problem but this is only when previously used folder name is used again without restart. Does problem still occur on latest Mozilla release?

I tested this on my Windows 2000 box and the bug exists on this system too. Also putting the "#" (pound) symbol in the subfolder's name also prevents messages from being read.

(In reply to comment #2) > I tested this on my Windows 2000 box and the bug exists on this system too. > Also putting the "#" (pound) symbol in the subfolder's name also prevents > messages from being read. What is your Mozilla build ID you've tested? What is yor locale of OS? What is exact folder name? What files were created/renamed when folder of "#" and ";" are defined/renamed? (See mail directry just after folder creation/renaming) Please note that : Because patch of Bug 262018(for both "#" and ";" problem) for Mozilla trunk was checked-in on 11/18, older build is required to problem recreation, and newer build is required for fix verification. By the way, folder name of ";"(file name =";" when the patch was not applied) did not have problem on Japanese MS Win even before the patch. (After patch, hashed name is used as file name for folder of ";") But Bug 262018 comment #0 talks about ";" just before "/" in URI and problem when this case has been fixed by the patch. Do you know special meaning of ";" in file name/path name on Unix? (I only know first ".", hidden file, and last "~", back up file or home directry indicator on Unix)

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.