[prev in list] [next in list] [prev in thread] [next in thread] 

List:       java-apache-james
Subject:    Re: Virtual Domains on James
From:       Charles Benett <charles () benett1 ! demon ! co ! uk>
Date:       2001-01-24 9:58:12
[Download RAW message or body]

Serge Knystautas wrote:
> 
> ----- Original Message -----
> From: "Michael Wyraz" <evermind@wyraz.de>
> 
> > On Tue, 23 Jan 2001 12:02:43 -0500, Serge Knystautas wrote:
> > maybe there should be a possibility to make both. aliases and long names.
> if you have (like we do)
> > some hundred domains, it's almost impossible to mak an alias for each user
> :-/
> 
> Sorry, I meant aliases for the domain names.  So microsoft.com is aliased to
> ..ms and apache.org is aliased to .apache.  Then milo@microsoft.com becomes
> mile.ms (etc..).
> 
> The delimiter character seems to be something we have to resolve.  I think a
> single dot would work (that's what we use), but it's harder to prevent
> username collisions then.

I think it probably need to be configurable by the admin.

> 
> > i thougth the whole day about that problem. my conclusion is, that we
> don't need to make a
> > user rep. for each domain if the domain could be part of the username.
> more for that written below...
> 
> Sounds good, although I think it would be nice if we could.
> 
> > here my thougths for that (and some questions for implementing):
> >
> > 1. UsersRepository
> > a username consists of "user@domain.com". there are special VHost User
> > Repositories (how can be set which UserRepository classes are known by
> > james? i found no config option for that?). or the existing UserRep's are
> changed
> > (can UserRepositories, Mailets and Matchers access the configuration?).
> > I Think it's better to modify the existing for file rep. and make a new
> for database rep.
> > This change includes:
> > * a new Configuration Parameter "EnableVirtualHosting"
> > * a parameter for specifying valid seperator chars/strings between the
> username and the host part
> > * the new ep. implements a new column containing the domain part of the
> username.
> > *if virtual hosting is enabled the method "public boolean test(String
> name, Object attributes)" of the UsersRepository
> > matches all variants of username+valid seperator+host
> 
> I don't think you want to change UsersRepository... you just want to change
> the way the local account(s) user repository works.  What about the idea of
> a "roll-up" repository... a user repository that wraps multiple other user
> repositories?  I'm just making this up as I go.

You mean a UsersStore - which is where the cvs version was evolving. But
we do need to make changes so that people can reset passwords, etc.
Seperate mail enroute.

> 
> > 2. MailServer.getUserInbox
> > should now return for user "user@domain.com" (if EnableVirtualHosting is
> true):
> > [path to inbox]/domain.com/user/ (i think you know what i mean ;-)
> 
> If you map names from any domain to a unique username (so that the telnet
> app doesn't do anything special), then you don't have to do anything special
> here.
> 
> > 3. Mather: UserIs
> > if EnableVirtualHosting is true it should have the same behavior as
> ReceipientIs.
> > Alternatively one who uses Virtual Hosting has to use Reciepient is
> instead of UserIs.
> 
> I don't think you want to change how things work based on such a meta
> setting.  I think if you as an admistrator want RecipientIs, you should use
> RecipientIs.  If you want UserIs, you should use UserIs.  The
> RecipientIsLocal matcher might need to change a bit though.
> 
> > but there's another thing that would be usefull in this case:
> > Domains (aka ServerNames) are currently configured in the xml config.
> > for virtual domains it would be much better if there were a (maybe
> aditional) DomainsRepository
> > which could be implemented with town. So there's no need to restart for
> adding a domain and it's users.
> 
> I'm not sure exactly how this would work.  Could you explain some more?
> 
> Serge Knystautas
> Loki Technologies
> http://www.lokitech.com/
> 
> ------------------------------------------------------------
> To subscribe:        james-on@list.working-dogs.com
> To unsubscribe:      james-off@list.working-dogs.com
> Archives:  <http://www.mail-archive.com/james%40list.working-dogs.com/>
> Problems?:           jons@apache.org


------------------------------------------------------------
To subscribe:        james-on@list.working-dogs.com
To unsubscribe:      james-off@list.working-dogs.com
Archives:  <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?:           jons@apache.org

[prev in list] [next in list] [prev in thread] [next in thread]