KB916803 - preventing mailbox being deleivered to .pst

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

Guest

I recently experienced a problem where outlook clients, who use both exchange
and POP3 to receive their email (they use 2 profiles and have their mail sent
to a shared .pst) were unable to receive appointments to their delivery
location i.e. their .pst, from the exchange server . This was not acceptable
as these clients travel outside the domain and rightly expect to get their
mail delevered as they have come to expect when using POP3. After a bit of
research the culprit for this problem turned out to be the exchange server
update KB916803.

Hopefully, this will serve both as an aid to others experiencing similar
problems and a push to microsoft to sort this update out.
 
Darbee said:
I recently experienced a problem where outlook clients, who use both
exchange and POP3 to receive their email (they use 2 profiles and
have their mail sent to a shared .pst) were unable to receive
appointments to their delivery location i.e. their .pst, from the
exchange server .
Click to expand...

Why are they not using Cached Exchange mode and VPN or RPC over HTTP to
connect to the Exchange server on the road so that they don't need more than
one account?
 
Brian Tillman said:
Why are they not using Cached Exchange mode and VPN or RPC over HTTP to
connect to the Exchange server on the road so that they don't need more than
one account?
Click to expand...
 
Darbee said:
they do use a VPN over the internet .whether or not the client has
connected to exchange or POP3, the issue is that this update
prevents calender appointments being extracted to a personal
folder's inbox. for those without 2003 and a limited sized mailbox-
also a scenario i cover, this could be an issue and the update is
the cause.
Click to expand...

My point is that if your server is an Exchange server, then you have no need
to use PSTs.
 
Brian Tillman said:
My point is that if your server is an Exchange server, then you have no need
to use PSTs.
Click to expand...

however, this still doesn't detract from the previous issue of the calender
limitations caused by the update to a pst. but i'm wondering if you have a
constructive solution or any idea to the original findings concerning mail
delivered to a pst, aside from dont deliver to a pst
 
try switching the default email account from the exchange server to the pop3
account? This has worked for me.
 
Back
Top