Noel behind the guru of James scalability, you probably have the most about of data to support this. We could start with Hut's questions on James' user and add a few extra:
Q: How long has James been running in production? A: Since 1999.
Q: How stable is James? On a suitable server does it crash once a week, month, or never?
A (Kenny's): I've been running my James install for about 5 months and I found it not running only one time. I don't know if it was James or badness on my server that caused it to die, but regardless, it's very stable.
Q: How many messages can James handle before it experiences lag or buffer overload? Could it handle a T1 line with incoming messages?
A: <Noel, could you add stats on the battery of tests you run?>
Q: Has anyone had any problem incorporating custom Mailets into the server or experienced any unusual problem with database connections?
A: <Yes, it is difficult to add custom mailets. See the tutorial [here]. Database connection code is getting reworked and will not survive a database outage.>
Q: Is there a published list of corporate users that anyone knows about?
A: <Hmmm... maybe start compiling a list? Send an email out to james-user and start collecting and publishing names?>
Q: Would you recommend James (version 2.1.3) as a production, scalable MTA? A: Yes.
Other questions?
-- Serge Knystautas President Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
