Closed
Bug 281996
Opened 20 years ago
Closed 19 years ago
unable to retrieve all mail from server
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: bugzilla41, Assigned: sspitzer)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050208 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050208 I am unable to retrieve all mail from my server (verizon.net). I might get some of it, one or two, or as many as fifteen. Right now I have 31 messages sitting on the server. Preferences: leave mail on server is unchecked. I have no trouble retrieving them from another mail account, such as yahoo, but not from my main account. Also, although I might get some of them, when I check all of the message are still there; i.e., those that I retrieved still appear on the server. I cannot get the rest of them. Reproducible: Always Steps to Reproduce: 1.checking automatically download all message in mail/newgroup preferences 2.double clicking the get messages button 3. Actual Results: I still cannot retrieve the messages. The blue bar at the bottom right indicates it is trying, but never completes to indicate it has retrieved them all. Expected Results: I should have retrieved all messages
Reporter | ||
Comment 1•20 years ago
|
||
I think I figured it out. I deleted the compreg.dat file, and it seems to be ok now. I had come across that in searching to solve a problem with downloading while I was at work, and tried it for the mail. It seems to have done the trick. Unless it persists, consider this closed. Thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Comment 2•20 years ago
|
||
*** Bug 281995 has been marked as a duplicate of this bug. ***
Comment 3•20 years ago
|
||
*** Bug 281997 has been marked as a duplicate of this bug. ***
Updated•20 years ago
|
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Comment 4•20 years ago
|
||
A bug cannot be "fixed" unless there was some patch applied to fix a reproducible mozilla bug. You neither described a reproducible problem, nor submitted nor applied any patch, so this was neither a bug, nor was it "fixed".
Reporter | ||
Comment 5•20 years ago
|
||
OK. I see the difference. I'm not a techie. But my problem is solved anyway. Sorry for the bother.
Comment 6•19 years ago
|
||
No specific bug / patch referenced as the fix. -> WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•