The SYS and AUTH POP Response Codes
draft-gellens-pop-err-01

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3206.
Author Randall Gellens
Last updated 2013-03-02 (Latest revision 2001-03-01)
RFC stream Legacy stream
Intended RFC status Proposed Standard
Formats
txt htmlized pdf bibtex bibxml
Stream Legacy state (None)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Became RFC 3206 (Proposed Standard)
Telechat date (None)
Responsible AD (None)
Send notices to (None)
Email authors IPR References Referenced by Nits Search email archive
draft-gellens-pop-err-01 
A new Request for Comments is now available in online RFC libraries.

        RFC 3206

        Title:      The SYS and AUTH POP Response Codes
        Author(s):  R. Gellens
        Status:     Standards Track
        Date:       February 2002
        Mailbox:    randy@qualcomm.com
        Pages:      6
        Characters: 9917
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-gellens-pop-err-01.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3206.txt

This memo proposes two response codes: SYS and AUTH, which enable
clients to unambiguously determine an optimal response to an
authentication failure.  In addition, a new capability
(AUTH-RESP-CODE) is defined.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.