Subject: Re[2]: Pass-through
routing
Author: Ron Herardian at GSS
Date: 07-19-97 04:25
I happen to have been with Hubert Lipinski when we
invented HUBPASS for CompuServe at the last (ever) cc:Mail Interchange
conference in San Francisco. CompuServe wanted to give all subscribers
the same PO name to simplify addressing, installation, support, and
maintenance.
To meet the customer requirement the Router at the
hub PO would have to determine the user's home PO. Cutting through
the red tape, Hubert went ahead and added the feature to Router enabling
CompuServe to move ahead. Originally, it was undocumented.
Normally the Router gets the user's home PO name
from the Mobile handshake and, if it's not the hub name, executes
the Remote Call Through sequence immediately by looking up the address
of the user's home PO in the directory and executing a Type I connection.
HUBPASS, on the other hand, allows all users to specify
the hub PO name as their home PO name in the Mobile configuration.
The Router with HUBPASS finds the user name in the directory first,
then finds their PO name, and then executes the normal Remote Call
Through sequence.
To answer your question, no, I don't recommend using
HUBPASS for ordinary cc:Mail systems, as compared with an e-mail service
provider. For systems with only 5,000-10,000 users (under 50 POs),
it's actually easier to troubleshoot and maintain using full and explicit
cc:Mail addressing in conjunction with directory synchronization.
Arguably, this is personal preference but consider some of the implications.
For example, part-time Mobile users may know their
home PO name and could be confused if their address in Mobile was
the name of the hub instead. Similarly, your help desk personnel have
to understand HUBPASS in addition to Remote Call Through to support
Mobile users in the field. In fact, addressing by user name is valid,
but if you use HUBPASS in an ordinary cc:Mail system, it will become
known to users that they can have multiple addresses, e.g. "John
Valentine AT PO1" and "John Valentine AT HUB."
My advice: Just use the products the way they were
designed for small systems unless your system actually is very large.
It doesn't pay to get fancy when the product will work just fine out
of the box.
Ron
--
Subject: Re: Pass-through routing
Author: Hayley_Smith@intuit.com (Hayley Smith)
at INTERNET
Date: 07-18-97 17:56
Hi Ron,
Hope I'm not out of line sending this to you. Your
advice on the ccmail-l list has been helpful and I wanted to see if
I could get an opinion from you. I especially appreciate any techinical
insight into the workings of cc:Mail as I feel fairly competent when
it comes to supporting/working with the product. (I seem to recall
meeting you at a cc:Mail bay area users group meeting, but that would
have been a couple of years ago.)
Do you recommend using the HUBPASS parameter for
mobile dialins? At one of our sites we don't use it, so in mobile
the user's home address is their subordinate home po. At another site
the parameter is in use, so the mobile home address is the hub, even
though their actual home po is actually a subordinate to the hub.
I've gotten differing opinions from various cc:Mail
reps about use of this parameter. Any insight you can provide is greatly
appreciated!
Many thanks in advance.
Hayley Green Smith
Email Systems Administrator, Intuit
415-944-3662
hayley_smith@intuit.com
Subject: Re: Pass-through routing
Author: "cc:Mail Interest Group" <CCMAIL-L@LISTSERV.OKSTATE.EDU>
at Internet
Date: 7/18/97 5:03 PM
Dan,
In theory all you need is a drive mapping to PO2.
In fact, you should not do this over WAN links. However, you can get
away with it if the pipes are clean and fast enough. If the pipes
are dirty and slow it will be your worst nightmare--corruptions, connect
problems, and all.
Good luck!
Ron
--
Subject: Pass-through routing
Author: "cc:Mail Interest Group" <CCMAIL-L@LISTSERV.OKSTATE.EDU>
at INTERNET
Date: 07-17-97 14:24
I have a user whose home post office is PO2, which
is subordinate to PO1. He isa user who splits his time between mobile
and local use. Our dial-in router (NTRouter 6) resides on PO1. PO2
and PO1 are separated by a WAN link, so performance is unacceptably
slow if he is a "local" user on PO1. Is there a way to enable
him to dial in to PO1, send and receive messages, while PO2 remains
his home post office?
PO2 (Router TCPIP)-----------WAN Link-----------(Router
TCPIP)PO1(Router Dialin)----------Remote Users
Thanks,
Dan