[Tickets #15080] Re: ActiveSync only works in initial configuration

noreply at bugs.horde.org noreply at bugs.horde.org
Mon Dec 13 16:52:16 UTC 2021


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

Ticket URL: https://bugs.horde.org/ticket/15080
------------------------------------------------------------------------------
  Ticket             | 15080
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | ActiveSync only works in initial configuration
  Queue              | Synchronization
  Version            | FRAMEWORK_5_2
  Type               | Bug
-State              | Unconfirmed
+State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
-Owners             |
+Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2021-12-13 16:52) wrote:

> Hi,
> I am running Horde 5.2.22 with ActiveSync enabled.
>
> On a brand new MS Surface (Win 11) with Office 365 (most up to date  
> Outlook version).
>
> Outlook is configured to sync with Exchange Server and the initial  
> download of all messages works fine. But after rebooting the machine  
> Outlook does not fully reconnect to ActiveSync. There is actually no  
> error message in Outlook - but the status shows that it is connected  
> to the server and is waiting for his response.
>
> So it look like that the baisc connection is fully working but some  
> service on the server does not respond propperly and Outlook does  
> not sync anything.
>
> I can't believe that this is a issue in the connector but most  
> likely in my configuration. Does  anyone have an idea which settings  
> / configuration I should double check?

I would need to see the activesync logs for the devices that are  
exhibiting this issue. I CAN tell you that I have pretty much given up  
on getting Outlook to work flawlessly with Activesync as Microsoft  
seems to continuously change how Outlook behaves with it.  I'm  
surprised you were able to get that far, to be honest, as last I  
checked the autodiscovery process that Outlook now uses requires it to  
go through O365.






More information about the bugs mailing list