> From: Sheer El-Showk <[EMAIL PROTECTED]>
> Date: Fri, 4 Aug 2000 21:13:32 +0000 (WET)
>
>
> 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.
>
> By the way, an entirely qmail solution shouldn't be a problem since the my
> clients seem to like the idea of linux and I am a big fan of qmail ;->
This is doable as long as you find some reasonably automated way to maintain
the .qmail files that forward the users identically everywhere.
Make domain.com a virtual domain at all locations. Tell qmail at all
locations that [EMAIL PROTECTED] is really [EMAIL PROTECTED] and
[EMAIL PROTECTED] is really [EMAIL PROTECTED] and so on.
Point MX records equally at all your locations. The outside world will send
the mail to one of your hosts which will then forward it to where you really
want it.
I'd probably maintain the .qmail-domain-* files for the virtual domain
in one central location and then rsync or rdist them to all the servers at the
same time.
Also, I think qmail-ldap has a facility for doing this more magically out of
LDAP.
Chris
> On Fri, 4 Aug 2000, Russell Nelson wrote:
>
> > Sheer El-Showk writes:
> > > I would like to host mail for a single domain (ie all users should be
> > > [EMAIL PROTECTED]) on several (geographically distributed) machines,
> > > with users in each area receiving their mail at the local mail sever.
> The
> > > hard part is, as bandwidth is a limiting issue, I don't want all the m
> ail
> > > to be forwarded through a single host (eg if user1 at location A is
> > > sending a 5 MB attachement to user2 at location B, I don't want that t
> o
> > > have to bounce off some central mail sever at location C). This means
> > > that all the mail servers serve the same domain name but have to be
> > > distinguishable (via DNS or sonmething sendmail does) by users served.
> >
> > Qmail lets you implement this using virtualdomains. You can
> > virtualize a domain on a per-use basis. So tell the qmail running at
> > location A that [EMAIL PROTECTED] is actually [EMAIL PROTECTED]
> >
> > Unfortunately, both sites A and B have to be running qmail and must be
> > configured with the user table. There's no global way to do what you
> > want. I suggest that you colocate the central mail server somewhere
> > where there's plenty of bandwidth, and configure it with the user table.
> >
> > --
> > -russ nelson <[EMAIL PROTECTED]> http://russnelson.com | If you think
> > Crynwr sells support for free software | PGPok | health care is expensiv
> e 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.
> >
>
--
Chris Garrigues http://www.DeepEddy.Com/~cwg/
virCIO http://www.virCIO.Com
4314 Avenue C
Austin, TX 78751-3709 +1 512 374 0500
My email address is an experiment in SPAM elimination. For an
explanation of what we're doing, see http://www.DeepEddy.Com/tms.html
Nobody ever got fired for buying Microsoft,
but they could get fired for relying on Microsoft.
PGP signature
