|Deletions are marked like this.||Additions are marked like this.|
|Line 1:||Line 1:|
|= Multi-Accessed Mailbox Practice =
||= Concurrent Access to Mailboxes =|
|Line 6:||Line 5:|
|Line 18:||Line 16:|
Concurrent Access to Mailboxes
[http://www.faqs.org/rfcs/rfc2180.html RFC 2180] explains the issues.
What should a server do when an expunge is done by a session while another concurrent session is accessing the same mailbox?
- Keep the message around until there are no sessions that see it. This is the preferred behavior.
- Give some dummy replies for the message. Such as empty flags, and other fields being NILs or whatever is legal for the field. The downside to this is that it violates the IMAP protocol if the client had already asked something about this message.
Don't return the FETCH reply for the message at all and return a tagged NO reply. Doing this makes some clients ask the same message range over and over again infinitely. This could be avoided also: http://mailman1.u.washington.edu/pipermail/imap-protocol/2006-September/000281.html
- Disconnect the client anytime you can't handle the request. I used to do this but it was annoying when it happened.
- Don't allow EXPUNGE until there's only session. I think this is the worst of the possibilities.
[http://mailman1.u.washington.edu/pipermail/imap-protocol/2007-May/000562.html The above order isn't the ideal from IMAP protocol point of view]