Code: Select all
omstat -q UNIX | grep "Do Not Reply at Fidelity INvestments" | cut -d" " -f 1 | while read msgid
do
omstat -q UNIX -j -R -m $msgid
done Code: Select all
omaddq -q TEMPdougp23 wrote:Hmmm... I will try this!!
The problem is one that has been discussed in a previous thread:
queue.manager is gobbling 100% of CPU. More than 300,000 messages now in the "Internet Mail" queue. I am sure that the vast majority are garbage.
I just need to figure out how all those messages are getting past Postini!
If you have issues with the queue manager starting (happened on a site which ended up as an open relay and had literally thousands of messages) it can be nigh on impossible to talk to Scalix. You can stop the Queue Manager processing and reading messages in the queue on start by adding settings to the general.cfg file. From the Docs (Admin guide page 136)....
QM_DONT_READ_MSG_AT_START=FALSE
When set to TRUE, this option specifies that all messages currently in the Scalix queues remain stationary when Scalix is restarted. New messages are processed normally. Set this option to TRUE if a major problem is encountered when the queue manager attempts to read queued messages from disk when Scalix starts up. This allows Scalix to start. Set the option back to FALSE and restart Scalix when the problem is resolved.
QM_FAILURE_DELAY_SEC=seconds
Specifies the number of seconds between messages being retried by the queue manager. When a message fails to be processed because the process that was handling the message died, the queue manager delays the message for this number of seconds before retrying the message. The default is 30. See also QM_MAX_FAILURES