From owner-freebsd-hackers  Sat Jul 22 19:17:26 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id TAA13497
          for hackers-outgoing; Sat, 22 Jul 1995 19:17:26 -0700
Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id TAA13491
          for <hackers@FreeBSD.org>; Sat, 22 Jul 1995 19:17:22 -0700
Received: (from nate@localhost) by trout.sri.MT.net (8.6.11/8.6.11) id UAA00615; Sat, 22 Jul 1995 20:14:46 -0600
Date: Sat, 22 Jul 1995 20:14:46 -0600
From: Nate Williams <nate@trout.sri.MT.net>
Message-Id: <199507230214.UAA00615@trout.sri.MT.net>
In-Reply-To: roberto@blaise.ibp.fr (Ollivier Robert)
       "Re: MX records and sendmail" (Jul 23,  1:25am)
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: roberto@blaise.ibp.fr (Ollivier Robert)
Subject: Re: MX records and sendmail
Cc: hackers@FreeBSD.org
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

> > Machine A is connected to the Internet via a SLIP line, which goes down
> > whenever I need the phone or need the computer for non-BSD work. 
> > Machine B is on the Internet full-time, and is the primary DNS box for
> > my sub-net.
> 
> You can put two MX like this :
> 
> machine-a	IN	MX	10 machine-a.network.us.
> 		IN	MX	20 machine-b.network.us.

Okay, so this should work then.
machineA.domain.net    preference = 5,  mail exchanger = machineA.domain.net
machineA.domain.net    preference = 10, mail exchanger = machineB.domain.net

> if machine-a is up, then the mail will arrive there. If not, the secondary MX
> machine-b will then receive the mail and queue it for machine-a. When 
> machine-a is up, you can run the queue (sendmail -q) on machine-b.

Do I need to do anything special to the sendmail.cf on machine B for it to accept
email for machine A, or is the MX record enough?

> Some providers use a mailertable to put the mail to machine-a in a separate
> queue (using a special mailer entry) and then run the queue whenever the
> machine-a calls. It is a little harder to set up but works too.

Will machine-B attempt to send out the queued email at the -q##
intervals, or is MX queued email handled differently?


Nate