Kai,
You have a lot of reading to do in the archives. :-)
Your comments are based upon James v2 repositories, and we're looking at
replacing the user repositories with JNDI, and using JavaMail interfaces for
stores in James v3. And, yes, we'll have to implement optimized service
providers, as well as support the current formats.
Virtual hosting is something that still needs to be resolved, but it ought
to be in the context of the rest of what we're doing.
> Why do users need to have a unique name ?
> You could just request that they have a unique username / password hash
combination.
When e-mail comes in we need a unique mailbox. We don't need have their
password; we need a unique SMTP -> mailbox mapping. And what if two people
with the same name chose the same password? What do you do if someone loses
their password? You want a unique mailbox ID, although it does not have to
be their e-mail name.
> Give each user an unique numerical primary key, and create another table
> which just maps eMail Adresses to user-ids.
You might want to look at the JDBCVirtualUserTable mailet. Does that and
more, except we don't need a nuberical key. Non-numerical primary keys
aren't actually that bad, and we don't do much more than a straight lookup.
If we were doing a lot of database manipulation, I would agree with you.
FWIW, I'm hoping that in James v3 we will include hsqldb, so that we can
always assume the presence of a database, although there is a need to allow
some things to be in the file system if user want to configure it that way.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
