Is there any way you can investigate why the latest version is running for you? I was running a build just before 2.0a since January without a single crash and as of a few days ago am running a build just before 2.0a3 (hopefully made this weekend).
Final release is a bit unclear... I think the latest rounds of patches have cleaned up a number of minor issues. We're looking to upgrade the version of Avalon we're running on to some final releases, but hopefully we're getting close to that. IMAP... this is my next objective. I haven't had a lot of time to work on James and it has been focused mainly on stability/usability issues. However, I would really really like to use James for IMAP and will start turning my attention to that feature. Remote admin... what I just wrote up in the todo list is to add a few remote admin features, and then turn that into an object (perhaps to expose for RMI... I believe someone else submitted a proposal for this but I haven't looked that implementation). Then the telnet interface would just make calls to this new logic remote admin object. This should be easier than what you had to write in interfacing with a human-readable text telnet session. -- Serge Knystautas Loki Technologies - Unstoppable Websites http://www.lokitech.com/ Daniel Herlemont wrote: > >>Which version of James are you using? I would guess it's 1.2.1. Can >>you try to use the latest 2.0a2? > > > it was the latest version .. but I shall confess .. this was my fault since > I > deleted the james.sar file just after deployement. I thought that all filles > were deployed under the james directory but this was not the case. > > In any case, the latest version seems quite unstable, and disapear/crashes > from time to time. I have to restart the server quite often : 2 or 3 times a > day .. is it a known issue ? > > >>We are also preparing to make an >>alpha3 release shortly. > > great > > is there some planning for : > - a final release > - IMAP provider > - remote admin > > BTW I developed a very simple java wrapper of telnet admin commands ... > if anybody interested, I post it hereafter ... > this is crude, simple ... and not so clean .. because it rely on text > input/ouput that may change in future version > but it works ... -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
