Sascha Ottolski writes:
> I get Mail for somedomain.com over a first qmail-Server,
> qmail1.somedomain.com. There is another qmail-Server, qmail2.somedomain.com.
>
> A user might have an acoount on qmail1 _xor_ on qmail2, never on both. Know
> I'm thinking on how to forward the message in a simple an maintance-poor way.
> There could be a list on qmail1 with all users on qmail2, so if user is not on
> qmail1, look if she is on the list for qmail2; if yes, forward the message to
> qmail2; if not bounce the message.
>
> I'm also thinking that it might be possible to use LDAP for such an approach,
> but the patches on qmail.org are still called beta.
>
> Yes, we could use subdomains, but this is not an option (at least for the
> offical Mail-Domain, it might be possible use different subdomains internally
> only) as for the outer space the shall be only somedomain.com known, but no
> subdomains.
Sounds like exactly what I set up for Oakton Community College. They
have one incoming SMTP server, and two POP servers, one for students
and one for faculty. The incoming SMTP server does a LDAP lookup, and
forwards the mail to the appropriate host. That's where the database
lookup tip (http://www.qmail.org/top.html#databaselookup) came from.
The X program looked up the user's canonical email address. I don't
remember the exact name of the program, but it had some parameters
that we used to select the LDAP server and request a lookup of the
email address. It was from the umich distribution, and we used it
unmodified. I started to modify it to do the forward itself, then
said "This is crazy. We've got a kick-ass machine here (PII-300, 256K
RAM), why not *see* if it can work with some shell glue." And it's
been working for them just fine.
--
-russ nelson <[EMAIL PROTECTED]> http://crynwr.com/~nelson
Crynwr supports Open Source(tm) Software| PGPok | There is good evidence
521 Pleasant Valley Rd. | +1 315 268 1925 voice | that freedom is the
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | cause of world peace.
