Sheer El-Showk writes:
> Thanks, but my real concern is that all the mail NOT go through a SINGLE
> mail server (in terms of bandwithd). If I do what you suggested
> [EMAIL PROTECTED] still has to go through location A (the full message,
> including attachements has to be received at that location) which means
> that it becomes a bandwidth bottle-kneck (and since there will be many
> locations all with very little bandwidth supporting a large organization
> this can be a problem). At least that's how I understand it -- if you
> know some way that location A could tell the outside server just to route
> directly to location B, that's what I'm really looking for (sort of a SMTP
> user-based server resolution). Please correct me if I misunderstood what
> you said or if it doens't require full mail routing through location A.
You can't get the rest of the world to send mail to a single domain
except by going to the host that accepts mail for that domain. But
within your domain, you can split it any way you want. You could use
LDAP, you could use the DNS, you could use fastforward, you could use
a bunch of .qmail files. Personally, I'd use the DNS. It's an
efficient, scalable, secure (well, okay, it's secure if you use
djbdns), cross-host, cross-platform database. Just do this:
echo 'example.com:alias-example' >/var/qmail/control/virtualdomains
echo '|forward $EXT2@$EXT2.example.com'
Then set up a bunch of DNS records that point to the host with that
user's mailbox.
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com | If you think
Crynwr sells support for free software | PGPok | health care is expensive now
521 Pleasant Valley Rd. | +1 315 268 1925 voice | now, wait until you see
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | what it costs when it's free.
