Closed Bug 296076 Opened 20 years ago Closed 20 years ago

Erasing Netscape IMAP account deletes wrong account, persits (renamed) after restarting TB

Categories

(Thunderbird :: Account Manager, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: michaelklinowski, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Netscape account visibly removed before reboot. Once TB restarted, Netscape account reinstated with new name, _last_ POP account in the list removed. Actual mail remained in folder - just no longer displayed in the "Folder" column. Data can be recovered by replacing prefs.js with a backup copy. I originally thought it was an error caused by a TB crash while removing Netscape account the first time I tried. Error occurred again after recovering mail data (replacing prefs.js with a backup copy). I did not experiment with other account removal - this is my business email. Reproducible: Always Steps to Reproduce: 1.Open "Account Settings" 2.Choose Netscape IMAP account 3.Click Remove Account button 4.Verify account removed from "Folders" column (on left) 5.Restart TB 6.Observe that "removed" account has been reinstated, other POP account has been removed Actual Results: "removed" account has been reinstated(with a new name), other POP account has been removed. Expected Results: Removed the account I asked it to, not removed another account that I wanted to keep. I am marking this as Critical, athough data is recoverable. The user may not necessarily know how to recover the mail data and would consider this to be data loss. Feel free to downgrade this to Major if you so choose.
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
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.