Closed
Bug 319877
Opened 20 years ago
Closed 19 years ago
POP3 RETR message number is incorrect
Categories
(MailNews Core :: Networking: POP, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: rehfjo, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511
Build Identifier: Thunderbird Version 1.5 (20051201)
Checking a POP3 account sends an incorrect parameter for the RETR command. This error occurs with Thunderbird 1.0.7 as well as 1.5 RC1.
Outlook express sends the correct parameter for the RETR command.
A Sample conversation is included below, comments in <>:
S: +OK POP3 Server Ready <750360eed1e237ac6268f439819cb076@lokalhost>
C: AUTH
S: -ERR Unknown Command.
C: CAPA
S: +OK Brief Capabilities follow <response snipped>
c: USER robert
S: +OK Command Sucessful.
C: PASS password
S: +OK Authorized, Mailbox locked and ready.
C: STAT
S: +OK 1 2993
C: LIST
S: +OK 1 messages (2993 octets).
S: +OK 1 2993
C: UIDL
S: +OK
S: 1 4071365c00000bb7
C: RETR 0 <Client should be sending RETR 1, as defined in LIST response>
S: -ERR No such message (0).
Reproducible: Always
Steps to Reproduce:
1. Check mail on a POP3 account (with 1 message in POP mailbox)
2. Error dialog pops up with "The mail server responded with ....."
Actual Results:
2. Error dialog pops up with "The mail server responded with ....."
Expected Results:
Mail message should download normally, specifically, sending "RETR 1" instead of "RETR 0"
Standard install with no add-on's
Updated•20 years ago
|
Assignee: mscott → nobody
Component: General → Networking: POP
Product: Thunderbird → Core
QA Contact: general
Version: unspecified → Trunk
Summary: POP3 RETR parameter is incorrect → POP3 RETR message number is incorrect
OK, this was a bug in the POP server I was using, in the message I originally posted, the list command was incorrectly including "+OK" in the list response "+OK 1 2993". This caused the RETR command to incorrectly use an invalid parameter.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
| Assignee | ||
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•