Closed Bug 277584 Opened 20 years ago Closed 19 years ago

e-mail account deletion

Categories

(SeaMonkey :: Installer, defect)

1.7 Branch
x86
Windows 98
defect
Not set
major

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: randombyter, Unassigned)

Details

when i updated my mozilla 1.7 per Mozillas web page instructions in regards to a
security issue the process deleted all of my e-mail accounts and settings
including all of my e-mail. Even though the browser has some issues with some
web pages i just notify the webmaster but your e-mail client is now on my **** list
forever. I saw lots of remarks about lost e-mail in bug reports but very few
realistic solutions.
And if your updates do this type of damage without informing users of the
consequences the development group has a serious bug to fix. I guess I'll go
back to foxmail and tell everyone I've helped with setting up mozilla that they
need to switch.
i found accounts, they were renamed so i renamed them to the former
and all of my old e-mail seems to be intact
Did you rename these accounts? I didn't know Mozilla renames the accounts out of
nothing ;)?
The really bizzarre aspect of the renaming of the accounts is that in 
renaming one of the accounts only one letter was deleted in the middle 
of the accounts name, one of the other accounts was truncated by an 
entire extension. the others were unimportant so I have not investigated 
them yet. However, the process of updating my Mozilla browser,
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7) Gecko/20040616, from the
Mozilla web page announcement for a so called security patch left me in 
shock when I returned to the e-mail client and found all accounts gone 
and Mozilla asking me if I wanted to set up my mail accounts now. The clue
was in running an undelete program that found nothing that should not 
have been deleted and when I looked in the default e-mail location, voila,
I found large files with strange names and they are now duplicated elsewhere.
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: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.