| 1 |
Known Protocol Limitations |
| 2 |
========================== |
| 3 |
|
| 4 |
This chapter lists known limitations to protocols commonly in use today, that |
| 5 |
may impact your deployment. |
| 6 |
|
| 7 |
POP3 and Mailbox Locking |
| 8 |
------------------------ |
| 9 |
|
| 10 |
POP3, as described in :rfc:`1939`, requires a mailbox to be locked by a POP3 |
| 11 |
session. |
| 12 |
|
| 13 |
As such, when POP3 is used simultaneously across multiple clients, and a common |
| 14 |
set of mailboxes, an error similar to the following would occur:: |
| 15 |
|
| 16 |
Mailbox locked by POP server. |
| 17 |
|
| 18 |
The exact error message may be subject to the specific error message a client |
| 19 |
application wishes to display. |
| 20 |
|
| 21 |
Cyrus IMAP POP3 Implementation |
| 22 |
------------------------------ |
| 23 |
|
| 24 |
The Cyrus IMAP POP3 server implementation does not have the aforementioned |
| 25 |
problem of POP3 sessions locking mailboxes. As of version 2.4.0, Cyrus IMAP |
| 26 |
allows multiple POP3 sessions to operate on a single mailbox by providing a |
| 27 |
*virtual* snapshot of the mailbox, and all operations are executed to this |
| 28 |
snapshot. A safety mechanism ensures no messages are deleted until after all |
| 29 |
existing operations have closed the mailbox - including IMAP, LMTP and POP. |
| 30 |
|