http://www.exim.org/bugzilla/show_bug.cgi?id=391
Summary: please consider allowing multiple log_selector
statements
Product: Exim
Version: 4.63
Platform: All
OS/Version: Linux
Status: NEW
Severity: wishlist
Priority: low
Component: Logging
AssignedTo: ph10@hermes.cam.ac.uk
ReportedBy: mh+exim-bugzilla@zugschlus.de
QAContact: exim-dev@exim.org
Hi,
it should be possible to have multiple log_selector statements in the
configuration. That way, one could say like
log_selector = currently_selected +tls_cipher +tls_peerdn
in the configuration part dealing with TLS to add tls_cipher and tls_peerdn to
the logging items that might be set at a different place in the configuration.
It should be possible to issue "absolute" and "relative" log_selectors, with
relative log_selectors taking what is already set and adding or subtracting to
it, and absolute selectors completely overriding what was set at a different
place.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
--
## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
Summary: please consider allowing multiple log_selector
statements
Product: Exim
Version: 4.63
Platform: All
OS/Version: Linux
Status: NEW
Severity: wishlist
Priority: low
Component: Logging
AssignedTo: ph10@hermes.cam.ac.uk
ReportedBy: mh+exim-bugzilla@zugschlus.de
QAContact: exim-dev@exim.org
Hi,
it should be possible to have multiple log_selector statements in the
configuration. That way, one could say like
log_selector = currently_selected +tls_cipher +tls_peerdn
in the configuration part dealing with TLS to add tls_cipher and tls_peerdn to
the logging items that might be set at a different place in the configuration.
It should be possible to issue "absolute" and "relative" log_selectors, with
relative log_selectors taking what is already set and adding or subtracting to
it, and absolute selectors completely overriding what was set at a different
place.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
--
## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##