Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!samsung!uunet!mcsun!ukc!mucs!cns!ap.co.umist.ac.uk!jf
From: jf@ap.co.umist.ac.uk (John Forrest)
Newsgroups: comp.mail.sendmail
Subject: Re: resolv options when rewriting sender (inconsistencies).
Message-ID: <1990Jul11.082858.3570@cns.umist.ac.uk>
Date: 11 Jul 90 08:28:58 GMT
References: <1990Jul3.020637.28385@ulrik.uio.no> <5764@jhunix.HCF.JHU.EDU> <1990Jul10.151028.20873@ulrik.uio.no>
Sender: usenet@cns.umist.ac.uk (Usenet news user)
Reply-To: jf@ap.co.umist.ac.uk (John Forrest)
Organization: UMIST Computation, Manchester, UK.
Lines: 19

I'm not sure what all the fuss about this is. We havn't imported v5.64
yet - we use 5.61 - but the same code regarding resolver options
being turned off was in 5.61, so it is hardly a change. 

John Forrest,
Dept. of Computation,
UMIST.

PS. I had to change the 5.61 code to get it to work in our environment
(we run the nameserver, but just on our workstation cluster, since we
don't have TCP access to the outside world). To be compatable in the UK,
we had to be able to resolve something like cs.notts to cs.notts.ac.uk, 
even though we only know about notts.ac.uk and I've no idea if 
cs.notts.ac.uk is valid. We then had to decide to send it to somewhere
that knows about ac.uk (or notts.ac.uk). Wildcard MX'ing did not fullfil
this criterea - well it's sort of all or nothing, since we had many such
problems, so I ammended sendmail to do it. Perhaps I should register the
changes (they are all dependent on #define options)? But I'm not sure how
to do it!