Latencies with rules in Outlook 2003

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

Our company is using an exchange server which is located at, and managed by,
a third company. Now, one of our Outlook 2003 users is using different kind
of rules which are working perfectly. However when a message arrive, it
first arrives in the inbox and after a couple of minutes it looks like the
user receives the same message again (as he gets a new desktop alert) however
it is removed from the inbox and moved to the correct folder.

This user is also working with a data file which means that every mail that
arrives is immediately sent to the inbox of a local PST-file and not to the
mailbox that is provided by the third party. The reason why this particular
user has made this file is that he would like to read his mails permanently,
also when he is offline.

Does anyone know what the reason could be of this latency and provide me any
kind of help in this?

Thanks a lot.

Kind regards,
Eddy
 
Eddy_V said:
Our company is using an exchange server which is located at, and
managed by, a third company. Now, one of our Outlook 2003 users is
using different kind of rules which are working perfectly. However
when a message arrive, it first arrives in the inbox and after a
couple of minutes it looks like the user receives the same message
again (as he gets a new desktop alert) however it is removed from the
inbox and moved to the correct folder.

This user is also working with a data file which means that every
mail that arrives is immediately sent to the inbox of a local
PST-file and not to the mailbox that is provided by the third party.
The reason why this particular user has made this file is that he
would like to read his mails permanently, also when he is offline.
Click to expand...

That's not the way to accomplish that. Offline folders is a better method.
It gives the advantage of both worlds. When in the office, you connect to
the Exchange server where your mailbox resides. Out of the office, you work
with a local copy that behaves exactly like you're connected, but you're
not. When you get back and reconnect, everything syncs up and you're all
current.
 
Back
Top