Path: utzoo!mnetor!uunet!husc6!bloom-beacon!gatech!ukma!david
From: david@ms.uky.edu (David Herron -- Resident E-mail Hack)
Newsgroups: comp.mail.misc
Subject: Re: Using Sendmail and MMDF on the same host
Message-ID: <7854@g.ms.uky.edu>
Date: 13 Dec 87 19:10:15 GMT
References: <3047@phri.UUCP> <7807@g.ms.uky.edu> <540@ncrcan.Toronto.NCR.COM> <3062@phri.UUCP>
Reply-To: david@ms.uky.edu (David Herron -- Resident E-mail Hack)
Organization: U of Kentucky, Mathematical Sciences
Lines: 30

In article <3062@phri.UUCP> roy@phri.UUCP (Roy Smith) writes:
>	One difference between sendmail and MMDF is how the output side is
>interfaced (sendmail calls them mailers, MMDF calls them channels).  In
>sendmail, a separate program is executed to do the delivers (for example,
>for uucp delivery, sendmail will exec uux with the right arguments, and
>feed it the mail message as stdin).  In MMDF, the channels are compiled
>into the delivery agent.

eh?  come again?  If the channels are compiled into the system
then what's all that stuff in /usr/mmdf/chans?

MMDF uses seperate processes for most of the steps of moving
the mail around.  For instance, when you send mail, your user
agent starts up an instance of /usr/mmdf/submit and talks to
it across a pair of pipes.  Eventually the user agent tells submit
to send the mail, but all submit does is write the information
into the proper channel directories.  If the channel is marked
for immediate delivery then it starts up a /usr/mmdf/deliver
to handle the delivery.  IN any event, deliver eventually runs,
see's the message, and starts up the proper channel process
to handle the delivery.  (either local deliver, or by starting
up a uux, or whatever).

Certainly doesn't seem very compiled in when you got all these
processes running around.
-- 
<---- David Herron -- The E-Mail guy            
<---- or:                {rutgers,uunet,cbosgd}!ukma!david, david@UKMA.BITNET
<----
<---- Winter health warning:  Remember, don't eat the yellow snow!