scott@prism.gatech.EDU (Scott Holt) (10/01/90)
Does anyone know of a way to make Sendmail under AIX 3.1 understand nameserver MX records? Our primary mail drop here is a domain called prism.gatech.edu - which is actually an MX record pointing to hydra.gatech.edu in our name server. Our 6000s seem to have trouble sending mail to the prism domain; they claim that its an unknown host. Adding prism as an alias for hydra in my local /etc/hosts file works, but this is a kludge and impossible to maintain for similar mail domains. If the big clue here is something other than "port Sendmail 5.61", please let me know. Thanks, - Scott
robert@veritas.uucp (Robert G. Fries) (10/02/90)
Sendmail under AIX 3.1 allows you to specifiy exactly which namserver
records to use (MX, MB, etc..) in the sendmail.cf itself. This is the only
version of sendmail I have seen that allows this.
--
Robert G. Fries robert@veritas.com
VERITAS Software {uunet,apple}!veritas!robert
Santa Clara, CA 95054 (408) 727-1222 x583jackv@turnkey.tcc.com (Jack F. Vogel) (10/03/90)
In article <14315@hydra.gatech.EDU> scott@prism.gatech.EDU (Scott Holt) writes: > >Does anyone know of a way to make Sendmail under AIX 3.1 understand >nameserver MX records? Our primary mail drop here is a domain called >prism.gatech.edu - which is actually an MX record pointing to >hydra.gatech.edu in our name server. Our 6000s seem to have trouble >sending mail to the prism domain; they claim that its an unknown host. >If the big clue here is something other than "port Sendmail 5.61", please >let me know. Although the 3.1 sendmail is not a pure 5.61 port, it definitely does have the getmxrr code in it. As Robert Fries noted in another posting, it even has code for using other type records, although without server support this isn't particularly useful at the moment. So, I don't think your answer is to port 5.61. I would be fairly confident that there's a problem in your sendmail.cf. Before the routine getmxrr is called the options to the resolver to append the default domainname and to do a domain search are turned off, so you must be sure that this routine is passed a fully qualified name, otherwise the lookup will fail. This means you must pass whatever smtp mailer you are calling the fully qualified name. I have seen this problem in some of the sendmail.cf files used internally here at Locus. That is where I would begin. Also, if this is really a problem, have you called and opened an official problem report with IBM? You should do so if you haven't. Good Luck! Disclaimer: I speak for myself, not my employer. -- Jack F. Vogel jackv@locus.com AIX370 Technical Support - or - Locus Computing Corp. jackv@turnkey.TCC.COM
jeffe@sandino.austin.ibm.com (Peter Jeffe 512.823.4091) (10/05/90)
In article <1990Oct03.131111.23523@turnkey.tcc.com> jackv@turnkey.TCC.COM (Jack F. Vogel) writes: >In article <14315@hydra.gatech.EDU> scott@prism.gatech.EDU (Scott Holt) writes: >> >>Does anyone know of a way to make Sendmail under AIX 3.1 understand >>nameserver MX records? [...] > >Although the 3.1 sendmail is not a pure 5.61 port, it definitely does have >the getmxrr code in it. As Robert Fries noted in another posting, it even >has code for using other type records, although without server support this >isn't particularly useful at the moment. Well, BSD's BIND, which is the named shipped with AIX, has supported the MB, MG, and MR records since at least version 4.3. And I can't imagine any other self-respecting nameserver not supporting these records, since they have been defined all along in the RFCs (albeit as "experimental", but that's no concern of the server). All that's missing is for the nameserver admin to define the proper records, and for the rest of the world to catch up :-). >I would be fairly confident that there's a problem in your sendmail.cf. Before >the routine getmxrr is called the options to the resolver to append the default >domainname and to do a domain search are turned off, so you must be sure that >this routine is passed a fully qualified name, otherwise the lookup will >fail. That's correct, and all you should have to do is specify the ANY value for the K option (as well as the MX value). Sendmail should then expand the non-FQDN into the canonical form via an A or MX record that matches the hostname. So if you don't want the MB, MG, or MR records enabled, your OK line should look like: OK MX ANY and this should get you flying. ------------------------------------------------------------------------------- disclaimer: given the subjective nature of reality, the opinions contained herein can have no relationship to any other person's conception of reality, and cannot therefore constitute grounds for a lawsuit, right? Peter Jeffe ...uunet!cs.utexas.edu!ibmchs!auschs!sandino.austin.ibm.com!jeffe