We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
GitHub fields:
assignee = None closed_at = <Date 2015-06-14.13:55:08.967> created_at = <Date 2009-02-10.19:42:47.524> labels = ['type-feature', 'library'] title = 'nntplib needs updating to RFC 3977' updated_at = <Date 2015-06-14.13:55:08.965> user = 'https://bugs.python.org/travis'
bugs.python.org fields:
activity = <Date 2015-06-14.13:55:08.965> actor = 'martin.panter' assignee = 'none' closed = True closed_date = <Date 2015-06-14.13:55:08.967> closer = 'martin.panter' components = ['Library (Lib)'] creation = <Date 2009-02-10.19:42:47.524> creator = 'travis' dependencies = [] files = ['13020'] hgrepos = [] issue_num = 5209 keywords = ['patch'] message_count = 4.0 messages = ['81587', '81608', '122643', '245343'] nosy_count = 4.0 nosy_names = ['pitrou', 'travis', 'jelie', 'martin.panter'] pr_nums = [] priority = 'normal' resolution = 'out of date' stage = 'resolved' status = 'closed' superseder = None type = 'enhancement' url = 'https://bugs.python.org/issue5209' versions = ['Python 3.2']
The text was updated successfully, but these errors were encountered:
RFC 977 has been obsoleted by RFC 3977
Numerous new commands, standardized extensions, clarifications.
Sorry, something went wrong.
Attached is a difference which implements CAPABILITIES and MODE READER and leaves some TODO comments for other RFC 3977 commands.
Whether posting is allowed depends on whether it is included in results of CAPABILITIES; see RFC 3977 section 5.1.2. Deprecated: If the response code is 200, posting is allowed; if it 201, posting is not allowed."""
Whether posting is allowed depends on whether it
is included in results of CAPABILITIES; see
RFC 3977 section 5.1.2.
Deprecated: If the response code is 200, posting is allowed; if it 201, posting is not allowed."""
200 and 201 do not have a deprecated meaning in RFC 3977.
200 = posting may be available during the session (possibly after commands like STARTTLS or AUTHINFO have been successfully sent) 201 = posting will never be allowed in the session, whatever the user does.
I agree that the only way to know whether posting is allowed at a given time during the session is to send CAPABILITIES and to look for POST.
General RFC 3977 support was added as part of bpo-9360 (revision 0077ee30134c), so I am closing this one.
For the record there are a couple bits of the patch that someone might still find useful:
No branches or pull requests
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:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: