Email download problem from hmailserver using IMAP

1

Hello,
I’m using latest emclient as email client connecting to hmailserver 5.6.6-B2383.

I’m having problems when downloading the email for an offline usage (the customer use the mailbox as a repository to search into old emails) but the download stops.

Hmailserver log reports:

“DEBUG” 6224 “2017-10-11 08:58:56.491” “Creating session 3302”
“TCPIP” 6224 “2017-10-11 08:58:56.507” “TCP - 192.168.88.198 connected to 192.168.88.210:143.”
“DEBUG” 6224 “2017-10-11 08:58:56.516” “TCP connection started for session 3301”
“DEBUG” 6224 “2017-10-11 08:58:59.396” “Creating session 3303”
“TCPIP” 6224 “2017-10-11 08:58:59.404” “TCP - 192.168.88.198 connected to 192.168.88.210:143.”
“DEBUG” 6224 “2017-10-11 08:58:59.413” “TCP connection started for session 3302”
“DEBUG” 3676 “2017-10-11 08:59:07.890” “The read operation failed. Bytes transferred: 0 Remote IP: 192.168.88.198, Session: 3301, Code: 10054, Message: An existing connection was forcibly closed by the remote host”
“DEBUG” 4984 “2017-10-11 08:59:07.890” “The read operation failed. Bytes transferred: 0 Remote IP: 192.168.88.198, Session: 3292, Code: 10054, Message: An existing connection was forcibly closed by the remote host”
“DEBUG” 3676 “2017-10-11 08:59:07.901” “Ending session 3301”
“DEBUG” 4984 “2017-10-11 08:59:07.909” “Ending session 3292”

Emclient reports the following errors (errors change from time to time, they are not always the same):

08:27:48.470|03B|   A17 UID FETCH 49719 (BODY.PEEK[HEADER] BODY.PEEK[1.MIME] BODY.PEEK[1.1.MIME] BODY.PEEK[1.1] BODY.PEEK[1.2.MIME] BODY.PEEK[1.2] BODY.PEEK[2.MIME] BODY.PEEK[2] BODY.PEEK[3.MIME] BODY.PEEK[3] BODY.PEEK[4.MIME] BODY.PEEK[4])
08:27:48.524|052|   * 39505 FETCH (UID 49719 BODY[HEADER] {2172}
08:27:48.526|052|   Content-Type: text/html; charset=“iso-8859-1”
08:27:48.526|052|   Exception:
08:27:48.526|052|     Protocol violation
08:27:48.526|052|     Line Content-Type: text/html; charset=“iso-8859-1”
08:49:15.191|03B|   A46 UID FETCH 52214 (BODY.PEEK[HEADER] BODY.PEEK[1.MIME] BODY.PEEK[1.1.MIME] BODY.PEEK[1.1] BODY.PEEK[1.2.MIME] BODY.PEEK[1.2] BODY.PEEK[2.MIME] BODY.PEEK[2] BODY.PEEK[3.MIME] BODY.PEEK[3] BODY.PEEK[4.MIME] BODY.PEEK[4] BODY.PEEK[5.MIME] BODY.PEEK[5] BODY.PEEK[6.MIME] BODY.PEEK[6])
08:49:15.253|058|   * 42000 FETCH (UID 52214 BODY[HEADER] {2300}
08:49:15.308|058|   A46 OK UID completed
08:49:15.309|03B|   A47 UID FETCH 52215 (BODY.PEEK[HEADER] BODY.PEEK[1.MIME] BODY.PEEK[1.1.MIME] BODY.PEEK[1.1] BODY.PEEK[2.MIME] BODY.PEEK[2])
08:49:15.363|058|   * 42001 FETCH (UID 52215 BODY[HEADER] {792}
08:49:15.366|058|   Content-Type: application/pdf;  name=“Stampa Estratto Conto - senza scadenze.pdf”
08:49:15.366|058|   Exception:
08:49:15.366|058|     Protocol violation
08:49:15.366|058|     Line Content-Type: application/pdf;  name=“Stampa Estratto Conto - senza scadenze.pdf”

So is this a client or server problem?

Thanks

2

Is a client problem as I have the same problem with the newest version (2022).

Hope there will be a solution.

3

I would suggest putting those errors on the hMailServer forum if you haven’t already.

hMailServer forum - Index page

4

Today I found out that disabeling the NOD32 IMAP-scanner (Settings → E-mailclient → E-mail-protocols → IMAP → disable) solves the problem for me.

If any of you experience problems with the combination hMailserver and emClient, see if disabeling your virusscanner solves the problem.

1 Like
5

I can confirm the problems described by Kosternet regarding the combination Hmailserver - EM Client - Nod32 (Eset).

I assume the problem is due to the interpretation of IMAP messages by EM Client software. The Eset scanner puts some warnings in the IMAP Protocoll which causes EM Client to reject the whole connection. All other Clients I know are fine with the submitted protocoll, just EM Client is too picky and probably expects only 100% clean code.

6

@Okampmeyer

I can confirm the problems described by Kosternet regarding the combination Hmailserver - EM Client - Nod32 (Eset)

This type of thing happens with alot of other Antivirus scanning programs too such as eg: AVG, Avast etc, which are also known to interfere with eM Client receiving email and you have to usually disable the scanning part of the Antivirus program to get eM Client to receive mail.

However you can sometimes though eg: export the Antivirus program certificate and then import that certificate into eM Client to then possibly still work with Nod virus scanner enabled. Importing Antivirus certificates has worked “for some users” who had similar problems in the past.

So suggest to contact NOD technical support to see if they can assist you with doing that.

7

the problem is not due to an certificate problem which I can exclude. Noticeable is the fact that the problem arised with installation of Version 9.2 and can be reproduced on all my machines. Something in the interpretation of the IMAP protocol has been changed with version 9. Of course the problem can be solved by deactivating the imap protocol scanning or going back to version 8, which is not very satisfying.

emclient
emclient868×112 24.5 KB

Im not 100% sure whether the above snippet from the IMAP log causes the the complete malfunction, as the protocol seems to go through and is idling. Just Em Client seems to stop processing…

8

another thing I´m wondering about is the result of the diagnostic function that shows the correct functionality of IMAP, which is obviously wrong.

Something goes wierd and the user is not informed at all. The user somehow notices that no new messages arrive as a feedback. Catching malfunctions and documenting them has actually been standard for decades in IT. Just passing responsibility to someone else is easy.