-=> MAX CHAMBERLAIN wrote to WILLIAM MCBRINE <=-

 MC> Also it doesn't seem to make any difference whether I spell out
 MC> 'Program files' or use progra~1.

Ah... MultiMail doesn't care, but OLXed does. :-) This is probably the
issue -- you're passing a long pathname to OLXed (and a pathname with
spaces, at that), and it doesn't understand it.

It turns out that MultiMail/DOS will promote the short pathnames to their
long equivalents, and pass the long names to called programs, regardless of
what you specify in the mmail.rc. This is not true of the Win32 version
(nor, of course, the XT version, which never uses LFNs).

In version 0.37, temporary replies are created in the TEMP directory.
Presumably, the path to your temporary directory didn't cause problems for
OLXed. In 0.46, the way you have MultiMail set up, the temporary files are
under "Program Files", and OLXed doesn't understand that.

There are three possible solutions:

1. Use the "TempDir" keyword in mmail.rc to specify a pathname that fits
   within the 8.3 scheme -- remembering that it's not just what you put
   into the mmail.rc per se, but what it _resolves_ to.

2. Upgrade to the Win32 version, or downgrade to the XT port.

3. Switch to an editor that understands LFNs.

 MC> Not sure about having an MMAIL environment variable set... is this what
 MC> you mean?...

No. Environment variables are what you see when you type "set" at a command
prompt. NOT mmail.rc keywords.

 MC> # Base directories (derived from $HOME or $MMAIL)
 MC> HOME: c:\Program Files\mmdos37

That's not a valid mmail.rc keyword.

... \|/ ... \|/ ... \|/ ... Looks like time to mow the tagline.
--- MultiMail/Linux v0.46