Persistent incoming server network errors, but manual refresh fixes it?

[Kostya Vasilyev]

Re: Outlook outage
Yes, a timeout can be the reason for your problem. Also, it could be just an intermittent glitch on their server

MS has been migrating Hotmail / Outlook accounts to new servers for a few months now, and lately it seems that the pace has accelerated (judging by the "app not loading recent messages" support emails... so this is still messed up, by the way...)

[amw65]

Ah, okay, thanks. I didn't know that (change pop->imap v.v).
Thanks for the tip.
Well, right now, Aqua Mail works fine. I let Aqua Mail do the settings.
Aqua Mail is set to imap, whereas my Outlook 2013 is set to pop3.

Anyway, let's assume that it was the too frequent polls then...  :-)
(crossing my fingers it will not happen again)

Thanks again.
=

[Kostya Vasilyev]

Re: Aqua Mail is set to imap, whereas my Outlook 2013 is set to pop3

Just something to be aware of --

-- most if not all (but I'm not sure about Hotmail specifically) mail servers will "mark as read" on the server any messages fetch over POP3.

This won't affect Outlook, since POP3 does not have read/unread sync.

But IMAP does.

And messages getting changed to read -- will then sync into / update in AquaMail.

So if you see your unread messages getting marked as read in AquaMail, a bit after you've checked mail using Outlook -- then you know what it is.

To fix, if it's not what you'd like -- you can remove the account from AquaMail and add it as POP3 (using the Manual button on the account setup screen), or vice versa, remove the account from Outlook and add it back making sure to use IMAP.

With POP3 in both apps, the read/unread state of each message will be tracked by each app, independently of web mail and the other app.

With IMAP in both apps, all messages will be read/unread consistent between web mail and the apps.

[ryusoma]

hi -

I've sent in a debug log regarding this issue which I'm seeing on one of my devices as well.  The issue originally occurred last weekend, spontaneously resolved itself 2 days later, and recurred again this past weekend.

The problem seems very compartmentalized - I have two email accounts configured on a work phone using Aquamail.  Both connect to the same IMAP mail server, yet only one account appears to have this issue which has lasted 3 days now.  The account settings have not changed, the account is not locked out, and when the account is configured on my personal phone it operates correctly.  The only difference between the two is slightly different phone models (both LGs), different cell carriers, and different Cyanogenmod builds - neither of which were upgraded or changed.

On the problem phone/account, I have tried rebooting, airplane mode to stop access/timeouts, deleting and recreating the account and reinstalling the app itself.  The problem still recurs on this device.  This is getting absurd.  I can't leave this work account on my personal phone (mgmt will throw a tantrum) and the sheer volume of email per day (4 digits on a *good* day!) means it will eat my personal data plan in a week.

Any suggestion you have to mitigate the issue would be appreciated.

[StR]

I am sure, Kostya will will respond to you in regard to the debug log.
But in the mean time, - can you, please, describe the actual problem you are observing?
What is the error message that you see?

Do you have PUSH enabled?

One thought: have you asked you IT people if they changed something. E.g. if they set the IMAP server limiting the number simultaneous connections from one device (to exactly 1). In which case you might have second account not to allow connecting while the first one has not completely closed the connection yet.

As a test, try setting different sync frequencies, - where one is not just an integer factor multiple of the other one? say, 10 and 15 minutes? This way, at least at some point this will try to sync at different times.

[Kostya Vasilyev]

Yes, I've looked at the log and made a change (which I should be able to post pretty soon).

But it does look more like an issue with the mobile data provider, so I'm not even sure if the change will help or not.