Koozali.org: home of the SME Server

Outlook failures

Des Dougan

Outlook failures
« on: June 17, 2001, 10:14:59 AM »
I have a client using e-smith 4.1.1, with patches applied. One user has copied existing email messages from his laptop's local Outlook 2000 folders to his IMAP environment (in fact, he copied several folders). Since he did this, Outlook consistently crashes each time it polls the server for new mail. This is the second time it has done this - the first time I thought it was an Outlook problem and found a hit on MS's support site. I rebuilt the user, as the resolution indicated a corrupt IMAP account. Until the folders were copied, it worked fine, and similarly after I re-created the account, no problems until message folders copied.

Can anyone shed any light on this? I just logged in to the account via Webmail, and can't see the folders (other than the Inbox).

Thanks,

Des Dougan

David Helmuth

Re: Outlook failures
« Reply #1 on: June 18, 2001, 12:42:01 AM »
I too was having serious crashing problems w/Outlook.

I did 2 things and it is working for me now...

1.  Apply all patches for ms office / outlook (I am using Outlook 2000)
I went to office.microsoft.com and let it suggest all the updates.

2.  Apply the "changes" that are outlined in the following user contributed How-To's

Change the default location of IMP's folders
http://netsourced.com/e-smith/docs/imp-folders-howto.html

For good measure, increase the default attachement file size (not required)
http://netsourced.com/e-smith/docs/webmail-attachment-size-howto.html

I hope that helps.

Des Dougan

Re: Outlook failures
« Reply #2 on: June 18, 2001, 09:57:27 AM »
David,

Thanks for yuour help. I tried to upgrade to the latest SRs and found that the process needed the CD, which is at the office....

I also did a fair amount of testing on my home test box. This machine is on 4.1.2 and no matter what I did, I couldn't make Outlook fail. I therefore checked the 4.1.2 release notes and found that the IMAP daemon was upgraded in 4.1.2, so this may have resolved the problem. I will schedule the 4.1.2 upgrade on the production server and see whether that fixes things.


Des Dougan