From: Craig A Summerhill (craig@cni.org)
Date: Tue Mar 16 1999 - 18:15:04 CST
On Sat, 13 Mar 1999, Ashley M. Kirchner <ashley@pcraft.com> wrote:
>
> On Sat, 13 Mar 1999, Daniel Stenberg <daniel.stenberg@sth.frontec.se> wrote:
> :
> : As I see it, we have 3 different choices:
> :
> : 1 - Leave it as it is.
> : 2 - Allow all "text/*" and "message/*" headers to be shown.
> : 3 - Make another config file item where you can list all types you want
> : hypermail to show "inlined".
> :
> : I think I favour #3.
>
> So do I. Just turning everything on and forcing everyone to
> just cope with it, isn't the right way to go, and leaving them as is
> isn't the solution either. A config file item is the only thing I
> can think of. Now, with that, we'll also have to put some sort of
> default in it, with some explanation of what else people can turn
> on/off.
Coming back in after a long weekend...
Well, I'm in favor of whatever will help us roll out a relatively
stable version 2.x release which handles MIME.
I can live with #1 (although from the user/browser point of view
is seems less efficient). I guess I was thinking along the lines of
#2 when I sent the report last week. I have no objection to #3.
It seems like more work, but has the obvious advantage of being
extensible. I wonder how many messages will actually be affected
by this problem...
-- Craig A. Summerhill, Systems Coordinator and Program Officer Coalition for Networked Information 21 Dupont Circle, N.W., Washington, D.C. 20036 Internet: craig@cni.org AT&Tnet (202) 296-5098