> I'm wondering about this too...
> Has anyone implemented virtual domain on James?
No, not yet, but I think that everyone is wondering how it could be done
a) without having to re-write almost every key component and
b) in the most useful way.
> I think it can be done.
There are three issues, as I see it
1/ virtual hosts will have to be name virtual hosts, because for mail and news, SMTP
in particular, it is not practical to try to use different ports, SMTP will pretty
much always look for SMTP on 25 and 25 only and how many casual users will understand
that their POP3 box isn't on 110?
2/ there are user namespace issues, should we, for instance, use account names which
are unrelated to email user names, or should we instead use user.host.domain.tld for
log-ins and inboxes.
3/ and finally should repositories be common to all vhosts for each service or should
vhosts each have seperate repositories, and even then the issue of SMTP auth and TLS
faces the same question.
Multiple instance of James running on diferent ports should be possible as far as I
can see, and perhaps port forwarding based on host name rules might be a quick win.
IMHO, danny.
>Serge, would you please explain this feature?
>
> Oki
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
