From xemacs-m  Fri Apr 25 01:31:42 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 BAA23256
	for <xemacs-beta@xemacs.org>; Fri, 25 Apr 1997 01:31:40 -0500 (CDT)
Received: by crystal.WonderWorks.COM 
	id QQcmtm15970; Fri, 25 Apr 1997 02:31:40 -0400 (EDT)
Date: Fri, 25 Apr 1997 02:31:40 -0400 (EDT)
Message-Id: <QQcmtm15970.199704250631@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: VM-6.29 and ISO-2022-JP'd mail
In-Reply-To: <9704250432.AA26455@pluto.ritp.ye.IHI.CO.JP>
References: <9704250432.AA26455@pluto.ritp.ye.IHI.CO.JP>
X-Mailer: VM 6.30 under 20.2 XEmacs Lucid (beta2)
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

UENO Fumihiro writes:
 > I patched up from XEmacs-20.2-b1 to 20.2-b2 on DEC OSF/1 Ver.3.2D and
 > it works fine. But only VM-6.29 doesn't work well with ISO-2022-JP
 > mail.(So I must change VM-6.29 to VM-6.27)

Since you seem to be using tm-edit, I don't know whether this is
a VM problem or not.  I see that vm-send-using-mime is set to t,
so this might be confusing things; I don't know.

The last MULE change I made was just before 6.27 was released.  I
pulled all the charset encoding calls out VM's mail sending function
because encode-coding-region was scrambling marker positions which
in turn was scrambling the MIME attachment encoding.  This would
definitely break sending multibyte chars if you're relying on VM
(rather than tm) to encode them.  Seemed better to try to work out
whatever was going on with this code after 20.1 was released.

