From owner-freebsd-hackers Sat Jul 22 13:41:28 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id NAA03422 for hackers-outgoing; Sat, 22 Jul 1995 13:41:28 -0700 Received: from virgo.ai.net (virgo.ai.net [198.69.44.2]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id NAA03416 for ; Sat, 22 Jul 1995 13:41:19 -0700 Received: from aries.ai.net (aries.ai.net [198.69.44.1]) by virgo.ai.net (8.6.11/8.6.12) with ESMTP id QAA10002; Sat, 22 Jul 1995 16:49:02 -0400 Received: (from nc@localhost) by aries.ai.net (8.6.11/8.6.12) id QAA09927; Sat, 22 Jul 1995 16:41:01 -0400 Date: Sat, 22 Jul 1995 16:41:01 -0400 (EDT) From: Network Coordinator To: Nate Williams cc: hackers@FreeBSD.org Subject: Re: MX records and sendmail In-Reply-To: <199507221937.NAA00267@trout.sri.MT.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.org Precedence: bulk You shouldn't add Machine A to Machine B's Cw array. That will make Machine B think it actually *IS* machine A. What you should tell machine B to do is try machines directly if it is the most preferred site. [Ow should have a True in it]. Normally what will happen is say you have Site A MX 10 Site B in the DNS entry, what will happen is B will freak out trying to send back to itself on the MX try. Site B is the best site for A, it should try A directly. What will happen is the mail will be held in B's queue until A comes back online. What might work for you otherwise is: Site A MX 5 Site A MX 10 Site B so B will try to send the mail to A if it can. Though setting Ow to True works over here. Hope it helps, -Jerry. On Sat, 22 Jul 1995, Nate Williams wrote: > How do I go about setting up a MX record such that email to site A is > sent to site B but is only queued up instead of being delivered to the > users on Site B. > > 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. > > I added the MX record to point to machine B which machine A is down, but > it was orginally rejecting the email until I modified the sendmail.cf > file to accept mail to machine B. However, now it's delivering the > email to the users on machine B instead of queing up the email and > waiting until machine A is back up, and I can't send email from machine > B to A since B knows it's machine A. > > Is this possible? Since I have access to both machines, I know that I > can at least get the mail destined to machine A no matter what if it at > least spools on machine B. > > Thanks in advance, > > Nate > >