Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!mips!twg.com!david From: david@twg.com (David S. Herron) Newsgroups: comp.mail.uucp Subject: Re: Problems with MMDF and UUCP mail Message-ID: <7950@gollum.twg.com> Date: 17 Sep 90 00:14:41 GMT References: <7921@gollum.twg.com> Reply-To: david@twg.com (David S. Herron) Organization: The Wollongong Group, Palo Alto, CA Lines: 73 In article mju@mudos.ann-arbor.mi.us (Marc Unangst) writes: >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. er.. ah.. the Received: header lists both the sending and receiving host, so therefore the `local' host is appearing in the header somewhere. If I were to change the Received: header additions I'd make it a bit more verbose listing what channel it came from, the return address, one or more of the forward addresses, and (if known at that time) the outgoing channel. >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? If SCO's version of MMDF was compiled with NAMESERVER undefined then there's no-way-no-how you can do nameserver queries. NAMESERVER was there in the version SCO used (update 32). A good strategy to use with nameservers is to have a seperate database from which you generate nameserver files /etc/hosts /usr/mmdf/table/smtp.chn etc. The database can be a simple file and processed with an awk script. That's what we started with at the U of Kentucky before one of the guys changed it into a distributed database system in the process of earning a Masters Thesis. (results are in the Usenix large-systems workshop proceedings from September '89). de-digressing: If you use this seperate-database-and-generate-needed files-from-awk-script approach you make sure that *all* those files are up to date in one fell swoop. Yes, theoretically, the desire is to only use nameservers. I'm definitely one to campaign for more and stronger nameserver use (& abuse even..). But I also know quite well the needs of having a system be usable when part of it uses nameservers and part doesn't. >(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.) er.. ah.. the /usr/lib/sendmail that MMDF installs *is* command-line-compatible with Berzerkeley sendmail. At least enough-compatible to do the job of posting mail, and possibly a couplea other things. (Starting up an smtpd for instance..) It works fine for posting mail from mush, for instance. I've also used it from shell scripts w/o problem. -- <- David Herron, an MMDF & WIN/MHS guy, <- Formerly: David Herron -- NonResident E-Mail Hack <- <- Sign me up for one "I survived Jaka's Story" T-shirt!