Bug ID: 2339
           Summary: message-id not logged for own bounces
           Product: Exim
           Version: 4.91
          Hardware: x86
                OS: All
            Status: NEW
          Severity: bug
          Priority: medium
         Component: Logging

If exim gets message from remote server then it logs Message-Id nicely:

2018-11-21 19:13:39 1gPX0M-0005KP-Tq <= <> []
P=esmtps X=TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256 CV=no K S=3044

but if it generates own message - bounce then it doesn't log message-id even if
is is there (recipient of the bounce sees Message-id in headers):

2018-11-20 13:00:25 1gP4hc-00044Y-Mq <= <> R=1gP4hY-000445-6t U=exim P=local

Would be consistent to log it in bounce case, too (if it is available at that

You are receiving this mail because:
You are on the CC list for the bug.
## List details at Exim 
details at ##

Reply via email to