Summary: | kmail sent mail renames attachments with international characters | ||
---|---|---|---|
Product: | [Applications] kmail | Reporter: | Jose Medellin <jfmc2> |
Component: | mime | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | kekcuha |
Priority: | NOR | ||
Version: | 1.9.5 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Jose Medellin
2006-10-19 01:48:54 UTC
KMail uses the standard way to encode the names of attachments containing international characters. If this is a problem then enable "Outlook-compatible attachment naming" in the Composer configuration. 1. Initially Fixed by modifying the setting outlook-compatible-attachments=true 2. Changed default system locale to es_MX.UTF8 3. Problem back again ignoring outlook-compatible-attachemnts=true option in kmailrc Hi, Ingo... Sorry for not reading the darn instructions correctly... After I read your response I was able to find quite some information about this, but I swear that I did some research before and was unable to find a reference. Anyway, I solved it back then without problems, but unfortunately I'm back because the problem is as well. The thing is that the problem is back again and I'm guessing that it has something to do with the new locale of my machine (which is now UTF-8). I switched because I had several problems in my system and most of them are gone by now. The thing is that only today I realized that the problems with the attachments was back again. It is sending again the attachment "header" in the form of: name*=iso-8859-1''Some%20File%20%20Nam%F3%2Eods Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename*=iso-8859-1''Some%20File%20%20Nam%F3%2Eods even with the outlook-compatible-attachments=true option set in kmailrc!!!. I actually had some problems with the codepages so i was playing with those options. In appearance/Message window i've tried (my kde is in spanish so I don't have the exact legend): 1. - Default Character Set : UTF8 - Prevails over : Auto 2. - Default Character Set : UTF8 - Prevails over : 8859-1 3. - Default Character Set : 8859-1 - Prevails over : Auto 4. - Default Character Set : 8859-1 - Prevails over : UTF8 And also in editor codepage I've tried setting alone (meaning that I delete everything else): 1. - us-ascii 2. - 8859-1 3. - utf-8 4. - locale (which is set to utf-8) And it just doesn't work. I've been playing around with all those settings in an ordered way and just got the same result of kmail sending attachment "headers" the standard way (RFC - Compliant) ignoring the outlook-compatible-attachments=true setting no matter which of the aforementioned settings I changed I've tried at first running 'LC_ALL=en_US kmail' to see if the problem went away, but kmail stays in spanish so I guess it's not working (I remember I have to change X locale, not just kmail, so I have to reset or something and I can't do it right now, only later or tomorrow). I'm going to try some things different to try and debug this a little more, but I guessed that maybe I was missing something really stupid (again!) so I would post here to ask for your precious help.. Also... I used a new user (without any info... removed user kmailrc and only used /usr/share/kde/3.5/share/config/kmailrc - which had no other line but outlook-compatible-attachments=true -). I opened kmail and the option in kmail configuration of compatibility of attachments with outlook was checked, but upon composing a mail the same RFC-Compliant (Outlook incompatible) way of inserting attachments was used. Thanks a lot, and really really sorry if I'm wasting your time (again!) oohhh and BTW, have a great 2007!! Mede Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback. It's seems like this bug still valid in Kmail2 (i use version 5.1.3). Still unfixed in 5.2.3 And unfortunately i've submit duplicate bug- https://bugs.kde.org/show_bug.cgi?id=362650 |