Closed
Bug 1163929
Opened 10 years ago
Closed 10 years ago
[FFOS7715 v2.1s] [E-Mail] Cann't delete email messages in local drafts with qq email account
Categories
(Firefox OS Graveyard :: Gaia::E-Mail, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ffos_st, Unassigned)
References
Details
(Whiteboard: sprd434303)
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:40.0) Gecko/20100101 Firefox/40.0
Build ID: 20150503030209
Steps to reproduce:
Steps to reproduce:
Description: Cann't delete messages in local drafts with qq email account.
Device: SPRD 7715ea
Build Identifier: 20150512161136
Steps to Reproduce:
1) open E-Mail app, input Your name and qq email, then click Next;
2) select ActiveSync in Account type, then input Password, input ex.qq.com in Hostname textview, and input any character in Domain\Username textview, then click Next, Continue to Mail;
3) write a email message, and save to local drafts, then enter local drafts, select a email message and delete;
Actual Result: The email message still exist in local drafts
Expected Result: Delete email message successfully, the email message not exist in local drafts.
Repro frequency:10/10,100%
hi ffos_st, could you provide logcat log of this issue?
Thanks
Flags: needinfo?(ffos_st)
Comment 3•10 years ago
|
||
Thank you for the log.
I think there may be a few things going on here:
1) The account creation step should be failing. The email address doesn't matter when you manually create an activesync account. The Domain\Username field's value does. We are seeing a 403 error (Forbidden) on syncFolderList, which is consistent with this. It's not clear from the log why the account creation is succeeding in this case. I am assuming the QQ server's implementation implements somewhat significantly from the spec, although it wouldn't surprise me if we are doing something slightly wrong too.
2) It looks like the draft is deleted fine, but you might need to switch away from the folder to another folder and move back to the folder to see this complete. It appears that the mutex is being held longer than it should be or something like that. I'm a little less concerned about what's going on here since it could be fallout from the failure of syncFolderList or other related problems.
One important question is whether qq.com supports IMAP and we can just add an autoconfig entry to use IMAP instead. Because if their ActiveSync implementation behaves this differently for account creation, we're probably going to have other problems even when we do create a valid account.
Hi Andrew:
There are some things we find, and think it might be help with this issue.
1. qq.com supports IMAP, and it's incoming server hostname is "imap.qq.com" and outgoing server is "smtp.qq.com"
2. though I add log to debug the activeSync circumstance, and find that
when getOptions (protocol.js) to the qq server(ex.qq.com), even we add the wrong username and password to the setAuthHeader(), the qq server can not return error code。 so we can create the account successfully. but when we foldsync the qq server, it return the 403 error.
I think this is the rootcause, does the qq server do the right thing with the getOptions request?
and could we add some extra logic to ensure the username and password being verified before create account?
Flags: needinfo?(bugmail)
Comment 5•10 years ago
|
||
:squib, any thoughts on our manual setup case letting us create an account despite the settings being gibberish? I'm sure you've forgotten more than I've ever known about ActiveSync, but hopefully what is not forgotten still exceeds my understanding :) Please feel free to brain dump anything, even if you think it might be suspect! Thanks!
yong.ren, are you able to create an IMAP account on qq.com using manual setup and the servers you mention? Does the account seem to work? Thanks!
Flags: needinfo?(yong.ren)
Flags: needinfo?(squibblyflabbetydoo)
(In reply to Andrew Sutherland [:asuth] from comment #5)
>
> yong.ren, are you able to create an IMAP account on qq.com using manual
> setup and the servers you mention? Does the account seem to work? Thanks!
yes, I am able to create it using the config I mentioned in comment4,
If you don't mind, I can supply the qq imap autoconfig to you or
push it to the gaia repo directly.
Flags: needinfo?(yong.ren)
Comment 8•10 years ago
|
||
I assume that the current ActiveSync code in GELAM will report an error if we get a 403 when we initially connect to the server, right? I'm looking here: <https://github.com/mozilla-b2g/gaia-email-libs-and-more/blob/master/js/activesync/configurator.js#L155>. I think the logic goes like this (or if not, this is how it should be):
1) Do autodiscovery if necessary (which it isn't in this case).
2) Try to connect to the server to get version info (via an OPTIONS request). This also lets us verify your credentials.
3) Get your email!
If qq is succeeding in (2) and failing in (3), then qq is broken. It's possible that qq is using some autodiscover features we don't support (e.g. DNS MX lookups? Those are part of autodiscover, right?), which would explain why autodiscover isn't working here. Fixing that *could* help with the auth issues, but I don't think it would fix the manual-config case.
I'm all for adding an IMAP config, and I'm actually somewhat surprised that the MoMo ISPDB doesn't already have qq in it. Or is Gaia email not using the ISPDB anymore?
Really, I don't think we should support *any* non-Microsoft ActiveSync server (though I don't know how to detect this). No one seems to be able to get it right, including Google. At least Google had the good sense to discontinue their ActiveSync client, although I suspect a lot of their reason for doing so was to push people onto the Gmail app.
Flags: needinfo?(squibblyflabbetydoo)
Comment 9•10 years ago
|
||
Comment 10•10 years ago
|
||
Comment on attachment 8605154 [details] [review]
[gaia] ReyCG:work > mozilla-b2g:master
Hi asuth:
please review at my pull request for qq imap autoconfig, thanks
Flags: needinfo?(bugmail)
Attachment #8605154 -
Flags: review?(bugmail)
Comment 11•10 years ago
|
||
This looks fine for our purposes, but I'd like to actually get this on the Thunderbird ISPDB that the email app consults as part of the autoconfig process so that we can change it later if we need to. This will take a few days, but since it doesn't need to go on the device, the time pressure is less.
Comment 12•10 years ago
|
||
I've landed this in the ISPDB on bug 1189051.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(bugmail)
Resolution: --- → FIXED
Comment 13•10 years ago
|
||
Comment on attachment 8605154 [details] [review]
[gaia] ReyCG:work > mozilla-b2g:master
clearing review since this landed on the other bug. (Not doing r+ to avoid confusion where this would land in gaia.)
Attachment #8605154 -
Flags: review?(bugmail)
You need to log in
before you can comment on or make changes to this bug.
Description
•