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=16834>. 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=16834 smtpserver.log doesn't show Message-ID ------- Additional Comments From [EMAIL PROTECTED] 2003-02-13 08:53 ------- > Currently we log using Mail.getName(). That value is unique > for the message in James, and can be used for diagnostics. True, but it doesn't appear to be available to mailets; I'm now in the situation that, in DEBUG, smtpserver logs getName(); in production mode (INFO) it doesn't log even that much. Mailets can only log, say, Message-ID, which is thus rather difficult to correlate with SMTP transactions especially in high-volume situations or asynchrony (message sat in spool for a while, so the SMTP transaction and a mailet interaction are seperated in time). Correlation is thus difficult in development mode - where it's important - and near-impossible in production mode - where it's often critical. Most MTAs that I've worked with log the Message-ID in an SMTP transaction as a matter of course as INFO so that problems in production use with mail that's already moved can be traced. As it stands, there is no way to correlate what's in smtpserver.log with anything else, except where the sender+recipient combination happens to be unique (within the relevant scope - a particular morning for example). I acknowledge the architectural difficulty - that this would require smtpserver to parse the message or to depend upon something that did. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
