james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Closed: (JAMES-71) A unique message identifier
Date Sun, 06 Jun 2004 21:19:53 GMT

   The following issue has been closed.

View the issue:

Here is an overview of the issue:
        Key: JAMES-71
    Summary: A unique message identifier
       Type: Bug

     Status: Closed
 Resolution: INCOMPLETE

    Project: James
             James Core

   Reporter: Ville Rinne

    Created: Thu, 19 Dec 2002 8:46 AM
    Updated: Sun, 6 Jun 2004 2:18 PM
Environment: Operating System: Other
Platform: Other

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).

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message