| Summary: | kmail want not to decode x-uue attachments | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | Dmitry Morozhnikov <dmiceman> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Right. KMail doesn't decode UUencoded attachments. Please use MIME. Closing as WONTFIX because, last I heard, support for UUencode is not wanted in KMail. There may be a closed wishlist item for this, so you can try and find it and post comments on it. |
Version: (using KDE KDE 3.4.2) Installed from: Gentoo Packages Compiler: gcc3.4.4 OS: Linux Looks like kmail or libkmime does not treat attachments with CTE: x-uue as uuencoded. Such attachments are shown as plain text without decodind. Also they are saved to disk as is. Example message part: =============================================== ------------1AE01EB1B4611B2 Content-Type: text/plain; name="letter-alan.txt" Content-Transfer-Encoding: x-uue Content-Disposition: attachment; filename="letter-alan.txt" begin 644 letter-alan.txt M2&D@06QA;B$-"DAI($1M:71R>2$-"@T*05,^($YO=R!T:&%T('=E(&AA=F4@ M86QL(&AA9"!T:&4@=V5E:V5N9"!T;R!T86ME('-T;V-K+"!)(&%M('=R:71I =============================================== Instead of content i see "begin 644..." both in internal viewer and after "Save As..." Maybe adding one line to kdepim/libkmime/kmime_headers.cpp would fix this, but i`m not sure.. Such attachments are created with at least "X-Mailer: The Bat! (v1.61)"