🚀 go-pugleaf

Starting over a year ago, Marshall Rose made no bones about wanting
someone to help to configure MH-MIME for the NeXT.  At that time,
someone at NeXT had managed to get some version of MH to compile under
NeXT/Mach 2.1, but wasn't widely publicizing the patches ...although
that person did pipe up at a BANG meeting a year or so ago when I
brought up the subject there.

MH was otherwise difficult to compile on the NeXT for someone with a
limited time budget.  MH 6.8 is out now; perhaps things are different
for compiling it on a NeXT, since MH 6.8 makes a few more concessions
to ANSI C compatibility.

Well, no one can accuse MH of having a beautiful graphical user
interface based tool for creating MIME messages, but it does support
MIME, no question about it.

With respect to NeXTmail, by way of contrast, here is an excerpt from
my contribution to the FAQ (the new version of which isn't out yet)
regarding other multi-media e-mail user agents:

> The ability to create e-mail messages with audio and other non-textual
> contents has been around for a while, but almost always as part of a
> vendor-specific ``solution.''  This means that you can't create a
> message on a NeXT system containing PostScript information and ``Lip
> Service'' (NeXT's audio e-mail tool) and easily handle the same
> message on an HP 9000/710, a Sun SPARCstation IPC, and a Silicon
> Graphics Iris.  That's a problem that MIME helps to solve.

It isn't much different from what you said.  The point, which you've
already noted, Rodney, is that a multi-media e-mail solution that
works only with NeXTs doesn't cut the mustard.