-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Unicode response message #41
Comments
Thanks for submitting. Yeah, I'm not sure how best to handle this. IIRC originally we just did UTF-8 decoding, but then the SMTP protocol actually requires ASCII responses, so I changed it to that. I agree though this is situation where we might as well be liberal with what we accept (as you pointed out, there is still the status code). However:
|
Another possibility just come to my mind is that we can just print out the formatted bytecodes that are not fit in utf-8 chars, my temp solution just to get rid of the error is something like:
Thanks for giving very nice library. |
Yeah, I was just looking at that too 😄 Glad you're finding it useful! |
Fixed in 581d718. |
Hi Cole,
I was reading the test and see the test_live.py::test_qq_login has been marked because of utf-8 unsupported. As far as I investigated, the reason is that qq smtp service return non-ascii (and even non utf-8 chars):
535 Error: \xc7\xeb\xca\xb9\xd3\xc3\xca\xda\xc8\xa8\xc2\xeb\xb5\xc7\xc2\xbc\xa1\xa3\xcf\xea\xc7\xe9\xc7\xeb\xbf\xb4: http://service.mail.qq.com/cgi-bin/help?subtype=1&&id=28&&no=1001256\r\n
I was thinking of 2 posibility to solve this problem:
re
to eliminate non-utf8 (ascii) chars since it is the message, we still have response codeWhat do you think?
The text was updated successfully, but these errors were encountered: