You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Serge Knystautas <se...@lokitech.com> on 2002/03/22 20:29:30 UTC
Re: Virtual Domain Specific Users?
Mike wrote:
> I've been looking through the docs and the archive and have not found this question: If I have a box with a single static IP hosting three virtual domains (a.com, b.com, c.com), can I specify that a user belongs to a specific domain? I don't want all users to belong to all domains, just one.
>
> Thanks,
> Mike
>
The problem is POP needs to have unique user names since it does not
support virtual domains. So from an administrative perspective, the
trick is allowing the server to understand that you're working with the
"domain1.com" list of users, so then I can just think of "joesmith" as a
username. Then Joe would need to be told his username was
joesmith.domain1, or something like that. There have been several
proposals, but there hasn't been consensus, and not enough developer
cycles to just pick a decent one and implement/add it yet.
Serge Knystautas
Loki Technologies - Unstoppable Websites
http://www.lokitech.com/
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Virtual Domain Specific Users?
Posted by Serge Knystautas <se...@lokitech.com>.
Like Danny said, the biggest slowdown is from the lack of time of the
volunteers. There have been more significant conversations about the
challenges of virtual domains (search the archives for 'virtual domains'
in james-dev and james-user and you'll see about 60 messages spread
across the past 1.5 years).
It is a top priority, but it's not a simple change, and the patches in
the fall were not very elegant (in my opinion)... they avoided making
some more fundamental changes that are really necessary to support
virtual domains. They're fine patches if you need that in the short
term, so maybe we should include it as an optional download or
unsupported patch. I still have the emails in my inbox to hopefully get
to at some point. Incidentally, I'm supporting 5 domains on my James
server so I definitely would like a better way to approach it than have
to do my manually remember to add ".domain" to each user name and give
users the appropriate instructions.
If you've got the time to start a new project, I'd encourage you to try
to channel that energy towards the James project. I think there's a lot
of good code here and the cooperation will benefit everyone.
Serge Knystautas
Loki Technologies - Unstoppable Websites
http://www.lokitech.com/
Blas Rodriguez Somoza wrote:
> Hello
>
> I don't aggre. What seems to happen is that the people that actually
> develop James are interested in a personal mail server and not in a
> multidomain server. There is only two messages in September 2001 what can be
> called a discussion about multidomain in the last year. I implement
> multidomain some time ago and send it to the list but after that there is no
> answer.
>
> I understand that this is a change difficult to do because it affects
> several classes in the code, but without it James is only usable as a single
> domain server, what is enough for some people but not for all.
>
> Perhaps it is better to look for other server or start a new project.
>
> Regards
> Blas Rodriguez Somoza
>
> ----- Original Message -----
> From: "Serge Knystautas" <se...@lokitech.com>
> To: "James Users List" <ja...@jakarta.apache.org>
> Sent: Friday, March 22, 2002 8:29 PM
> Subject: Re: Virtual Domain Specific Users?
>
>
>
>>Mike wrote:
>>
>>>I've been looking through the docs and the archive and have not found
>>
> this question: If I have a box with a single static IP hosting three
> virtual domains (a.com, b.com, c.com), can I specify that a user belongs to
> a specific domain? I don't want all users to belong to all domains, just
> one.
>
>>>Thanks,
>>>Mike
>>>
>>
>>The problem is POP needs to have unique user names since it does not
>>support virtual domains. So from an administrative perspective, the
>>trick is allowing the server to understand that you're working with the
>>"domain1.com" list of users, so then I can just think of "joesmith" as a
>>username. Then Joe would need to be told his username was
>>joesmith.domain1, or something like that. There have been several
>>proposals, but there hasn't been consensus, and not enough developer
>>cycles to just pick a decent one and implement/add it yet.
>>
>>Serge Knystautas
>>Loki Technologies - Unstoppable Websites
>>http://www.lokitech.com/
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Virtual Domain Specific Users?
Posted by Danny Angus <da...@thought.co.uk>.
> I don't aggre. What seems to happen is that the people that actually
> develop James are interested in a personal mail server and not in a
> multidomain server. There is only two messages in September 2001
> what can be
> called a discussion about multidomain in the last year. I implement
> multidomain some time ago and send it to the list but after that
> there is no
> answer.
>
> I understand that this is a change difficult to do because it affects
> several classes in the code, but without it James is only usable
> as a single
> domain server, what is enough for some people but not for all.
In some respects you are right, it is indeed enough for many people that
James serve a single userbase.
However it is not true that "the people that actually develop James are
interested in a personal mail server and not in a multidomain server". In
fact adding virtual host support to James has been discussed a number of
times since september, and is understood to be a key goal.
The fact that it is suffering from lack of progress is largely due to the
fact that most of the developers of James are unable to make significant
commitments of their time at the moment.
The two Simple schemes for multiple domains which have been proposed do not
fully implement the functionality true virtual hosts would have (completely
seperate mailet processes, binding to different IP addresses for instance)
and both fall foul of the naming convention problem.
Personally I believe that naming conventions in any application are the last
resort. A true solution shouldn't restrict the variety of names that can be
used, and that a better solution is possible in this case.
d.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Virtual Domain Specific Users?
Posted by Blas Rodriguez Somoza <bl...@puertareal.com>.
Hello
I don't aggre. What seems to happen is that the people that actually
develop James are interested in a personal mail server and not in a
multidomain server. There is only two messages in September 2001 what can be
called a discussion about multidomain in the last year. I implement
multidomain some time ago and send it to the list but after that there is no
answer.
I understand that this is a change difficult to do because it affects
several classes in the code, but without it James is only usable as a single
domain server, what is enough for some people but not for all.
Perhaps it is better to look for other server or start a new project.
Regards
Blas Rodriguez Somoza
----- Original Message -----
From: "Serge Knystautas" <se...@lokitech.com>
To: "James Users List" <ja...@jakarta.apache.org>
Sent: Friday, March 22, 2002 8:29 PM
Subject: Re: Virtual Domain Specific Users?
> Mike wrote:
> > I've been looking through the docs and the archive and have not found
this question: If I have a box with a single static IP hosting three
virtual domains (a.com, b.com, c.com), can I specify that a user belongs to
a specific domain? I don't want all users to belong to all domains, just
one.
> >
> > Thanks,
> > Mike
> >
>
> The problem is POP needs to have unique user names since it does not
> support virtual domains. So from an administrative perspective, the
> trick is allowing the server to understand that you're working with the
> "domain1.com" list of users, so then I can just think of "joesmith" as a
> username. Then Joe would need to be told his username was
> joesmith.domain1, or something like that. There have been several
> proposals, but there hasn't been consensus, and not enough developer
> cycles to just pick a decent one and implement/add it yet.
>
> Serge Knystautas
> Loki Technologies - Unstoppable Websites
> http://www.lokitech.com/
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Virtual Domain Specific Users?
Posted by Serge Knystautas <se...@lokitech.com>.
Thanks Jeff... this looks basic enough that I can just take this, add
some information on how you manage the user accounts accordingly, and
make it into a mini HOWTO page for the James website. Then while we
sort out how to modify James to more readily support virtual domains, we
can at least provide some instructions.
Serge Knystautas
Loki Technologies - Unstoppable Websites
http://www.lokitech.com/
Jeff Keyser wrote:
> I've been able to tackle this problem in my environment using current James
> code, though it requires maintaining the config.xml file when you add/remove
> users. It's not a code-only solution, but it seems to work.
>
> I picked one domain as the "primary domain" that will hold all the
> mailboxes. I then wrote rules into config.xml to handle the other domains,
> and forward e-mail to this one domain. For me, this works really well
> because my primary domain is only used locally, and is not advertised for
> public e-mail addresses. Assuming I picked "a.com" as the main domain and
> also host domains "b.com" and "c.com," here are the interesting parts of
> config.xml:
>
> <servernames autodetect="FALSE">
> <!-- Note: Only the primary domain is needed -->
> <servername>a.com</servername>
> </servernames>
>
>
> <processor name="transport">
> <mailet match="HostIs=b.com" class="ToProcessor">
> <processor>b.com</processor>
> </mailet>
> <mailet match="HostIs=c.com" class="ToProcessor">
> <processor>c.com</processor>
> </mailet>
> <mailet match="RecipientIsLocal" class="LocalDelivery"/>
> <mailet match="HostIsLocal" class="ToProcessor">
> <processor>error</processor>
> </mailet>
> <mailet match="All" class="RemoteDelivery">
> <!-- Wherever you normally put outgoing messages -->
> </mailet>
> </processor>
>
> <processor name="b.com">
> <mailet match="UserIs=User1" class="Forward">
> <forwardto>User1@a.com</forwardto>
> </mailet>
> <!-- Add one entry per user in domain -->
> <mailet match="All" class="ToProcessor">
> <processor>error</processor>
> </mailet>
> </processor>
>
> <processor name="c.com">
> <mailet match="UserIs=User2" class="Forward">
> <forwardto>User2@a.com</forwardto>
> </mailet>
> <!-- Add one entry per user in domain -->
> <mailet match="All" class="ToProcessor">
> <processor>error</processor>
> </mailet>
> </processor>
>
> Maybe this will work for your environment, but if it doesn't, hopefully
> it'll spark a similar idea.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Virtual Domain Specific Users?
Posted by Jeff Keyser <JK...@telocity.com>.
I've been able to tackle this problem in my environment using current James
code, though it requires maintaining the config.xml file when you add/remove
users. It's not a code-only solution, but it seems to work.
I picked one domain as the "primary domain" that will hold all the
mailboxes. I then wrote rules into config.xml to handle the other domains,
and forward e-mail to this one domain. For me, this works really well
because my primary domain is only used locally, and is not advertised for
public e-mail addresses. Assuming I picked "a.com" as the main domain and
also host domains "b.com" and "c.com," here are the interesting parts of
config.xml:
<servernames autodetect="FALSE">
<!-- Note: Only the primary domain is needed -->
<servername>a.com</servername>
</servernames>
<processor name="transport">
<mailet match="HostIs=b.com" class="ToProcessor">
<processor>b.com</processor>
</mailet>
<mailet match="HostIs=c.com" class="ToProcessor">
<processor>c.com</processor>
</mailet>
<mailet match="RecipientIsLocal" class="LocalDelivery"/>
<mailet match="HostIsLocal" class="ToProcessor">
<processor>error</processor>
</mailet>
<mailet match="All" class="RemoteDelivery">
<!-- Wherever you normally put outgoing messages -->
</mailet>
</processor>
<processor name="b.com">
<mailet match="UserIs=User1" class="Forward">
<forwardto>User1@a.com</forwardto>
</mailet>
<!-- Add one entry per user in domain -->
<mailet match="All" class="ToProcessor">
<processor>error</processor>
</mailet>
</processor>
<processor name="c.com">
<mailet match="UserIs=User2" class="Forward">
<forwardto>User2@a.com</forwardto>
</mailet>
<!-- Add one entry per user in domain -->
<mailet match="All" class="ToProcessor">
<processor>error</processor>
</mailet>
</processor>
Maybe this will work for your environment, but if it doesn't, hopefully
it'll spark a similar idea.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>