Hi wietse, Thanks for your support. I know what to do now.
Regards, Roland de lepper Verstuurd vanaf mijn iPad Op 2 apr. 2013 om 15:53 heeft Wietse Venema <wie...@porcupine.org> het volgende geschreven: > In your second bounce message example, at the end of the DATA > command, the bounce message shows that server and client are out > of step. > > LINE BREAK HERE > > <s.dewa...@example.com>: host 129.50.20.41[129.50.20.41] > said:* 552 5.2.2 r.beer...@example.com Quota Exceeded (in > reply to end of DATA command) > > LINE BREAK HERE > > <s.kers...@example.com>: host 129.50.20.41[129.50.20.41] said: > 552 5.2.2 s.dewa...@example.com Quota Exceeded (in reply to > end of DATA command) > > LINE BREAK HERE > > I replaced the domain with "example". > > This shows two things: > > LINE BREAK HERE > > 1) Postfix uses the LMTP protocol to deliver mail to the remote > server at 129.50.20.41. Unlike SMTP this has one "end of data" > response per recipient. > > LINE BREAK HERE > > 2) The responses reveal that the remote LMTP server at 129.50.20.41 > is out of step with the Postfix LMTP client (replies for one > recipient are sent in place of another recipient). The Postfix > LMTP client code is 10+ years old. I therefore suspect bugs in > the remote remote LMTP server. You can demonstrate this with a > network sniffer (http://www.postfix.org/DEBUG_README.html#sniffer, > replace 25 with the port number that you use for LMTP) > > LINE BREAK HERE > > You may be able to prevent the "out of step" problem by turning off > PIPELINING support. > > LINE BREAK HERE > > /etc/postfix/main.cf: > > LINE BREAK HERE > > # Work around for buggy LMTP servers that mis-implement RFC 2920. > > LINE BREAK HERE > > lmtp_discard_lhlo_keywords = pipelining > > Wietse
