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 surkamp
Recipients exarkun, surkamp
Date 2010-01-25.21:05:04
SpamBayes Score 0.0002456974
Marked as misclassified No
Message-id <1264453506.56.0.425446163145.issue7779@psf.upfronthosting.co.za>
In-reply-to
Content
The SASL protocol says that the encoded base64 should be formed from:

null + login + null + password

The smtplib is not doing it, instead its "converting" the \012 (\0 + 2 first chars from password) in the char "\n", and it's right in the python way to see the things, it's not the bug reported here. The bug is a patch to change the null character representation from \0 to \x00 (using the hexadecimal representation) in the encode_base64 call to prevent the "conversion" and generate the right base64 encoded string.
History
Date User Action Args
2010-01-25 21:05:06surkampsetrecipients: + surkamp, exarkun
2010-01-25 21:05:06surkampsetmessageid: <1264453506.56.0.425446163145.issue7779@psf.upfronthosting.co.za>
2010-01-25 21:05:05surkamplinkissue7779 messages
2010-01-25 21:05:04surkampcreate