STR： 1. Open the Email app. 2. Load on the 126 mailbox. 3. Refresh the inbox. 4. Send an email, then have tone to prompt having sent successfully. 5. Check the sent folder. OBSERVED: 9. Display no email EXPECTED: 9. Display the email normally.
Summary: [tarako][SMS]Can't add the attachment of video from camera into MMS when automatic recording to stop → [dolphin][email]Unable display mail normally after loading on the 126 mailbox.
The sent message is asynchronously appended to the sent folder on non-gmail IMAP servers. The message should show up following successful appending and refreshing. It's conceivable there is some problem in appending on the 126 mailbox, however. Please provide a logcat; instructions are available at https://wiki.mozilla.org/Gaia/Email/RequiredBugInfo
I've marked comment 2 private because it includes credentials. In bug 951076 we forced 163.com to use IMAP since 163.com's ActiveSync implementation did not work well with our ActiveSync implementation, but their IMAP implementation was okay. Looking at the DNS MX entries for 126.com, it appears that it's the same mail provider... specifically, both MX entries map to sub-domains of mxmail.netease.com Based on bug 951076, it seems like we need to add additional autoconfig entries to force us to avoid using ActiveSync for 126.com. Are you aware of other domains operated by netease that we should likewise configure to force to IMAP? Unfortunately, because of our autoconfig heuristics, AutoDiscover will result in us not contacting our ISPDB to perform a DNS MX lookup, so just adding a local autoconfig for the netease.com/mxmail.netease.com wouldn't be sufficient. If netease operates a large number of mail domains, it might make sense for us to blacklist things at a lower level, especially if there's a distinctive characteristic put forth during autoconfig. But if it's just a few domains, just adding the autoconfig entries is probably the safest, especially if we need to uplift to older versions.
I have test qq mailbox, and sina mailbox. they both can't login success through ActiveSync AutoDiscover process. I doubt the Autodiscover can work well. I suggest we should follow android's logic, if we did not autoconfig the mailbox, we should give user a hint to configure the Email manually. BTW: if you have any problem, you can need info for me instead of chaochao. thanks.
I've filed bug 1048677 about checking what the Android email client is doing differently than us for ActiveSync. If you or others are able to spend some time to understand what's happening differently, it would be definitely be appreciated. The source for our ActiveSync implementation can be found at https://github.com/mozilla-b2g/jsas/tree/worker-thread and it can run tests/experiments from within Firefox (desktop) itself. For the specific servers in question, it still might make sense for us just to add local autoconfig entries to configure the servers for IMAP. All three appear to have IMAP servers (imap.126.com, imap.qq.com, and imap.sina.com), and all three seem to have valid SSL certificates although imap.sina.com seems misconfigured to only provide the final certificate and not the entire certificate chain from the Geotrust root that it should be providing. As a result Firefox OS gives a security error on imap.sina.com. For imap.sina.com, it would be good if we could contact them to let them know about their misconfiguration. There seems to be some contact info at http://www.sina.com.cn/contactus.html but I only speak English and Google Translate is not working as well as I'd hope; I may be able to get someone in our Taiwan or China offices to help me out with trying to contact them to address their configuration issue.
(In reply to yong.ren from comment #4) > I have test qq mailbox, and sina mailbox. they both can't login success > through ActiveSync AutoDiscover process. I doubt the Autodiscover can work > well. I suggest we should follow android's logic, if we did not autoconfig > the mailbox, we should give user a hint to configure the Email manually. > > BTW: if you have any problem, you can need info for me instead of chaochao. > > thanks. Thank you Andrew. I will do some tests and ask beijing BD team to help on contacts them to fix their servers.
BTW, for sina.com, we can use pop3+SMTP to configure, and stmp.sina.com port number should be 25. As mentioned by Andrew, the imap.sina.com server is configured in a wrong way. Even Android and iOS will fail on this.
Firefox OS is not being worked on
Status: NEW → RESOLVED
Last Resolved: 5 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.