Thanks Philip, I will try this. And I apreciate your clarification
about the call to the exim at the point of the PIPE. It was some
confusing to me how the PIPE works.
On Wednesday, June 25, 2003, at 06:29 AM, Philip Hazel wrote:
> On Tue, 24 Jun 2003, Daniel Bendersky wrote:
>
>> BUT, doiong the TELNET to the localhost to see the debug, at the point
>> of the PIPE, the current exim process pass the message to a new
>> process
>> using the "command= /usr/sbin/exim -oMr spam-scanned -bS" so I lost
>> the
>> information, because the command call exim at the default port 25.
>
> You misunderstand the way Exim works. That call to Exim does not use
> TCP/IP at all. No port is involved. The daemon is not involved. It runs
> a completely new exim process and passes the message on the standard
> input.
>
> You might be able to add -d to that command, but that will work only if
> the calling process (the pipe transport) is running as an Exim admin
> user.
>
> If you want to see debugging from that command, why don't you just run
> it separately? Just run
>
> /usr/sbin/exim -oMr spam-scanned -bS -d
>
> with some suitable input file?
>
> Alternatively, add -odq to your command so that Exim queues the message
> without delivery. Then you can run a delivery with debugging turned on
> by using
>
> exim -d -M <message-id>
>
>
> --
> Philip Hazel University of Cambridge Computing Service,
> ph10@??? Cambridge, England. Phone: +44 1223 334714.
> Get the Exim 4 book: http://www.uit.co.uk/exim-book
>
>
>
>
--
Saludos....
Daniel Bendersky.
------------------------------------------------------------------
Daniel Bendersky Director de Operaciones y Tecnología
dbenders@??? http://www.netline.cl
NETLINE Av. Vitacura # 2939 of. 202
Oficina : +56 2 751 2600 Las Condes, Santiago - CHILE
Celular : +56 9 998 9122 Fax2mail : +56 2 751 2651
Voice2mail: +56 2 751 2618
"Success is a journey, not a destination"
------------------------------------------------------------------
