Matcher JAR is placed in /james_install/lib. Removing it from there causes a ClassNotFoundException in spoolmanager.log, so I know that is not the issue. No clues either in /log/phoenix.log or /temp/phoenix.console. /var/mail/error is also empty.
So, James manages to find the Matcher class OK...but that's it. Mails sent to accounts on localhost (I'm running the server in localhost only, for testing purposes) go through OK. But the matcher itself is not doing anything at all, or if it is it is not writing anything to any log as far as I can see. On 4/12/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
Dan Jacob ha scritto: > 1) By mailet.log, I of course meant the mailet.<timestamp>.log file. > This is still empty. > 2) The problem is that it fails before returning anything. As you can > see from the code, the log() call is made first before doing any > matching, so I should at least see that. I grepped all the logs in > /james-install/apps/james/logs and saw nothing. > 3) Same result with class="Null", or anything else. The point is that > the spoolmanager.log file does not show any errors on instantiation at > all. > 4) I am using OS X 10.4, but whether or not this is causing the > problem I have no idea due to the lack of debugging info. > > This only fails with custom matchers, but the problem is that I have > no way of debugging them, as the DEBUG setting has absolutely no > effect whatsoever. I have tried other log levels such as FATALERROR > and ERROR, to no avail. This is weird. Can you also check the jamespath/temp/phoenix.console file and the jamespath/log/* logs for exceptions? What james version are you using? Where do you place your own matcher? Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Dan Jacob --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
