Message238910
I doubt that it is good idea to close connection on *any* error. For example in _getresp() resp.decode() can raise an exception, but this failure isn't related to the ability of sending QUIT and other commands.
Sample error handling in your first message looks more reliable. Set special flags after failing command (but only if error is related to the connection), and ignore QUIT errors if it is set. After successful command this flag should be reset. |
|
Date |
User |
Action |
Args |
2015-03-22 14:47:50 | serhiy.storchaka | set | recipients:
+ serhiy.storchaka, pitrou, jwilk, martin.panter |
2015-03-22 14:47:50 | serhiy.storchaka | set | messageid: <1427035670.35.0.503021511728.issue22350@psf.upfronthosting.co.za> |
2015-03-22 14:47:50 | serhiy.storchaka | link | issue22350 messages |
2015-03-22 14:47:50 | serhiy.storchaka | create | |
|