RFC 2683:IMAP4 Implementation Recommendations
RFC-Ref
Previous
|
Next
Frontpage
|
Contents
|
Keywords
IMAP4 Implementation Recommendations
1. Abstract
2. Conventions used in this document
3. Interoperability Issues and Recommendations
3.1. Accessibility
3.1.1. Multiple Accesses of the Same Mailbox
3.1.2. Severed Connections
3.2. Scaling
3.2.1. Flood Control
3.2.1.1. Listing Mailboxes
3.2.1.2. Fetching the List of Messages
3.2.1.3. Fetching a Large Body Part
3.2.1.4. BODYSTRUCTURE vs. Entire Messages
3.2.1.5. Long Command Lines
3.2.2. Subscriptions
3.2.3. Searching
3.3. Avoiding Invalid Requests
3.3.1. The CAPABILITY Command
3.3.2. Don't Do What the Server Says You Can't
3.4. Miscellaneous Protocol Considerations
3.4.1. Well Formed Protocol
3.4.2. Special Characters
3.4.3. UIDs and UIDVALIDITY
3.4.4. FETCH Responses
3.4.5. RFC822.SIZE
3.4.6. Expunged Messages
3.4.7. The Namespace Issue
3.4.8. Creating Special-Use Mailboxes
3.4.9. Reference Names in the LIST Command
3.4.10. Mailbox Hierarchy Delimiters
3.4.11. ALERT Response Codes
3.4.12. Deleting Mailboxes
3.5. A Word About Testing
4. Security Considerations
5. References
6. Author's Address
7. Full Copyright Statement
8. Acknowledgement
Previous
|
Next
Frontpage
|
Contents
|
Keywords
Web
RFC-Ref
RFC-Ref.org
Frontpage
Global Index
RFC
Sister Sites
Chess-Ref.org
Law-Ref.org
InChI.info
Zvon.org
