Unexpected lmtpproxy response

Lawrence Greenfield leg+ at andrew.cmu.edu
Wed Dec 11 14:29:50 EST 2002

   From: "JP Howard" <jh_lists at fastmail.fm>
   Date: Wed, 11 Dec 2002 15:18:40 +0800

   On Wed, 11 Dec 2002 17:06:51 +1100, "Rob Mueller" <robm at fastmail.fm>
   > Every now and then, we see the following error in our logs:
   > Dec  6 22:29:20 www postfix/lmtp[15516]: 7319A58B2: to=<xyz>,
   > relay=/var/imap/socket/lmtpprox[/var/imap/socket/lmtpprox], delay=218,
   > status=bounced (host /var/imap/socket/lmtpprox[/var/imap/socket/lmtpprox]
   > said: 250 2.1.5 ok (in reply to DATA command))

I can't think of any obvious reason why this might happen. Due to the
lmtpengine abstraction, it should be pretty damn hard for it to be
sending the wrong number of error messages somewhere. But it's
possible there's a weird error path.

I think step #1 would be to try to get a protocol log. This is hard,
since it can be a lot of data.


More information about the Info-cyrus mailing list