Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!umich!ox.com!mudos!mju
From: mju@mudos.ann-arbor.mi.us (Marc Unangst)
Newsgroups: comp.mail.uucp
Subject: Re: Problems with MMDF and UUCP mail
Message-ID: <26wgP2w163w@mudos.ann-arbor.mi.us>
Date: 14 Sep 90 04:06:48 GMT
References: <7927@gollum.twg.com>
Organization: The Programmers' Pit Stop, Ann Arbor MI
Lines: 21

david@twg.com (David S. Herron) writes:
> As to whether this is a problem?  Sendmail sites generally have the
> UUCP originator be `daemon' so I don't see how that's very different
> from MMDF sites having the originator be `mmdf'.  Can you explain further?

Let's say that site A runs MMDF and talks to site B via UUCP.  Site B
is a dumb UUCP site that doesn't run a smart-mailer, and consequently
can't handle RFC-822 headers.  The MUA there is the /bin/mail
distributed with the system, which also doesn't understand RFC-822
headers.  User "user1" on site A sends mail to "user2" on site B.
MMDF mangles the From_ line so it reads "From siteb!mmdf ... remote
from sitea".  user2 tries to reply to the message using /bin/mail's
<r>eply command.  The reply is sent to "siteb!mmdf", which is where
the From_ line says the message came from.

Do you understand now?

--
Marc Unangst               | "da-DE-DA: I am sorry, the country you have
mju@mudos.ann-arbor.mi.us  | dialed is not in service.  Please check the
...!umich!leebai!mudos!mju | number and try again."  -- Telecom Kuwait