[horde] Updating mail status on phone via activesync

Wed May 1 11:45:41 UTC 2013

On 30 Apr 2013 19:44, "Michael Wisniewski" <wisniewski at mwiz.org> wrote:
>
>
> Quoting Michael J Rubinsky <mrubinsk at horde.org>:
>
>> Quoting Michael Wisniewski <wisniewski at mwiz.org>:
>>
>>> Quoting Michael J Rubinsky <mrubinsk at horde.org>:
>>>
>>>> Quoting Michael Wisniewski <wisniewski at mwiz.org>:
>>>>
>>>>> Quoting Michael J Rubinsky <mrubinsk at horde.org>:
>>>>>
>>>>>> Quoting Michael Wisniewski <wisniewski at mwiz.org>:
>>>>>>
>>>>>>> Quoting Michael J Rubinsky <mrubinsk at horde.org>:
>>>>>>>
>>>>>>>> Quoting Michael Wisniewski <wisniewski at mwiz.org>:
>>>>>>>>
>>>>>>>>> Quoting mrubinsk at horde.org:
>>>>>>>>>
>>>>>>>>>> Quoting Michael Wisniewski <wisniewski at mwiz.org>>
>>>>>>>>>>>
>>>>>>>>>>> I have a Galaxy S3 phone sync'ed up through activesync to my
Horde install.  When I receive a new message, my phone alerts me with a new
message.  If read on the desktop and deleted, my phone does not update the
message status as "read" and/or deleted.  I have to physically go in and
refresh the mailbox on the phone.
>>>>>>>>>>>
>>>>>>>>>>> Is there an option in Horde that will allow it to update the
phone with the message status after it has been updated through the web
interface?
>>>>>>>>>>>
>>>>>>>>>>> Thanks!
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Horde mailing list
>>>>>>>>>>> Frequently Asked Questions: http://horde.org/faq/
>>>>>>>>>>> To unsubscribe, mail: horde-unsubscribe at lists.horde.org
>>>>>>>>>>>
>>>>>>>>>> It will update automatically when a new email arrives in the
mailbox (assuming the mailbox is being pushed).
>>>>>>>>>>
>>>>>>>>>> I think I'm probably going to allow mailboxes that support
MODSEQ to trigger a sync on flag changes as well.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I was wondering if there is a trick to get this to work.  I have
push setup on the phone and it still does not seem to want to update the
status.  I'm running the 5.1.0-git with the 6.1.0-get version of imp.
>>>>>>>>
>>>>>>>>
>>>>>>>> Sounds like your IMAP server does not support CONDSTORE or MODSEQ
>>>>>>>> --
>>>>>>>
>>>>>>>
>>>>>>> I think I have dovecot configured to allow condstore.
>>>>>>>
>>>>>>> ----------
>>>>>>> wisniewski at snoopy:~$ telnet localhost 143
>>>>>>> Trying 127.0.0.1...
>>>>>>> Connected to localhost.
>>>>>>> Escape character is '^]'.
>>>>>>> * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID
ENABLE IDLE STARTTLS AUTH=PLAIN] Dovecot ready.
>>>>>>> a login wisniewski <foo>
>>>>>>> a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID
ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND
UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE
QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS
COMPRESS=DEFLATE ACL RIGHTS=texk] Logged in
>>>>>>> b capability
>>>>>>> * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE
IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT
CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC
ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS COMPRESS=DEFLATE
ACL RIGHTS=texk
>>>>>>> b OK Capability completed.
>>>>>>> ^]quit
>>>>>>> ----------
>>>>>>>
>>>>>>>
>>>>>>> This is what tells me condstore is running.....right?  I don't see
modseq and a quick google search of modseq and dovecot hasn't popped
anything that easily tells me how to enable it.
>>>>>>
>>>>>>
>>>>>> MODSEQ is part of the CONDSTORE extension, but some IMAP servers do
not support (or do not enable support by default) for per-mailbox MODSEQ
values.
>>>>>>
>>>>>> Dovecot, however, should work out of the box, and in fact this works
fine for me here. I would need to see your logs to see what is going on for
you.
>>>>>>
>>>>>>
>>>>>> --
>>>>>> mike
>>>>>>
>>>>>> The Horde Project (www.horde.org)
>>>>>> mrubinsk at horde.org
>>>>>
>>>>>
>>>>> Mike,
>>>>>
>>>>> Is there a good place to put the logs?  Can I send them directly to
you and then post the relevant contents here so it will help others?  Will
the generic "mail_debug = yes" work with dovecot for you?
>>>>
>>>>
>>>> Just the activesync log. In fact, I really only am interested in the
lines that start something like "Saving state for INBOX" or similar. I want
to see what the message cache looks like.
>>>>
>>>
>>> I posted my activesync debug log here...
>>>
>>> http://pastebin.com/Vv1gtRDF
>>>
>>> At about 9:32:08, I sent a test message to myself and shortly after, it
alerted on the phone.  At about 9:32:50-ish, I went into the web interface
and read and deleted the message.  The message status never updated on the
phone after that.
>>
>>
>>
>> 2013-04-30T09:32:57-05:00 INFO: CONDSTORE and CHANGES
>>
>> This shows you do, indeed have a server that supports CONDSTORE with per
mailbox MODSEQ.
>>
>> 2013-04-30T09:32:57-05:00 INFO: [2823] Found 1 message changes in INBOX.
>>
>> This shows the message change was correctly detected.
>>
>> <snip some unrelated entries>
>>
>> 2013-04-30T09:32:57-05:00 DEBUG: [2823] O    <Folder>
>> 2013-04-30T09:32:57-05:00 DEBUG: [2823] O     <SyncKey>
>> 2013-04-30T09:32:57-05:00 DEBUG: [2823] O
 {517fd591-0e48-4c77-abb0-0ac30a000103}4
