14 years ago
5 years ago


(Reporter: facorread, Unassigned)


1.7 Branch

Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050414
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050414

When attaching a rtf document to a new message, it is attached inline and its
contents show in the sent message. An example message:

From - Mon Apr 18 15:17:39 2005
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00800000
Message-ID: <>
Disposition-Notification-To: Fabio Correa <>
Date: Mon, 18 Apr 2005 15:15:30 -0500
From: Fabio Correa <>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050319
X-Accept-Language: en-us, en, es-co
MIME-Version: 1.0
To: ---Recipients---
Subject: Acta 42
Content-Type: multipart/mixed;

This is a multi-part message in MIME format.
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

---Message body:

Apreciados amigos:

Les envío el acta 42 y les invito a hacer sus observaciones. Sigo 
esperando sus comentarios al acta 41.


Content-Type: text/plain;
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;

02020603050405020304}Times New Roman;}{\f27\fswiss\fcharset0\fprq2{\*\panose

---More RTF code---

Reproducible: Always

Steps to Reproduce:
1.Write a new e-mail message.
2.Attach a rtf file.
3.Send the message
Actual Results:  
My recipients should receive the RTF as an attachment.

Expected Results:  
My recipients get a mail message without an attachment, but with lots of strange
codes in the mail body.

The soultion is obvious:

Content-Disposition: attachment;

Comment 1

14 years ago
Sorry, I exchanged the "Actual results" and "Expected results". My mistake.

Comment 2

14 years ago
Related to Core bug 150983, Suite bug 205871 and/or Core bug 213393?


14 years ago
Whiteboard: DUPEME
Version: unspecified → 1.7 Branch


14 years ago
Assignee: sspitzer → mail
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


5 years ago
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.