[horde] Outlook EAS ActiveSync errors

[Michael J Rubinsky]

Adding back to the horde@ list

Quoting Nels Lindquist <nlindq at maei.ca>:

> Hi, Michael.
>
> On 2018/05/30 10:53 AM, Nels Lindquist wrote:
>> Hi, Michael.
>>
>> On 2018/05/28 6:49 PM, Michael J Rubinsky wrote:
>>>
>>> Quoting Nels Lindquist <nlindq at maei.ca>:
>>>
>>>> Looks like Enigmail automatically encrypted that last message
>>>> since I have your PGP key locally; if you have trouble please
>>>> let me know and I'll resend it in the clear.
>>>
>>> Hi Nels, I received it just fine, but can you turn up the
>>> verbosity on the EAS log? It's missing the logging for saving the
>>> device state.
>>
>> Okay, I've uploaded another archive to the same ownCloud location
>> as before.
>>
>> The logfiles are filtered to start at midnight local yesterday, but
>> the ActiveSync logging wasn't turned up to DEBUG until the
>> morning.
>>
>> Please let me know if I can provide anything else.
>
> Just wondering if anything turned up in the second set of logs, or if
> there's anything else I can gather for you?

It looks like your IMAP server is either broken, misconfigured, or  
Horde_Imap_Client is buggy with respect to cyrus and MODSEQ/CONDSTORE  
functionality:

The initial pairing of the INBOX.Deleted Items folder, for example:

[19803][2018-05-29T14:48:45-06:00] >>>: INBOX.Deleted Items IMAP  
PREVIOUS MODSEQ: 0
[19803][2018-05-29T14:48:45-06:00] >>>: IMAP status:  
a:4:{s:8:"messages";i:81;s:7:"uidnext";i:91;s:11:"uidvalidity";i:1522344794;s:13:"highestmodseq";i:98;}
[19803][2018-05-29T14:48:45-06:00] >>>: INITIAL SYNC


You can see in the IMAP Status that your server is returning a  
HIGHESTMODSEQ value of 98. Then, during some subsequent sync, the  
following is logged:


[30045][2018-05-29T14:51:41-06:00] >>>: INBOX.Deleted Items IMAP  
PREVIOUS MODSEQ: 98
[30045][2018-05-29T14:51:41-06:00] >>>: IMAP status:  
a:4:{s:13:"highestmodseq";i:0;s:8:"messages";i:81;s:7:"uidnext";i:91;s:11:"uidvalidity";i:1522344794;}

Here you see we correctly stored the previous MODSEQ value of 98, but  
you can see in the IMAP status returned from the server that it is now  
reporting a 0. This is incorrect. From what I can tell looking through  
the Horde_Imap code, and looking at your imap log, it looks like at  
the time the mailbox is opened, the IMAP status does not include the  
MODSEQ data for some reason. I can try to look into this further, but  
I honestly don't know when I'll have time for this.  In the meantime,  
you can try to enable QRESYNC on your IMAP server and see if that  
helps, as this would be a different initial IMAP conversation.






> Thanks,
>
> Nels Lindquist <nlindq at maei.ca>



-- 
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 9272 bytes
Desc: PGP Public Key
URL: <https://lists.horde.org/archives/horde/attachments/20180610/403634c9/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 821 bytes
Desc: PGP Digital Signature
URL: <https://lists.horde.org/archives/horde/attachments/20180610/403634c9/attachment-0003.bin>