Thanks. I don't have the notifications set up, but the mail icon shows unread messages.
I'll delete my account and start fresh.
Thanks
I'm an Exchange Admin and yeah, this has been a thorn in my side both personally and professionally.
Not sure what's causing it, never had complaints from iOS 6 users, but with iOS 7, having this issue.
Here's a couple steps I did to identify when the issue is happening:
- User is setup in a purely Exchange environment.
- Exchange Server 2013 w\ Update 2 applied.
- User gets email notification on iPhone first, desktop second (odd, but the way it seems to work).
- If the user opens the email on their desktop, it's marked read on their desktop\server, but not on their iPhone.
- If the user deletes the email on their desktop, it's deleted on the desktop\server, however remains on the phone until they unlock their phone and open the email app.
- Same issues persist when I setup a user as IMAP.
EDIT: Furthermore, on a personal experience note, iOS 7 seems to have a bothersome glitch with mail in general where the badge doesn't go away even when a message is opened and closed in the mail app, clearly marked as read in the app, but the badge still persists until the email is opened a second or third time, or until the Mail app is killed and reopened and the message re-read.
Troubleshooting steps I've gone through:
- Completely deleted and purged user Exchange account, and issue persists
- Had user turn off auto-lock and leave their phone on, and issue persists
- Had user try deleting email in OWA and issue persists
Not sure what more can be done at this point. My observation is that the issue is Apple's Mail app isn't communicating in the background. Maybe it has to do with iOS 7 managing what apps can do in the background, but Mail certainly shouldn't be limited, especially since it's on an Exchange Server, and in my opinion, email is the most important communication to the device.
If anyone else has found anything that might point to isolation of the issue or a possible work-around, please let me know. I've submitted the issue to both Apple and MS, but experience tells me they don't react quickly, so this may be an issue we have to live with for a while.