At 12:38 PM +0000 2/16/01, Alan Fry wrote:
>I have sent two test files (a text file that failed to make it
>through to the list) to Ask Bjorn Hansen and received these replies:
>
>1) in relation to a 'BinHex' attachement:
>At 2:53 am -0800 16/02/01, Ask Bjoern Hansen wrote:
>>yes, application/mac-binhex40 is filtered out. If you can ask on the
>>list and get consensus for not doing that I'll take it out.
>
>2) in relation to an 'AppleDouble' (MIME'd) attachment.
>At 2:53 am -0800 16/02/01, Ask Bjoern Hansen wrote:
>>in the second file you sent, the data part of the attachment would
>>have made it through. And be easily readable for all mail readers
>>too. (it is just text after all).
>
>So the question to us all is: do we want the 'BinHex' filter removed?
>
>My own feeling is I _would_ like to see it removed. Unencoded
>scripts, documents with long lines and/or high-ascii characters
>always get mangled along the way. For Mac users 'BinHex' is kind of
>the conditioned reflex and for Eudora fans the usual (?) default
>setting.
It shouldn't be, for just the reasons Ask mentioned. Just have
Eudora use Appledouble. If that's not the default these days, it
should be. It makes no difference if you're sending to other Mac
users, and makes a great difference if you're not. Don't assume that
anyone here is necessarily reading mail under Mac OS.
(That said, I don't see any reason to filter out BinHex, but it
shouldn't be used for mailing lists.)
>
>Alan Fry
--
--
Paul Schinder
[EMAIL PROTECTED]
