From owner-freebsd-hackers Wed Feb 12 20:58:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA17901 for hackers-outgoing; Wed, 12 Feb 1997 20:58:09 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA17896 for ; Wed, 12 Feb 1997 20:58:08 -0800 (PST) Received: from lightside.com (hamby1.lightside.net [207.67.176.17]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id UAA08638 for ; Wed, 12 Feb 1997 20:58:01 -0800 (PST) Received: by lightside.com (SMI-8.6/SMI-SVR4) id UAA01601; Wed, 12 Feb 1997 20:50:59 -0800 Date: Wed, 12 Feb 1997 20:50:59 -0800 From: jehamby@lightside.com (Jake Hamby) Message-Id: <199702130450.UAA01601@lightside.com> To: jb@cimlogic.com.au, terry@lambert.org Subject: Re: MIME applications for FreeBSD Cc: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-MD5: wIvODx8KA6q2hZ5UNMSFgA== Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert writes: > As to what binary data is permitted to be encoded: > > 1) Any binary data the sender and the recipient can agree upon > > > Though I'd be perfectly happy to see this limited to binary data for > which public source reference implementations exist (ie: no more Word > documents unless Microsoft publically documents Word file format, no > PDF documents unless Adobe documents their "encryption" preventing > the use of non-Adobe readers, but not preventing any Adobe reader from > decoding the document, etc., etc.). Absolutely! Although figuring out the lowest common denomintor for, e.g. rich text, often leads to all sorts of oddities. For example, I just received a price quote for a Micron PC by E-Mail, in of all things, UUENCODED RTF format! As I happily uudecoded it, and imported it into WordPerfect 6.0 for UNIX on my SPARCstation, I couldn't help but wonder about the poor PC lusers running Eudora, etc., and trying to figure THAT out. Hmm, now that I think of it, Netscape does automagically decode UUencoded pictures from USENET (hmm, wonder what Netscape programmer was reading alt.binaries.pictures.erotica when he thought of adding that feature ;), maybe it does the same thing for E-Mail? Oh well.. Another comment on this dangerously off-topic thread: There is now commercial gateway software designed specifically to look at MIME attachments and convert them into a format friendly to the recipient. They even go so far as to add an appropriate resource fork if the recipient is a Mac user, or add the 3-character extension if the recipient is a PC user. Wonder what happens if the recipient's using UNIX? :) Anyway, I used to get really upset when PC/Mac users at work sent me MS Office documents as attachments, but now that WABI is fast enough for me, I just use that. Now that I have a decent version of WABI at home (Solaris/x86), it looks like that won't be a problem with my personal mailbox either, but of course, if somebody sent me a Word document in my private mailbox, I'd probably delete it as a matter of principle... :). -- Jake