| 1 |
.. _imap-features-delayed-expunge: |
| 2 |
|
| 3 |
=============== |
| 4 |
Delayed Expunge |
| 5 |
=============== |
| 6 |
|
| 7 |
When a user or IMAP client expunges a message or an entire folder, |
| 8 |
messages become unavailable to the user. |
| 9 |
|
| 10 |
When the deletion is accidental, administrators may have to recover the |
| 11 |
messages from some place. When the messages are purposefully deleted, |
| 12 |
the user may have done so not with the best of intentions. |
| 13 |
|
| 14 |
In any case, the time between a message arriving and being deleted may |
| 15 |
not be sufficient to ensure the message is replicated, included in the |
| 16 |
next backup cycle, and generally available for recovery or compliance |
| 17 |
with the regulatory environment. |
| 18 |
|
| 19 |
Cyrus IMAP introduces *delayed expunge*, which ensures message files are |
| 20 |
not immediately unlinked from the filesystem, and instead makes purging |
| 21 |
the message files from the filesystem a separate event. |
| 22 |
|
| 23 |
This enables administrators to quickly recover access to messages that |
| 24 |
have been accidentally deleted, as well as allows the environment to |
| 25 |
ensure messages remain available for inclusion in the next backup cycle. |
| 26 |
|
| 27 |
------------------------------------------ |
| 28 |
Configuring Cyrus IMAP for Delayed Expunge |
| 29 |
------------------------------------------ |
| 30 |
|
| 31 |
To enable or disable Delayed Expunge, please check the following |
| 32 |
settings in :cyrusman:`imapd.conf(5)`. |
| 33 |
|
| 34 |
.. include:: /imap/reference/manpages/configs/imapd.conf.rst |
| 35 |
:start-after: startblob expunge_mode |
| 36 |
:end-before: endblob expunge_mode |
| 37 |
|
| 38 |
.. seealso:: |
| 39 |
|
| 40 |
* :ref:`imap-reference-manpages-systemcommands-unexpunge` |
| 41 |
* :ref:`imap-features-delayed-delete` |
| 42 |
* :ref:`imap-admin-deleted-expired-expunged-purged` |
| 43 |
|
| 44 |
Back to :ref:`imap-features` |