Bug 2133 - Mangled non-ASCII chars when FROM and body encoding differ
Summary: Mangled non-ASCII chars when FROM and body encoding differ
Status: RESOLVED WONTFIX
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: UI/Compose Window (show other bugs)
Version: 3.7.5
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2010-03-03 16:54 UTC by Tobias Nissen
Modified: 2010-03-04 09:32 UTC (History)
0 users

See Also:


Attachments
How the message appears in Claws (203.30 KB, image/png)
2010-03-03 17:28 UTC, Tobias Nissen
no flags Details
How the message and its source appear in Claws (281.34 KB, image/png)
2010-03-03 17:29 UTC, Tobias Nissen
no flags Details
How a reply by a Claws user to the concerning message appears (201.50 KB, image/png)
2010-03-03 17:30 UTC, Tobias Nissen
no flags Details
How the compose window looks like when replying to the concerning msg (247.78 KB, image/png)
2010-03-03 17:31 UTC, Tobias Nissen
no flags Details
The raw message causing trouble (5.98 KB, text/plain)
2010-03-03 17:31 UTC, Tobias Nissen
no flags Details
The corrupted (?) mail right out of my Maildir (5.48 KB, text/plain)
2010-03-03 22:41 UTC, Manfred Schmitt
no flags Details
Screenshot when replying (20.10 KB, image/png)
2010-03-03 22:42 UTC, Manfred Schmitt
no flags Details
Replied to message from Maildir (5.17 KB, text/plain)
2010-03-03 22:44 UTC, Manfred Schmitt
no flags Details

Description Tobias Nissen 2010-03-03 16:54:26 UTC
When replying to certain messages, the non-ASCII chars from the quote of the original message sometimes are mangled. Example message:

http://groups.google.de/group/linux.debian.user.german/msg/1aa6872e40b7916a?dmode=source

I think it has something to do with the fact that FROM and body use a different encoding. Messages where FROM and body are in the same encoding don't seem to be affected.

3.7.4 shows the same behaviour.
Comment 1 Colin Leroy 2010-03-03 17:14:11 UTC
I rather think that this message's encoding has been mangled on the way, probably due to 8bit encoding. 

Can you attach a screenshot showing the mail from the From: line to the first "aptitude -V" line, for example ?

Also, can you attach the message source ? I'm not sure the web interface respects the original correctly.

Thanks
Comment 2 Tobias Nissen 2010-03-03 17:28:52 UTC
Created attachment 813 [details]
How the message appears in Claws
Comment 3 Tobias Nissen 2010-03-03 17:29:21 UTC
Created attachment 814 [details]
How the message and its source appear in Claws
Comment 4 Tobias Nissen 2010-03-03 17:30:46 UTC
Created attachment 815 [details]
How a reply by a Claws user to the concerning message appears
Comment 5 Tobias Nissen 2010-03-03 17:31:18 UTC
Created attachment 816 [details]
How the compose window looks like when replying to the concerning msg
Comment 6 Tobias Nissen 2010-03-03 17:31:43 UTC
Created attachment 817 [details]
The raw message causing trouble
Comment 7 Manfred Schmitt 2010-03-03 22:39:36 UTC
The mail that arrived on my server grabbed out of the Maildir (and also in claws-imapcache) has Content-Transfer-Encoding: 8bit, not quoted-printable and looks exactly like the version in googlegroups.
Nonetheless only on replying non-ASCII chars in header and body get mangled.
The mail was a Reply-To to a quoted-printable mail which seems ok to me.
I'm using the de_DE@euro locale.
Comment 8 Manfred Schmitt 2010-03-03 22:41:24 UTC
Created attachment 818 [details]
The corrupted (?) mail right out of my Maildir
Comment 9 Manfred Schmitt 2010-03-03 22:42:41 UTC
Created attachment 819 [details]
Screenshot when replying
Comment 10 Manfred Schmitt 2010-03-03 22:44:42 UTC
Created attachment 820 [details]
Replied to message from Maildir
Comment 11 Manfred Schmitt 2010-03-03 22:53:21 UTC
I'm using claws 3.7.4 backported to Lenny from Debian/unstable if that matters in this case.
Comment 12 Colin Leroy 2010-03-04 09:20:55 UTC
Thanks. There's indeed a problem.
Comment 13 Colin Leroy 2010-03-04 09:32:34 UTC
After a better look, the problem is indeed in the mail. The iso-8859-1 encoded name is no problem, as you can test by removing the encoded part.

But in the signature, the 

Note You need to log in before you can comment on or make changes to this bug.