1095144 - [email/activesync] Report MaximumDevicesReached (Status code 177) errors to the user, preferably as part of the account creation process

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::E-Mail, enhancement)

Description

[Andrew Sutherland [:asuth] (he/him)]

In bug 1093572 (the public version of bug 1091448), we are seeing apparent account creation/sync failure because our call to SyncFolderList is returning with error 177 (MaximumDevicesReached).  This is almost certainly the result of a combination of QA-style testing using an account in conjunction with our change to generate unique device id's in bug 825538.

This will require new strings and as such constitutes a feature for release planning purposes.

Most specifically, the response looks like the following and takes a while to be returned:
<FolderHierarchy:FolderSync>
  <FolderHierarchy:Status>
    177
  </FolderHierarchy:Status>
</FolderHierarchy:FolderSync>

Info on the code can be found at:
- Spec: http://msdn.microsoft.com/en-us/library/ee218647%28v=exchg.80%29.aspx
- Random blog post: http://blogs.msdn.com/b/webdav_101/archive/2012/02/09/eas-177-response-code-or-why-cant-i-sync-any-more-devices.aspx

Other random links:
- Knowledgebase including a link to request resets for Outlook 2013 and a workaround of using a different protocol: http://support.microsoft.com/kb/2802703
- Microsoft apparently released some type of service pack for outlook 2013? http://support.microsoft.com/kb/2727079
- Interesting blog post with some scripting stuff: http://thoughtsofanidlemind.com/2014/01/15/eas-device-partnerships/
- Exchange 2013 cmdlet: http://technet.microsoft.com/en-us/library/bb125032%28v=exchg.150%29.aspx

Comment 2

[Andrew Sutherland [:asuth] (he/him)]

Er, and we should look into things to see if we can get the 177 error earlier or if it's only during syncFolderList.  In the event syncFolderList is it, then let's just roll that into the account setup process to the extent possible.  That might moot the syncblocked mechanism slightly.

We should probably also mention in the string that IMAP is usually a viable/far superior work-around.

Comment 3

[BMO Automation]

Firefox OS is not being worked on