The problem with peering as I see it is that you cannot control where (which
physical server) a user's mailbox is created on. It migh be possible to
write a script that creates the users mailbox on a specific server, by
creating a subdirectory on the server with a mailbox file in it, but this is
not supported by the Imail interface (and I decided not to try it).
As a corporate customer (non-isp) this is something I would like to see
IPswitch add to the product. That way, I can put a peered server across a
leased line from my Internet Gateway, and give branch office users local
access. But until there is a supported method of making sure that the
Seattle users mailbox is setup on the peered Seattle server, not on the
Atlanta server I cannot use peering.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Len Conrad
Sent: Thursday, November 18, 1999 11:28 AM
To: [EMAIL PROTECTED]
Subject: Re: [IMail Forum] remote POP mail
RTFM, see 'peering'. If this works for you, it would allow you maintain
only one mail domain, spread across yr local and remote POP sites. The
remote site would send mail to its local Imail.
This also gives you MX redundancy, at the cost of some msg traffic incoming
being sent to the "wrong" server which would forward it to the right server.
You create mailboxes on local to the users which is your best attempt to
reduce your timeout pb, allowing every body to smtpsend/popreceive with
their local server.
Len
===============
>Hi all
>Remote users are frequently experiencing timeouts when sending and/or
>receiving mail.
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
