Clarence,
*ALL* binary files have to be encoded in order to send them as e-mail or as
e-mail attachments! E-mail must be ASCII text.
The problem as I see it is that Arachne (1.66?) is not decoding the
transmitted file, but just changing the name to that of the encoded file.
UUencoded files are usually sent with a default extension, .UUE
Base64 (MIME) encoded files are usually sent with a default extension, .B64
These give the "automatic" decoder the information about what to use to
decode the file (although it doesn't work when *I* encode a file and send it
as an attachment.)
Roger Turk
Tucson, Arizona
Clarence Verge wrote:
>>Samuel W. Heywood wrote:
>
> Several days later I decided to look at QS.ZIP with a file viewer. I found
> that it had been MIME64 encoded. I decoded it with MIME64.EXE. This
program
> produced QS.ZIP, 41,680 bytes. PKUNZIP was then very happy with it.
> Mystery solved!
Hi Sam;
Good work ! PART of the mystery solved - the "what".
Now, "why" are A166's attachments MIME64 encoded when
apparantly A162/4's are not ?
The Arachne.cfg variable MailEncoding allows Mime or UUencode.
There isn't any "None" option I don't think. (Must check)
I also don't know if this refers to Mail body, attachments or both.
I have never selected UUencode and I just checked my current and old
Arachne.cfgs and this variable was always set to "Mime" in my setup.
Maybe this is the first time it worked ?
If so, we will definitely need the "None" option.
Where did you get MIME64.exe ?
- Clarence Verge<<
