getting sendmail to be more verbose/debugging

[semino...@my-deja.com]

Hi,

Couldn't find this in the FAQ. Apologies if it is there and I was too
dumb to see it.

I am trying to get sendmail, running in daemon mode, to be a bit more
verbose. I have written a delivery agent, but in certain cases, when
mail is sent through my MDA a signal 13 (broken pipe) is received by
the daemon and reported. I do a "I'm here" logging first thing in my
deliver agent (very solid/robust logging), but I never get that far. I
would like to see the exact call that sendmail is trying.

When I try a command line call to sendmail, I don't see any problems
when I use "-d". But -d doesn't seem to effect sendmail in daemon mode.

Any clues to help me debug, or get my sendmail daemon to be verbose
enough to diagnose this?

Mark

Sent via Deja.com http://www.deja.com/
Before you buy.

[Jim Davis]

In article <8shu43$qul$1...@nnrp1.deja.com>, <semino...@my-deja.com> wrote:
:
:I am trying to get sendmail, running in daemon mode, to be a bit more

:verbose. I have written a delivery agent, but in certain cases, when
:mail is sent through my MDA a signal 13 (broken pipe) is received by
:the daemon and reported. I do a "I'm here" logging first thing in my
:deliver agent (very solid/robust logging), but I never get that far. I
:would like to see the exact call that sendmail is trying.
:
:When I try a command line call to sendmail, I don't see any problems
:when I use "-d". But -d doesn't seem to effect sendmail in daemon mode.

For a roughly similar thing I ran

/path/to/sendmail -bD -v -d11.1

and then checked things out by 'telnet localhost smtp' and typing in
the SMTP commands to simulate receiving mail to my account. The '-bD'
runs sendmail in daemon mode but keeps it in the foreground, and the
-d11.1 shows more details about delivery.
--
Jim Davis <jda...@cs.arizona.edu>