Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!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: <1990Jul18.143855.11452@murdoch.acc.Virginia.EDU>
Date: 18 Jul 90 14:38:55 GMT
References: <1990Jul17.204302.18027@d.cs.okstate.edu>
Sender: news@murdoch.acc.Virginia.EDU
Organization: University of Virginia
Lines: 18

klarich@d.cs.okstate.edu (KLARICH TERRY JAME) writes:
>Currently, I have mmdf installed on an ultrix machine which I manage.  I would
>like to provide a variety of mail interfaces for the users.  After looking at
>mush, I thaught I would try and get it up and running.  I have two questions I
>can't seem to find the answers for.  First, is there any way to keep mush
>from messing up the "._.mail" file used by mmdf?  Second, could some one
>let me know what is actually required to get mush to talk to
>"/usr/mmdf/submit"?

I'm not familiar with the "._.mail" file?  What is it used for?  Is
it a lockfile?  What sort of locking does your MMDF installation use?

Regarding your second question, you should be ok if you just change
the "/usr/mmdf/bin/submit" in config.h-dist to "/usr/mmdf/submit" in
config.h.  What are the symptoms of mush's failure to communicate with
submit?

    -- Marc Rouleau