Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!sun-barr!decwrl!ucbvax!bloom-beacon!eru!hagbard!sunic!mcsun!hp4nl!charon!piet
From: piet@cwi.nl (Piet Beertema)
Newsgroups: comp.mail.sendmail
Subject: Re: Local Configuration Error
Message-ID: <2229@charon.cwi.nl>
Date: 25 Sep 90 09:15:26 GMT
References: <1990Sep20.182739.29113@mp.cs.niu.edu> <2223@charon.cwi.nl> <1990Sep24.212433.774@mp.cs.niu.edu>
Sender: news@cwi.nl
Organization: CWI, Amsterdam
Lines: 19


	With the only MX record pointing to the local host, the action
	is to look up an A-record.
Right. In my opinion that should give a "local configuration error"
too, but you won't agree with that.

	There are 26 upper case letters of the alphabet available for
	macros, and most configuration files use only a small number
	of them. The lower case letters have internal predefined meanings.
	Why do you have to violate the internal predefined meaning
The predefined meaning of $w is the "hostname of this site".
Redefining $w to be precisely the same but only with another
representation can be useful (if only to make $=w in the sample
config files work) and doesn't "violate" anything. I therefore
maintain that $w should *always* be made fully qualified before
comparing it to the contents of MX records.

--
	Piet Beertema, CWI, Amsterdam	(piet@cwi.nl)