Are you generating any Dr. Watson errors?  If so are you able to correspond the PID back to the process that was trying to deliver the mail.  This can help you isolate the specific file in the queue that is causing the queuemanager to crash.  I had the same issue with an earlier version of imail circa 8.05.  It was one spammer who I was able to block that was sending some bad messages.
 
Not that this next option solves the problem, but if you need some help in baby sitting the server we have a windows service that we developed to keep an eye out for situations like this when we were having the issue under earlier versions..  It's also nice to have something monitoring your queue in case some thing goes wrong.  QueueMon may give you some reprieve while you work to fix the issue.
 
Darrell
-------------------------------------------
Check out http://www.invariantsystems.com for utilities for Declude And Imail.  IMail/Declude Overflow Queue Monitoring, MRTG Integration, and Log Parsers.
----- Original Message -----
Sent: Friday, October 15, 2004 12:43 PM
Subject: [IMail Forum] Queuemgr stopping / crashing - V 8.13

I'm having a problem with queuemgr stopping or crashing 50+ times per day.
 
Lots of "ERR 005" in the log files...
 
Lots of Pop-up messages -
"Queuemgr.exe has generated erros and will be closed by Windows. You will need to
restart the program. An error log is being created."
 
Lots of messages in the system error log -
"The IMail Queue Manager Service service terminated unexpectedly. 
It has done this 40 time(s).  The following corrective action will be taken in
0 milliseconds: No action. "
 
Sometimes the "Automatic Restart" option under "Queue Manager" service options
works, but often it seems like it doesn't. 
 
I've checked for folders nested too deeply in users, and if I clear out the spool
directory completely, the problems go away for a while, but come back after a
day or so.
 
Getting pretty tired of babysitting this thing. Anybody have any ideas?
 
Thanks,
Dean Cooper
[EMAIL PROTECTED]

Reply via email to