Closed
Bug 1089132
Opened 10 years ago
Closed 10 years ago
Yandex mail: unable to connect to server
Categories
(Firefox OS Graveyard :: Gaia::E-Mail, defect)
Firefox OS Graveyard
Gaia::E-Mail
Tracking
(b2g-v2.1 verified, b2g-v2.2 verified)
VERIFIED
FIXED
People
(Reporter: krisko210, Assigned: asuth)
References
Details
Attachments
(3 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:32.0) Gecko/20100101 Firefox/32.0 Build ID: 20140925003805 Steps to reproduce: Configure new account for yandex.com email server (either automatical, or manual setup). Actual results: No mails are displayed. Mail sending works. When trying to sync emails I get: Unable co connect to server Expected results: Emails should be listed.
maybe related to this issue? http://www.sraoss.jp/pipermail/sylpheed/2012-November/005441.html
Assignee | ||
Comment 2•10 years ago
|
||
Can you provide a logcat as described at https://wiki.mozilla.org/Gaia/Email/RequiredBugInfo? This will help us identify what is going wrong. Thanks!
Flags: needinfo?(krisko210)
Assignee | ||
Comment 3•10 years ago
|
||
Also if you could please indicate the exact version of Firefox OS you are using.
Device: Firefox Flame OS Version: 2.2.0.0-prerelease (mozilla-central-flame-kk) Build Id: bc168c17 (latest build) Confirm the net connection is working: yes, other accounts work properly e-mail domain yandex.com
Flags: needinfo?(krisko210)
this log is from: adb logcat -v time -s GeckoDump:V Gecko:V GeckoConsole:V OomLogger:V | tee mail_dump.txt I was unable to get any log file from SecretDebugMode...
Same problem in 2.1 aurora: Device: Flame Version: 2.1.0.0-prerelease (mozilla-aurora-flame-kk) Build: 154da5e1 (2014-11-05 00:09:18)
Summary: Yandex mail: unable co connect to server → Yandex mail: unable to connect to server
Assignee | ||
Comment 7•10 years ago
|
||
Thanks for the log! I've also created a testing account and looked into this further. When syncing I do see the reported problem. We're sending: W6 UID SEARCH NOT DELETED SINCE "1-Jan-1990" and we're getting back W6 Command syntax error. If I manually run the command without the quotes, it works. RFC 3501 explicitly dictates that it's fine for dates to be enclosed in double-quotes in the grammar, although the example does not use them. I suppose we'll be enhancing imap-handler to not generate the quotes in this case. A separate issue observed during testing: When adding the account, I experienced a "NO" response to my attempt to LOGIN. The human-readable payload was "Imap activation in progress. Try later." followed by an "sc=" tag with something that looks like an alphanumeric hash. It did work again the next time I tried.
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → bugmail
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Assignee | ||
Comment 8•10 years ago
|
||
Patch for the date quoting issue provided to upstream at https://github.com/whiteout-io/browserbox/pull/42 I also ran into a mimefuncs bug since Yandex likes to say the charset is "x-unknown" when not specified (or when the IMAP server screws up in parsing the message body). The pull request for that is https://github.com/whiteout-io/mimefuncs/pull/8 I'm speculatively rolling both fixes into the omnibus patch.
Depends on: 1097421
This bug is now fixed, thanks for your help.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Comment 10•10 years ago
|
||
Yes, fixed on trunk with bug 1097421 with commit https://github.com/mozilla-b2g/gaia-email-libs-and-more/commit/ba3b6c9b977aa0d10b22273d350bb240e83865d0, v2.1 uplift coming soon. Marking verified since you tested it. Thanks for doing so and commenting to that effect!
Status: RESOLVED → VERIFIED
status-b2g-v2.1:
--- → affected
status-b2g-v2.2:
--- → fixed
Resolution: WORKSFORME → FIXED
Assignee | ||
Comment 11•10 years ago
|
||
Oops, rather, commit https://github.com/mozilla-b2g/gaia-email-libs-and-more/commit/78c12236670342c54a7ce7f0f0efa609cd4cda36
Assignee | ||
Comment 12•9 years ago
|
||
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
Comment 13•9 years ago
|
||
This issue has been verified successfully on Flame 2.1,2.2 See attachment:Verify_image.png Reproducing rate: 0/5 Flame 2.1: Gaia-Rev 73be51f998031f06db0cd660c0e388fa621c9f4c Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/05dd053f1d90 Build-ID 20150103001211 Version 34.0 ------------------- Flame 2.2: Gaia-Rev 698e6e8a098cc060b26cd6f25171633c4c7e739d Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/57e4e9c33bef Build-ID 20150103010205 Version 37.0a1
You need to log in
before you can comment on or make changes to this bug.
Description
•