< stuff deleted... >
>
> > > In fact, from a human factors point of view, it seems likely that
> > > "non-obvious" (a better term might be "user hostile") mail names are
> >
> > I believe the scheme should be chosen to make it difficult to mistype an
>
> The non-obvious naming scheme is simply going to encourage people to not use
> email and/or use the built-in alias/addressbook feature of the mailer to map
> A more feasible naming policy for a large organization might be via domain
> or sub-domain
>
> Peter_Smith @
corporate .
organiztion .
com - external
> Peter_Smith @
corporate - internal
>
> Pete_Smith @
advertising .
organization .
com
<...>
> This is still not perfect but somewhat easier to remember and more along the
You're right about this not being perfect - I'd go further - it isn't
workable in the long run. Consider the situation of one entity's
subdomain matching another entity's domain.
I think that part of the solution here is a directory service/mechanism
such as that which can be provided with whois++. Proper integration of
such a service with key management and mail systems should eliminate this
problem - and should do so properly.
This only really connects with firewalling in that it presents issues
similar to those raised with getting users across a firewall (user
training/knowledge/understanding).
> Fact is the the VP Finance is responsible for the screw-up for not verifying
As a VP who isn't in charge of Finance, I agree.... <g>
--david
________________________________________________________________________
David Holmes Bunyip Information Systems Inc
Vice President, Operations Montreal, Canada
e-mail: delphys @
bunyip .
com voice: +1 514 875 8611 fax: +1 514 875 8134
References:
|
|
