Skip to content

Commit

Permalink
Add example hook to allow Windows 10 Mail.app to ignore provisioning.
Browse files Browse the repository at this point in the history
Allows Mail.app to connect, as UNPROVISIONED, regardless of provisioning
setting of server.
  • Loading branch information
mrubinsk committed Mar 11, 2017
1 parent c3c476b commit 65b1492
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions horde/config/hooks.php.dist
Expand Up @@ -1271,6 +1271,13 @@ class Horde_Hooks
// return Horde_ActiveSync::PROVISIONING_FORCE;
// }

// // Example for working around Windows 10 Mail.app broken provisioning
// // support. This allows Mail.app to connect UNPROVISIONED regardless
// // of the provisioning setting of the server.
// if (strpos($device->userAgent, 'MSFT-WIN-3') === 0 &&
// strpos($device->properties[Horde_ActiveSync_Device::NAME], 'DESKTOP') === 0) {
// return Horde_ActiveSync::PROVISIONING_NONE;
// }
// return -1;
// }

Expand Down

3 comments on commit 65b1492

@PaulFreund
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for pulling out this old PR but I have a question. What is the reason you included filtering for the DESKTOP- filtering in the first place?

@mrubinsk
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's just an example on how to filter for different properties. I don't remember if the Horde_ActiveSync_Device::NAME property was needed to differentiate between different applications or not. The reasoning for filtering for Mail.app in general is because (at least at the time this was written) it did not support the PROVISION feature/command so if PROVISIONING was set as required that app would be unable to connect.

@PaulFreund
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you very much for your feedback! It seems there are still issues with the current app and Windows 11 and provisioning. I get errors about security enforcements (0x85010013) that I was not able to fix with my online account. Since the user agent is quite unique I think it should be enough to filter for that.

Please sign in to comment.