Print This FAQ

<<Back To Faq 6.2.7

Complete FAQ Listing

6.2 Receiving (POP3/IMAP) Email RFCs

6.2.1 RFC 2298 Extensible Message Format for Message Disposition Notifications (MDNs)
6.2.10 RFC 1731 IMAP4 Authentication Mechanisms
6.2.11 RFC 2342 IMAP4 Namespace
6.2.12 RFC 2359 IMAP4 UIDPLUS extension
6.2.13 RFC 3348 IMAP4 Child Mailbox Extension
6.2.14 RFC 2683 IMAP4 Implementation Recommendations
6.2.15 RFC 2971 IMAP4 ID extension
6.2.16 RFC 3502 IMAP MULTIAPPEND Extension
6.2.17 RFC 3503 Message Disposition Notification (MDN) profile for IMAP
6.2.18 RFC 3516 IMAP4 Binary Content Extension
6.2.19 RFC 2476 Message Submission
6.2.2 RFC 1939 Post Office Protocol - Version 3 (POP3)
6.2.20 RFC 2244 ACAP -- Application Configuration Access Protocol
6.2.21 RFC 1056 PCMAIL: A distributed mail system for personal computers
6.2.22 RFC 1204 Message Posting Protocol (MPP)
6.2.23 RFC 1339 Remote Mail Checking Protocol
6.2.3 RFC 1734 - POP3 AUTHentication command
6.2.4 RFC 1957 Some Observations on Implementations of POP3
6.2.5 RFC 2384 POP URL Scheme
6.2.6 RFC 2449 POP3 Extension Mechanism
6.2.7 RFC 3206 SYS and AUTH POP Response Codes

* You Are Here *

Scroll To Answer

Discuss

6.2.8 RFC 2195 IMAP/POP AUTHorize Extension for Simple Challenge/Response
6.2.9 RFC 3501 Internet Message Access Protocol - version 4rev1(IMAP4)

6.2.7 RFC 3206 SYS and AUTH POP Response Codes Printer Friendly Email This FAQ Discuss

http://www.ietf.org/rfc/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.

The formatted version of this faq can be found at http://www.SystemWebMail.com/faq/6.2.7.aspx