From owner-freebsd-questions@FreeBSD.ORG Thu Sep 30 22:11:31 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 450F216A4CE for ; Thu, 30 Sep 2004 22:11:31 +0000 (GMT) Received: from bjwcs.com (swing.bjwcs.com [208.185.25.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id D39F843D1F for ; Thu, 30 Sep 2004 22:11:30 +0000 (GMT) (envelope-from brently@bjwcs.com) Received: from SAMBA [66.252.69.26] by bjwcs.com with ESMTP (SMTPD32-8.05) id A4909E900E0; Thu, 30 Sep 2004 18:11:28 -0400 From: "Brent Wiese" To: Date: Thu, 30 Sep 2004 15:11:24 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <20040926184512.GA48082@happy-idiot-talk.infracaninophile.co.uk> Thread-Index: AcSj+QUKuYZ66I1fQiGuxFEGzAXS7gDQGwIg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-Id: <200409301811921.SM01528@SAMBA> Subject: RE: Backup Mail Server Questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Sep 2004 22:11:31 -0000 > That's the hard part. The Secondary MX'ing part is fairly easy. All > you do is get your friend to add an MX record to the DNS > 'yourfriend.com' zone listing your server as a high numbered MXer: > > $ORIGIN yourfriend.com. > > @ IN MX 0 smtp.yourfriend.com. > 10 smtp2.yourfriend.com. > 30 smtp.you.com. > > And then add: > > yourfriend.com RELAY > > to /etc/mail/access and rebuild access.db. That means your machine > will accept e-mails addressed to users @yourfriend.com and queue them > up for relaying onto to his servers as soon as they come back up > again. If his site has to go down for an extended length of time, you > can make special arrangements to store incoming mail for longer than > the usual 5 days and then flush it over to him when he comes back up. I have a question that builds off this. Is there a way to make the backup MX server understand that some mail is ultimately destined for it and try to deliver it locally? Here would be an example: Mydomain.com is MX'd to mail.mydomin.com, which handles email for all my users. On that server, I've set up an alias for support@ that is actually a forward to my ticket system box (ie: support@tickets.mydomain.com). In the event my main mail server is down, I'd like to use the tickets.mydomain.com box as the backup MX. Its already running SMTP to handle the tickets, so seems a logical choice. What would be ideal is to have mail destined for support@ to be delivered locally. So, for example, a user can create a ticket saying the mail server is down (of course that is only useful if admins have off-site email addresses the ticket system notifies for redundancy, but that's easy enough). Mostly interested in knowing how to do this under Postfix, but I'm not married to it. Thanks, Brent