[BarricadeMX] Archive

Lists Index Date Thread Search

Article: 28
From: Mike Bacher
Date: 2010-03-05 14:13:05 -0500
Subject: Re: Re: Re: Re: BMX log searching

Understood.  However, that is not the transaction-id I want -- what I want to 
see is this one:

Mar  5 13:11:40 mscan2 sendmail[14906]: o25JBbDk014895: to=<rws@soandso.com>, 
delay=00:00:03, xdelay=00:00:01, mailer=esmtp, pri=135822, relay=[x.x.x.x] 
[x.x.x.x], dsn=2.0.0, stat=Sent (1040517 message accepted for delivery)

The '1040517' is the message ID from my CommuniGate Pro host that we send 90% of 
our mail to once BMX scans it.  Right now, I have to go grep'ing through 
/var/log/maillog for this.

> That is not exactly true. If you're willing into put up with extra
> logging then you can have the sendmail transaction-id in a smtpf log line.
> 
> Using either verbose+=smtp (smtp session logging)
> 
> Mar  5 01:48:25 mx smtpf[27915]: m241mM279150001700 #483 route:snert.com
> << 250 2.0.0 o250mMb4030633 Message accepted for delivery
> 
> and/or verbose+=smtp-dot (response line at dot)
> 
> Mar  5 01:52:27 mx smtpf[27915]: m241qQ279150006600 #304
> domain=route:127.0.0.1 << 250 2.0.0 o250qQJS014992 Message accepted for
> delivery
> 
> You'll see that the sendmail transaction-id appears in the response sent
> to smtpf, which in turn is logged.
> 

-- 

------------------------------------------
Mike Bacher / mikeb@tulsaconnect.com
Director of Operations, TulsaConnect
Phone: 918-584-1100x110 Fax: 918-582-5776
Visit Tulsa's Best Internet Data Centers:
http://www.tulsaconnect.com/
------------------------------------------

Lists Index Date Thread Search