gregh@aplcomm.JHUAPL.EDU (Robert G. Hollingsworth) (01/25/91)
For incoming mail, we can set up mail exchange hosts using bind's MX feature. We'd like to have the same 'centralized' control over outgoing mail where mail to Internet hosts would be routed through one or two or our hosts before being sent out to the Internet. I know this can be accomplished using sendmail.cf options; however, this would require changing a lot of sendmail.cfs. Does anyone know of a an easier method to accomplish this? Thanks, Greg Hollingsworth gregh@mailer.jhuapl.edu
jeff@crash.cts.com (Jeff Makey) (01/26/91)
The global nature of the DNS database means that you could not keep your
"outgoing MX" records private if you are directly on the Internet. The
only time you can safely create bogus MX records (or any other type, for
that matter) is when you do not have IP connectivity to the rest of the
Internet, such as is often the case with TCP/IP LANs that are connected
to the rest of the world via UUCP. In this case, you can have your own
root server and have an MX record direct "*." wherever you want.
The DNS is for public data. Private routing data must go somewhere
else, such as sendmail.cf.
:: Jeff Makey
Department of Tautological Pleonasms and Superfluous Redundancies Department
Posting from my temporary home at ...
Domain: jeff@crash.cts.com UUCP: nosc!crash!jeffpeiffer@umn-cs.cs.umn.edu (Tim Peiffer (The Net Guy)) (01/27/91)
In article <357@aplcomm.JHUAPL.EDU> gregh@aplcomm.JHUAPL.EDU (Robert G. Hollingsworth) writes:
For incoming mail, we can set up mail exchange hosts using bind's MX
feature.
We'd like to have the same 'centralized' control over outgoing mail
where mail to Internet hosts would be routed through one or two or our
hosts before being sent out to the Internet. I know this can be
accomplished using sendmail.cf options; however, this would require
changing a lot of sendmail.cfs. Does anyone know of a an easier
method to accomplish this?
How about setting everybody up with mailhost.jhuapl.edu? You can then
MX mailhost to whatever you would like. I know that this would
involve changing the sendmail.cf. But, then again, this would mean
you would only need one sendmail.cf for other than your MX hosts.
mailhost in a whatever.his.address.is
in mx 0 primary.mx.host.
etc....
One behavior that might come up is that if the primary mx host is
down, the available alternates will immediately forward to the
internet. This seems to go against what the MX record is for, but
then again, that is the behaviour that I think you are looking for.
I haven't given this much thought though.
Tim
-----------
Tim Peiffer peiffer@cs.umn.edu or
Computer Science Dept ..!rutgers!umn-cs!peiffer
University of Minnesota
MPLS MN 55455
--
-----------
Tim Peiffer peiffer@cs.umn.edu or
Computer Science Dept ..!rutgers!umn-cs!peiffer
University of Minnesota
MPLS MN 55455