grossman@oscar.tn.cornell.edu () (04/13/91)
I've named my cell theory.cornell.edu, but I'm unable to get a machine named "theory.cornell.edu" right now for various political reasons. Will amds will work properly if I have the post office machine aliased to some other machine? Thus, if I have a machine "elmo.tn.cornell.edu", will an MX record for theory.cornell.edu pointing at elmo.tn.cornell.edu work? At least enough to bring it all up, test, demo, and convince these people to give me the right name? Thanks. -- David Grossman INTERNET: grossman@theory.tn.cornell.edu IBM Supercomputing Technology Center VNET: DJG at RHQVM21 Engineering and Theory Center Bldg. PHONE: (607) 254-8628 Hoy Rd.
rdew@ALW.NIH.GOV (Bob Dew) (04/15/91)
We had a similar problem at our work place. It is possible to install AMDS using post office machines that are named something other than the cell name. We recently completed an AMDS installation on our cell, alw.nih.gov, without using administrative access on the machine whose name is alw.nih.gov. We use an MX forwarding trick, like the one you describe, though for slightly different purposes. As long as your incoming and outgoing sendmail headers are doctored to match the name of your cell, it shouldn't matter what physical machine you choose to serve as an AMDS post office. Bob Dew National Institutes of Health Bethesda MD rdew@alw.nih.gov (301) 496-5361
Craig_Everhart@TRANSARC.COM (04/16/91)
The only downside of not having some PO machine be the same name as the cell name is that somebody out there will try sending mail to the From: address of a message (foo@theory.cornell.edu) without using MX records to get there. Certainly you should be able to get a good bit working before requiring a machine with the same name as the cell name. Craig
Craig_Everhart@TRANSARC.COM (04/19/91)
Paul Traina reminded me that all hosts are now required to do MX vectoring (rfc1123 paragraph 5.3.5, quoted below), so it should no longer be necessary to have a PO machine with the same name as the cell name, except to accommodate ``broken'' mail senders. Craig from RFC 1123: > 5.3.5 Domain Name Support > SMTP implementations MUST use the mechanism defined in Section > 6.1 for mapping between domain names and IP addresses. This > means that every Internet SMTP MUST include support for the > Internet DNS. > In particular, a sender-SMTP MUST support the MX record scheme > [SMTP:3]. See also Section 7.4 of [DNS:2] for information on > domain name support for SMTP.