[exim-dev] [Bug 436] pipe logging from Exim Filter

Top Page
Delete this message
Reply to this message
Author: bug436
Date:  
To: exim-dev
Old-Topics: [exim-dev] [Bug 436] New: pipe logging from Exim Filter
Subject: [exim-dev] [Bug 436] pipe logging from Exim Filter
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

http://www.exim.org/bugzilla/show_bug.cgi?id=436





------- Comment #5 from ph10@??? 2007-03-21 10:26 -------
I have now had a good look at the code. I am afraid that what you ask is not
possible without a huge amount of work. What is logged is the command as
generated by a router or filter. (If the command is specified in the transport,
it does not appear in the log - the original address does.) The expansion
happens down in the transport's separate process - and what is more, it happens
argument by argument (as documented), not as one long line. The expanded
information is never passed back to the external delivery process. To achieve
what you want, the notional command line would (a) have to be re-constructed
from the internal argument list (and here there are potential problems with
quoting or not quoting), and (b) then a way of passing it back to the external
calling process would have to be implemented, and (c) then a way of using the
information for the logging would have to be created. All of this is a lot of
work for only a modest gain (IMO). I'm afraid I won't be doing this any time
soon. Sorry about that.

--
Configure bugmail: http://www.exim.org/bugzilla/userprefs.cgi?tab=email