Running ssmtp -t with input like --- Date: Thu, 27 Nov 2003 16:57:42 +0000 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: test
test --- will result in the following being sent to *both* recipients: --- Date: Thu, 27 Nov 2003 16:57:42 +0000 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: test test --- That is, it ends the To: line at the first comma. It's easy to see why from the source, is finds the comma, puts in a null to easily read the address, but then never puts the comma back in. Additionally, running ssmtp -t with input like --- Date: Thu, 27 Nov 2003 16:57:42 +0000 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: test test --- results in a message being sent to "[EMAIL PROTECTED]", "@math.berkeley.edu", "[EMAIL PROTECTED]". That is, when there is a comma at the end of a line, it still interprets the empty space at the end of the line as an address. Most smtp servers seem to ignore the invalid address, but I have had at least one refuse to deliver because of it. Thank you, Robert -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
