[exim-dev] [Bug 2339] message-id not logged for own bounces

2019-02-17 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2339 Jeremy Harris changed: What|Removed |Added Assignee|ni...@exim.org |jgh146...@wizmail.org Status|NEW

[exim-dev] [Bug 2339] message-id not logged for own bounces

2019-01-01 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2339 --- Comment #3 from Jeremy Harris --- Fix for consideration: https://bugs.exim.org/attachment.cgi?id=1164 -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[exim-dev] [Bug 2339] message-id not logged for own bounces

2019-01-01 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2339 Jeremy Harris changed: What|Removed |Added See Also||https://bugs.exim.org/show_ |

[exim-dev] [Bug 2339] message-id not logged for own bounces

2019-01-01 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2339 Jeremy Harris changed: What|Removed |Added Severity|bug |wishlist --- Comment #2 from Jeremy Harris ---

[exim-dev] [Bug 2339] message-id not logged for own bounces

2018-11-21 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2339 Jeremy Harris changed: What|Removed |Added See Also||https://bugs.exim.org/show_ |

[exim-dev] [Bug 2339] message-id not logged for own bounces

2018-11-21 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2339 --- Comment #1 from Arkadiusz Miskiewicz --- My use case was: trying to find out if bounce was delivered to remote system and the message was relayed via few servers. Much easier (check only destination server would be enough) to track by message-id