…ning un-encoded UTF-8 characters, and mail drops that are accessed using POP3 [ RFC1939 ] might natively store UTF-8. This specification extends POP3 [ RFC1939 ] using the POP3 extension mechanism [ RFC2449 ] to permit un-encoded UTF-8 [ RFC3629 ] in headers, as described in "Int…

…ning un-encoded UTF-8 characters, and mail drops that are accessed using POP3 [ RFC1939 ] might natively store UTF-8. This specification extends POP3 [ RFC1939 ] using the POP3 extension mechanism [ RFC2449 ] to permit un-encoded UTF-8 [ RFC3629 ] in headers, as described in "Int…

…ernet Message Access Protocol (IMAP) [RFC3501], the Post Office Protocol (POP) [RFC1939], and/or Simple Mail Transfer Protocol (SMTP) Submission [RFC6409] usually has Transport Layer Security (TLS) [RFC5246] support but often does not use it in a way that maximizes end-user confi…

…et Message Access Protocol (IMAP) [ RFC3501 ], the Post Office Protocol (POP) [ RFC1939 ], and/or Simple Mail Transfer Protocol (SMTP) Submission [ RFC6409 ] usually has Transport Layer Security (TLS) [ RFC5246 ] support but often does not use it in a way that maximizes end-user …

…Internet email protocols include SMTP [ RFC5321 ], IMAP [ RFC3501 ], and POP3 [ RFC1939 ]. IMAP and POP3 are both message store access protocols used by message store user agents (MUAs) to manipulate email messages after delivery. [ RFC4409 ] defines a "profile" of the SMTP servi…

…y application protocols like IMAP [ RFC3501 ], the Post Office Protocol (POP) [ RFC1939 ], and the Extensible Message and Presence Protocol (XMPP) [ RFC6120 ]. The effect is to make modular authentication, so that newer authentication mechanisms can be added as needed. This memo …

…y deployed to remotely access a message store. The Post Office Protocol (POP) [ RFC1939 ] provides simple download-and-delete access to a single mail drop (which is a subset of the functionality typically associated with a message store). The Internet Message Access Protocol (IMA…

…y deployed to remotely access a message store. The Post Office Protocol (POP) [ RFC1939 ] provides simple download-and-delete access to a single mail drop (which is a subset of the functionality typically associated with a message store). The Internet Message Access Protocol (IMA…

…te non- ASCII characters in some header fields. While extensions to both POP3 [ RFC1939 ] and IMAP [ RFC3501 ] have been defined that include automatic upgrading of messages that carry non-ASCII information in encoded form -- including RFC 2047 decoding -- of messages by the POP3…

…sage or a set of messages available from a mailstore over IMAP [ RFC3501 ], POP RFC1939 ], or web [ RFC2616 ] can instead use the imap: [ RFC5092 ], pop: RFC2384 ] or http: [ RFC2616 ] URIs, respectively. . Security Considerations In the past, the mailserver: URI scheme was never…

…it or by having the receiver of access pull the message, such as by using POP [ RFC1939 ] and IMAP [ RFC3501 ]. 4.5 . Implementation and Operation A discussion of any interesting system architecture often bogs down when architecture and implementation are confused. An architectur…

…ay authentication (e.g., HTTP Basic authentication or POP APOP authentication [ RFC1939 ]), this message also contains a server-side authentication verification value. When the client's verification value is incorrect (e.g., because the user-supplied password was incorrect), the …

…sage or a set of messages available from a mailstore over IMAP [ RFC3501 ], POP RFC1939 ], or web [ RFC2616 ] can instead use the imap: [ RFC5092 ], pop: RFC2384 ] or http: [ RFC2616 ] URIs, respectively. . Security Considerations In the past, the mailserver: URI scheme was never…

…ssage or a set of messages available from a mailstore over IMAP [RFC3501], POP [RFC1939], or web [RFC2616] can instead use the imap: [RFC5092], pop: [RFC2384] or http: [RFC2616] URIs, respectively. It should say: There were some previous attempts to provide detailed documentation…

…ssage or a set of messages available from a mailstore over IMAP [RFC3501], POP [RFC1939], or web [RFC2616] can instead use the imap: [RFC5092], pop: [RFC2384] or http: [RFC2616] URIs, respectively. It should say: There were some previous attempts to provide detailed documentation…