Attaching an html document confuses outlook



15 years ago
10 years ago


(Reporter: jtate, Assigned: sspitzer)


Firefox Tracking Flags

(Not tracked)



(1 attachment)



15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla Thunderbird 0.5 (20040207)

This probably is not a bug in Thunderbird, but rather Outhouse, but should be
noted just in case it is.  I'm not familiar enough with RFC-822 to know exactly
what's going on.

When composing a text/plain message and attaching a text/html file to said
message to an Outlook or Outlook Express user, the HTML attachment is shown as
the message and the text/plain message as the attachment.

I assume that this is because of outlook's preference for HTML mail, and
mishandling the message, but the format of the message should be reviewed for
RFC compliance.

Reproducible: Always
Steps to Reproduce:
1. Compose an e-mail in text format to a MS Outlook user
2. Attach a HTML file to the message.
3. Send the message, and view the result in Outlook.

Actual Results:  
HTML attachment is displayed as the message with a text/plain attachment rather
than the other way around.

Expected Results:  
Text/plain message should have been displayed instead of the text/html message.

Comment 1

15 years ago
Created attachment 145482 [details]
Sample message as composed by thunderbird

Comment 2

14 years ago
That message looks OK to me, but I don't claim to be an RFC compliance 
specialist.  The text/html part *does* have
  Content-Disposition: inline; filename="List.html"
(see bug 65794) but that shouldn't affect the order of parts in a 
multipart/mixed message.
Assignee: mscott → sspitzer
Component: Message Compose Window → Composition
OS: Windows XP → All
Product: Thunderbird → MailNews
Hardware: PC → All
Version: unspecified → Trunk
Product: MailNews → Core
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.