> Hint:
>
> smtp and pop3 are not valid answers.
If implemented well, and smartly, they can work (as I have done)...took me
about three weeks, but the system is secure, efficient, low bandwidth and
user-friendly. For internal mail to [EMAIL PROTECTED], the e-mail is
attempted to be sent locally. If not possible, it is sent to our main relay.
This in itself cuts down bandwidth. External mail to [EMAIL PROTECTED] is
sent to our main relay, which then delivers the mail via NFS to a user as if
it was local. Save the extra Delivered-to and relay lines in the mail. Less
bandwidth, less confusion. The system is fairly complex in setup, but it is
modulised so if something goes wrong, it is easy to hunt it down...
Well I don't know if that helps anyone but it might encourage you that with
qmail (and a bit of thought ;> ) anything is possible...
/BR
Manager
InterPlanetary Solutions
http://ipsware.com/
> -----Original Message-----
> From: John White [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, August 20, 2000 9:30 AM
> To: qmail mailing list
> Subject: Re: FW: qmail domain heiarchy
>
>
> On Sat, Aug 19, 2000 at 01:52:35PM -0500, Barry Smoke wrote:
> > >Who is they? The remote schools? All connections? How "dedicated"
> > >is a connection which is often down?
> >
> > remote schools...
>
> Ok.
>
> > I would like to have some sort of system that catches mail to
> this server,
> > checks the headers against a list of local users(take one of
> our elementary
> > schools for example....a list of 20 teachers on stored on the
> proxy that the
> > mail is checked against) if mail matches a user, deliver it to
> said user via
> > a qmail process on local proxy.
>
> I really just don't understand what you mean here.
>
> > Basically I'm wondering if I can cluster the main bryant.k12.ar.us qmail
> > server out with processes on the proxy server....somehow.....
> >
> > If one node is undetected...no prob...all other mail is delivered
> > normally....queued mail is delivered when connection is back up....
>
> It sounds like what you might want to do is put a qmail server on
> each of the servers at each of the location. Make the terminal
> delivery point for each teacher the qmail server at his location.
>
> It's pretty simple, then, to make a .qmail entry for each teacher
> at a remote location, forwarding mail the qmail server for that
> location.
>
> For example, if teacherA is at schoolN, this would be put in
> bryant.k12.ar.us's mx:
>
> ~teacherA/.qmail:
>
> &[EMAIL PROTECTED]
>
> > > >i would like to do this without running other domains....
>
> Not quite sure what you mean by that.
>
> > >I'm not sure how you want each person at each school to receive mail.
>
> > ??? pop3, smtp....
>
> Oh, in that case, just have the mail delivered by smtp. The
> teachers can then retrieve their mail via pop3.
>
> I'm asking whether you want teachers at remote locations to
> have their mail delivered to a local qmail server so mail
> can be retrieved during a network connection outage, or whether
> having the mail at a single qmail server which would require
> the network connection being up to check mail.
>
> In other words, you seem to have a specific path of delivery
> in mind. What the hell is it?
>
>
> John White
>
