Re: decoding

[Ron Johnson <ron.l.johnson@cox.net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/09/08 18:31, Frank McCormick wrote:
> 
> 
> Someone sent me an email which **appears* to be base64 encoded?
> 
> 
> here's the first few lines:
> 
> --Boundary_(ID_lsgMnwyfMlYdcpjna13q/Q)
> Content-type: text/plain; charset=utf-8
> Content-language:
> Content-transfer-encoding: base64
> 
> U29tZSBSZWFsbHkgR3JlYXQgTW9tZW50cyBvZiBSYWRpbyB0aGlzIHdlZWsuIFdlIGhlYXJkIGZy
> b20gaW5zaWRlIEJ1cm1hIGEgUXVlYmVjZXIncyBmaXJzdCBoYW5kIGFjY291bnQuIFdlIGxhdWdo
> ZWQgb3ZlciB0aGUgVm9nZWwgZmFtaWx5J3Mgc3RpbGwgZHVyaW5nIFByb2hpYml0aW9uIGFuZCB3
> 
> 
> 
> It ends with :
> 
> 
> --Boundary_(ID_Ta8U5Dd8tk/FeCjCVPGiyw)--
> 
> --Boundary_(ID_lsgMnwyfMlYdcpjna13q/Q)--
> 
> 
> Base64 doesn't know what to do with this file.
> 
> Help anyone?

This is gmail stupidity.  It's how Google sends html-enabled mail.
The only solution is to ask the sender to enable plain-text.

- --
Ron Johnson, Jr.
Jefferson LA  USA

We want... a Shrubbery!!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIJQsXS9HxQb37XmcRAlunAJ9SMKTQJwofwl390Adf2jFiYCTZygCcDxAl
TT2U2oNRvSg8lH3KYwkU7ds=
=uaOm
-----END PGP SIGNATURE-----