Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.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: <oowgP1w163w@mudos.ann-arbor.mi.us>
Date: 14 Sep 90 03:56:23 GMT
References: <7921@gollum.twg.com>
Organization: The Programmers' Pit Stop, Ann Arbor MI
Lines: 27

david@twg.com (David S. Herron) writes:
> MMDF quite carefully puts Received: headers into messages.  Are you sure
> you're seeing what you're seeing?  :-)

Well, it quite carefully puts a Received: header in the message when
it receives the message from another host.  But there's never a
Received: header added for the local host, which I feel it should do.

I've also another question: We have a TCP/IP LAN set up using ODT-NET
with two machines so far, but probably more on the way (and maybe a
direct Internet connection coming sometime).  I'd like MMDF to use
SMTP to deliver to machines on the network, but I don't want to have
to make up a /usr/mmdf/table/smtp.chn file that includes every machine
on the network.  I'd rather have it ask the nameserver (yes, there's
one running) to translate the name into an IP address, and send it to
our main gateway machine if the nameserver doesn't know about that
domain name.  There doesn't appear to be a way to do this.  Is there?

(I also consider it somewhat slimey for MMDF to install its own
version of /usr/lib/sendmail that isn't command-line-compatible with
Berkeley sendmail.  I hope that won't cause problems when I try to
install PD MUAs later on.)

--
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