DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16833>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16833 smtpserver.log often doesn't show "error" events [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2003-02-06 16:45 ------- > Only 2 of the ~90 errors appeared in smtpserver.log at all; > at first blush (until I found var/mail/error), they had > simply dissappeared. Thank you for your efforts. :-) This particular report illustrates a misconception of how the James pipeline works, and where things are logged. Apparently, these messages were properly handled by smtpserver, and somewhere in the pipeline a matcher decided to dump them into te error spool (probably mis-addressed). Changing the spoolmanager and mailet logs to DEBUG from INFO in SAR- INF/environment.xml will log the path taken by each message through the pipeline, and should indicate what caused each message to end up in the error spool. I am closing this reports on the grounds that it doesn't indicate a defect. If there turn out to be specific defects in the code, please do open reports for them. Thank you, again. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
