Re: [exim] Testing pipe transport

am 2006-05-19 12:12 schrieb Tony Finch:
> On Thu, 18 May 2006, Peter Velan wrote:
>>
>> But now I need a combination of both: a locally injected "intest" which
>> is run through ACL, routers and transports. Is it possible?
>
> Sounds to me like you want to do a normal delivery with debugging turned
> on. -N tests the transport setup but not the delivery (i.e. in your case
> piping to a program).

You are right on this and its the actual way I'm doing testing now.

What I want to accomplish is this:

A robot sends a mail to exim, which target is a real external address.
Exim has to detect it as a special one (by means of ACLs) and routes it
to a perl script via pipe transport. My perl script creates a totally
new message and injects this locally to exim.

It works very well, but one thing should never happen (in the testing
phase): the message is not detected as special one and is delivered to
the original external address.

So what I want is this: inject message locally to exim with debugging
turned on and use eximtest.conf, but whatever happens, never deliver to
original real address, instead deliver to a local test account. For
sure, if - but only if! - after I made my job, then no message will
leave exim.

BTW: The mentioned injection of the new message by my perlscript always
targets a defined testing account, so there's no problem with this.

Peter