You are viewing a plain text version of this content. The canonical link for it is here.

Posted to server-dev@james.apache.org by "Tellier Benoit (JIRA)" <ji...@apache.org> on 2019/01/09 03:03:00 UTC

[jira] [Resolved] (MAILBOX-366) Events should have an eventId

     [ https://issues.apache.org/jira/browse/MAILBOX-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tellier Benoit resolved MAILBOX-366.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.3.0

https://github.com/linagora/james-project/pull/2067 solved this

> Events should have an eventId
> -----------------------------
>
>                 Key: MAILBOX-366
>                 URL: https://issues.apache.org/jira/browse/MAILBOX-366
>             Project: James Mailbox
>          Issue Type: New Feature
>            Reporter: Tellier Benoit
>            Priority: Major
>             Fix For: 3.3.0
>
>
> Backed by a UUID randomly generated.
> This needs to be serialized and deserialized.
> Upon Listener execution, we need to pop eventId in the MDC. -> this can be used later on for correlation with the dead letter



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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