| 1 |
====================================== |
| 2 |
Duplicate Message Delivery Suppression |
| 3 |
====================================== |
| 4 |
|
| 5 |
Messages are delivered to IMAP users in a seemingly endless stream and |
| 6 |
near continuous flow, but sometimes something fails. |
| 7 |
|
| 8 |
A sending MTA awaits confirmation from a receiving MTA or MDA, and a |
| 9 |
receiving MTA or MDA often waits giving out that confirmation until |
| 10 |
after it has assured delivery was actually successful. |
| 11 |
|
| 12 |
In cases where exactly in between the receiving MTA or MDA receiving |
| 13 |
that assurance, and the sending MTA being sent the confirmation, |
| 14 |
something fails, the sending MTA has not received confirmation, and it |
| 15 |
will therefore re-attempt delivery. |
| 16 |
|
| 17 |
This constitutes duplicate delivery -- of the same message, and should, |
| 18 |
for a better user experience, be avoided -- unless your helpdesk is |
| 19 |
idling and you want to keep it busy. |
| 20 |
|
| 21 |
Cyrus IMAP employs technology to detect an attempt to deliver a |
| 22 |
duplicate of a message already delivered, and can suppress the duplicate |
| 23 |
from being posted to the users' mailboxes. |
| 24 |
|
| 25 |
.. note:: |
| 26 |
|
| 27 |
This section needs more content. Would you like to |
| 28 |
:ref:`help out <contribute-docs>`? |
| 29 |
|
| 30 |
.. todo:: Please write me. |
| 31 |
|
| 32 |
Back to :ref:`imap-features` |