[Tickets #13495] Re: "Reply state" not synched over devices

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/13495
------------------------------------------------------------------------------
  Ticket             | 13495
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | "Reply state" not synched over devices
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
  State              | Not A Bug
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2014-08-25 17:13) wrote:


>> After looking at this further, though, it's not going to be possible
>> to work around this since we have NO way of knowing if it's a reply
>> vs a forward, nor do we know the original UID of the original IMAP
>> message, or even what folder it's from (so we can't efficiently look
>> it up).
>
> I'm not really understanding what you mean..
>
> Think about this test-scenario:
>
> 1. I get a message from lets say "client at gmail.com"
>   -> message-header:
> ------------8<----------------------------------------------------------------
> Message-ID:  
> <CACQS2qqQrAa2QMi=pHRB4Rgn8XZtAhuqCq99LvT-Kp4SbU4LNQ at mail.gmail.com>
> ------------8<----------------------------------------------------------------
>
> 2. I reply to this message from OL2013:
>   -> message-header(s):
> ------------8<----------------------------------------------------------------
> References:  
> <CACQS2qqQrAa2QMi=pHRB4Rgn8XZtAhuqCq99LvT-Kp4SbU4LNQ at mail.gmail.com>
> In-Reply-To:  
> <CACQS2qqQrAa2QMi=pHRB4Rgn8XZtAhuqCq99LvT-Kp4SbU4LNQ at mail.gmail.com>
> ------------8<----------------------------------------------------------------
>
> 3. I forward this message from OL2013:
> ------------8<----------------------------------------------------------------
> References:  
> <CACQS2qqQrAa2QMi=pHRB4Rgn8XZtAhuqCq99LvT-Kp4SbU4LNQ at mail.gmail.com>
> In-Reply-To:  
> <CACQS2qqQrAa2QMi=pHRB4Rgn8XZtAhuqCq99LvT-Kp4SbU4LNQ at mail.gmail.com>
> ------------8<----------------------------------------------------------------
>
> ..so the problems in coding would be:
>   1. saving the original "Message-ID" vs. "UID"

In order to set the "Answered" flag directly on the IMAP server we  
need to know the folder the original message is in as well as the  
message's UID. We don't know either of these things from the simple  
SENDMAIL command that OL2013 is issuing. All we have is the  
In-Reply-To header - which tells us nothing about about which folder  
the original email is located in. It's possible to search for this  
message on the IMAP server, but since we don't know which folder it's  
in, it is a potentially inefficient operation for little gain (setting  
the Answered or Forwarded flag - something the client should be doing  
on it's own).

>   2. finding a possibility to distinguish if it's a REPLY or FORWARD  
> (parsing the Subject is not OK since it could be changed)

Correct. Since the In-Reply-To header is sent in both reply and  
forward operations, we don't know which action was performed. I guess  
parsing the subject could be an option, but as you say, it's not 100%  
reliable since it can be changed...