Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!ames!ncar!mephisto!mcnc!uvaarpa!murdoch!virginia.acc.Virginia.EDU!mer6g
From: mer6g@virginia.acc.Virginia.EDU (Marc Rouleau)
Newsgroups: comp.mail.mush
Subject: Re: mush and mmdf help wanted
Message-ID: <1990Jul22.043711.3548@murdoch.acc.Virginia.EDU>
Date: 22 Jul 90 04:37:11 GMT
References: <1990Jul17.204302.18027@d.cs.okstate.edu> <7641@gollum.twg.com>
Sender: news@murdoch.acc.Virginia.EDU
Organization: University of Virginia
Lines: 32

david@twg.com (David S. Herron) writes:
>klarich@d.cs.okstate.edu (KLARICH TERRY JAME) writes:
>>  Second, could some one
>>let me know what is actually required to get mush to talk to
>>"/usr/mmdf/submit"?
>
>Out of the box mush talks to submit by the way of the sendmail
>emulator included with MMDF.

No.  Out of the box mush talks to submit by way of the established
command line interface.  The default is "submit -mlnr" if memory
serves.  I believe this has been so for at least two years.

>  One problem, which I haven't tracked
>down yet, is that (at least with the mush installed at ms.uky.edu)
>the return-address-for-errors ends up pointing at the postmaster.
>Not good..

I think the fake sendmail interface to submit is a lamentable hack,
especially when mush, elm, and mh already support submit's perfectly
good command line interface.

>User agents are supposed to use one of two sets of routines for
>talking to submit.  They are the ml_*() and mm_*() routines, and
>are located in libmmdf.a and compiled from source under lib/mmdf.

Ugh.  I think the command-line interface is much cleaner.  One of
the many reasons is that lots of MMDF sites lack source.  It would
be foolish for developers of portable user agents to require that
installers of their packages have copies of libmmdf.a handy.

    -- Marc Rouleau