205871 - Incorrect display of .rtf attachment

Status: NEW

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Michael Baffoni]

I received an email with an attached .rtf file.  Mozilla displayed the raw
contents of the file, rather than suppress it (or use some sort of .rtf viewer
for that matter).  Here is an excerpt of the attachment:

-------
------=_NextPart_000_1275_361_2a3b
Content-Type: text/richtext; name="Jermille Resume.rtf"
Content-Transfer-Encoding: 8bit

Content-Disposition: attachment; filename="Jermille Resume.rtf"

{\rtf1\ansi\ansicpg1252\uc1
\deff0\deflang1033\deflangfe1033{\fonttbl{\f0\froman\fcharset0\fprq2{\*\panose
02020603050405020304}Times New Roman;}{\f3\froman\fcharset2\fprq2{\*\panose
05050102010706020507}Symbol;}
{\f28\fscript\fcharset0\fprq2{\*\panose 03010101010201010101}Monotype
Corsiva;}{\f31\froman\fcharset238\fprq2 Times New Roman
CE;}{\f32\froman\fcharset204\fprq2 Times New Roman
Cyr;}{\f34\froman\fcharset161\fprq2 Times New Roman Greek;}
{\f35\froman\fcharset162\fprq2 Times New Roman
Tur;}{\f36\froman\fcharset177\fprq2 Times New Roman
(Hebrew);}{\f37\froman\fcharset178\fprq2 Times New Roman
(Arabic);}{\f38\froman\fcharset186\fprq2 Times New Roman Baltic;}
---------

If it matters, this was sent via a hotmail account.... (Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_1275_361_2a3b"
Message-ID: <[e-mail]>)

Mozilla 1.4b release (Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b)
Gecko/20030507).

Comment 1

[Philip Wall]

This is related to bug #150983 and I can confirm that it is still present in
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3) Gecko/20030312
I would suggest that Mail News should instead of defaulting to plain/text it
should default to application/binary or atleast not attempt to show RTF
attachments inline and not send them that way.

Comment 2

[Vytautas]

This issue still appears in Mozilla1.6. 

Is any way to disable automatic opening of attachments?
This can be solution for the moment.

Comment 3

[Michael Baffoni]

Yes, just go to view->display attachments Inline and uncheck the preference.

Comment 4

[Mike Cowperthwaite]

Microsoft's RTF is registered with IANA as  text/rtf  and is not handled 
natively by Mozilla; an attachment with this type will not be displayed inline.
In my installation at least, attaching a .RTF file under Windows results in an 
attachment with text/rtf as the type.  This may because my registry has:
  HKEY_CLASSES_ROOT\.rtf
    Content-Type="text/rtf"

On the other hand,  text/richtext  is described in RFC1341, and is handled 
natively by Mozilla (there is also  text/enriched  -- RFC1896 -- again handled 
natively).  If an attachment has one of those types (and those types are how 
Mozilla determines handling of an attachment), Mozilla will display it inline 
even if it has Content-Disposition:attachment -- this is bug 147461.

If the text of the attachment does not follow the RFC, that is not Mozilla's 
fault.

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 6

[Jean-François Perron]

this bug did happen to me seamonkey 2.0 official windows XP SP2
the attachment was filename.doc but in rtf, I could see raw rtf in the attachment display.
my opinion is if rtf rendering is not possible, do not try to show inline.
of course I could open the attachment as usual in usual text viewer or text editor

Comment 7

[Serge Gautherie (:sgautherie)]

(In reply to comment #6)

Which Content-Type? text/rtf, text/richtext, other?

Comment 8

[Jean-François Perron]

I do not know where I can get the "content type" you are speaking about (it's an email message, did you get it ?)
I can recognize rtf stuff that's all, and the rendering in a text processor was ok, let's see how was the beginning : 
 
dossier exemple.doc

{\rtf1\ansi\deff1\adeflang1025
{\fonttbl{\f0\froman\fprq2\fcharset0 Times New Roman;}{\f1\fswiss\fprq0\fcharset0 Arial;}{\f2\fswiss\fprq2\fcharset0 Arial;}{\f3\fswiss\fprq0\fcharset0 Arial;}{\f4\fnil\fprq0\fcharset0 Wonton ICG;}{\f5\fnil\fprq2\fcharset0 Lucida Sans Unicode;}{\f6\fnil\fprq2\fcharset0 Tahoma;}{\f7\fnil\fprq0\fcharset0 Tahoma;}}
{\colortbl;\red0\green0\blue0;\red128\green128\blue128;}

Comment 9

[Jean-François Perron]

Ctrl U gave lot of information :
--cut
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
--cut
--------------040203000808040608020602
Content-Type: text/plain;
 name="dossier exemple.doc"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="dossier exemple.doc"

e1xydGYxXGFuc2lcZGVmZjFcYWRlZmxhbmcxMDI1DQp7XGZvbnR0Ymx7XGYwXGZyb21hblxm
cHJxMlxmY2hhcnNldDAgVGltZXMgTmV3IFJvbWFuO317XGYxXGZzd2lzc1xmcHJxMFxmY2hh
--cut

Comment 11

[peter]

The bug also affects the TB 3.1.2 upgraded from 2.x: if the .rtf file is opened in TB directly from atachement, it gets opened by the right application, (say, OOo.org), however being opened as plaintext (raw). If the file is saved to the disk and opened from there in Explorer, it is displayed by the same app, however correctly this time.

This bug may be related to Bug 363764.