Reply to thread

Message: [QUOTE="Robertson, William L, post: 6757341"] I have a user with a problem that I've replicated on my own machine. User running Mac OS 10.5.5, Entourage 2008 with all patches installed. Our Exchange server is Server 2003, running on a Win XP box. His Exchange account is configured to connect to the Exchange server via OWA. User moves messages from his Sent Items folder to various folders elsewhere within his Exchange mailbox. Typically he does this at the end of the day. Then he goes home, using another similarly configured Mac, opens Entourage and the messages are not where they're supposed to be, but back in the Sent Items folder. In trying to troubleshoot this, we would move a message, manually Synchronize Now both the Sent Items folder and the target folder, then quit Entourage. We then used Safari to connect to his Exchange account via OWA. The message would still be in Sent Items, but there would also be a copy in the target folder. On my own machine I replicated this problem. With further testing, it appears that it may be that the manual Synchronize Now command may not do what it says it's doing. Here's why I think that: I open Entourage and move a message from my Sent Items folder to another folder in my Mailbox. I manually sync both the Sent Items and the target folders. In both cases, the message displays at the bottom of the window that the folder is syncing. I close Entourage. I open Safari and connect to my Exchange account. The message I moved is in both the Sent Items folder and in the target destination folder. I log off of OWA and quit Safari. I open Entourage. As usual, it goes through a sync process on all the server folders, including, as I watch, the Sent Items and the target folder. When that finishes, the message I moved is only in the target folder, no longer in the Sent Items folder. This suggests to me that the Synchronize Now command isn't doing what it's supposed to be doing. What is the process behind the scenes governing synchronization with the server? Is there a time lag issue here? [/QUOTE]

Verification