RFC 1939 APOP support indicated by <1896.697170952@dbc.mtview.ca.us> here:POP3 servers without the optional APOP command expect the client to log in with the USER and PASS commands:==Server implementations====Related requests for comments (RFCs)==* RFC 918 – POST OFFICE* RFC 937 – POST OFFICE PROTOCOL – VERSION 2* RFC 1081 – Post Office Protocol – Version 3* RFC 1939 – Post Office Protocol – Version 3 (STD 53)* RFC 1957 – Some Observations on Implementations of the Post Office Protocol (POP3)* RFC 2195 – IMAP/POP AUTHorize Extension for Simple Challenge/Response* RFC 2384 – POP URL Scheme* RFC 2449 – POP3 Extension Mechanism* RFC 2595 – Using TLS with IMAP, POP3 and ACAP* RFC 3206 – The SYS and AUTH POP Response Codes* RFC 5034 – The Post Office Protocol (POP3) Simple Authentication and Security Layer (SASL) Authentication Mechanism==See also==* Email encryption==Notes====References====External links==* IANA port number assignments* POP3 Sequence Diagram (PDF)
Это пример сессии с поддержкой зашифрованных паролей (APOP, RFC 1939):== Примечания ==== Ссылки ==* Список UNIX-демонов* Протокол POP3 на примерах;Ссылки на упоминавшиеся RFC* RFC 918 — POST OFFICE PROTOCOL* RFC 937 — POST OFFICE PROTOCOL — VERSION 2* RFC 1081 — Post Office Protocol — Version 3* RFC 1939 — Post Office Protocol — Version 3 (STD 53)* RFC 1957 — Some Observations on Implementations of the Post Office Protocol (POP3)* RFC 2195 — IMAP/POP AUTHorize Extension for Simple Challenge/Response* RFC 2384 — POP URL Scheme* RFC 2449 — POP3 Extension Mechanism* RFC 2595 — Using TLS with IMAP, POP3 and ACAP* RFC 3206 — The SYS and AUTH POP Response Codes* RFC 5034 — The Post Office Protocol (POP3) Simple Authentication and Security Layer (SASL) Authentication Mechanism