Re: [IMail Forum] queuemgr problems again

[Matt]

Randy, I have seen others mention similar things with Declude 3.x and IMail 8.2+.  I wouldn't discount the possibility of this having something to do with Declude.  You should report it to them just to be safe. Declude is handling all of these messages by calling IMail by the command line to process them, but this isn't how E-mail is normally handled by IMail without Declude.  That one piece could be responsible for this non-universal behavior, and things also tend to misbehave when running at 100%.  I have definitely heard others having queuemgr crashes on some versions of Declude 3.x.  Declude needs to be throttling their processes when they start to approach 100% CPU utilization, but right now they are only set up to throttle based on a number of processes which isn't appropriate and it can cause things to crash as the server redlines.  It is never really safe to pound on a server at 100% with many different processes.  Exceptions start to happen that aren't otherwise seen in normal operation, and I'm sure that Windows has it's own issues with this.  When things slow down and threads take longer to execute, you can also run into Mystery Heap issues that can cause instability.  I'm not completely sure if the Mystery Heap is an issue with the 3.x environment. As another test, you might try moving files out of Declude's proc folder and then rebooting.  Declude might be pounding on queuemgr before it is ready, or just pounding it back into submission.  Moving these files would at least help to narrow it down. Matt randy armbrecht wrote: Here's a little more info on the QM issue: We have recently noticed that one element that is a problem for QM is when the system receives a large number of messages at one time. We just implemented last week an external app that provides a daily email to users in a particular domain (about 500 email addresses); when QM receives these messages it goes to 100% for a few seconds then dies off; spool backs up, etc. etc.. Stop/Starting services doesn't fix anything. Rebooting doesn't fix anything at all. The only way to correct this is to stop all services, rename the spool folder, create a new spool folder, move all virus,spam, web and proc folders back into the spool folder and restart all services. Then I have to go back to the old spool folder and move messages back into the proc directory for re-processing. Let me state again, this is not a Declude issue, as declude processes the messages just fine and places them back in Spool for final delivery processing; it this final derlivery process that stops cold and results in the backup. DNS is not an issue, as I run DNS on the same machine - a Dual Xeon 3.0 with 2GB Ram. DNS lookups perform flawlessly and with no delays. I did notice today on the desktop fo the server itself a POP-UP system error dealing with QM that read: "The istruction at 0x06651357 referencing memory at 0x4e49476f memory could not be "read"" I have never seen this error before on the other cases, as we normally work with the servers thru a remote access (even though the servers are in our server room down the hall); this time I happened to be in the server room when the issue occured so I hopped right on to the server directly. We're at the point where we are buying the SM 3.0 upgrade version today and loading it on our old mail server hardware (dual pIII 800) for testing and whatnot, and will be planning a migration very soon. Randy A. Global Web Solutions, Inc. 804.346.5300 877.600.GLOBAL (4562) Hi Randy, Let me know and we'll sort out getting you access to the 2006.03 pre-release. it contains web performance and QM performance changes. bye for now, kg To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/