Skip to content
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

pop3/smtp: return *WEIRD_SERVER_REPLY when not understood #8506

Merged
merged 1 commit into from
Mar 29, 2022

Conversation

bagder
Copy link
Member

@bagder bagder commented Feb 24, 2022

This leaves the CURLE_RECV_ERROR error code for explicit failure to
receive network data and allows users to better separate the problems.

Fixes #8356
Reported-by: Rianov Viacheslav

This leaves the CURLE_RECV_ERROR error code for explicit failure to
receive network data and allows users to better separate the problems.

Ref #8356
Reported-by: Rianov Viacheslav
Closes #8506
@bagder bagder force-pushed the bagder/smpt-recv-weirdreply branch from c5595db to 5a9d7c4 Compare March 29, 2022 12:02
@bagder bagder closed this in 5a9d7c4 Mar 29, 2022
@bagder bagder merged commit 5a9d7c4 into master Mar 29, 2022
@bagder bagder deleted the bagder/smpt-recv-weirdreply branch March 29, 2022 13:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

response reading failure is accompanied by 2xx reply code
2 participants