The Doctor: > > Just continuing > > ----- Forwarded message from Mail Delivery System > <mailer-dae...@doctor.nl2k.ab.ca> ----- > > X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on doctor.nl2k.ab.ca > X-Spam-Level: > X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham > version=3.3.1 > X-Original-To: postmaster > Delivered-To: postmas...@doctor.nl2k.ab.ca > Date: Fri, 23 Apr 2010 07:38:48 -0600 (MDT) > From: Mail Delivery System <mailer-dae...@doctor.nl2k.ab.ca> > To: Postmaster <postmas...@doctor.nl2k.ab.ca> > Subject: Postfix SMTP server: errors from idcmail-mo2no.shaw.ca[64.59.134.9] > > Transcript of session follows. > > Out: 220 doctor.nl2k.ab.ca ESMTP Postfix (2.8-20100323) > In: XXXX idcmail-mo2no.shaw.ca > Out: 402 4.5.2 Error: command not recognized > In: HELO idcmail-mo2no.shaw.ca > Out: 250 doctor.nl2k.ab.ca > In: MAIL FROM:<sender> > Out: 250 2.1.0 Ok > In: RCPT TO:<REcipient> > Out: 250 2.1.5 Ok > In: DATA > Out: 354 End data with <CR><LF>.<CR><LF> > Out: 451 4.3.0 Error: queue file write error > > Session aborted, reason: lost connection > > For other details, see the local mail logfile > > ----- End forwarded message ----- > > > And from a heavily debugged log
We need NON-VERBOSE logging that shows the ENTIRE MESSAGE LIFE CYCLE from SMTP port to final delivery. We do not need verbose logging. We do not need a fragment from the middle of the message's life cycle. Wietse