Closed
Bug 819544
Opened 13 years ago
Closed 12 years ago
[email/IMAP] gmail IMAP disabled regexp does not detect IMAP being disabled at a domain level.
Categories
(Firefox OS Graveyard :: Gaia::E-Mail, defect, P4)
Tracking
(blocking-basecamp:-)
VERIFIED
FIXED
| blocking-basecamp | - |
People
(Reporter: dsubramanian, Assigned: asuth)
Details
Attachments
(3 files)
Unagi Build ID:2012 1207062543 V 1.0.0
Steps to Reproduce:
1. Go to email app
2. Set up an email account using "other email" option
3. Enter Name, email and password (eg xxxxxxxxxxxx@qanalydocs.com)
4. Sync the email acct
Actual result:
After few days tried to open emails from the acct set up. "Bad password" error msg appears with "Retry with new password button". When retry button is clicked it. It populates emails that has already been synced before. Press the "drawer icon" to go to account settings. Found last sync "!" .
Expected result:
1. Should be able to sync email from "other email".
2. Should give a proper error message as there was no sync.
3. Pressing "Retry with new password" button should have not taken back to inbox.
| Reporter | ||
Comment 1•13 years ago
|
||
| Reporter | ||
Comment 2•13 years ago
|
||
| Reporter | ||
Updated•13 years ago
|
blocking-basecamp: --- → ?
Summary: [Email] OTHER emails account SET UP gives "Bad password" error message with "retry new password" button → [Email] OTHER emails account SET UP gives "Bad password" error message with "retry new with password" button
| Reporter | ||
Updated•13 years ago
|
Summary: [Email] OTHER emails account SET UP gives "Bad password" error message with "retry new with password" button → [Email] OTHER emails account SET UP gives "Bad password" error message with "retry with new password" button
| Assignee | ||
Comment 3•13 years ago
|
||
Thank you very much for the logcat!
The adb logcat indicates:
Connect error: bad-user-or-pass formal: Error: Error while executing request: [ALERT] IMAP access is disabled for your domain. Please contact your domain administrator for questions about this feature. (Failure) on imap.googlemail.com 993
This suggests we should add a regexp detection for this case in adddition to our check for individuals which is:
'[ALERT] Your account is not enabled for IMAP use.'
Summary: [Email] OTHER emails account SET UP gives "Bad password" error message with "retry with new password" button → [email/IMAP] gmail IMAP disabled regexp does not detect IMAP being disabled at a domain level.
| Assignee | ||
Comment 4•13 years ago
|
||
er, and if it's not clear, we interpret this as a password failure because it's a reasonable guess.
Comment 5•13 years ago
|
||
BB+, P3 - user should be informed of what happened.
blocking-basecamp: ? → +
Priority: -- → P3
Comment 6•13 years ago
|
||
(In reply to Andrew Sutherland (:asuth) from comment #4)
> er, and if it's not clear, we interpret this as a password failure because
> it's a reasonable guess.
Looking at the UI, why don't we have an option for manually configuring the account if we get a bad username/password response? I really think that should be a second button, just in case we end up sending the wrong username.
| Assignee | ||
Comment 7•13 years ago
|
||
(In reply to Jim Porter (:squib) from comment #6)
> (In reply to Andrew Sutherland (:asuth) from comment #4)
> > er, and if it's not clear, we interpret this as a password failure because
> > it's a reasonable guess.
>
> Looking at the UI, why don't we have an option for manually configuring the
> account if we get a bad username/password response? I really think that
> should be a second button, just in case we end up sending the wrong username.
Can you describe the situation you are envisioning that would lead to this? We should only create accounts after successful credential validation, and e-mail servers should not be changing the username portion out from under us. This bug is certainly not an example where manual configuration would make sense.
Comment 8•13 years ago
|
||
(In reply to Andrew Sutherland (:asuth) from comment #7)
> Can you describe the situation you are envisioning that would lead to this?
> We should only create accounts after successful credential validation, and
> e-mail servers should not be changing the username portion out from under
> us. This bug is certainly not an example where manual configuration would
> make sense.
Oh, is this a screen we get *after* setup? I thought the setup screen had changed. Nevermind!
Comment 9•12 years ago
|
||
This sounds like an edge case for the target audience. Minus'ing, thanks.
blocking-basecamp: + → -
Priority: P3 → P4
| Assignee | ||
Comment 10•12 years ago
|
||
Fixing this as part of bug 816039.
Assignee: nobody → bugmail
Status: NEW → ASSIGNED
| Assignee | ||
Comment 11•12 years ago
|
||
This is now fixed. This was done in https://github.com/mozilla-b2g/gaia-email-libs-and-more/pull/99 as part of bug 809552.
Note that we give the same error as if it was a single-user account with IMAP disabled. Presumably the gmail UI will tell them they need their administrator to turn IMAP on or something like that.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 12•12 years ago
|
||
Resolved - verified on Unagi build 20130102070202
Comment 13•12 years ago
|
||
no repro in build 20130112070202 for Unagi -shown message "You must enable IMAP for your Gmail account"
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•