Hello All,

Our users typically operate in cached mode on Exchange server. We need a
server side application (Visual Studio) to interrogate the Exchange server
to see if the mail items has been pulled from the server and cached to the
local machine, we also need to know if the mail item has been opened/read
(which we were able to do - that was the simple part). The application will
run on the server, so account access should not be a problem.

Any suggestions, Microsoft technical support has not been much help to date.
We were told that there is no indicator in the Exchange repository to tell
if the item was cached to the client, seems like ActiveSynch or something
similar would be leveraging this type of indicator so it would not have to
reload all headers, only those not cached.

Suggestions"

Thanks

There is no magic property. What do you do if you access the same mailbox
from multiple machines or profiles?

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"news.comcast.net" wrote in message
...
Hello All,

Our users typically operate in cached mode on Exchange server. We need a
server side application (Visual Studio) to interrogate the Exchange server
to see if the mail items has been pulled from the server and cached to the
local machine, we also need to know if the mail item has been opened/read
(which we were able to do - that was the simple part). The application
will run on the server, so account access should not be a problem.

Any suggestions, Microsoft technical support has not been much help to
date. We were told that there is no indicator in the Exchange repository
to tell if the item was cached to the client, seems like ActiveSynch or
something similar would be leveraging this type of indicator so it would
not have to reload all headers, only those not cached.

Suggestions"

Thanks

The issue is one of knowing at the server that the remote system has had
access (not necessarily read) to the email system and that the cache has
been refreshed. It is a unique environment where we need to know if the
user was or was not in communication range and had communicated with the
system. If we just rely upon on messages read, it gives false positives
(e.g. I could have had my cache refreshed but not read the email) and forces
us to use an alternative (e.g. satellite) method of pushing the email out.
The alternative method of communication is higher priority and more costly.

Thanks


"Dmitry Streblechenko" wrote in message
...
There is no magic property. What do you do if you access the same mailbox
from multiple machines or profiles?

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"news.comcast.net" wrote in message
...
Hello All,

Our users typically operate in cached mode on Exchange server. We need a
server side application (Visual Studio) to interrogate the Exchange
server to see if the mail items has been pulled from the server and
cached to the local machine, we also need to know if the mail item has
been opened/read (which we were able to do - that was the simple part).
The application will run on the server, so account access should not be a
problem.

Any suggestions, Microsoft technical support has not been much help to
date. We were told that there is no indicator in the Exchange repository
to tell if the item was cached to the client, seems like ActiveSynch or
something similar would be leveraging this type of indicator so it would
not have to reload all headers, only those not cached.

Suggestions"

Thanks

If you have code running on the client side, you could of course add a
special property to a message that will signal to tehe server that the
message had been accessed.
But that would mean modifying the message and posting teh data back to the
server.

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"news.comcast.net" wrote in message
...
The issue is one of knowing at the server that the remote system has had
access (not necessarily read) to the email system and that the cache has
been refreshed. It is a unique environment where we need to know if the
user was or was not in communication range and had communicated with the
system. If we just rely upon on messages read, it gives false positives
(e.g. I could have had my cache refreshed but not read the email) and
forces us to use an alternative (e.g. satellite) method of pushing the
email out. The alternative method of communication is higher priority and
more costly.

Thanks


"Dmitry Streblechenko" wrote in message
...
There is no magic property. What do you do if you access the same mailbox
from multiple machines or profiles?

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"news.comcast.net" wrote in message
...
Hello All,

Our users typically operate in cached mode on Exchange server. We need
a server side application (Visual Studio) to interrogate the Exchange
server to see if the mail items has been pulled from the server and
cached to the local machine, we also need to know if the mail item has
been opened/read (which we were able to do - that was the simple part).
The application will run on the server, so account access should not be
a problem.

Any suggestions, Microsoft technical support has not been much help to
date. We were told that there is no indicator in the Exchange repository
to tell if the item was cached to the client, seems like ActiveSynch or
something similar would be leveraging this type of indicator so it would
not have to reload all headers, only those not cached.

Suggestions"

Thanks