On Fri, Aug 04, 2000 at 05:25:46PM -0500, Ben Beuchler wrote:
> On Fri, Aug 04, 2000 at 09:13:32PM +0000, Sheer El-Showk wrote:
>
> > Thanks, but my real concern is that all the mail NOT go through a SINGLE
> > mail server (in terms of bandwithd). If I do what you suggested
>
> I don't think it's possible to avoid that. Which server mail is sent to
> is a function of DNS, not mail server configuration. The only way an
> MTA has of knowing where to send a piece of mail is by looking up an MX
> record for it. It can only look up based on domain. DNS does not know
> anything about users and should not.
>
> So. Your only real option is to have a single mail server accepting
> mail and then distribute it to other servers. This does not fix your
> bandwidth problem. But, with a little research you can find one of
> several ways to use the primary mail server only as a way to accept
> inbound mail and then redistribute it to any one of several other mail
> servers based on multiple criteria.
What about having two servers with the same MX priority? That should work.
adam@spotted:~$ dig earthlink.net mx
; <<>> DiG 8.2 <<>> earthlink.net mx
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4
;; flags: qr rd ra; QUERY: 1, ANSWER: 10, AUTHORITY: 0, ADDITIONAL: 0
;; QUERY SECTION:
;; earthlink.net, type = MX, class = IN
;; ANSWER SECTION:
earthlink.net. 0S IN MX 5 mx09.earthlink.net.
earthlink.net. 0S IN MX 5 mx00.earthlink.net.
earthlink.net. 0S IN MX 5 mx01.earthlink.net.
earthlink.net. 0S IN MX 5 mx02.earthlink.net.
earthlink.net. 0S IN MX 5 mx03.earthlink.net.
earthlink.net. 0S IN MX 5 mx04.earthlink.net.
earthlink.net. 0S IN MX 5 mx05.earthlink.net.
earthlink.net. 0S IN MX 5 mx06.earthlink.net.
earthlink.net. 0S IN MX 5 mx07.earthlink.net.
earthlink.net. 0S IN MX 5 mx08.earthlink.net.
--Adam
