> we are using this stuff in real production
Many of us run JAMES in production and do not have the problem(s) you are
having.
> and we need tools for which we can find good support.
> As we are unable to find many people who actually understand James
> we do not feel we can support it adequately in a production environment.
You only posted configuration fragments, and removed information that might
have helped. There is plenty that the JAMES logs could provide to indicate
what is going on with your system, but we can't see any of that because you
don't want to post to an open list.
If volunteer support isn't adequate for your needs, I know of at least two
companies (full disclosure: one is mine) offering additional, fee-based,
support for JAMES. There may be others of which I haven't heard.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
