Hi,
I sometimes encounter similar setups.
I usually solve this by identifying one server as a central system
(example.com) and then using sudomomains for mail-routing to the
branches (paris.example.com, berlin.example.com).
On the central system you'll have to maintain the virtual:
us...@example.com us...@paris.example.com
us...@example.com us...@berlin.example.com
routing is done in the transport file:
paris.example.com smtp:192.168.10.3
berlin.example.com smtp:192.168.20.3
(You can use external addresses, but I prefer to use vpn connections so
all traffic is encrypted between the branches.)
On each branch system you'll have to set the mydestination in main.cf to
paris.example.com or berlin.example.com, respectively.
And you should set the central system as relay host in main.cf at the
branches. You just have to create the users working at this place, no
need for a virtual.
This way all traffic initiated in a branch is relayed to the central
(because mydestination does not match for @example.com), there the
virtual entry forwards it back to the branch. So all traffic within a
branch takes a loop via the central system.
The advantage is that you can easily install and maintain all filter
stuff (anti-virus, anti-spam, e-mail-archive) at the central system, as
any e-mail has to pass by here.
I hope you'll get the idea :-) Otherwise please feel free to ask.
Groetjes
Claus
--
Claus R. Wickinghoff, Dipl.-Ing.
using Linux since 1994 and still happy... :-)
