nntplib throws spurious NNTPProtocolError

[msapiro]

BPO	37919
Nosy	@msapiro

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2019-08-22.17:22:32.936>
labels = ['3.8', '3.7', 'library', '3.9']
title = 'nntplib throws spurious NNTPProtocolError'
updated_at = <Date 2019-08-22.17:22:32.936>
user = 'https://github.com/msapiro'

bugs.python.org fields:

activity = <Date 2019-08-22.17:22:32.936>
actor = 'msapiro'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-08-22.17:22:32.936>
creator = 'msapiro'
dependencies = []
files = []
hgrepos = []
issue_num = 37919
keywords = []
message_count = 1.0
messages = ['350214']
nosy_count = 1.0
nosy_names = ['msapiro']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue37919'
versions = ['Python 2.7', 'Python 3.5', 'Python 3.6', 'Python 3.7', 'Python 3.8', 'Python 3.9']

[msapiro]

This is really due to an nntp server bug, but here's the scenerio.

A connection is opened to the server.

An article is posted via the connection's post() method.

The server responds to the article data with

240 Article posted <value of message-id>

but due to the server bug, if the message-id is long, this response comes on two lines as

240 Article posted
<value of message-id>

The post() method reads only the first line and returns it.

Then the connection's quit() method (or some other method) is called, and it sees the second line of the prior response as the server's response rather than the actual response, and raises NNTPProtocolError.

Arguably, NNTPProtocolError is appropriate in this scenario, but if so, it should be raised by the post() method and not by a subsequent method.

[hugovk]

Note the nntplib module is deprecated in 3.11 and set for removal in 3.13.

See PEP 594 – Removing dead batteries from the standard library and #91217.

[AlexWaygood]

Note the nntplib module is deprecated in 3.11 and set for removal in 3.13.

See PEP 594 – Removing dead batteries from the standard library and #91217.

Considering this issue has had no activity for over two years, there are 7k+ open issues in the CPython repo, the nntplib module is now deprecated, and there is currently no active maintainer for nntplib in the core dev team, I think it's exceedingly unlikely that a fix will be merged for this problem. I'm therefore closing this issue.

Cc. @msapiro.