OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Meng Weng Wong (mengwongdumbo.pobox.com)
Date: Mon Oct 01 2001 - 23:01:27 CDT

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    I am trying to troubleshoot a very rare syndrome: a
    successful smtp delivery is normal in every respect except
    that the "to=<...>" line does not appear in the logs. This
    causes muttering and much consternation.

        Oct 1 18:32:43 smtpd[5423]: D0E793E640: client=localhost.localdomain[127.0.0.1]
        Oct 1 18:32:44 cleanup[4905]: D0E793E640: message-id=<004501c14ac7$78b4d9b0$1200a8c0gsicomp.on.ca>
        Oct 1 18:32:44 qmgr[4884]: D0E793E640: moving from incoming -> active
        Oct 1 18:32:44 qmgr[4884]: D0E793E640: from=<owner-freebsd-questionsFreeBSD.ORG>, size=3551, nrcpt=1 (queue active)
        Oct 1 18:32:44 qmgr[4884]: D0E793E640: deleting queue file under defer
        Oct 1 18:32:44 qmgr[4884]: D0E793E640: assigning recipients to delivery requests and closing messagefile.
        Oct 1 18:32:44 qmgr[4884]: D0E793E640: qmgr_deliver: attempting send request to transport=smtp, recipient=hamiltjexecpc.com
        Oct 1 18:32:44 qmgr[4884]: D0E793E640: qmgr_deliver finished writing to transport=smtp, recipient=hamiltjexecpc.com
        Oct 1 18:32:44 smtp[5398]: D0E793E640: handling request from owner-freebsd-questionsFreeBSD.ORG to hamiltjexecpc.com
        Oct 1 18:32:45 smtp[5398]: D0E793E640: communicating status 0 back to qmgr.
        Oct 1 18:32:45 qmgr[4884]: D0E793E640: qmgr_active_done starting
        Oct 1 18:32:45 qmgr[4884]: D0E793E640: deleting queue file under active
        Oct 1 18:32:45 smtp[5398]: D0E793E640: communicated status back to qmgr with errorcode 0. responsibility ends.
        Oct 1 18:32:45 qmgr[4884]: D0E793E640: all done. removed.

    I have been observing something like this roughly once in
    every 100,000 deliveries.

    Could tainted external input (eg. in the 250 response status
    text) cause the msg libraries to decline to print a msg_info()?

    I'm trying to rule out as much as possible before I blame
    syslogd. Under what conditions could the msg, vstring, and
    syslog libraries conspire to not print a line of output?
    Maybe the smtp server response is exceeding some buffer
    length? Any thoughts?

    -
    To unsubscribe, send mail to majordomopostfix.org with content
    (not subject): unsubscribe postfix-users