To all those saying "this worked," has this been a permanent fix for your mailbox?
I myself am an Exchange user on a hosted exchange plan with Go Daddy on Exchange Server 2013 I believe.
I continually get "Unread" messages mainly in the "Junk Mail" folder, but occasionally it starts in the "Trash" folder as well. Over time, this number continues to accumulate and I will see the number as a notification in the folder tree. It is extremely annoying.
I agree that turning Mail off, resetting, and turning it back on clears this up. Temporarily.
The first time I accumulate a decent number of unread messages again in Junk, whether I swipe and delete them or Edit/Trash All, The middle of the display will show "No Mail" but there will be unread messages again. The fix may stick for a short while, but the glitch always returns.
I have tried with the account set to push to the affected folders, as well as fetch or manual. This glitch can surface again even when deleting all my Junk Mail directly from my Outlook 2016 client. Same when I was on Outlook 2013 and even Outlook 2010. As soon as I return to iOS mail and the Junk Mail or other folder "syncs up," bam Unread Messages may return.
At this point I am convinced this is a LONG STANDING issue with iOS Mail on Apple's side. Seeing users suffering this with Gmail, Yahoo, and other services, It is not an Exchange or hosting issue. None of my other email clients show these phantom unread messages, only iOS mail. SOmething gets stuck in cache or similar and can only be fixed by toggling the account and refreshing it.
In my case, the issue always returns. I am curious if that is the same for all. It is a nice workaround, but if you cannot live with the unread messages count showing in the folder tree it is frustrating to need to do this every couple of days to keep the number low or accurate.
I am tempted at this point to ditch iOS Mail app and maybe use Outlook. For whatever reasons, I have always preferred the default app but this is ridiculous already. THis thread started what, over 4 years ago? FIX IT APPLE!
I am good at testing and resolving issues like this but so far I myself am struggling to find anything other than what has already been mentioned, both on my own and by digging through the interwebs.
Should any of you want to try and tackle this as a team, just post and I will join in. I have been quietly lurking and following this topic for some time. I will still be watching and ready to jump in head first.
Let's either get this fixed or help Apple actually fix it. Fingers crossed for iOS 10. Has anyone here been using iOS 10 already and able to confirm whether or not this problem still manifests? Thanks for reading and any future conversation.