Closed
Bug 227201
Opened 22 years ago
Closed 18 years ago
Adding a profile that was previously removed will trash old mail
Categories
(Thunderbird :: Account Manager, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: david.jobet, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.1; Linux)
Build Identifier:
Say we have a mail account named Free.
Remove that account.
Add it again (with same name).
Old mail have now disapear because it seems Thunderbird will create a new
profile, overwriting the old one without asking before if old found mail
should be trashed or kept.
Reproducible: Always
Steps to Reproduce:
1.Remove account "Free"
2.Add account "Free"
Actual Results:
Old mail from "Free" have disapeared
Expected Results:
Asked a directory named "Free" already exist. Checked it look like a
Thunderbird directory. Look for existent mails. Ask if old mail should be
trashed or kept.
Comment 1•21 years ago
|
||
(In reply to comment #0)
The problem with this is that it's probably in the basic folder creation
routines, as this happens with not just accounts creation/deletion/renaming, it
happens with folders in general.
Z wrote:
> This bug is not MIME-related.
>
> Try this:
>
> Right click on Inbox
> New Folder...
> Dummy > Ok
> Put 1 mail msg in it (a mail msg you can afford to lose forever)
> Rename Dummy to New Dummy > Ok
> Rename New Dummy to Dummy > Ok
> Open Dummy ... Ok, where's the mail message?
Wow! Magic!
I didn't know this bug existed.
Not only that, try this:
Make folder foo
Rename to foobar
Rename to foo (messages vanish)
Rename to foobar
*choke*
"the folder could not be renamed. Perhaps the folder is being reparsed, or the
new name is not a valid folder name."
--
BMO
Comment 2•19 years ago
|
||
I cannot reproduce this with Thunderbird 2 beta 2.
Can you ?
Updated•19 years ago
|
QA Contact: account-manager
Comment 3•18 years ago
|
||
no response, so closing WFM based on comment 2.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•