PDA

View Full Version : Has Unread/Read status completely stopped working?



aphexii
Aug 19, 2008, 10:53 AM
I know that Mobile Me has never worked as expected, with the unread/read status pushing to our devices (and according to the Apple Article on the subject, its as designed for now).

Anyway, even the article notes that the read/unread status should update upon a manual 'pull' check (opening Mail on the iPhone or Send/Receive in Mail.app), but the past few days its not updating the status that way either.

Anyone else notice this?


MBHockey
Aug 19, 2008, 11:07 AM
I know that Mobile Me has never worked as expected, with the unread/read status pushing to our devices (and according to the Apple Article on the subject, its as designed for now).

Anyway, even the article notes that the read/unread status should update upon a manual 'pull' check (opening Mail on the iPhone or Send/Receive in Mail.app), but the past few days its not updating the status that way either.

Anyone else notice this?

Yep, i started a thread about this earlier this morning. Quite annoying!
xraydoc
Aug 20, 2008, 11:43 PM
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 2_0_2 like Mac OS X; en-us) AppleWebKit/525.18.1 (KHTML, like Gecko) Version/3.1.1 Mobile/5C1 Safari/525.20)

I noticed this today as well. Not only will read statuses not update, but unread counts on the iPhone are sometimes incorrect and mail deleted on my Mac will remain on the phone whereas it used to update correctly. Not sure if this is a 2.0.2 issue or a MobileMe issue - seemed to start at about the same time, though.
MBHockey
Aug 21, 2008, 12:17 AM
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 2_0_2 like Mac OS X; en-us) AppleWebKit/525.18.1 (KHTML, like Gecko) Version/3.1.1 Mobile/5C1 Safari/525.20)

I noticed this today as well. Not only will read statuses not update, but unread counts on the iPhone are sometimes incorrect and mail deleted on my Mac will remain on the phone whereas it used to update correctly. Not sure if this is a 2.0.2 issue or a MobileMe issue - seemed to start at about the same time, though.

That's interesting -- that has never worked for me at all with MobileMe.