https://bugs.exim.org/show_bug.cgi?id=2672
Bug ID: 2672
Summary: log_selector for QT exclusive of RT
Product: Exim
Version: 4.94
Hardware: All
OS: All
Status: NEW
Severity: wishlist
Priority: low
Component: Logging
Assignee: unallocated@exim.org
Reporter: jgh146exb@wizmail.org
CC: exim-dev@exim.org
Currently "queue time" as reported by QT includes the time taken to receive the
message. That means only data-transfer time, not including delays in ACL.
It can still be confusing.
We have a separate selector for "receive time" which logs (RT) the time from
the beginning of the DATA phase to just after the spool data file is finished
being written. The start point is the same as for QT; a subtract wouldn't be
hard.
Possibly we should use "QTx" rather than "QT" for the exclusive mode.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
Bug ID: 2672
Summary: log_selector for QT exclusive of RT
Product: Exim
Version: 4.94
Hardware: All
OS: All
Status: NEW
Severity: wishlist
Priority: low
Component: Logging
Assignee: unallocated@exim.org
Reporter: jgh146exb@wizmail.org
CC: exim-dev@exim.org
Currently "queue time" as reported by QT includes the time taken to receive the
message. That means only data-transfer time, not including delays in ACL.
It can still be confusing.
We have a separate selector for "receive time" which logs (RT) the time from
the beginning of the DATA phase to just after the spool data file is finished
being written. The start point is the same as for QT; a subtract wouldn't be
hard.
Possibly we should use "QTx" rather than "QT" for the exclusive mode.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##