Closed
Bug 216449
Opened 22 years ago
Closed 21 years ago
mail is not retrived from mailbox due to RETR command did not succeed
Categories
(MailNews Core :: Networking: POP, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 146453
People
(Reporter: dlandgraf, Assigned: sspitzer)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
the server side contains one e-mail with a bad header in one of my two e-mail
accounts. under outlook express the following error message is given:
Cannot retrieve message 1. Account: 'mail (1)', Server: '127.0.0.1', Protocol:
POP3, Reactie van server: '-ERR no such message.', Poort: 9999, Beveiligd(SSL):
Nee, Serverfout: 0x800CCC90, Foutnummer: 0x800420CD
Outlook Express skips this message giving an alert, but retrieves all other
messages from this partucular mailbox. Mozilla Mail however hooks up with
an alert RETR command did not succeed , but fails to retrieve other messages
from this particular mail box
Reproducible: Always
Steps to Reproduce:
1.opened mailbox
2.get messages ( read messages)
3.
Actual Results:
Alert:
the RETR command did not succeed. Mail server mail.home.nl repond: no such message
Expected Results:
show the alert, but retrieve all other messages in the mailbox
Comment 1•22 years ago
|
||
Probably duplicate of bug 146453. This problem also occurs on Mac OS X build
1.5b nightly 20030814. Suspect part of problem may be antiquated POP software on
server; in my case, the IMail server: "+OK X1 NT-POP3 Server mail.wwow.com
(IMail 5.04 17742-1)". But Mozilla still should respond better. Is there no way
to send a request to force a current message list from the server?
Comment 2•21 years ago
|
||
*** This bug has been marked as a duplicate of 146453 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•