For some strange reason, using the pipe
command does not work as expected for me in Exim, and neither Google nor ServerFault has been able to provide a solution for this problem so far. :-(
I'm therefore switching over to searching for an alternative solution (a.k.a. workaround) instead, more specifically not explicitly using the pipe
command at all, which makes me seek the answer to the following new question instead:
How can I, using any available config method in Exim, make sure that incoming emails (including their complete contents such as headers, body etc) are sent to an external script on the same server (in my case, a Python script), in a similar fashion to what the pipe
command is supposed to do, but not using the pipe
command explicitly as I do in my other question?
My own primary suggestion so far is that I could configure a dedicated transport for this, similar to this one, and then just make it so that all incoming emails are routed through this transport? My problem is just that I currently don't know how to accomplish the "make it so that all incoming emails are routed through this transport" part, so any solutions to this simple sub question might actually also be a valid reply to this entire question(!).
Also, this other question is seemingly using something called a "smarthost" to redirect (copies of) incoming email to a certain transport, but I'm still lacking both a sufficient understanding and the complete config directives to make practical use of it, but a possible answer might use this too perhaps?
(and please include real Exim config file input in your reply, and assume I have no previous knowledge of neither any particular Exim nor SMTP terminology)