➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients barry, lpolzer, r.david.murray
Date 2013-11-25.16:50:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1385398205.86.0.639758696968.issue19679@psf.upfronthosting.co.za>
In-reply-to
Content 
Are you referring to implementing rfc 3463 and rfc 5248 insofar as they are applicable?  That seems useful.  I don't see anything in the RFC about the 'xab x.y.z text' form of the message, though.  Where is that documented?  IMO these messages should only be emitted if we got an ELHO...actually I would expect there to be an extension keyword associated with this, but I don't see one in the RFC.

The conn argument is a separate issue.  (And probably should not change for backward compatibility reasons.  Also, it doesn't have to be a socket, although it would indeed be unusual if it wasn't.)
History
Date User Action Args
2013-11-25 16:50:05r.david.murraysetrecipients: + r.david.murray, barry, lpolzer
2013-11-25 16:50:05r.david.murraysetmessageid: <1385398205.86.0.639758696968.issue19679@psf.upfronthosting.co.za>
2013-11-25 16:50:05r.david.murraylinkissue19679 messages
2013-11-25 16:50:05r.david.murraycreate