Some binary basics: 1. Binary files cannot be sent via e-mail; e-mail is limited to a specific set of low-end ASCII characters. [Some of you have found this out in experimenting with accented letters, etc.] 2. Attachment encoding method is always determined by the mailmachine that does the attaching. Period. The internet is *not* a time machine, and your mailer cannot send a signal out that says "Hey, I got your attachment but I only want UU stuff so resend it UU so I receive it two minutes ago." 3. InSight/Arachne automatically decodes *properly* encoded attachments, regardless of how your mailer is set. The problem is the "properly" part ... I'm hoping to get samples soon that will enable me to make a very detailed inspection of the encoded attachments of 1.66 vs 1.64 or earlier. 4. I have no experience with Linux/UNIX, but generally speaking all internet 'mailmachines' should, and usually do, automatically decode encoded attachments. l.d. P.S. There is no reason to mess around with Arachne.cfg if you want to send UU encoded messages. All you need do is click the radio button selecting UU. And yes, some people do prefer UU to MIME. Although MIME may not tell the decoding software how long the encoded file is, or what size the decoded file is supposed to be, there's no reason why a decoder can look for an EOF indicator [which is standard IIRC]. And MIME *will* do something that UU won't: It will decode what is there, even if it's not complete. I've received 'broken files' -- generally graphics -- and MIME has decoded what there was and written a file that was readable as a partial graphic. <G> -- Learn about B'FOR Join B'FOR - B'mothers For Open Records <a href="http://www.b-for.org">B'FOR web site</a> [Associate members of triad also welcome; membership confidential.] Every member counts! We need numbers to produce valid statistics. -- Arachne V1.64, NON-COMMERCIAL copy, http://arachne.cz/
