Hi, This is in regards to the 0301 patch, but I doubt that this has been changed since then. The behavior of qmail-send after being patched with qmail-ldap is compliant with the "Qmail-send bounce message format" specification. This happens whether you use the custombouncetext control file or not. Using the custombouncetext feature in it's current mode of operation has the potential to break ezmlm bounce processing. http://cr.yp.to/proto/qsbmf.txt is the reference. There is only supposed to be four paragraphs, each with one empty line between. The current behavior is that if you don't use control/custombouncetext then you see three blank lines between the first and the second paragraphs. --- Hi. This is the qmail-send program at ssh.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <[EMAIL PROTECTED]>: Sorry, no mailbox here by that name. (#5.1.1) --- Below this line is a copy of the message. Return-Path: <[EMAIL PROTECTED]> Received: (qmail 26207 invoked from network); 27 Jun 2001 19:51:57 -0000 Received: from unknown (HELO ssh.com) ([10.1.0.42]) (envelope-sender <[EMAIL PROTECTED]>) --- If you use control/custombouncetext then you see a blank line between the first paragraph and your custom bounce text. This is incorrect, and should be something like ******************* . Also, you see two blank lines after the custom bounce text instead of the required one line. --- Hi. This is the qmail-send program at ssh.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. This is a test, your message bounced. SSH Communications Security <[EMAIL PROTECTED]>: Sorry, no mailbox here by that name. (#5.1.1) --- Below this line is a copy of the message. Return-Path: <[EMAIL PROTECTED]> Received: (qmail 13017 invoked from network); 27 Jun 2001 16:05:09 -0000 Received: from unknown (HELO ssh.com) ([10.1.0.48]) (envelope-sender <[EMAIL PROTECTED]>) --- This is an example of a bounce using custom bounce text that is in compliance with DJB's specification: --- Hi. This is the qmail-send program at ssh.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. ************************************* This is a test, your message bounced. SSH Communications Security ************************************* <[EMAIL PROTECTED]>: Sorry, no mailbox here by that name. (#5.1.1) --- Below this line is a copy of the message. Return-Path: <[EMAIL PROTECTED]> Received: (qmail 13017 invoked from network); 27 Jun 2001 16:05:09 -0000 Received: from unknown (HELO ssh.com) ([10.1.0.48]) (envelope-sender <[EMAIL PROTECTED]>) --- The line of *'s between the default bounce text and the custom bounce text is because you can't start the line with a - character according to qsbmf. The line of *'s above and below the custom bounce text could be hard coded, I suppose. I noticed that the current behavior already strips newlines out of the middle of the control/custombouncetext file, which is good if it works in all situations otherwise it is still broken. Since this should be relatively easy to fix, and there are already far to many add on patches to the great patch we come here for, I will leave this as a bug report instead of a patch. Best regards, Mike Jackson
