From xemacs-m  Sat Mar 15 18:51:09 1997
Received: from beavis.bayserve.net (jmiller@port79.bayserve.net [206.148.244.170])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id SAA26485
	for <xemacs-beta@xemacs.org>; Sat, 15 Mar 1997 18:51:07 -0600 (CST)
Received: (from jmiller@localhost) by beavis.bayserve.net (8.7.5/8.7.3) id TAA00462; Sat, 15 Mar 1997 19:59:40 -0500
Date: Sat, 15 Mar 1997 19:59:40 -0500
Message-Id: <199703160059.TAA00462@beavis.bayserve.net>
From: Jeff Miller <jmiller@bayserve.net>
To: xemacs-beta@xemacs.org
Subject: Re: A new XEmacs mine
In-Reply-To: <QQchaw23342.199703160041@crystal.WonderWorks.COM>
References: <m3wwr9v26y.fsf@jens.metrix.de>
	<kigk9n9j63b.fsf@jagor.srce.hr>
	<m3bu8kbtv7.fsf@jens.metrix.de>
	<199703160008.TAA00401@beavis.bayserve.net>
	<199703160040.TAA00436@beavis.bayserve.net>
	<QQchaw23342.199703160041@crystal.WonderWorks.COM>
Reply-to: jmiller@bayserve.net
Mime-Version: 1.0 (generated by tm-edit 7.105)
Content-Type: text/plain; charset=US-ASCII

>>>>> "KJ" == Kyle Jones <kyle_jones@wonderworks.com> writes:

KJ> Jeff Miller writes:
>> >>>>> "JM" == Jeff Miller <jmiller@bayserve.net> writes:

>> hmmmm.... vm did not decode that attachment for me.  I did Mail-Send
>> Using Mime-> Use Mime, then Attach File.
>> 
>> did it decode ok for others? 

KJ> Arrived utterly broken here.  Relevant headers.

That's what I was afraid of. did I do something in the wrong sequence?

I sent myself the same file attaching it with MIME-Edit, which I think
comes with tm.  Vm got that one ok. 

KJ> MIME-Version: 1.0
KJ> 	boundary="Ng6iC88CYfp4l4jDuy/bIyEpoAl2dWyr3tN5qK8C"
KJ> Content-Type: text/plain; charset=US-ASCII


