(*** This bug was imported into bugs.kde.org ***) Package: kmail Version: 1.91 kmail is unable to automatically unpack uuencoded attachments such as those typically sent by Eudora. The following is an example message: Received: [... snip snip ...] Message-Id: [... snip snip ...] X-Sender: [... snip snip ...] X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu 13 Jul 2000 05:45:39 +0100 To: [... snip snip ...] From: [... snip snip ...] Subject: [... snip snip ...] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=====================_305378==_" Content-Length: 45855 Status: RO --=====================_305378==_ Content-Type: text/plain; charset="us-ascii"; format=flowed [... snip snip ...] --=====================_305378==_ Content-Type: application/msword; name="foo.doc"; x-mac-type="42494E41"; x-mac-creator="4D535744" Content-Transfer-Encoding: x-uuencode Content-Disposition: attachment; filename="foo.doc" begin foo.doc MT\1X*&Q&N$`````````````````````/@`#`/[_"0`&```````````````! M````.P``````````$```/0````$```#^____`````#H```#_____________ M____________________________________________________________ [... snip snip ...] (```````````` ` end --=====================_305378==_-- -- "Once ... in the wilds of Afghanistan I lost my corkscrew and we were forced to live on nothing but food and water for days." -- W. C. Fields "My Little Chickadee" ________________________________________________________________ Jon Connell Senior Software Engineer Development Systems Email : Jon.Connell@arm.com ARM Ltd Direct Office : +44 1223 400540 110 Fulbourn Rd Office Switch : +44 1223 400400 Cambridge Office Fax : +44 1223 400410 CB1 9NJ Mobile : +44 7720 046764 UK Visit ARM Modelling at http://www.arm.com/DevSupp/EDA/ ________________________________________________________________
Please forward me an example mail. BFN Don. On Mon 17 Jul 2000 Jon Connell wrote: > Package: kmail > Version: 1.91 > > kmail is unable to automatically unpack uuencoded attachments such as > those typically sent by Eudora. The following is an example message: > > Received: [... snip snip ...] > Message-Id: [... snip snip ...] > X-Sender: [... snip snip ...] > X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 > Date: Thu 13 Jul 2000 05:45:39 +0100 > To: [... snip snip ...] > From: [... snip snip ...] > Subject: [... snip snip ...] > Mime-Version: 1.0 > Content-Type: multipart/mixed; > boundary="=====================_305378==_" > Content-Length: 45855 > Status: RO > > > --=====================_305378==_ > Content-Type: text/plain; charset="us-ascii"; format=flowed > > [... snip snip ...] > > --=====================_305378==_ > Content-Type: application/msword; name="foo.doc"; > x-mac-type="42494E41"; x-mac-creator="4D535744" > Content-Transfer-Encoding: x-uuencode > Content-Disposition: attachment; filename="foo.doc" > > > begin foo.doc > MT\1X*&Q&N$`````````````````````/@`#`/[_"0`&```````````````! > M````.P``````````$```/0````$```#^____`````#H```#_____________ > M____________________________________________________________ > > [... snip snip ...] > > (```````````` > ` > end > > --=====================_305378==_--
On Mon 17 Jul 2000 Don Sanders wrote: >Please forward me an example mail. Errm. I did. I cut out some confidential bit that's all. Jon. >BFN >Don. > >On Mon 17 Jul 2000 Jon Connell wrote: >> Package: kmail >> Version: 1.91 >> >> kmail is unable to automatically unpack uuencoded attachments such as >> those typically sent by Eudora. The following is an example message: >> >> Received: [... snip snip ...] >> Message-Id: [... snip snip ...] >> X-Sender: [... snip snip ...] >> X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 >> Date: Thu 13 Jul 2000 05:45:39 +0100 >> To: [... snip snip ...] >> From: [... snip snip ...] >> Subject: [... snip snip ...] >> Mime-Version: 1.0 >> Content-Type: multipart/mixed; >> boundary="=====================_305378==_" >> Content-Length: 45855 >> Status: RO >> >> >> --=====================_305378==_ >> Content-Type: text/plain; charset="us-ascii"; format=flowed >> >> [... snip snip ...] >> >> --=====================_305378==_ >> Content-Type: application/msword; name="foo.doc"; >> x-mac-type="42494E41"; x-mac-creator="4D535744" >> Content-Transfer-Encoding: x-uuencode >> Content-Disposition: attachment; filename="foo.doc" >> >> >> begin foo.doc >> MT\1X*&Q&N$`````````````````````/@`#`/[_"0`&```````````````! >> M````.P``````````$```/0````$```#^____`````#H```#_____________ >> M____________________________________________________________ >> >> [... snip snip ...] >> >> (```````````` >> ` >> end >> >> --=====================_305378==_-- -- "After two days in hospital I took a turn for the nurse." -- W. C. Fields ________________________________________________________________ Jon Connell Senior Software Engineer Development Systems Email : Jon.Connell@arm.com ARM Ltd Direct Office : +44 1223 400540 110 Fulbourn Rd Office Switch : +44 1223 400400 Cambridge Office Fax : +44 1223 400410 CB1 9NJ Mobile : +44 7720 046764 UK Visit ARM Modelling at http://www.arm.com/DevSupp/EDA/ ________________________________________________________________
On Mon 17 Jul 2000 Jon Connell wrote: > Package: kmail > Version: 1.91 > > kmail is unable to automatically unpack uuencoded attachments such as > those typically sent by Eudora. The following is an example message: UU-Encoded Attachments are no Email standard. Use Base64 encoding like everybody else and you are fine. --Stefan (former Eudora user)
On Mon 17 Jul 2000 Stefan Taferner wrote: >On Mon 17 Jul 2000 Jon Connell wrote: >> Package: kmail >> Version: 1.91 >> >> kmail is unable to automatically unpack uuencoded attachments such as >> those typically sent by Eudora. The following is an example message: > >UU-Encoded Attachments are no Email standard. >Use Base64 encoding like everybody else and you are fine. Fair enough. Time to go and bang some heads... Jon. -- The C Programming Language -- A language which combines the flexibility of assembly language with the power of assembly language. ________________________________________________________________ Jon Connell Senior Software Engineer Development Systems Email : Jon.Connell@arm.com ARM Ltd Direct Office : +44 1223 400540 110 Fulbourn Rd Office Switch : +44 1223 400400 Cambridge Office Fax : +44 1223 400410 CB1 9NJ Mobile : +44 7720 046764 UK Visit ARM Modelling at http://www.arm.com/DevSupp/EDA/ ________________________________________________________________
On Mon 17 Jul 2000 Jon Connell wrote: > On Mon 17 Jul 2000 Don Sanders wrote: > >Please forward me an example mail. > > Errm. I did. I would like a raw mail message as an attachment. > I cut out some confidential bit that's all. If you can reproduce the problem with a new mail that's fine but I do want a complete mail (file->save as then send the file as an attachment) rather than just a description of a mail. Thanks Don. > > Jon. > > >BFN > >Don. > > > >On Mon 17 Jul 2000 Jon Connell wrote: > >> Package: kmail > >> Version: 1.91 > >> > >> kmail is unable to automatically unpack uuencoded attachments such as > >> those typically sent by Eudora. The following is an example message: > >> > >> Received: [... snip snip ...] > >> Message-Id: [... snip snip ...] > >> X-Sender: [... snip snip ...] > >> X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 > >> Date: Thu 13 Jul 2000 05:45:39 +0100 > >> To: [... snip snip ...] > >> From: [... snip snip ...] > >> Subject: [... snip snip ...] > >> Mime-Version: 1.0 > >> Content-Type: multipart/mixed; > >> boundary="=====================_305378==_" > >> Content-Length: 45855 > >> Status: RO > >> > >> > >> --=====================_305378==_ > >> Content-Type: text/plain; charset="us-ascii"; format=flowed > >> > >> [... snip snip ...] > >> > >> --=====================_305378==_ > >> Content-Type: application/msword; name="foo.doc"; > >> x-mac-type="42494E41"; x-mac-creator="4D535744" > >> Content-Transfer-Encoding: x-uuencode > >> Content-Disposition: attachment; filename="foo.doc" > >> > >> > >> begin foo.doc > >> MT\1X*&Q&N$`````````````````````/@`#`/[_"0`&```````````````! > >> M````.P``````````$```/0````$```#^____`````#H```#_____________ > >> M____________________________________________________________ > >> > >> [... snip snip ...] > >> > >> (```````````` > >> ` > >> end > >> > >> --=====================_305378==_--
--------------Boundary-00=_K2OUZXZHYUDX85A9SC48 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon 17 Jul 2000 Don Sanders wrote: >On Mon 17 Jul 2000 Jon Connell wrote: >> On Mon 17 Jul 2000 Don Sanders wrote: >> >Please forward me an example mail. >> >> Errm. I did. > >I would like a raw mail message as an attachment. > >> I cut out some confidential bit that's all. > >If you can reproduce the problem with a new mail that's fine but I do > want a complete mail (file->save as then send the file as an attachment) > rather than just a description of a mail. Here is a uuencoded attachment. Eudora can actually sent Base64 mails but= =20 I guess that since many MUAs can handle uuencode kmail should too. Jon. --=20 "As the poet said 'Only God can make a tree' -- probably because it's so hard to figure out how to get the bark on". -- Woody Allen ________________________________________________________________ Jon Connell Senior Software Engineer Development Systems Email : Jon.Connell@arm.com ARM Ltd Direct Office : +44 1223 400540 110 Fulbourn Rd Office Switch : +44 1223 400400 Cambridge Office Fax : +44 1223 400410 CB1 9NJ Mobile : +44 7720 046764 UK Visit ARM Modelling at http://www.arm.com/DevSupp/EDA/ ________________________________________________________________ =00 --------------Boundary-00=_K2OUZXZHYUDX85A9SC48 Content-Type: application/octet-stream; name="general.idf" Content-Transfer-Encoding: x-uuencode Content-Disposition: attachment; filename="general.idf" begin 644 general.idf M4DE&1H8"``!)1$8@3$E35"`!``!-34%0:&1R("D````I``````$```$````8 M````1V5N97)A;"!-241)($EN<W1R=6UE;G0`>`!I;G-TI0```*4````````` M```````````4````*````!@````P````56YS<&5C:69I960@0V]M<&%N>0!5 M`&X`<P!P`&4`8P!I`&8`:0!E`&0`(`!#`&\`;0!P`&$`;@!Y````1V5N97)A M;"!-241)($EN<W1R=6UE;G0`1P!E`&X`90!R`&$`;``@`$T`20!$`$D`(`!) M`&X`<P!T`'(`=0!M`&4`;@!T````(`!C87!S&````!@````!`````0```!`` M```0````$````&-H86X4````%````/_]`````@``=``L``````!25-44@$` M`$U-05!H9'(@*@```"H``````0```0```!D```!097)C=7-S:6]N(&]N($-H M86YN96P@38``&EN<W38````V````````````````````!0````H````*0`` M`%(```!5;G-P96-I9FEE9"!#;VUP86YY`%4`;@!S`'``90!C`&D`9@!I`&4` M9``@`$`;P!M`'``80!N`'D```!-241)($EN<W1R=6UE;G0@=VET:"!$<G5M M<R!O;B!#:&%N;F5L(#$V`$T`20!$`$D`(`!)`&X`<P!T`'(`=0!M`&4`;@!T M`"``=P!I`'0`:``@`$0`<@!U`&T`<P`@`&\`;@`@`$`:`!A`&X`;@!E`&P` M(``Q`#8`````8V%P<Q@````8`````0````$````0````$````!````!C:&%N 8%````!0```#_?P```(```"``(``````` end --------------Boundary-00=_K2OUZXZHYUDX85A9SC48 Content-Type: text/plain; name="unnamed" Content-Transfer-Encoding: 7bit -- Louise MacGregor Software Engineer ARM Ltd 110 Fulboun Road Cambridge Tel: 01223 400710 mailto:Louise.Macgregor@arm.com --------------Boundary-00=_K2OUZXZHYUDX85A9SC48--
Is there any reason we still have this bug open? Maybe its time to close it?
Subject: Re: Support for Content-Transfer-Encoding: x-uuencode Zack Rusin wrote: > Is there any reason we still have this bug open? Maybe its time to close it? Well, depends upon your philosophy. uuencoded attachments appear to be popular with a number of simple Windows clients, so they show up from time to time. True it ain't standard, but it should be something KMail can handle. Does KMail allow you to switch the mime type of attachments (some Windows clients assign application/octet-stream to everything because the Windows shell uses the filename extension instead). Jon.
As Jon wrote it depends on our philosophy whether we should ignore this wish or not. We should probably be able to understand x-uuencode. But we should of course never create it ourselves. Probably the best and simplest way to add support for this would be to simply use uudecode or some other existing uu-program for decoding.
For adding support for decoding uuencoded message(s,parts) we would have 3 options: a) add it into KMReaderWin b) add it to the mimelib (where also base64 is handled) c) add it to KMime I opt for (c). Comments?
Subject: [nPATCH #6402] Add x-uuencode decode support to KMail. Hi! Well, it's really nano, since it only consists of moving the default: branch of switch statements and checking for a valid KMime::Codec being returned. The rest of the diff is indention due to the if ( codec )'s. Attached is also a test message with an x-uuencode attachement. It's somehow not shown as it should in smart attachment mode, seems like KMail wants to show it inline, although the CD is set to attachment... Oh, of course you'll need an uptodate libkdenetwork... Marc