278083 - message is continuously re-loaded

Status: RESOLVED INCOMPLETE

(MailNews Core :: Networking, defect)

Description

[Maatje]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: Mozilla Thunderbird 1.0 (Windows/20041206)

Message received, Thunderbird 1.0 attempts to read it. Apparently it fails and 
keeps trying. The PoC message below consists of an embedded message which 
contains has a cid referall to a MIME message part with a x-wav content type. 
The content of the CID MIME message part is missing.

This situation happens in real world because of viruses which are stripped and 
returned to their perceived senders. Senders are often forged, so this occurs 
in the wild as a random, non-intentional attack.

PoC raw SMTP message: (copy to file and send message)
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="boundary01"
Content-Disposition: inline

--boundary01
Content-Type: Message/RFC822

Mime-Version: 1.0
Content-Type: multipart/alternative;	boundary="3562634623"

--3562634623
Content-Type: text/html
Content-Transfer-Encoding: 7bit

<iframe src="cid:cid"></iframe>

--3562634623
Content-Type: audio/x-wav; name="test.wav"
Content-Transfer-Encoding: base64
Content-Id: <cid>

--3562634623--

--boundary01--


Reproducible: Always

Steps to Reproduce:
1. Send PoC message to SMTP server
2. Get message from POP3 server
3. Attempt to read message
Actual Results:  
Message seems to be reloaded continuously. Cursor keeps flashing. Progress bar 
keeps returning.

Expected Results:  
Load the message one time, no retries.

Comment 1

[Maatje]

Attachment: Thunderbird reloads this message continuously

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 4

[timeless]

i'm going to try to move this bug to core. for people not reading activity log, dveditz reopened it.

Comment 5

[Scott MacGregor]

Reporter, can you see if this is still a problem in Thunderbird 1.5?

Comment 6

[Scott MacGregor]

This test case isn't even a valid RFC822 message that I can even get Thunderbird to parse as a message. We need a better test case and confirmation that this is a problem in Thunderbird 1.5 before we can block 1.8.0.2 on this.