Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site utai.UUCP
Path: utzoo!utcsri!utai!mendell
From: mendell@utai.UUCP (Mark Mendell)
Newsgroups: net.mail
Subject: Re: Sendmail problems - HELP!
Message-ID: <403@utai.UUCP>
Date: Sun, 31-Mar-85 21:05:57 EST
Article-I.D.: utai.403
Posted: Sun Mar 31 21:05:57 1985
Date-Received: Mon, 1-Apr-85 10:48:19 EST
References: <325@mnetor.UUCP> <655@plus5.UUCP>
Organization: CSRI, University of Toronto
Lines: 33

As the person who wrote (hacked?) the sendmail.cf files for utcsri (and
most of the other machines here), I will agree that it is very painful to
handle both UUCP & ARPA style addresses.  We support uucpsystem!...!user,
user@ethersystem, and for backwards compatability ethersystem!user.  In
addition, we also have a CSNET connection to worry about.  I have munged
the distributed sendmail.cf files until it works most of the time, and
send all complaints to /dev/null (or challenge the complainer to do better).

    The basic algorithm is:

    - if the path is knownUUCPsite!anything, send it to that UUCP site.

    - if the path is anything@CSNETsite, send it to CSNET

    - if the path is anything@AnySite, send it to AnySite

    - if the path is anything!anythingElse, send it to anything & let them
	worry about it.

    - otherwise, we have a local name

    L.sys and CSNET site names are read in at freeze time.

    I wouldn't mind hearing about better algorithms.  We had a problem with
conflicts between CSNET names & local network nicnames, that caused some mail
to be sent to Amsterdam for a couple of days.  I came up with a shell script
that munges the CSNET name file until it doesn't conflict.
-- 
Mark Mendell
	    Computer Systems Research Institute    University of Toronto
	    Usenet:	{linus, ihnp4, allegra, decvax, floyd}!utcsrgv!mendell
	    CSNET:	mendell@Toronto
	    ARPA:	mendell%Toronto@CSNet-Relay