Thanks again for your comment but you are missing my question.
My question is "how do I decode mail contents manually but efficiently?"
This is useful knowledge if mails are archived in a web page and if one
wants to read their content.
For example, mail content comes actually in following form:
...
Content-Type: application/octet-stream
Content-Disposition: attachment; filename="foo.tar.gz"
Content-Transfer-Encoding: base64
...(encoded 7bit text)...
Then I need to add "begin-base64 644 foo.tar.gz" before encoded section
before I manually parse the original file using uudecode.
I know Mutt parses them properly. That's why I asked here.
This process is quite cumbersome if multiple files are attached.
Regards,
Osamu
On Mon, Feb 26, 2001 at 04:37:20PM -0500, Rich Lafferty wrote:
> On Mon, Feb 26, 2001 at 01:42:09PM -0800, Osamu Aoki ([EMAIL PROTECTED])
>wrote:
> > Thanks Rich, but uudecode does Base64 at least on Debian system.
> >
> > On Mon, Feb 26, 2001 at 12:59:29PM -0500, Rich Lafferty wrote:
> > > "Application/octet-stream" means "I don't know what this is other than
> > > to say that it's a bunch of bytes". In particular, it doesn't say it's
> > > uuencoded; if anything, it leans toward *not* being uuencoded, since
> > > the "standard" 7-bit encoding for 8-bit data in MIME is Base64.
> >
> > Problem was I needed to add a line before successfully decoding
> > my Base64 coded text to binary. I was looking for better/automatic
> > command line scheme.
>
> Right, but keep in mind that "application/octet-stream" doesn't mean
> it's base64, either. All it means is that the sending agent had
> absolutely no information about the content at all other than that it
> was not 7-bit text.
>
> -Rich
--
+ Osamu Aoki <[EMAIL PROTECTED]>, GnuPG-key: 1024D/D5DE453D +
+ Fingerprint: 814E BD64 3288 40E7 E88E 3D92 C3F8 EA94 D5DE 453D +
+ http://www.aokiconsulting.com/pc/ Cupertino, CA USA +
