[exim-dev] [Bug 2339] New: message-id not logged for own bou…

Top Page
Delete this message
Reply to this message
Author: admin
Date:  
To: exim-dev
New-Topics: [exim-dev] [Bug 2339] message-id not logged for own bounces, [exim-dev] [Bug 2339] message-id not logged for own bounces, [exim-dev] [Bug 2339] message-id not logged for own bounces, [exim-dev] [Bug 2339] message-id not logged for own bounces, [exim-dev] [Bug 2339] message-id not logged for own bounces
Subject: [exim-dev] [Bug 2339] New: message-id not logged for own bounces
https://bugs.exim.org/show_bug.cgi?id=2339

            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
          Assignee: nigel@???
          Reporter: arekm@???
                CC: exim-dev@???


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

2018-11-21 19:13:39 1gPX0M-0005KP-Tq <= <> H=smtp.example.com [1.1.1.1]
P=esmtps X=TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256 CV=no K S=3044
id=E1gPX0M-0001Vq-K4@???

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
S=37268

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

--
You are receiving this mail because:
You are on the CC list for the bug.