Hi again,
Its defiantly a combination of both XMail and WAI that causes the problem. 2 months ago I installed XMail and WAI and had the same problem. Then I reinstalled XMail - no WAI - and did not have any problems for 2 months. (older versions of both XMail and WAI) Now after reinstalling the WAI, the problem is back again. However, I did not have the problem on my 'test' server - that is virtually identical software setup - but only a single CPU machine. I'd go with Bill's idea of running it on only one CPU, except I can't work out how to set the CPU affinity for a service, or how to call XMail from the cmd prompt (to use FireDaemon). While I guess a batchfile that restarts the service once a day - and deletes the spool folder would work - I'd rather find and fix the problem. Regards, Scott At 12:22 PM 29/05/2002 +0200, you wrote: >Hi, > >| I stopped running frozcache.vbs and it does not make a difference. > >therefore I think so WAI is innocent -- all other communication goes >trough CTRL protocol (ctrlclnt.exe). > >BTW: I am using XMail on dual processor server too with no probs... > >-- [EMAIL PROTECTED] > >- >To unsubscribe from this list: send the line "unsubscribe xmail" in >the body of a message to [EMAIL PROTECTED] >For general help: send the line "help" in the body of a message to >[EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
