[81645] in North American Network Operators' Group
Re: Localized mail servers, global scope
daemon@ATHENA.MIT.EDU (Andre Oppermann)
Wed Jun 22 12:49:01 2005
Date: Wed, 22 Jun 2005 18:45:58 +0200
From: Andre Oppermann <nanog-list@nrg4u.com>
To: Valdis.Kletnieks@vt.edu
Cc: Tony Finch <dot@dotat.at>, Andrew Staples <andrews@ltinet.net>,
nanog@merit.edu
In-Reply-To: <200506221640.j5MGelEE019031@turing-police.cc.vt.edu>
Errors-To: owner-nanog@merit.edu
Valdis.Kletnieks@vt.edu wrote:
> On Wed, 22 Jun 2005 17:23:22 BST, Tony Finch said:
>
>>You need a table of name -> location mappings which each mail server can
>>use to route email. You could distribute the table using whatever
>>technology you like, e.g. LDAP. Google for Schlumberger Exim LDAP for a
>>complicated example, though it can be done much more simply.
>
> That's all fine and good once the mail gets into his e-mail infrastructure.
>
> The problem he's going to hit is that he wants *my* mail server to send mail to
> 'fred@example.com' to get routed to the MX in San Fran where Fred is, and *my*
> mail server to send mail 'johann@example.com' to get routed to the MX in Geneva
> where Johann is, and avoid having a central MX that then does routing.
>
> And basically, he's screwed, because the MX lookup is only based on the RHS
> of the target address. AT *best* he can deploy a @NN.example.com and have
> different MX entries for US.example.com and FR.example.com and so on (but he
> already said that's a suboptimal).
He needs something like the distributed clustering of qmail-ldap. Any mail-
cluster member can accept messages for all others and does direct internal
redistribution without going through HQ. No country specific subdomains needed.
Everything has user@example.com.
--
Andre
