User Agent: Mozilla/5.0 (Windows NT 5.1; rv:33.0) Gecko/20100101 Firefox/33.0 Build ID: 20141113143407 Steps to reproduce: 1.Apply for a mailbox. 2.Email suffix for:firstname.lastname@example.org Actual results: 1.Use SMTP to send mail no problem, IMAP email has a problem 2.Using ACTIVESYNC send mail no problem, receive mail only mail title no content. Expected results: NETC. FR mailbox can receive email,IMAP email no problem.
Hi Do those bug 1100693 or 1100694 have the patch to fix it? Thanks!
There is no patch for this yet, I believe :dveditz was just de-duping bugs so we can just use one to track a fix. The docs, when going netc.fr, which redirects to net-c.com, indicate the service supports IMAP connections, not ActiveSync: http://www.net-c.com/netc/en/imap4-pop3-client-access.php So we should dig into the problem the IMAP pathway had, and avoid the ActiveSync pathway. To do this, it is really helpful if you can attach a capture of the logcat from the device when the error seems to occur, info for how to do that is here: https://wiki.mozilla.org/Gaia/Email/RequiredBugInfo
It looks like there are multiple things going on here: - The UIDNEXT prober problem for v2.1/v2.2 happens (bug 1093467). - Seeing an INTERNALDATE parse failure on trunk it looks like; specifically, seeing error: WWAR: message problem, skipping message Error: Not a good IMAP date-time: 20-Nov-2014 04:57:56 exports.parseImapDateTime@app://email.gaiamobile.org/js/ext/composite/configurator.js:10356:1 exports.chewHeaderAndBodyStructure@app://email.gaiamobile.org/js/ext/composite/configurator.js:10141:34 Sync.prototype._handleNewUids/</<@app://email.gaiamobile.org/js/ext/imap/protocol/sync.js:170:27 Sync.prototype._handleNewUids/<@app://email.gaiamobile.org/js/ext/imap/protocol/sync.js:158:1 BrowserBox.prototype.listMessages/<@app://email.gaiamobile.org/js/ext/composite/configurator.js:6511:1 BrowserBox.prototype.exec/<@app://email.gaiamobile.org/js/ext/composite/configurator.js:6072:17 ImapClient.prototype._processServerResponse@app://email.gaiamobile.org/js/ext/composite/configurator.js:5592:24 ImapClient.prototype._processServerQueue@app://email.gaiamobile.org/js/ext/composite/configurator.js:5535:1 Which means the server has decided not to include timezone information. Which is awkward but not the world, given that many servers just provide +0000 and we can assume that in the case that the value is missing. I'll tentatively fold this into the omnibus patch.
Assignee: nobody → bugmail
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Er, awkward but not the end of the world. I'll stop ignoring my hunger pangs and go eat something so my brain can work more betterish.
Implemented and tested as part of the omnibus upgrade. (Since we also experience the UIDNEXT problem and the createFolder problem, I think it makes sense to lump this in.)
Depends on: 1097421
Summary: [OPEN_C]NECT could not successfully received the mail → [email/IMAP] Handle missing timezone for INTERNALDATE date-time, as generated by netc.fr / net-c.com
Fixed as part of bug 1097421's omnibus patch. Many servers were experiencing more than one bug, and we had experienced some upstream drift, and especially for uplift tracking, it made sense to land these together. See the gaia-email-libs-and-more pull request's specific commits for the specific fixes and tests. I am planning to request v2.1 uplift shortly after performing v2.1 testing.
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
status-b2g-v2.1: --- → affected
status-b2g-v2.2: --- → fixed
Resolution: --- → FIXED
Batching marking v2.1 fixed since the uplift of bug 1097421 occurred on Dec 9th, thereby fixing all dependent bugs of bug 1097421 on v2.1. Uplift commit comment is https://bugzilla.mozilla.org/show_bug.cgi?id=1097421#c6
status-b2g-v2.1: affected → fixed
You need to log in before you can comment on or make changes to this bug.