Hi, Has any thought been given into having a truly unique identifier for each message passing through James? We recently applied James to an email-proxy project in which we had to log each message when received and then change it's status once successfully forwarded or deemed unforwardable. Basically our problem was that when a message was received by James and then forwarded by our custom mailet (and thus re-entered into the pipeline but this time sent to the RemoteDelivery-mailet) there was no way of knowing which message is which during mail delivery.
At first we thought about using Message-ID for identifying each message but since it is only an optional header it can't exactly be called a fool-proof way of identifying messages. Also after looking at the RFC's we noticed that only the from, to and date headers are mandatory (?) and it's not possible to create a truly unique message identifier from these fields. We solved our problem by modifying SMTPHandler to add a custom header containing our own unique id read from a sequence. This solved our problem but unfortunately required us to make the modification (albeit a small one) into James. I was wondering if anybody has any thoughts on this or perhaps there is a way that we have overlooked that provides the solution to this problem? I guess one way would be to automatically generate the Message-ID header if it's missing, which I think some SMTP-servers do (?). How ever I'm not familiar enough with SMTP-servers in general to know if this is a valid solution or not. cheers, Ville Rinne -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
