Since I didn't see anyone else reply, I'll give it a shot:
- Is James recommened for production?
I, personally, am not ready to trust it for production, YET. But it is
getting close. I'd like to know of others' experiences, because I'd like to
put it in production this summer.
- Is there any limit on user accounts?
I use database repositories, and I am not aware of a James imposed
limit.
- Can user quotas be set in James
I don't know of any support for them at this time, but you could create
a UserOverQuota matcher that checked quotas. Why a matcher? So so that you
can use the ToProcessor mailet to control what happens to overquota'd mail.
Those are my opinions. YMMV. I'd certainly like to hear other views.
--- Noel
-----Original Message-----
From: mohan [mailto:[EMAIL PROTECTED]]
Sent: Saturday, May 25, 2002 1:57
To: [EMAIL PROTECTED]
Subject: James Scalability - Users Account countwise; User quota
management
Hi Dear James User List,
We are planning to use James for a website where lot
of users are expected to register.
In this context, i want to know whether James is
recommened in such production level environment. Is
there any limit on the number of user accounts with
James? Any case study in this regard is available?
Also i need one more clarification. Whether user quota
can be set in James? If so how can it be done?
Thanks and regards,
Mohan
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
