GNOME Bugzilla – Bug 737082
Geary does not support Yandex Mail IMAP server
Last modified: 2014-10-30 02:20:40 UTC
Yandex has a good free webmail system here: http://mail.yandex.com. IMAP/SMTP is also available at imap.yandex.com/smtp.yandex.com, but Geary has problems showing mailbox contents. There's a message "No conversation in folder" for each mailbox I choose in the left panel although the mailbox list and unread counts are ok. Mozilla Thunderbird, all versions of Outlook, Apple Mail and many other clients work fine with Yandex Mail. Logs have this: [deb] 21:44:51 19,256724 geary-controller.vala:1199: Folder Other:kappa@yandex.com:INBOX selected [deb] 21:44:51 0,000021 geary-controller.vala:1247: Switching to Other:kappa@yandex.com:INBOX... [deb] 21:44:51 0,036458 imap-engine-minimal-folder.vala:463: wait_for_open_async Other:kappa@yandex.com:INBOX: opening remote on demand... [deb] 21:44:51 0,000038 imap-engine-minimal-folder.vala:557: Fetching information for remote folder Other:kappa@yandex.com:INBOX [deb] 21:44:51 0,000085 imap-engine-minimal-folder.vala:561: Opening remote folder INBOX [deb] 21:44:51 0,000032 geary-controller.vala:1335: Switched to Other:kappa@yandex.com:INBOX [deb] 21:44:51 0,000107 app-conversation-monitor.vala:316: ConversationMonitor seeding with local email for Other:kappa@yandex.com:INBOX [deb] 21:44:51 0,000166 [0000/213.180.204.124:993/GEARY_IMAP_CLIENT_CONNECTION_STATE_CONNECTED S] a076 select INBOX [deb] 21:44:51 0,021592 app-conversation-monitor.vala:322: ConversationMonitor seeded for Other:kappa@yandex.com:INBOX [deb] 21:44:51 0,104877 [0000/213.180.204.124:993/GEARY_IMAP_CLIENT_CONNECTION_STATE_CONNECTED R] * FLAGS (\Answered \Seen \Draft \Deleted $Forwarded) [deb] 21:44:51 0,000143 imap-client-session.vala:1568: [0000/imap.yandex.com/default:993 GEARY_IMAP_CLIENT_SESSION_STATE_SELECTING] Received bad response * 949 EXISTS: Unknown server response: * 949 EXISTS [deb] 21:44:51 0,000016 [0000/213.180.204.124:993/GEARY_IMAP_CLIENT_CONNECTION_STATE_CONNECTED] recv bad response * 949 EXISTS: Unknown server response: * 949 EXISTS [deb] 21:44:51 0,000135 imap-folder.vala:222: INBOX RECENT 7 [deb] 21:44:51 0,000019 [0000/213.180.204.124:993/GEARY_IMAP_CLIENT_CONNECTION_STATE_CONNECTED R] * 7 RECENT [deb] 21:44:51 0,000176 [0000/213.180.204.124:993/GEARY_IMAP_CLIENT_CONNECTION_STATE_CONNECTED R] * OK [UNSEEN 13] [deb] 21:44:51 0,000300 [0000/213.180.204.124:993/GEARY_IMAP_CLIENT_CONNECTION_STATE_CONNECTED R] * OK [PERMANENTFLAGS (\Answered \Seen \Draft \Flagged \Deleted $Forwarded \*)] Limited [deb] 21:44:51 0,000190 [0000/213.180.204.124:993/GEARY_IMAP_CLIENT_CONNECTION_STATE_CONNECTED R] * OK [UIDNEXT 29626] Ok [deb] 21:44:51 0,000181 [0000/213.180.204.124:993/GEARY_IMAP_CLIENT_CONNECTION_STATE_CONNECTED R] * OK [UIDVALIDITY 1304433998] Ok [deb] 21:44:51 0,000230 [0000/213.180.204.124:993/GEARY_IMAP_CLIENT_CONNECTION_STATE_CONNECTED R] a076 OK [READ-WRITE] select completed [deb] 21:44:51 0,000114 imap-engine-minimal-folder.vala:123: Other:kappa@yandex.com:INBOX: Begin normalizing remote and local folders [deb] 21:44:51 0,000011 imap-engine-minimal-folder.vala:139: Other:kappa@yandex.com:INBOX: Unable to verify UIDs: missing remote UIDNEXT (true) and/or UIDVALIDITY (true) [deb] 21:44:51 0,000064 imap-engine-minimal-folder.vala:582: Unable to prepare remote folder Other:kappa@yandex.com:INBOX: normalize_folders() failed [deb] 21:44:51 0,000159 [0000/213.180.204.124:993/GEARY_IMAP_CLIENT_CONNECTION_STATE_CONNECTED S] a077 close [deb] 21:44:51 0,054263 [0000/213.180.204.124:993/GEARY_IMAP_CLIENT_CONNECTION_STATE_CONNECTED R] a077 OK close complete
It's working for me. What IMAP/SMTP settings are you using?
imap.yandex.com:993 SSL/TLS smtp.yandex.com:587 STARTTLS I suppose, the result is dependent on mailbox contents then. So I provided logs. Any other information I could add?
The key line in your log file is this: Unable to verify UIDs: missing remote UIDNEXT (true) and/or UIDVALIDITY (true) This means some pretty important (and required, according to the IMAP spec) information was not sent from the server. I'll need you to send me a full network trace to go further. Please run Geary like this from the console: $ geary --debug --log-serializer --log-deserializer > geary.log Since this will contain sensitive personal information, I suggest looking through it and editing out anything you don't want to transmit to me. In particular, your password will be in this file. Please mail to geary@yorba.org, don't post it here. Thanks!
Done, thanks. Some points I noticed: 1) Looks like Geary does not recognize our untagged CAPABILITY response. 2) Same for UIDNEXT/UIDVALIDITY item in STATUS responses. 3) Same for untagged EXISTS response after SELECT. 4) And UIDNEXT/UIDVALIDITY responses after SELECT are somehow recognized but ignored.
(disclosure: I work for Yandex and am able to help from the other side)
This is a duplicate of a long-standing bug. Please see it for more information. *** This bug has been marked as a duplicate of bug 714892 ***