Strange bounce message
Hi there, I'm using postfix 2.7.0-1ubuntu0.2 for our main MTA for our company. Last week my manager has send an email to everybody in the company at once. For some users the email bounced because of a quota limit they exceeded. This can be right, but not the bounce message. It said: Original Message Subject: Undelivered Mail Returned to Sender Date: Thu, 28 Mar 2013 16:15:36 +0100 (CET) From: mailer-dae...@brabantia.com (Mail Delivery System) To: robert.p...@brabantia.com This is the mail system at host webaccess.brabantia.com.I'm sorry to have to inform you that your message could notbe delivered to one or more recipients. It's attached below.For further assistance, please send mail to postmaster.If you do so, please include this problem report. You candelete your own text from the attached returned message. *The mail system d...@brabantia.com : host 129.50.20.41[129.50.20.41] said:* 552 5.2.2 dirk.moya...@brabantia.com Quota Exceeded (in reply to end of DATA command) Please read the cursive red line. d...@brabantia.com is not my mailsystem. This is the Zarafa server which use Postfix as MTA. This system checks teh LDAP auth with out Active Directory. I have another one: Original Message Subject: Undelivered Mail Returned to Sender Date: Thu, 28 Mar 2013 16:15:32 +0100 (CET) From: mailer-dae...@brabantia.com (Mail Delivery System) To: robert.p...@brabantia.com This is the mail system at host webaccess.brabantia.com.I'm sorry to have to inform you that your message could notbe delivered to one or more recipients. It's attached below.For further assistance, please send mail to postmaster.If you do so, please include this problem report. You candelete your own text from the attached returned message. *The mail system s.dewa...@brabantia.com : host 129.50.20.41[129.50.20.41] said:* 552 5.2.2 r.beer...@brabantia.com Quota Exceeded (in reply to end of DATA command) s.kers...@brabantia.com : host 129.50.20.41[129.50.20.41] said: 552 5.2.2 s.dewa...@brabantia.com Quota Exceeded (in reply to end of DATA command) Please see the cursive red line again. Same IP, other emailaddress. Actually this have to be a hostname. Just for your reference, our MTA (Postfix) is in our DMZ. The Zarafa-server (129.50.20.41) is in our trust zone. Why do we get this strange bounce message? If you need more info, please let me know. Kind regards, Roland de Lepper
Re: Strange bounce message
Roland de Lepper: This is the mail system at host webaccess.brabantia.com.I'm sorry to have to inform you that your message could notbe delivered to one or more recipients. It's attached below.For further assistance, please send mail to postmaster.If you do so, please include this problem report. You candelete your own text from the attached returned message. *The mail system a...@brabantia.com : host 129.50.20.41[129.50.20.41] said:* 552 5.2.2 ....@brabantia.com Quota Exceeded (in reply to end of DATA command) You have a strange text formatting problem. What Postfix sends is this: This is the mail system at host webaccess.brabantia.com. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system a...@brabantia.com: host 129.50.20.41[129.50.20.41] said: 552 5.2.2 ....@brabantia.com Quota Exceeded (in reply to end of DATA command) Please read the cursive red line. a...@brabantia.com is not my mailsystem. This is the Zarafa server which use Postfix as MTA. This system checks teh LDAP auth with out Active Directory. You have some intermediate software that removes all line breaks from the Postfix bounce message, making the text unreadable. Wietse
Re: Strange bounce message
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
Re: Strange bounce message
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
Re: Strange Bounce
On 4/24/2009, Vince Sabio (vi...@vjs.org) wrote: I'd rather not post information like that _pro forma_; if there's some subset of that information that might be of help in diagnosing this issue, then I'd be happy to post it. I realize that my reluctance to post the entire data set might limit the likelihood of getting to the bottom of this error. It will not just limit it, it will probably cause most everyone to totally ignire you. Oh... and its also extraordinarily silly... what exactly do you think you are protecting by refusing to post it? -- Best regards, Charles
Re: Strange Bounce
Charles Marcus wrote (on Fri, Apr 24, 2009 at 05:51:51AM -0400): On 4/24/2009, Vince Sabio (vi...@vjs.org) wrote: I'd rather not post information like that _pro forma_; if there's some subset of that information that might be of help in diagnosing this issue, then I'd be happy to post it. I realize that my reluctance to post the entire data set might limit the likelihood of getting to the bottom of this error. It will not just limit it, it will probably cause most everyone to totally ignire you. Oh... and its also extraordinarily silly... what exactly do you think you are protecting by refusing to post it? Perhaps his reluctance stems not from disclosing it, but from having it sit in archives forever, waiting to be scraped. With that in mind, would the denizens of this list mind posters supplying links to the necessary info, said links to vanish when the thread is over? That's what I'd like to do.
Strange Bounce
One of my users sent me the attached bounce (note: I've made some purely cosmetic changes to the bounce message, to remove the user's e-mail address and change FQDNs so that the server doesn't start getting spammed as a result of this posting -- but the content of the bounce has not been materially changed). It does not make sense to me ... the spool file no longer exists, but I cannot conceive of a reason why it would have two hard links (per the bounce message). None of the other spool files have multiple hard links. Is this a Postfix error? A known bug? An unknown bug? I am running Postfix v2.0.18 on FreeBSD v7.0. Any help/pointers greatly appreciated. Thanks, Vince Return-Path: Received: from hermes.mailbounce.net (71.126.154.133) by pop.hermes.vjs.org with ESMTP (Eudora Internet Mail Server 3.1.5) for user_address; Thu, 23 Apr 2009 02:52:24 -0400 Received: by hermes.mailbounce.net (Postfix) id 0D5074A6B4D; Thu, 23 Apr 2009 02:52:10 -0400 (EDT) Date: Thu, 23 Apr 2009 02:52:10 -0400 (EDT) From: mailer-dae...@hermes.mailbounce.net (Mail Delivery System) Subject: Undelivered Mail Returned to Sender To: user_address Auto-Submitted: auto-replied MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary=DD6454A6B4B.1240469530/hermes.mailbounce.net Message-Id: 20090423065210.0d5074a6...@hermes.mailbounce.net X-Antivirus: avast! (VPS 090423-0, 04/23/2009), Inbound message X-Antivirus-Status: Clean This is the mail system at host hermes.mailbounce.net. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system list-manag...@hermes.listmoms.net: cannot update mailbox /mail/postfix/spool/list-managers for user list-managers. file has 2 hard links Reporting-MTA: dns; hermes.mailbounce.net X-Postfix-Queue-ID: DD6454A6B4B X-Postfix-Sender: rfc822; user_address Arrival-Date: Thu, 23 Apr 2009 02:52:09 -0400 (EDT) Final-Recipient: rfc822; list-manag...@hermes.listmoms.net Original-Recipient: rfc822; list-manag...@hermes.listmoms.net Action: failed Status: 5.2.0 Diagnostic-Code: X-Postfix; cannot update mailbox /mail/postfix/spool/list-managers for user list-managers. file has 2 hard links
RE: Strange Bounce
-Original Message- From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] On Behalf Of Vince Sabio Sent: Friday, 24 April 2009 1:06 PM To: postfix-users@postfix.org Subject: Strange Bounce One of my users sent me the attached bounce (note: I've made some purely cosmetic changes to the bounce message, to remove the user's e-mail address and change FQDNs so that the server doesn't start getting spammed as a result of this posting -- but the content of the bounce has not been materially changed). It does not make sense to me ... the spool file no longer exists, but I cannot conceive of a reason why it would have two hard links (per the bounce message). None of the other spool files have multiple hard links. Is this a Postfix error? A known bug? An unknown bug? I am running Postfix v2.0.18 on FreeBSD v7.0. Any help/pointers greatly appreciated. Thanks, Vince While someone might have some immediate ideas, it'd be more helpful to post the relevant entries from the Postfix log, and the output of your postfix -n, as specified in the list welcome message. I'd also grep the postfix log for warning messages that might be related to the spool file. This all assumes you manage the hermes.mailbounce.net server.
RE: Strange Bounce
** At 13:17 +1000 on 04/24/2009, MacShane, Tracy wrote: From: owner-postfix-us...@postfix.org One of my users sent me the attached bounce (note: I've made some purely cosmetic changes to the bounce message, to remove the user's e-mail address and change FQDNs so that the server doesn't start getting spammed as a result of this posting -- but the content of the bounce has not been materially changed). It does not make sense to me ... the spool file no longer exists, but I cannot conceive of a reason why it would have two hard links (per the bounce message). None of the other spool files have multiple hard links. Is this a Postfix error? A known bug? An unknown bug? I am running Postfix v2.0.18 on FreeBSD v7.0. Any help/pointers greatly appreciated. While someone might have some immediate ideas, it'd be more helpful to post the relevant entries from the Postfix log, This seems to encompass the error (wrapping turned off): Apr 23 02:52:10 hermes postfix/qmgr[829]: DD6454A6B4B: from=user_address, size=1762, nrcpt=1 (queue active) Apr 23 02:52:10 hermes postfix/local[71190]: D9AC04A6B4A: to=list-manag...@hermes.listmoms.net, relay=local, delay=0.13, delays=0.11/0.02/0/0, dsn=2.0.0, status=sent (delivered to mailbox) Apr 23 02:52:10 hermes postfix/qmgr[829]: D9AC04A6B4A: removed Apr 23 02:52:10 hermes postfix/local[71191]: DD6454A6B4B: to=list-manag...@h/ca ermes.listmoms.net, relay=local, delay=0.16, delays=0.12/0.02/0/0.02, dsn=5.2.0, status=bounced (cannot update mailbox /mail/postfix/spool/list-managers for user list-managers. file has 2 hard links) Apr 23 02:52:10 hermes postfix/cleanup[71188]: 0D5074A6B4D: message-id=20090423065210.0d5074a6...@hermes.mailbounce.net Apr 23 02:52:10 hermes postfix/bounce[71193]: DD6454A6B4B: sender non-delivery notification: 0D5074A6B4D Apr 23 02:52:10 hermes postfix/qmgr[829]: 0D5074A6B4D: from=, size=3780, nrcpt=1 (queue active) Apr 23 02:52:10 hermes postfix/qmgr[829]: DD6454A6B4B: removed Apr 23 02:52:10 hermes postfix/smtp[71206]: 0D5074A6B4D: to=user_address, relay=mail.listmoms.net[71.126.154.132]:25, delay=0.13, delays=0.02/0.05/0.02/0.05, dsn=2.6.0, status=sent (250 2.6.0 message received OK) Apr 23 02:52:10 hermes postfix/qmgr[829]: 0D5074A6B4D: removed and the output of your postfix -n, as specified in the list welcome message. I'd rather not post information like that _pro forma_; if there's some subset of that information that might be of help in diagnosing this issue, then I'd be happy to post it. I realize that my reluctance to post the entire data set might limit the likelihood of getting to the bottom of this error. I'd also grep the postfix log for warning messages that might be related to the spool file. What you see above is it. __ Vince Sabio vi...@vjs.org
