Chris Garrigues wrote:
>
> > From: Greg Elliott <[EMAIL PROTECTED]>
> > Date: Thu, 12 Jul 2001 10:58:33 +0930
> >
> > The problem I am trying to resolve is where <user3> mails <user4> at the
> > address <[EMAIL PROTECTED]>
> > I do not want the mail to be sent back to the central mail server and then
> > returned to the address
> > <[EMAIL PROTECTED]>.
> > Instead I would like the branch mail server to realise that <user4> is a
> > local user and just deliver the mail to <user4>'s
> > local mail store.
>
> I suspect the easiest thing to do would be to get the qmail-ldap patches and
> install ldap.
>
> Keep the master LDAP database on the central server and run replica databases on
> each on the branch servers.
I have a master LDAP server on it's own machine, because I use it for
alot more than just email accounts. I have a replica LDAP server on all
mail servers. LDAP replication is done real-time via SSL, only the
master accepts modifications. Mail authentication is pointed to the
local LDAP server on the mail server, so imap/pop passwords never fly in
the clear. If you have failover LDAP and the local server dies for some
reason, it will pick up a remote server and you will be in the clear
unless you are on a vpn. I have asked Sam Varshavchik to implement SSL
in Courier's authldap module.
> Each server would then be able to use LDAP to determine where the mail really
> belongs.
The mail routing works very well to remote offices in US, Japan, and
Germany. You also need Henning's dash-trick patch. This is required so
that you can store aliases and pointers to ezmlm lists in LDAP,
otherwise you have to use the same outgoing mail server for all offices
and that is not too cool. I can provide details on how to do this if
needed.
> I haven't used all the functionality that this would require, but I'm fairly
> certain that qmail-ldap has everything you'd need.
And alot more. Join the qmail-ldap mailing list from www.nrg4u.com.
Regards,
Mike
