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
--------------------------------------------
There is no magic.
"Noel J.
Bergman" To: "James Users List"
<[EMAIL PROTECTED]>
<noel@devtech. cc:
com> Subject: RE: Virtual hosting redux, smtp
mapping, etc.
30/04/2002
07:51
Please respond
to "James
Users List"
> Your mapping system is certainly a more flexible/thorough solution, but
> would require a fair amount of code [than a simple mailet].
Actually, my proposal requires nothing more than a simple mailet and an
addition to the user admin code.
> isolating the POP3 user namespace of one virtual domain from other
> virtual domains is a difficult task.
There is no notion of virtual domains in the Post Office Protocol (POP3).
But that does not mean that a single post office is capable of storing
messages addressed to only a single domain.
> A mapping system between rfc822 addresses and POP3 mailbox names
> is not going to achieve that isolation.
I am not trying to isolate POP3 name spaces. For a given POP3 server,
there
is only one name space. I'm simply trying to handle RFC822 addresses for
multiple domains, which is otherwise broken in James.
> How will you deal with the instance where you have
> "[EMAIL PROTECTED]" and "[EMAIL PROTECTED]"?
user tom-smith
user tom-jones
map [EMAIL PROTECTED] tom-smith[@localhost]
map [EMAIL PROTECTED] tom-jones[@localhost]
Or some other suitable example. The point is that each user knows the name
of the mailbox, and the server knows how to map from the domain name space
to the post office name space.
> the POP3 protocol expects that each POP3 server defines it
> own namespace
I don't know why you perceive that I've said otherwise.
> In order to achieve your virtual hosting requirements, you would need to
> have one IP address for each POP3 namespace.
Why do you keep talking about separate POP3 name spaces? Is this some
preconceived notion that you have? You appear to be reading something from
my messages that simply isn't there.
I am talking about mapping to the singular, server-specific, POP3 name
space
from rfc822 addresses (domain specific name spaces). The issue is message
delivery (simple mail TRANSPORT protocol), not reading mailboxes (Post
Office Protocol).
> A futher point to note is that not all JAMES users use an RDBMS for their
> UserRepository. Will this work with the file based system?
Yes, of course. :-)
In fact, one reason for the addition to the user admin code is that not
everyone uses JDBC. Otherwise, we could do administration by simply
managing the server tables directly.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]
>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]
>
-----------------------------------------------------------------------------------------------
Have you seen our website?.... http://www.vodafone.co.nz
CAUTION: This correspondence is confidential and intended for the named recipient(s)
only.
If you are not the named recipient and receive this correspondence in error, you must
not copy,
distribute or take any action in reliance on it and you should delete it from your
system and
notify the sender immediately. Thank you.
Unless otherwise stated, any views or opinions expressed are solely those of the
author and do
not represent those of Vodafone New Zealand Limited.
Vodafone New Zealand Limited
21 Pitt Street, Private Bag 92161, Auckland, 1020, New Zealand
Telephone + 64 9 357 5100
Facsimile + 64 9 377 0962
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
