And the integrity of the pst cache file might need checking. This is done by running "scanpst.exe", that is somewhere in the Office pgm directory. I have also seen some strange slowdowns using Cyrus and a damaged pst., mostly at first opening of Outlook. Deleting the pst file cache and allowing Outlook to recreate it is also a viable solution, provided you aren't on a slow link and have a large mailbox.

A damaged "main" pst can also be the cause of slowdowns. This is the one that Tasks/Contacts etc reside in and would be the normal delivery point for POP3 mail. Both pst's by default reside in;

C:\Documents and Settings\<username>\Local Settings\Application Data\Microsoft\Outlook

Another big trap with Outlook and IMAP is doing message searches. It only searches the cached data in the pst so you have to download the entire message set first. I'll admit I have only seen this in Outlook 2000, but assume it is the case for later versions. You may also want to do the registry change that downloads the full IMAP header set to the cache. (IMAPFullHeaders something) At the very least you then see both the To: and From: fields in the message list. Very important if you are using IMAP as a public folder like filing system.

Also look into "Compacting" the pst file. I haven't done any testing on this but it seems to speed some Outlook operations.

Apologies for waffling on!

Cheers Bob

Ciprian Marius Vizitiu wrote:
must always remember that Outlook keeps a local copy of the headers in a PST
file associated with that IMAP account. If that file resides on a badly
fragmented FAT32 and/or the .pst file is approaching the 2GB limit "strange
things start to happen". :-s


----
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Reply via email to