File: known_protocol_limitations.rst.txt

package info (click to toggle)
cyrus-imapd 3.12.1-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 60,540 kB
  • sloc: ansic: 280,382; perl: 146,834; javascript: 9,624; sh: 5,730; yacc: 2,660; cpp: 2,263; makefile: 2,103; lex: 675; xml: 621; awk: 303; python: 273; asm: 262
file content (30 lines) | stat: -rw-r--r-- 1,111 bytes parent folder | download | duplicates (16)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Known Protocol Limitations
==========================

This chapter lists known limitations to protocols commonly in use today, that
may impact your deployment.

POP3 and Mailbox Locking
------------------------

POP3, as described in :rfc:`1939`, requires a mailbox to be locked by a POP3
session.

As such, when POP3 is used simultaneously across multiple clients, and a common
set of mailboxes, an error similar to the following would occur::

    Mailbox locked by POP server.

The exact error message may be subject to the specific error message a client
application wishes to display.

Cyrus IMAP POP3 Implementation
------------------------------

The Cyrus IMAP POP3 server implementation does not have the aforementioned
problem of POP3 sessions locking mailboxes. As of version 2.4.0, Cyrus IMAP
allows multiple POP3 sessions to operate on a single mailbox by providing a
*virtual* snapshot of the mailbox, and all operations are executed to this
snapshot. A safety mechanism ensures no messages are deleted until after all
existing operations have closed the mailbox - including IMAP, LMTP and POP.