IMAP Inbox updates fail after successful initial setup with Hushmail [answered]

Tracked by Jolla (In progress)

asked 2014-02-05 11:56:39 +0200

Jollabullad
126 ●4 ●8 ●11

updated 2015-04-16 18:58:52 +0200

I have issues with fetching and sending email from my Hushmail account (IMAP) using Jolla Email App. The initial setup will fetch the content of the inbox correctly, but after that any subsequent update will fail with "Problem with Sync". <strikethrough>Sending email is also a no go</strikethrough>. The same settings for both for my desktop PCs and the Maildroid (android) app installed to my Jolla device from Yandex store.

Update #10: Updated to 1.1.4.28 (Äijänpäivänjärvi)(early access). Enabled hushmail account. No changes. Did not do a complete account reinstall this time either.

Update #9: Updated to 1.1.2.15 (Yliaavanlampi) (early access). Enabled hushmail account. No changes. Did not do a complete account reinstall this time either.

Update #8: Updated to 1.1.1.27. No changes.

Update #7: Updated to 1.1.0.39. No changes.

Update #6: Updated the device to opt-in latest firmware 1.1.0.38 (Uitukka). Enabling the Hushmail email account and selecting Update from the pulley still results in 'Problem with Sync'. Also observed that when going to an individual sub folder, the initial sync from the folder will fetch all the emails currently in the folder, but any attempt to select 'Update' from the pulley menu also results in 'Problem with Sync'.

I have not deleted and recreated the email account after update #5 even when I have updated the firmware, as the release notes have not indicated anything email related that would have warranted that, atleast from my point of view with no better knowledge of any internal changes. I will recreate the account upon request, but only if a dev can point out that it would actually be of any use at this time.

Update #5: Updated the device to latest firmware 1.0.7.16 (Saapunki) and recreated the hushmail account once again. Initial setup still works, sending email works, requesting inbox update still results in 'Problem with Sync'. Latest message server log attached.

Messageserver log 2014-06-10 (http://pastebin.com/pcqKwAiu)

Account created around 15:56, initial hushmail inbox fetch was already done when I started the email application at 16:09 so I sent an email to test outgoing email, around 16:13 I sent email to ACCOUNT@hushmail.com from another email address to test fetching updated inbox, waited until the log was appended by the system around 16:17.

Update #4: Updated the device to latest firmware 1.0.5.16 and recreated the hushmail account again. Initial setup is ok, after that all update requests from the pulley menu fail with 'Problem with sync'. So no change here.

Messageserver log 2014-04-15

First pulley update request around 14:42, update request for other email account at 14:46, another pulley update for hushmail account at 14:48 and after that I just left the device idle for a long time, it seems to have done automatic email checks and stuff.

Update #3: As per request, performed the recreation of the account and the pulley update to get better logs.

Messageserver log 2014-03-19

Journalctl log 2014-03-19

Update #2: Updated device to 1.0.4.20 (Ohijärvi) and recreated the account using the original method. Same outcome, fetching email fails after initial success.

Messageserver log 1.0.4.20

Journalctl log 1.0.4.20

I am using latest update 1.0.3.8 (Naamankajärvi).

Edit: The SSL issue was misconfiguration based on Hushmail documentation insisting on using SSL instead of TLS in port 587. Removed SMTP SSL part from the title.

I have included links to relevant logs uploaded to pastebin and also a detailed step by step instruction how to reproduce / what happened on screen.

When I request an update via the pulley, the server tells us that there are new messages:

[2200] Feb 04 22:53:26 [Debug] IMAP : "2" RECV: * OK [UNSEEN 36] mailbox contains unseen messages

However the process fails for some reason and the new email is not fetched.

SMTP seems to fail because of an SSL issue:

[2200] Feb 04 22:49:26 [Warning] socketError: 13 : "Error during SSL handshake: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol"

I am not running anything mission critical with the device at the moment so I can assist with futher testing, if needed (the hushmail account requires purchased desktop version to allow IMAP/POP). My laptop did not behave this morning, so no wireshark logs, will try to provide if needed.

Thanks.

Detailed setup, update and new email description

messageserver log

ag-tool log

journalctl log

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by Jollabullad
close date 2015-05-23 18:50:45.510625

Comments

Same issue over here with my Hushmail account. Was disappointed this was not corrected in 1.0.3.8. This is the only issue that prevents me using my Jolla as my everyday phone.

PJW_2273 ( 2014-02-05 12:15:50 +0200 )edit

@PJW_2273 - Sorry was not aware of such issue.

@Jollabullad - Are you sure you have SSL over 587 ? Normally that's for TLS, error is clear it can't do the SSL handshake since the server says it's not supported.

VDVsx ( 2014-02-05 18:06:28 +0200 )edit

@VDVsx: yes, it seems that changing this to TLS fixes the SSL sending issue.

Hushmail documentation actually instructs to use SSL instead of TLS with this port:

I thought I had tested this combination too, but perhaps that was for 1.0.2.x firmware or there was something else wrong with that combo. Anyway, I am happy that that part is working :)

