Message status doesn't sync with exchange server

[ward.jay]

I'm using Entourage 2004 (with all the updates) to connect to my
exchange server. The server is hosted on Mailstreet.net and apparently
Entourage is using DAV to connect to the server.

The problem I'm having is that message status codes (replied,
forwarded, etc.) are not being synchronized with the Exchange server.
If I reply to a message in Entourage, Outlook running on my PC
connected to the same exchange server won't show the message as having
been replied to.

If I reply to a message on my Blackberry, the status shows up as
"Replied" in Outlook on the PC, but there is no status change in
Entourage.

Is there a solution to this?

Thanks,
Jay

 

[Mark Evans]

Hi Jay,

we are having the exact same problem.
Here is the deal...
I have read that new mail notification and mail read state
notifications back to exchange rely on UDP notifications from the
Exchange servers. This seems highly related to the behavior I am
seeing with my users. If two users are working on the public folder at
the same time and one reads the message or replies to it the event is
not immediately synchronized to the Exchange server. Microsoft built
in a WebDAV check every 1 minute as a fallback when UDP notifications
are not available.

So... more than likely MailStreet isn't allowing the UDP broadcasts
back and they might have the WEBDAV calls turned off on the server. I
have read that this can be a problem. Check out Microsoft's "Working
with Exchange Server" pdf.

If you find out anything plese let me know!

 

[ward.jay]

Mark,

I have not solved my problem yet, but I do believe there must be some
subtle nuances in the connection methods that I do not understand.

Outlook is connecting to MailStreet via http using URLs that look like
"https://mail.mse9.exchange.ms" and all is working correctly. The
replied-to and forwarded flags work correctly and sync between the
blackberry and the exchange server.

Entourage is also connected to MailStree via HTTP, but using URLs like
"https://owa.mse9.exchange.ms". I'm guessing that connecting through
Outlook Web Access (owa) is somehow different and is what's causing the
problem.

I'll check out that document you pointed to and see if there is any
explanation in there.

Jay