| Summary: | kmail sends replies to attachment-emails with arabic encoding | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | Daniel Quinn <expendable.0> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | 1.8 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
the email from the outlook user
my reply |
||
additional note. i just tried a test email *without* an attachment to/from the same user and ran into the same issue. i'm attaching the two emails Created attachment 10883 [details]
the email from the outlook user
Created attachment 10884 [details]
my reply
Duplicate of # 103151 Workaround mentioned: switch of "keep original charset" in the charset options. Some versions of Outlook just display a blank e-mail. Evolution and kmail show it as English text. I can confirm this bug. Also using gentoo, gcc (GCC) 3.3.5-20050130 (Gentoo 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1); Linux asus 2.6.11-gentoo-r9 . Really annoying. Seems to happen mainly in response to Outlook xml messages. I can also confirm this bug and it does seem to be xlm messages from outlook users. May also depend on the version of Outlook as I've only had 2 customers report this as an issue. I can confirm this in FreeBDS-6.0-RELEASE and KDE-3.4.3. |
Version: 1.8 (using KDE 3.4.0, Gentoo) Compiler: gcc version 3.4.3 20041125 (Gentoo Linux 3.4.3-r1, ssp-3.4.3-0, pie-8.7.7) OS: Linux (x86_64) release 2.6.11-gentoo-r6 if you receive an email with an attachment and reply to it, the encoding switches to arabic, even if the encoding in the originating email is us-ascii. example: i sent myself an email with an attachment and received it with the following headers: ... MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_Cb2dCPfzQEXOsOQ" ... --Boundary-00=_Cb2dCPfzQEXOsOQ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline <content here> ... --Boundary-00=_Cb2dCPfzQEXOsOQ Content-Type: text/plain; charset="us-ascii"; name="myattachment.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="myattachment.txt" ... i then hit "reply" and received an email with the following headers: ... MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline ... now i'm sure i could have manually selected the encoding for the return email, but it seems to me that the encoding autodetection isn't working right or it would have used us-ascii for the return mail. i haven't noticed this until recently mainly due to the fact that kmail doesn't complain. but apparently, outlook users get a little popup that asks them to install arabic font in order to read my emails... needless to say, clients are getting confused ;-)