I'll correct the title.

Jollabullad ( 2014-02-05 19:16:18 +0200 )edit

I first raised this issue with this question https://together.jolla.com/question/7744/bug-imap-sync-works-once-then-fails/ which was closed as a duplicate of known issues despite my concern it was not.

I was not able to clarify the issue as well as @Jollabullad - I don't have the knowledge, and no help was offered as to how to troubleshoot. Hopefully with these logs and details the issue has the possibility of being resolved in a future release

PJW_2273 ( 2014-02-06 09:42:24 +0200 )edit

For reference here are the hushmail settings:

IMAP server hostname and port

IMAP server Server hostname: imap.hushmail.com Port number: 993 SSL: Enabled

SMTP server hostname and port

Server hostname: smtp.hushmail.com Port: 25 TLS: Enabled

Alternate SMTP server 1 Server hostname: smtp.hushmail.com Port: 587 SSL: Enabled (instead of TLS)

Alternate SMTP server 2 Server hostname: smtp.hushmail.com Port: 465 SSL: Enabled (instead of TLS)

PJW_2273 ( 2014-02-06 09:48:55 +0200 )edit

answered 2015-02-24 15:16:43 +0200

VDVsx

3840 ●25 ●84 ●62

https://twitter.com/VDVsx

Started investigating this issue since a kind user borrow me a premium account(Thanks again). After checking the code and the RFC[1] it seems to be a server bug, as far as I can tell, related to QRESYNC, the server always abruptly closes the connection after accepting a valid SELECT command from our client, if I disable QRESYNC it works fine, but the server is advertising this capability so it should work or should not be advertised. I've contact Hushmail about this via their regular contact form, let's see if I ever get a reply. I know that QRESYNC is not widely used and very few clients have support for it, but I don't want to disable it all together since several other providers use it and it works fine with our client.

[1] - https://tools.ietf.org/html/rfc7162

edit flag offensive delete publish link

Comments

@VDVsx Ok, cool. Let's hope they are co-operative. We, the paying hushmail customers, can/should also contact them if they do not reply.

Jollabullad ( 2015-02-24 17:35:29 +0200 )edit

Actually sent a link to this page to Hushmail.com with a more detailed description than "plz see this link". Perhaps this helps to get some attention from them.

Jollabullad ( 2015-02-24 21:06:27 +0200 )edit

They replied back asking for more logs, so seems to be proceeding well. Thanks.

VDVsx ( 2015-02-25 09:06:54 +0200 )edit

@VDVsx I sent a follow up email to Hushmail. I referenced this page. There response was

I'm not sure if we ended up receiving those logs or not. Like I said though, as far as I know, we are not working on compatibility with that mail program. Could you please follow-up with the individual who requested the logs.

mad_dev ( 2015-04-21 17:55:43 +0200 )edit

@mad_dev - I send them the logs and followed back, they replied devel team didn't had time to investigate yet. I can reproduce this problem with other email program with QRSYNC enabled and I send them prove that is their server not complaining to the specs, so far no response. I'm happy to share this data with you just send me a email to mail-logs at jolla dot com.

VDVsx ( 2015-04-24 09:56:36 +0200 )edit

IMAP Inbox updates fail after successful initial setup with Hushmail [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by Jollabullad
close date 2015-05-23 18:50:45.510625

Comments

2 Answers

Comments

Comments

Question tools

Stats

Related questions

IMAP Inbox updates fail after successful initial setup with Hushmail [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by Jollabullad close date 2015-05-23 18:50:45.510625

Comments

2 Answers

Comments

Comments

Question tools

Public thread

Stats

Related questions

The question has been closed for the following reason "the question is answered, an answer was accepted" by Jollabullad
close date 2015-05-23 18:50:45.510625