From xemacs-m  Thu Feb 27 17:48:31 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id RAA10233
	for <xemacs-beta@xemacs.org>; Thu, 27 Feb 1997 17:48:28 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	id QQcetr02047; Thu, 27 Feb 1997 18:48:27 -0500 (EST)
Date: Thu, 27 Feb 1997 18:48:27 -0500 (EST)
Message-Id: <QQcetr02047.199702272348@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: Re: Bug in vm
In-Reply-To: <kigene2xsje.fsf@jagor.srce.hr>
References: <199702271328.OAA09887@daedalus.tnt.uni-hannover.de>
	<kigene2xsje.fsf@jagor.srce.hr>
X-Face: /cA45WHG7jWq>(O3&Z57Y<"WsX5ddc,4c#w0F*zrV#=M
        0@~@,s;b,aMtR5Sqs"+nU.z^CSFQ9t`z2>W,S,]:[+2^
        Nbf6v4g>!&,7R4Ot4Wg{&tm=WX7P["9%a)_da48-^tGy
        ,qz]Z,Zz\{E.,]'EO+F)@$KtF&V

Hrvoje Niksic writes:
 > Heiko Muenkel <muenkel@tnt.uni-hannover.de> writes:
 > 
 > > It seems, that this was caused by the character '? '. I'd inserted
 > > this character with C-q C-@ in my email.
 > > 
 > > Kyle, is this a bug in vm, or is it not allowed to send this character
 > > by email?
 > 
 > That character is allowed, if you use the 8bit
 > content-transfer-encoding (which shouldn't be done in email).

I think you mean "binary" instead of "8bit".  Unencoded NULs are
not allowed in messages marked as 8bit encoded.

 > [...]
 > The real question is: why did VM choose to use base64 instead of
 > quoted-printable?

Any MIME body in a composition that would require a 'binary'
content transfer encoding gets BASE64 encoded.

