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=15517>. 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=15517 A unique message identifier Summary: A unique message identifier Product: James Version: 2.0a3 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: James Core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Currently there is no truly unique way to identify a message in James. Because the Message-ID header is optional it can't be relied on to be present at all times. A solution would be to create the Message-ID if it is not already present, another one would be to not use the Message-ID header at all but use a custom header or attribute in each mail received, containing a unique identifier generated in some manner. This problem manifests itself for example in a situation where James receives mail and forwards it to another address and you need to link these two events together (receiving the message and successfully sending it to another server) currently there is no way know which message is which (if you want to do logging where you log when a message is received and when it is successfully forwarded or returned to the sender as unforwardable). -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
