Closed
Bug 229584
Opened 21 years ago
Closed 21 years ago
pop3 download of message with bad character (0x00) confuses mozilla
Categories
(MailNews Core :: Networking, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 223062
People
(Reporter: newsletters, Assigned: sspitzer)
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031107 Debian/1.5-3 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031107 Debian/1.5-3 If I get mail containing a bad character (seen at least with 0x00), Mozilla Mail doesn't send anything to the server. The mozilla icon indicates that the connection stays open (verified by the Ethereal logs). After the connection terminates (server timeout) Mozilla doesn't react to further "get messages" clicks. Reproducible: Always Steps to Reproduce: 1. A mail with a 0x00 must be in one of the pop3 boxes. 2. Try to download the messages. The first with that bad character will cause the problem. 3. Actual Results: mozilla refuses to properly handle bad messages. Expected Results: should worn about non-rfc-compatible mail, remove the bad characters, continue the pop3 session.
Reporter | ||
Comment 1•21 years ago
|
||
Failed pop3 log in text-format
Reporter | ||
Comment 2•21 years ago
|
||
note the double 0x00 at the and of the mail
Reporter | ||
Comment 3•21 years ago
|
||
Concerning Reproduceable: Always: It worked today possibly because the bad mail was no more the last mail in the pop3 box.
Summary: pop3 download of message with bad character (0x00) confuses mozilla → pop3 download of message with bad character (0x00) confuses mozilla
Comment 4•21 years ago
|
||
This bug has already been fixed some time ago. Please always test with a quite recent build before submitting a bug. *** This bug has been marked as a duplicate of 223062 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•20 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
•