Closed
Bug 198308
Opened 22 years ago
Closed 22 years ago
new, multiple file folders generated when accessing email
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
People
(Reporter: regor, Assigned: asa)
Details
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130
when i access my email, the file "nstmp and nstmp-n [where n is a number] is
generated. usually there are three files, - nstmp, nstmp-1, nstmp-2 generated
each time. when i delete the folders, the next time the file nstmp-n being the
next numbers in sequence are generated. have no idea why. this is for 1.2.1
version.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
also need to mention problem with latest version 1.3. when i attempt to delete
the emails after they are downloaded to my system, i am usually able to remove
only one or two. i have a small pgm that show the data being transfered and
there is a data dropoff and nothing being transferred in the meantime. in i go
back to the browser itself, it seems to be working and shows the transmission
taking place. if i shut down the browser and restart it i can usually get
maybe one or two emails deleted and then the signal drops off. also sometimes,
and not every time, the files "mstmp" are generated when attempting to delete
the emails. this occurred in both the 1.3a version and the latest version 1.3,
that i downloaded from your site yesterday. don't know whether it is mozilla
doing it or email account. did talk with the support on my isp, and they are
saying that it is the browser that is the problem. also they didn't really want
to talk about supporting mozilla, only netscape and outlook express. awaiting
reply. wish i could give you more info, but that is what is happening.
*** This bug has been marked as a duplicate of 88515 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•