IMAP Error unexpected end of network stream

[pipars]

Hello, I am proud owner of AquaMail app and would like to mention that I love this email client.
Yesterday, I decided to switch my accounts from POP to IMAP on HTC One M9 Android. All went well.

Now, this morning I found myself on the Bell (Canada) mobile network and realised that none of my accounts are synchronised. I first suspected the firewall on the server and finally turned it off completely, but this didn't help. For some reason, all works perfectly fine from home landline internet, but not from mobile network. (POP still works fine everywhere). The only difference I could find is that on the mobile network my device has IPv6 and I guess connects from IP6 network to my IP on the server. (server does not have Ipv6 address)

The error message in the debug log says "unexpected end of network stream". If I try to create an account on the mobile network it would not let me with the same error message. So, I thought that the issue might be in the fact that somehow it will not work from Ipv6 network.

Just now I decided to see what will happen if I create the same account from the native HTC email client. ... and it worked fine on the mobile network. So, I am now suspecting that this is something that can probably be fixed in Aqua-Mail?

Thank you. Any help appreciated.

[pipars]

Thanks for replying.
There isn't much to change on the mobile network (at least no access to fine tune it). And it works fine on wifi.

[Kostya Vasilyev]

1 - Aqua Mail's mail sync / network code doesn't care what type of connection it is, whether you're in Canada or Mozambique, if your mobile data is LTE or EDGE, etc....

2 - Different mail apps are completely free to use different IMAP commands, nothing wrong with Aqua Mail's that I'm aware of

3 - Unexpected end of network stream means the network connection was aborted while the app was expecting response to a command it had sent.

- Could be a network issue (I'd bet on this one since same commands are executing just fine for you if the device is connected to WiFi)

- Or could be a server issue (can't deal with some command and aborts the network connection, and it's on mobile data only because of load balancing and server versions differ between the two).

If you wish to capture the issue in the app's debug log, the instructions are linked in my signature just below.

[pipars]

The issue "auto-resolved" itself . So .. I guess there was something with the mobile network.