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 "René Cordier (Jira)" <se...@james.apache.org> on 2022/01/19 07:43:00 UTC

[jira] [Resolved] (JAMES-3704) Improve mail MDC on system edge

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

René Cordier resolved JAMES-3704.
---------------------------------
    Fix Version/s: 3.7.0
       Resolution: Done

> Improve mail MDC on system edge
> -------------------------------
>
>                 Key: JAMES-3704
>                 URL: https://issues.apache.org/jira/browse/JAMES-3704
>             Project: James Server
>          Issue Type: Improvement
>          Components: Remote Delivery
>    Affects Versions: master
>            Reporter: Karsten Otto
>            Priority: Minor
>             Fix For: 3.7.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> In general, James operators can easily track the processing of any given mail via the "mail" MDC field in the logs. However, there are two points where this information is not available:
>  # During initial message hooks and spooling, which marks the beginning of processing when the mail first enters James.
>  # During remote delivery, at the end of processing when the mail finally leaves James, since DeliveryRunnable works in a separate thread pool.
> For improved diagnostics, the "mail" MDC field should be available in these cases as well.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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