363763 - Some email body with remote content displays as blank content (view as original HTML)

Status: RESOLVED WORKSFORME

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Olivier Vit (just a reporter)]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.9a1) Gecko/20061209 SeaMonkey/1.5a
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.9a1) Gecko/20061209 SeaMonkey/1.5a

Email messages with remote content appear as blank messages until the user authorizes the display of the remote content.

As a result, it isn't possible to read the email content without providing the sender all the tracking information being collected through remote images.

Reproducible: Always

Steps to Reproduce:
1. receive a message containing remote content, whose sender doesn't belong to an address book
2. display the message
3. 

Actual Results:  
it's blank

Expected Results:  
should display the local content

happens on old messages then isn't related to changes in the message body

Comment 1

[Olivier Vit (just a reporter)]

Attachment: source of a sample email received from ebay

Comment 2

[Olivier Vit (just a reporter)]

related to bug 360288 ?

Another very simple message is properly displayed (only the local content) see next attachement

Comment 3

[Olivier Vit (just a reporter)]

Attachment: With this message, the body is displayed properly

Comment 4

[Olivier Vit (just a reporter)]

Fixing the title: doesn't happen for all message contents, but always happens for given messages, for example the ones from ebay

Comment 5

[Mike Cowperthwaite]

I can't reproduce this with SM 1.5a-1209, Win2K.


(See bug 338675, which has a (different) problem with eBay messages like the one you provided, except that your message doesn't have that problem.)

Comment 6

[Olivier Vit (just a reporter)]

upgraded to Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.9a1) Gecko/20061217 SeaMonkey/1.5a

Now works fine for 95% of the time, but even for the same message it can work and fail on another try. Really strange.

Will keep you posted

Comment 7

[Serge Gautherie (:sgautherie)]

Can you reproduce with SeaMonkey v2.0a1pre ?

Comment 8

[Olivier Vit (just a reporter)]

I'm afraid I reverted to v1.1.9 and stopped testing the development builds 

Since nobody is copied to this bug, I would assume that nobody else has had this issue ?