Uh guys ..
Any binary file attached to e-mail *must* be encoded -- either MIME or
UU. That includes zip files.
You've apparently found the problem, but it's not what you think it is.
<G>
The problem is that Arachne has, for some reason in ver 1.66, stopped
automatically decoding certain attached files. I rather routinely
receive MIME encoded attachments, and have never had a problem with
Arachne automatically decoding them.
Yet another reason not to "move up" to ver 1.66
Although the files which come with Arachne are *named* uuencode.exe &
uudecode.exe, they are not anywhere like the "original" UU en/de
programs I have; for one thing they are *much* smaller, and for another
thing they apparently can en/decode both UU & MIME. MIME is the better
bet for a couple of reasons -- most browsers are built to decode it
automatically [except, it seems, Arachne v1.66], and the encoded files
are measurably smaller than uuencoded files.
I have *two* MIME en/decoders, but an Arachne user shouldn't *need* them
... except in the 'new disimproved 1.66 version' <G>
l.d.
====
On Mon, 28 Aug 2000 18:10:09 -0500, 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 ?
