Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!rusmv1!grasp2.univ-lyon1.fr!wolf
From: wolf@grasp2.univ-lyon1.fr (Christophe Wolfhugel)
Newsgroups: comp.mail.sendmail
Subject: Re: Temporarily disable MX usage
Message-ID: <1991Feb27.130810.25307@rusmv1.rus.uni-stuttgart.de>
Date: 27 Feb 91 13:08:10 GMT
References: <1991Feb21.181945.3595@rusmv1.rus.uni-stuttgart.de> <1991Feb21.173954.907@mp.cs.niu.edu>
Sender: news@rusmv1.rus.uni-stuttgart.de (USENET News System)
Organization: INSA Departement Informatique, Lyon, France
Lines: 19

Well, I got the solution to this problem. Here it is, hoping it might
help other users. The idea is not to disable temprarily the MX record, but
to use 2 (or more) MX records per host. Each of the local hosts at our
domain currently has one 'MX 10' record pointing to our MX. So when my
listserv sends mail locally it goes through the MX, what I don't want.

By adding a second MX record for each local host pointing to the host
itself (at MX 0 record) the new scheme is:
  - first try to deliver to MX 0 (the host itself)
  - if it fails deliver to the next MX (in this case MX 10).

Another solution that I've been suggested is to setup a second DNS that
can be only accessed locally and with each host being it's own MX.

Thanks to Neil Rickert and Mark D. Baushke for their precious help.
-- 
Christophe Wolfhugel (on irc: Zolf)   |  Email: wolf@grasp1.univ-lyon1.fr
INSA Lyon - Departement Informatique  |  IRC'admin at node grasp1.univ-lyon1.fr
69621 Villeurbanne Cedex, France      |  Fax: (+33) 72 44 08 00