From owner-freebsd-hackers  Wed Feb 12 09:21:17 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA12152
          for hackers-outgoing; Wed, 12 Feb 1997 09:21:17 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA12145
          for <hackers@freebsd.org>; Wed, 12 Feb 1997 09:21:12 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA00715; Wed, 12 Feb 1997 10:15:47 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702121715.KAA00715@phaeton.artisoft.com>
Subject: Re: MIME applications for FreeBSD
To: jb@cimlogic.com.au (John Birrell)
Date: Wed, 12 Feb 1997 10:15:47 -0700 (MST)
Cc: hackers@freebsd.org
In-Reply-To: <199702120310.OAA08085@freebsd1.cimlogic.com.au> from "John Birrell" at Feb 12, 97 02:10:35 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> I'm curious about what people regard as typical MIME applications
> that a site is expected to support. The volume of business email
> containing MIME "application/msword" has now exceeded my level of
> tolerance. When I consider changing ISPs and they send the
> application form MIME encoded for an application I do not have...
> When I receive support updates from a company we _pay_ for support
> and they send them MIME encoded... Grrr. Enough!
> 
> Opinions?

1)	Boundry identification
2)	Multile logical message bodies seperated by boundry identifiers
3)	Content transfer encoding for binary data

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.).


					Regards,
					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.