Aaron,
No worries. I'm glad that we're on the same page now.
When you log into the post office (POP3), you don't specify a domain, only a
login name. You might be assigned a login name like domain.user or even
user@domain. Each of these is just a convention to resolve name collision.
One might suggest that we could use the IP address to know which domain
we're serving. Something like:
<virtual IP>
<server>domain</server>
...
</virtual>
Few (if any) providers would be willing to waste an IP address per domain
for that purpose. It is not the same as using an IP address for each www
domain because of reverse DNS; generally an STMP server supports many
domains (located through the MX record).
--- Noel
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 29, 2002 17:31
To: James Users List
Subject: RE: Virtual hosting redux, smtp mapping, etc.
Ah ha! I am with you now. I am afraid that I tend to leap toward extremes
- either the minimum possible solution or the ultimate solution. What you
are proposing is something more of a happy medium.
Your mapping system certainly looks like it will work. I agree that it
does not seem like a significant design change, either. (More of a design
addition.) I do wonder, however, whether it might not be worth considering
a mechanism for separating multiple domains into multiple POP3 namespaces.
[EMAIL PROTECTED] and [EMAIL PROTECTED] would then map to two different
toms in two different user repositories.
Obviously, this would involve a more significant design change and may not
be worth the effort. Any thoughts?
ADK
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
