User-Agent: Mozilla/5.0 (Windows; U; Win98; de; rv:1.8.1) Gecko/20061010 Firefox/2.0 Build Identifier: When forwarding a received message which was originally sent as multipart/related, Thunderbird corrupts the special German characters ä ö ü ß. Reproducible: Always Steps to Reproduce: 1. Receive a mail in multipart/related which contains German special characters ä ö ü ß 2. Forward this mail. 3. In the compose window, these characters are corrupted. Actual Results: Corrupted characters. Expected Results: Correct characters

Please supply a message that exhibits the problem: save it as a .EML file, and attach the file to this bug using the Create New Attachment link, above.

*** Bug 361885 has been marked as a duplicate of this bug. ***

Thanks! That message has both text/plain and text/html parts -- which part are you displaying when you view the message? And when you forward, is the compose window HTML or plain text? If both displaying and composing in HTML: are you seeing the images in the forwarded message? That message appears to be properly constructed; if you compare to bug 307023 comment 8, it is structured like the third example I describe there; and as described at that comment, I'm seeing your message properly decoded (both images and 8-bit characters) in the forward window; 8-bit characters are also properly coming across if I view or compose in plain text. The 8-bit character in the Subject header is also being copied correctly to the Subject of the forward. That is: I can't reproduce your problem with this message: I'm seeing these results (both correct and expected) in TB 1.5.0.8 and 2b1-1122. What are your settings for: Tools | Options | Display | Fonts Outgoing Mail [?????] [?] Use the default character encoding in replies Tools | Options | Composition | General [?] For messages that contain 8-bit characters, use 'quoted-printable'... And also: View | Character Encoding | Autodetect > which item is selected?

Reporter, does the issue still occur in the latest supported 2.0.0.x / Shredder trunk nightlies? (1.5.0.x is now end-of-life and the latest supported 2.0.0.x is 2.0.0.16)

Hello, this bug is still active with Version 2.0.0.16 (20080708). But the behavior is different. - I downloaded the attachment in comment #3 and saved id to C:\ - I started Thunderbird and opened this message by "File -> Open" - I forward this mail as inbound Result: Text field is completely empty. My settings as requested: Tools | Options | Display | Fonts Outgoing Mail [?????] --_> ISO-8859-15 [?] Use the default character encoding in replies --> Not activated Tools | Options | Composition | General [?] For messages that contain 8-bit characters, use 'quoted-printable'... -----> Not activated View | Character Encoding | Autodetect is off. Instead, ISO-8859-1 is selected.

id -> it

What I should not: I use the German version of Thunderbird.

What I should note: I use the German version of Thunderbird.

Using "strange mail" attached for test here on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1pre) Gecko/20090711 Lightning/1.0pre Shredder/3.0b3pre ID:20090711031603 I have: comment #0: WFM comment #6: confirmed: I see only header of forward as attached in screenshot Anyone can confirm this?

(In reply to comment #11) > screenshot I could observer it using Strange Mail attached to Comment #3, using both Forward_button and Shift+Forward_button, with View/Message Body As/Simple HTML only. No problem with View/Message Body As/Original HTML & Plain Text. > (Build Id) > Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1pre) Gecko/20090713 Shredder/3.0b3pre

The Strange Mail attached to Comment #3 coresponds to (2) of Bug 394322 Comment #6. According to Comment #6, bug summary and comment #0 is already WORKSFORME(already fixed by unknown patch). And I think problem of Comment #6 is DUP of Bug 394322.

Comment #3 & Comment #6 From abonky@web.de is different from original problem of this bug(Comment #0), and Comment #0 is already WORKSFORME. Closing as WORKSFORME. abonky@web.de, see Bug 394322. If your problem is different from Bug 394322, open separate bug after search B.M.O well for already opened bug.