Here's an update to my problems... First, thanks to Kenny for helping (offline) as he answered a lot of the questions I had.
I started fresh and was able to get the system running very easily (at least SMTP/POP3). The main problem here was I wasn't aware I had to run James once (bin\run.bat) and then shut it down and edit some xml files that it created on the first run (that was really strange, and IMHO needs to be changed to some setup script or something). Once I got past that, James was accepting email for local users just fine. The other issue, was that I wanted to create my own matcher/mailet and wanted to be able to debug everything through IDEA, I assumed that if I downloaded just the "SRC" version, and got it to compile through IDEA, I could run it. Well that is possible, but with Phoenix in the picture, it's not as straightforward as it looks. >From just looking at the mailet concept, it seems like a very extensible, and easy way for someone to add on conditional (matcher) functionality). It turned out that while it was extensible, the only way I could get it to work was to add my own classes (which I initially had in a separate com/company package) inside James itself and build it along with James. Once I did that, I could get my matchers/mailets to work. Since a lot of what I want to do isn't related to James (I just need the email), this forces me to simply create a new package/class and have my mailet call that. Kind of a waste of a class (i.e. mailet), but it seems like the only way to do it right now. I hope all this makes sense. Feel free to reply if there are any questions... Again, thanks to all who have helped (so far :) ). -----Original Message----- From: Kenny Smith [mailto:[EMAIL PROTECTED]] Sent: Monday, December 09, 2002 12:13 PM To: James Users List Subject: Re: Back to square one with James Hi Noel, When I read his messages, I immediately understood his problem because I just went through it. There wasn't a specific question, it was more of "I really have no idea where to begin" stage. There is documentation on how to install and configure james at first, but I think its missing that little bit of "total dummy" information that I certainly needed when first starting. I've been trying to find time to write up a kick start type document for the clueless like me, but I'm sure you understand how hard it is to find time to do anything extra. :) The good news is though that I believe we've gotten him to a working state! :) Kenny Smith JournalScape.com Noel J. Bergman wrote: > Kenny, > > We don't really know what the problem is, yet. Since his initial post, he > has not replied to any message, so we don't know what progress has/hasn't > been made. It may simply be that he has yet to go through config.xml. > Since you've been talking with him, you may have a better idea of what has > and hasn't been done, and what is and isn't working. > > One thing that would be useful would be to change all of the log types to > DEBUG from INFO until James is working, and then change them back. > > --- Noel > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
