The biggest one for me is that I have to start the server once before I do anything, because the files have to be expanded etc.
I tried to setup James 2.2 with the it.praxis Bayesian Spam stuff and it took me like 3-4 hours (even after reading the documentation) to get James to start and recognize the classes. I'm still pretty stressed about the whole CPU thing I went through recently so I don't want to spend too much time working on James right now (just trying to relax). Maybe sometime next week I'll put together a description of what I had to go through to get it working.
Kenny
boxed wrote:
Noel J. Bergman wrote:
Configuration for James is actually rather simple. It comes pretty much
configured for basic operation, and advanced stuff is fairly easy, too.
Much easier than sendmail, qmail, etc. I think that the problem you ran
into was because you didn’t realize the meaning of a file URL, which is
documented in the config.xml, by the way, and did MORE configuration than
you needed to do.
I disagree. Sure, there is little real config needed to do, but my real problem (and I suspect most new users problem) is that if I screw it up, it gives me 300 lines of total crap instead of just saying "you fucked up line x in this way". Try doing a nested XML comment in some place of config.xml by the way. It will give you a 300 line stack trace error _without telling you what line the error is on_.
The user experience from the first 10 minutes I spent on this product were totally horrible. If you intend to compete with commercial products (and I really hope you do) the end user experience must be taken into account.
Anders Hovmöller
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
