[69316] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Mailserver requirements

daemon@ATHENA.MIT.EDU (Jeff Workman)
Mon Apr 5 20:04:45 2004

Date: Mon, 05 Apr 2004 20:03:58 -0400
From: Jeff Workman <jworkman@pimpworks.org>
To: Richard Welty <rwelty@averillpark.net>, NANOG <nanog@nanog.org>
In-Reply-To: <Mahogany-0.66.0-11751-20040405-174819.00@averillpark.net>
Errors-To: owner-nanog-outgoing@merit.edu




--On Monday, April 05, 2004 5:48 PM -0400 Richard Welty 
<rwelty@averillpark.net> wrote:

> for that matter, if i were running a very very large mail farm with high
> volume in one or both directions, separating the inbound mail handlers
> (MX hosts) from the outbound mail relays would be something that i'd
> seriously consider doing as part of the architecture. this would interact
> very badly with the mail rejection strategy outlined in the original post
> in this thread.

While I think it's pretty anal-retentive to require a mail sender to have a 
valid MX record, I don't see what would be so hard about setting up MX 
records for this scenario:

inbound-mx01	IN A		192.168.1.98
inbound-mx02	IN A		192.168.1.99
outbound-01		IN A		192.168.1.100
			IN MX 10 	inbound-mx01
			IN MX 20	inbound-mx02

Or am I missing something?

-J

--
Jeff Workman | jworkman@pimpworks.org | http://www.pimpworks.org

home help back first fref pref prev next nref lref last post