1. Re: MIME and Demo
On Tue, 15 Jul 1997 06:59:29 -0700 Lucius L Hilley III
<luciuslhilleyiii at JUNO.COM> writes:
>Mime stands for Multi part message, Or something like that.
MIME="MultiPurpose Internet Mail Extension".
The spec sets standards for both single and multi-part messages.
>Mime Automatically encodes using UUencode or Base64 or just plain
>text where needed.
Base64 only no UUcode
====================8< SNIP >8====================
>It gave me Text BUT. It has all those =3D things in it.
That was because the Content-Transfer-Encoding was "Quotable-Printable".
This means all 7bit characters are UNencoded and all other characters are
represented by an = sign and two hex digits. So =3D is ASCII(61) or an
= sign. Use a text editor with replace to change all the =3D's to
plain old = to fix the output.
People sending shrouded or binary programs should encode in Base64 IMHO.
Text before the code start identifier is ignored so you can send
explanations along with the code. Also there is no need to encode plain
text messages as I see some people doing, Unless their ISP is kludging up
7 or 8bit text.
I have just gotten into this because I recieved some data at work that
would not decode and found that the sender had cut and pasted some code
into a MIME headered message, of course the message did not match the
header. Takes all kinds. <g>
If you want to find out about the basics of file formats used on the
Internet grab a copy of "Internet File Formats" by Tim Kientzle from your
local library. I wouldn't buy it for my reference library but it does
explain the basics.
Larry D. Poos
-[USMC (Retar{bks}{bks}ired) Havelock, NC]-
-(Just Downsized) Programming and System Consultant, LTAD Enterprises -
e-mail: ldpoos at juno.com
FidoNet: 1:3629/101.6
