From xemacs-m  Wed Mar 12 06:53:11 1997
Received: from beavis.bayserve.net (jmiller@port3.bayserve.net.244.148.206.in-addr.arpa [206.148.244.99])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id GAA10484
	for <xemacs-beta@xemacs.org>; Wed, 12 Mar 1997 06:53:08 -0600 (CST)
Received: (from jmiller@localhost) by beavis.bayserve.net (8.7.5/8.7.3) id HAA01277; Wed, 12 Mar 1997 07:57:50 -0500
Date: Wed, 12 Mar 1997 07:57:50 -0500
Message-Id: <199703121257.HAA01277@beavis.bayserve.net>
From: Jeff Miller <jmiller@bayserve.net>
To: xemacs-beta@xemacs.org
Subject: XE19.15-b98+VM6.19
In-Reply-To: <9703121017.AA02466@ndsoft.com>
References: <9703121017.AA02466@ndsoft.com>
Reply-to: jmiller@bayserve.net
Mime-Version: 1.0 (generated by tm-edit 7.105)
Content-Type: text/plain; charset=US-ASCII

>>>>> "AJK" == Amir J Katz <amir@piccard.ndsoft.com> writes:

AJK> I forgot to mention that when I hit the 'decode MIME' button, vm
AJK> said that mmencode returned with a non-zero status - I use an external
AJK> decoder instead of VM's built-in one.

AJK> in My ~/.vm:

AJK> (setq vm-mime-base64-decoder-program  "mmencode"
AJK>       vm-mime-base64-decoder-switches (list "-u")
AJK>       vm-mime-base64-encoder-program  "mmencode")

I started doing something similar:

(setq vm-mime-base64-decoder-program "/usr/bin/mmencode"
      vm-mime-base64-encoder-program "/usr/bin/mmencode"
      vm-mime-base64-decoder-switches '("-u")
	)

does using the full path for mmencode produce different results for you?
Perhaps 19.14 & 19.15 compute paths differently? 

The above is working for me with 19.15b98 & linux.

jeff

