------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=55898 ------- Additional Comments From mutz@kde.org 2003-09-30 11:24 ------- Subject: Re: support for uuencoded attachments doesn't work On Monday 29 September 2003 15:10, Wolf-Michael Bolle wrote: > To change the direction of this discussion a little bit: How hard > would it be in KMail to add parsing the ASCII part of an email for > uuencoded stuff and feed that into the attachment handling? Hacking it in? Probably easy. Doing it right? Very hard. Comparable to PGP clearsigning and that one is already ubiquitous in KMail. Look how many files #include ... There is a reason why uuencode and clearsigning are both deprecated: Combining such things is combinatorically infeasible. Outlook can be configured to not send uuencoded mail, or at least send them as MIME attachments with Content-Transfer-Encoding: x-uuencode, which we support for reading. You can extract the attachments from uuencode-mails by piping them trough a script that calls uudecode and writes the results to a attachment-dump directory with a constructed name. Search the kmail@kde.org archives. Or use KNode. This feature has _very_ low priority, and a steadily decreasing one, too, as uuencoded mails get more and more uncommon. My personal barrier for patch-acceptance is very high with this one. You'd need to design, write and refactor quite a bit of code to provide generic hooks for abstracting the various just-do-it-inline methods, such as PGP clearsigning, inline uu-, yenc- and base64 encoded "attachments", geek codes, etc. But _if_ you've invested that much energy into it, rest assured that I'll help you get it polished for inclusion. Marc _______________________________________________ KMail Developers mailing list kmail@mail.kde.org http://mail.kde.org/mailman/listinfo/kmail