From: Tony Ross (tross@appworx.com)
Date: Wed Jun 28 2000 - 20:35:08 CDT
Thanks for that observation on the functionality, Peter.
Although uuencoded files as attachments are handled as you suggest, it
would good if uuencoded files as inline content (the traditional
transport method) were decoded and converted to a MIME attachment.
In your estimation, what would be required to accomplish this? I'm
just curious how all the other people have handled this somewhat
antiquated transport method using hypermail.
tony
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 6/28/00, 1:23:31 PM, pcm@rahul.net (Peter C. McCluskey) wrote
regarding Re: does uudecode actually work?:
> tross@appworx.com (Tony Ross) writes:
> >Greetings;
> >
> >We are receiving quite a number of emails with uuencoded files in the
> >body, and hypermail 2b29 is not uudecode'ing these; it leaves the
> >uuencoded file in the body of the html file.
> It looks from skimming the relevant parts of the source code like
> uudecode is only used for mime attachments that say they are
uuencoded.
> I don't see any reason to decode other uuencoded text. The uuencoded
file
> I recently sent (not as an attachment) wouldn't look very good if it
were
> decoded into a gzip'd tar file.
> --
>
-----------------------------------------------------------------------
-------
> Peter McCluskey | The US Idea Futures Exchange: speculate on
> http://www.rahul.net/pcm | political,financial issues at
http://www.usifex.com