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 orsenthil
Recipients Dario D'Amico, Mario Colombo, barry, junpengruan, miss-islington, orsenthil, pepoluan, r.david.murray, rahul-kumi, redstone-cold
Date 2021-04-27.05:03:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAPOVWOTg0LUm7KkgxJAdk+XDzsLEvOmCXkEjfWoPeNZ8VgUOVQ@mail.gmail.com>
In-reply-to <1619499772.74.0.693910345514.issue27820@roundup.psfhosted.org>
Content
Please open a new issue. It has better chances of being fixed quickly.

On Mon, Apr 26, 2021 at 10:02 PM junpengruan <report@bugs.python.org> wrote:

>
> junpengruan <632077280@qq.com> added the comment:
>
> Hi
> I think there is another bug when initial_response_ok=False. When using
> AUTH PLAIN, the server will response like:
> ------------------
> C: AUTH PLAIN
> S: 334 ok. go on
> ------------------
> and it's not base64 encoding, while in the auth() it will decode the
> resp(here is "ok, go on") which will cause a binascii.Error:
>
> Traceback (most recent call last):
>   File "/usr/lib/python3.6/smtplib.py", line 644, in auth
>     challenge = base64.decodebytes(resp)
>   File "/usr/lib/python3.6/base64.py", line 553, in decodebytes
>     return binascii.a2b_base64(s)
> binascii.Error: Incorrect padding
>
> I think this fit the title "a bug in smtplib when
> initial_response_ok=False", should I just comment on this issue or open a
> new issue?
> Thanks!
>
> ----------
> nosy: +junpengruan
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue27820>
> _______________________________________
>
History
Date User Action Args
2021-04-27 05:03:58orsenthilsetrecipients: + orsenthil, barry, r.david.murray, redstone-cold, Dario D'Amico, Mario Colombo, miss-islington, rahul-kumi, pepoluan, junpengruan
2021-04-27 05:03:58orsenthillinkissue27820 messages
2021-04-27 05:03:57orsenthilcreate