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 jelie
Recipients jelie, pitrou, travis
Date 2010-11-28.09:25:20
SpamBayes Score 0.0009079848
Marked as misclassified No
Message-id <1290936322.09.0.39531917492.issue5209@psf.upfronthosting.co.za>
In-reply-to
Content
> +        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.
History
Date User Action Args
2010-11-28 09:25:22jeliesetrecipients: + jelie, pitrou, travis
2010-11-28 09:25:22jeliesetmessageid: <1290936322.09.0.39531917492.issue5209@psf.upfronthosting.co.za>
2010-11-28 09:25:20jelielinkissue5209 messages
2010-11-28 09:25:20jeliecreate