[Tickets #12007] Re: Messages not deleted via AS sync when deleted from IMAP client

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12007
------------------------------------------------------------------------------
  Ticket             | 12007
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Messages not deleted via AS sync when deleted from
                     | IMAP client
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
  State              | Not A Bug
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2013-02-01 17:15) wrote:

> Can I ask to clarify for others finding this behaviour in future and  
> wondering;
>
> This is a choice in the Horde AS code? I.e. when seeing a message  
> marked as /deleted on IMAP AS leaves it there as the AS protocol it  
> has no facility to tell a client the message is marked for deletion  
> (but not yet deleted/expunged)?

It's not really a choice, because there *is* no such thing as a  
message marked for deletion in AS.  A message is either in the mailbox  
or it is not. The /deleted flag is not a supported flag in the  
protocol, there is no mechanism to tell the client it is "marked for  
deletion" and there is no way of displaying such messages in a  
different manner (such as with a line though them).

Technically, what the code does is ask for any changes since the last  
known modseq value. It then discards any messages returned from this  
query that have the /deleted flag now set.

> And in theory (and probably with some strange side effects) - the AS  
> code *could* choose to tell the client the message was deleted at  
> this point?

No, because that would put the client and the server in an  
inconsistent state. There is a command called SOFTDELETE that could be  
abused for this purpose, but it still needs to be implemented (and is  
a current TODO listed in the library docs). It's normally used for  
removing messages from the client (email or appointments) that fall  
outside of the client's configured time window.

> And lastly - shouldn't the message be marked as 'read' via AS? Is  
> that a separate bug? (happy to raise one).

Actually, yes, I suppose it should. The way the code works currently  
is the entire message is ignored, so the /seen flag is never caught.  
No need for a new ticket, I'll take care of it.