AquaMail causes Outlook on desktop to not be able to mark emails as read.

[Johnathon]

I seem to have this issue on and off, but I have the issue on Outlook on both my laptop and desktop.

When my phone is on and AquaMail is running, it seems to randomly cause emails I read from my laptop or desktop through Outlook 2013 to not get marked as read. In order to get it to mark as read I have to read it on my phone through AquaMail or (sometimes) restart Outlook and it will work for that email, but will then have the problem again down the line. I have both Gmail and personal email accounts that all seem to have the issue.

I don't see others having this issue so I'm not sure if this is a bug or I just missed a setting that stops this from happening. Any help would be appreciated.

[Kostya Vasilyev]

>> not get marked as read

Where? In Outlook, Aqua, or web mail?

Please check web mail to see at what point (Outlook -> mail server or mail server -> Aqua) thing go wrong.

If it's "in AquaMail" then I might know what it is in Gmail accounts... Should be fixed in latest 1.5.5-..-dev versions (here on the forum under "Development builds", or in my G+ "beta" community):

https://plus.google.com/u/0/communities/112921486711044378404

[Johnathon]

Correct

If I read it in AquaMail it marks as read successfully. If I read it in Outlook it'll mark as read, but then go back to marked as unread when it next updates. It remains "unread" in GMail/Webmail. If I turn off my phone, Outlook stops having an issue and can mark emails as read without an issue.

[Kostya Vasilyev]

>> then go back to marked as unread when it next updates

I understand that when you see the message change in Outlook, but..

...does the change on the mail server (web mail) happen right then, or at some earlier point? You should be able to tell by having web mail open at the same time.

As for Aqua, do you use IMAP push in this account / folder? Can you try turning it off to see if it makes a difference?

And as usual, the only way for me to really investigate, rather than to throw out wild guesses, is if you captured the issue in the app's debug log (see just below).