Re: Net_SMTP - deadlock / robustness
| From: | Chuck Hagenbuch | Date: | Fri, 24 Dec 2004 00:57:31 +0000 |
| Subject: | Re: Net_SMTP - deadlock / robustness | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-35237@lists.php.net to get a copy of this message | ||
Quoting Matthias Pigulla <mp@webfactory.de>:
Otherwise, we might want to check parameters more carefully; or we might even improve handling of the return codes to make sure no "extra" replies keep hanging around in the buffers. Actually, having the extra 502 return code hanging in the buffer is what makes us running into this dead end street - if we would completely read the return buffer after each command, we could see that the DATA command actually succeeded.So, look at the code in _parseResponse(). I'm just not sure how to correctly interpret that response from Qmail. It's saying that part of the "address" succeeded, and then part failed - like 2 RCPT TO commands. _parseResponse() already handles regular multiline responses, so maybe the way to go is to make sure we don't send any commands that can be interpreted as multiple commands - i.e, disallow newlines in commands other than DATA (any others?). Does that sound like a workable solution? -chuck -- "But she goes not abroad in search of monsters to destroy." - John Quincy Adams