L.D. Best wrote:
>
> 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.
Uh L.D.....;
The failure of Arachne to decode them doesn't enter into the picture when
they get received by Netscape. When Ron sends the file to me with A1.64
I receive it fine with Netscape. If he sends it with A1.66, the file grows
to the size Sam said he received.
Sam got it back to the right size with MIME64.exe.
Now. Either ALL files are MIME64 encoded and Netscape automatically decodes
them invisibly - excepting files sent by A166 wich may have the wrong type
set - thereby confusing Netscape, Arachne, and whatever Sam receives with,
OR .... hell I don't know - could it be simply that we really can send 8 bit
info down the pipe and have been doing so for some time ?
At least as attachments ? I have Netscape set to "Allow 8 bit" I see my
Arachne has "MailBodyEncoding" set to 7bit. But what about attachments ?
I really don't see any reason (except possibly protocol) to not allow 8 bit.
And, of course, the tendency of some modems to hangup when they get certain
strings <G>
Seriously, allowing for your expertise in these matters L.D., it looks like
it could be wrong file type. Should be easy enough to check.
- Clarence Verge
--
- Help stamp out FATWARE. As a start visit: http://home.arachne.cz/
--