>> 2013-04-30T09:32:57-05:00 DEBUG: [2823] O     <SyncKey/>
>> 2013-04-30T09:32:57-05:00 DEBUG: [2823] O     <FolderId>
>> 2013-04-30T09:32:57-05:00 DEBUG: [2823] O      INBOX
>> 2013-04-30T09:32:57-05:00 DEBUG: [2823] O     <FolderId/>
>> 2013-04-30T09:32:57-05:00 DEBUG: [2823] O     <Status>
>> 2013-04-30T09:32:57-05:00 DEBUG: [2823] O      1
>> 2013-04-30T09:32:57-05:00 DEBUG: [2823] O     <Status/>
>> 2013-04-30T09:32:57-05:00 DEBUG: [2823] O     <Commands>
>> 2013-04-30T09:32:57-05:00 DEBUG: [2823] O      <Remove>
>> 2013-04-30T09:32:57-05:00 DEBUG: [2823] O       <ServerEntryId>
>> 2013-04-30T09:32:57-05:00 DEBUG: [2823] O        1217
>> 2013-04-30T09:32:57-05:00 DEBUG: [2823] O       <ServerEntryId/>
>> 2013-04-30T09:32:57-05:00 DEBUG: [2823] O      <Remove/>
>> 2013-04-30T09:32:57-05:00 DEBUG: [2823] O     <Commands/>
>> 2013-04-30T09:32:57-05:00 DEBUG: [2823] O    <Folder/>
>>
>> This is a perfectly valid command sent from the server to the client
telling it to delete the email with message uid 1217 from the INBOX on the
client.
>>
>> If your client is ignoring this command, then it's broken.
>
>
> Thank you for taking a look at this and giving an update.  I'm using the
default "E-Mail" program on the Galaxy S3.  The E-Mail program, IMHO, is a
little drab and makes me wonder if they just whipped it together.
>
> In the meantime, I've just been using K9Mail with Dovecot and it keeps
everything in sync.  It would be nice if the updates were working, but I
have found a work-around for it.
>
> It would be interesting if others with a S3 have the same problem.
>
> Thanks again for your time in looking into this issue.

It works for me on the S3, but then I use the Enhanced Email client that
has a setting called disable EAS smart reply which apparently shows the
reply/forwarded icons in outlook..

Simon