{"thread":{"id":"25025","subject":"Re: [PATCH] post-receive-email: ensure sent messages are not empty","startedAt":"2010-09-07T19:04:31Z","lastAt":"2010-09-07T19:04:31Z","messageCount":1,"participants":["Kevin P. Fleming"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"150240","messageId":"4C868CBF.6040903@digium.com","threadId":"25025","inReplyTo":"1283886126-4005-1-git-send-email-kpfleming@digium.com","subject":"Re: [PATCH] post-receive-email: ensure sent messages are not empty","fromName":"Kevin P. Fleming","fromEmail":"kpfleming@digium.com","sentAt":"2010-09-07T19:04:31Z","receivedAt":"2010-09-07T19:04:31Z","isPatch":true,"sender":{"key":"kpfleming@digium.com","avatar":null},"body":"On 09/07/2010 02:02 PM, Kevin P. Fleming wrote:\n> Changes the logic in the script to determine whether an email message\n> will be sent before invoking the send_mail() function; otherwise, if\n> the logic determines that a message will not be sent, send_mail() will\n> cause an empty email to be sent. In addition, ensures that if multiple\n> refs are updated and a message cannot be sent for one of them,\n> the others are still processed normally.\n> \n> Signed-off-by: Kevin P. Fleming <kpfleming@digium.com>\n\nJust bringing this one back to the list again, since Junio's preparing\nfor a freeze for 1.7.3. Allowing post-receive-email to generate an empty\nemail message can be quite problematic, depending on the MTA in use on\nthe system where the script is run... in our case, it caused the MTA to\ngenerate bounce messages which were then delivered to the admin of our\ncorporate MTA, who had no clue what was causing them since they had no\ncontent.\n\n-- \nKevin P. Fleming\nDigium, Inc. | Director of Software Technologies\n445 Jan Davis Drive NW - Huntsville, AL 35806 - USA\nskype: kpfleming | jabber: kfleming@digium.com\nCheck us out at www.digium.com & www.asterisk.org\n"}]}