Closed Bug 1111662 Opened 8 years ago Closed 8 years ago

[email/autoconfig] Copy autoconfig entry to to compensate for mozilla switch to gmail


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

Not set


(Not tracked)



(Reporter: asuth, Assigned: asuth)




(1 file)

The ISPDB changes I proposed in bug 1109991 aren't something we can do yet, so we need to do the stopgap of copying the local autoconfig entry over to

The imminently attached patch does this.  With this patch applied, what I observe on my trunk flame device and trunk b2g-desktop is the correct behaviour of:
- I am immediately bounced to the Mozilla SSO thing, there is no Google auth page.  (Yay!)
- I have to re-enter my e-mail address on that page for some reason (boo! but clearly not our fault since we told Google the address and it's just a question of it not getting propagated.)
- I enter that stuff and hit okay or whatever, and then I end up at the Google page to confirm the capabilities to the email app.
- The flow completes.

So I propose we land this on trunk.  Probably not on v2.1 because of the risk of getting these settings permanently wedged in there.
Assignee: nobody → bugmail
Attachment #8536640 - Flags: review?(jrburke)
Attachment #8536640 - Flags: review?(jrburke) → review+

I put a note on the pull request about how we didn't wait for the try builds because this entry is effectively inert data that's untestable.  Reiterating that, this shouldn't cause breakage.

Although I guess the Python tests could get unhappy if they're using a Mozilla zimbra account and depending on autoconfig.  I looked around in gaia/tests/python/gaia-ui-tests, particularly gaia/tests/python/gaia-ui-tests/gaiatest/tests/functional/email and didn't see any signs of being used, although it's hard to be 100% sure because the data files that control things don't live in the gaia tree as far as I can tell.  But it looks like only gmail is directly tested and then the other IMAP tests use a server on the local test network somehow.

In the event the Python tests do get unhappy, I think the right course of action is to disable the Python test in question.  Anywho, I will keep an eye on the try status.
Closed: 8 years ago
Resolution: --- → FIXED
Gip tests passed, paranoia stage over.
You need to log in before you can comment on or make changes to this bug.