Outlook 2002 SP2 problem with multiple pst files

R

Ron Pleshek

I can't get a Rule to work that moves an incoming message to a folder that
is in a different pst file than the inbox. When I set up the rule (using
Rule Wizard), the 1st incoming message that meets the rule criteria gets
moved to the correct folder. However the next incoming message that meets
the rule criteria causes Outlook to hang. Outlook freezes, doesn't respond
to mouse clicks, and the Outlook application task must be ended via task
manager to recover. Then if I startup Outlook again it takes a while for it
to come up (>30 sec) and when it does the message that should have been
moved is in the Inbox and the rule (sometimes) no longer lists the
destination folder I configured - instead the rule has reverted to "move to
specified folder". Outlook can't seem to find the folder I configured.



This is very easy to reproduce. To simplify things, I've deleted all
pre-existing Rules and then I added a new empty pst file by configuring
File->Data File Management->Add. I added a folder (foo) to this new pst.
Then I added a rule to move messages to the foo folder when they contain my
email address in the Sender's Address, and set the rule to stop processing
once forwarded. I send email to myself and the 2nd email sent hangs
Outlook. I've verified this on someone elses laptop as well so it has
nothing to do with the data in my pst files.



I've tried setting up a rule that moves the incoming message to a folder
that is in the same .pst file as the inbox, and that seems to work fine.



My configuration is as follows: I have 1 email account set up in outlook
2002 SP2 on a laptop running Microsoft Windows 2000 SP4. The reason I'm
using multiple .pst files is to get around the 2Gb pst filesize limit.



Any help would be appreciated. I've searched the Microsoft tech support
pages and haven't found a bug listing similar to this. Most users at my
company use Eudora so there isn't much expertise in the IS dept on Outlook.





Ron
 
R

Ron Pleshek

Turns out this has been diagnosed as incompatibility between Outlook 2000
and McAfee VirusScan v 4.5.1 SP1. The problem goes away if scanning on
incoming email is disabled.

Ron
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top