In order to support Telefonica's Exchange server (and probably a bunch of other Exchange servers out there), we need to allow ActiveSync usernames that aren't the same as the email address. There are a few parts to this: 1) Support this in the connection code (including grabbing the username from Autodiscover) 2) Have autoconfig files provide rules for building a username 3) Let users manually enter a username if autoconfig fails. NOTE: This will have l10n impact, although we can probably just copy the existing "Username" string from the IMAP settings. Requesting blocking-basecamp, since I think Telefonica would really like this, and it should also greatly increase the number of Exchange servers we can talk to.
I've already done (1) as part of some work to help out Andrew on some blocking work of his.
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
There's one remaining question: we can support autoconfigure for tid.es, but only for one of their internal domains. Do we think it would be valuable to add this for dogfooders at Telefonica? It would mean that users in our domain of choice (e.g. HI) would get autoconfig, but everyone else there would have to manually enter the server and their username.
(In reply to Jim Porter (:squib) from comment #4) > There's one remaining question: we can support autoconfigure for tid.es, but > only for one of their internal domains. Do we think it would be valuable to > add this for dogfooders at Telefonica? It would mean that users in our > domain of choice (e.g. HI) would get autoconfig, but everyone else there > would have to manually enter the server and their username. To clarify, the options are: A) *everyone* with a tid.es account has to do manual config B) people in the "HI" domain at tid.es don't have to do manual config, but everyone else with a tid.es account has to do manual config.
I'm guessing this was flagged QARegressExclude as a result of bug 826585. If so, I've checked in a workaround to that, so it should be ok to test again.
Jim, what are the steps to test this?
Probably the easiest way is to use one of our partner-provided test accounts, listed on the intranet here: https://intranet.mozilla.org/Gaia/Email
Oops, it seems people have added some more accounts there, so you'll want to test on the tid.es or o2.com servers.
ok, we can test internally with that, but can't put that information in a moztrap test case. Thank you, Jim.
You need to log in before you can comment on or make changes to this bug.