Adrian,
<DISCLAIMER>
I've only been playing with qmail for a few months and it's only
installed on one server, but here's what I would suggest.
</DISCLAIMER>
Setup qmail/ldap at all of your pops. Enable clustering (in qmail) and
have the local (remote POPs) mail servers replicate the core/primary
ldap server (see FAQ for OpenLDAP (slurpd i think). You can then define
mailhost (I think that's the attribute name--somebody correct me if I'm
wrong) for each user in LDAP to the the mail server at their primary
POP. This seems like the cleanest way to approach the problem.
You could then setup caching dns server as the remote POPs and use bind
9 views (not very familiar with this) for each POP so that
mail.yourdomain.tld == local mail server. This really isn't necessary,
but it would make life a little easier for your support people.
Anyone want to correct/critique this generalization?
Thanks,
Mike
Adrian Ho wrote:
>
> On Wed, 6 Jun 2001, Lye On Siong Johnny wrote:
>
> > I have the follow scenario. Assuming my office is separate into 10
> > different locations, with about 50 staff in each location. Is that
> > anyway whereby I can configure a mail server or something equivalent
> > at each location such that the machine will know which are the local
> > user, and send it to the local machine, and if not, they will send it
> > out. This is to reduce the amount of out-going traffic
>
> You can either have a central server that knows where everyone is, and the
> 10 local servers simply relay non-local mail to it, or replicate that
> knowledge amongst the 10 local servers. Either way:
>
> <http://cr.yp.to/qmail/pictures/PIC.local2alias>
>
> --
> Adrian Ho [EMAIL PROTECTED]
