>
> The problem is that email clients don't supply the realm
> information when they authenticate. If they log in as
> their email address then this isn't a problem because
> the login name contains the domain info but the "holy
> grail" in my mind's eye would be to allow [EMAIL PROTECTED]
> and [EMAIL PROTECTED] to both be able to authenticate as "bob".
> In this case the domain information needs to be drawn
> from somewhere else. I'm mostly convinced at this point
> that until we are able to do name based virtual domains
> as in HTTP/1.1 or can do DNS queries on "mail.foo.com:imap"
> and get back both ip address and port information from
> the DNS server, the best answer is to use a FQEA as the
> login id.
This probably the best way to go. I remeber a email client once
( eudora???) that used [EMAIL PROTECTED] as the username to
mean connect to popserver.com use username person. If it
supported [EMAIL PROTECTED]@popserver.com I dont know.
Until someone writes the RFC it wont exist .....
( how do you get to write RFC I know in the past
you just did one but now ?)
--
Simon
