Don't blame Sam.
His attachment on my e-mail came through the way it was supposed to.
But on mail from my oldest son, yesterday, I got the same type of "I
ain't gonna convert this so take a look" treatment from Arachne.
NOW what??!!
And, to answer Roger's question -- Arachne had no way of knowing that
DIZ is a text file! So it was encoded.
Glenn, or ??? Where do we add a line designating *.DIZ as text??
l.d.
====
On Sun, 20 Feb 2000 13:51:36 -0500, Roger Turk wrote:
> Sam Heywood,
> Here is how your "attached file, FILE_ID.DIZ is an ascii text file" came thru:
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> P.S. BTW, the attached file, FILE_ID.DIZ is an ascii text file which
> describes the program in Herr Muchsel's own words.
> <snip>
> --MIME-multipart-message-boundary-951059545
> Content-Type: application/octet-stream ;name=FILE_ID.DIZ
> Content-ID: arachne-namespace/C:\AMISETUP\FILE_ID.DIZ
> Content-Description: File "FILE_ID.DIZ" (type application/octet-stream, size 0
> KB)
> Content-Transfer-Encoding: base64
> QU1Jc2V0dXAgMi45OSAtIEV4dGVybmFsIFNldHVwIChBTUkgSGlnaA0KRmxleCBvciBXaW5C
> SU9TIHJlcXVpcmVkKS4gSWYgeW91IGV2ZXINCmNvbnNpZGVyZWQgeW91ciBidWlsdC1pbiBz
> ZXR1cCBhcw0KaW5jb21wcmVoZW5zaWJsZSwgYm9yaW5nLCBpbmNvbnZlbmllbnQNCm9yIGlu
> Y29tcGxldGUsIHlvdSBoYXZlIGJlZW4gd2FpdGluZyBmb3INCkFNSXNldHVwLiBBTUlzZXR1
> cCBjYW4gc2F2ZSB5b3VyIGNvbmZpZw0KdG8gZGlzayBhbmQgcmVzdG9yZSBpdC4gWW91IGNh
> biBldmVuDQpjaGFuZ2Ugc2V0dXAgb3B0aW9ucyBtaXNzaW5nIGluIHlvdXINCkJJT1MhIEFN
> SXNldHVwIGNyYWNrcyB5b3VyIHBhc3N3b3JkLA0KYXV0by1kZXRlY3RzIGhhcmQgZGlza3Ms
> IHByaW50cyBhDQpwZXJzb25hbCBCSU9TIG1hbnVhbCAmIG11Y2ggbW9yZS4NCg==
> --MIME-multipart-message-boundary-951059545--
> -- This mail written by a user of Arachne, the Ultimate Internet Client�
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> The question is, why did an ASCII text file get encoded into a "base64"
> encoded format?
> Roger Turk
> Tucson, Arizona
-- Arachne V1.60;b1, NON-COMMERCIAL copy, http://arachne.cz/
