There are only two methods that integrate Mailet logging with James:
MailetContext.log(String);
MailetContext.log(String, Throwable);
At the moment, both of these log at the INFO level. The problem is that if
someone decides that they only want warnings and errors, then Mailet
Exceptions are lost. Unfortunately, the continued lack of proper log
support in the Mailet API means that Mailet authors have no control over
when log entries are recorded.
Entries like "ToProcessor: Sending mail
org.apache.james.core.MailImpl@177115 to transport" should arguably at
DEBUG. The RemoteDelivery mailet is especially verbose. Some of the
information is quite useful, other entries are not.
Currently we're stuck with this problem, so we have to pick a global
compromise between verbosity and lose of critical information. Until this
problem can be fixed, at the least exceptions thrown by a mailet should be
considered a warning, if not an error. True, some of them aren't, but we're
still stuck with a compromise, and better to assume that an exception is
important than to discard it.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
