Internet Mail gateway not processing messages - take 3
Posted: Tue Oct 02, 2007 11:18 am
Hi All,
We have a problem with the UNIX queue (Internet Mail gateway) on out Scalix 10.0.5 server. This problem keeps reappearing every so often so I'm inclined to think there is some other underlying cause.
Basically, every so often all outbound mail gets stuck in the UNIX queue (which is displayed as Internet Mail Gateway when you run a 'service scalix status').
Previously, 'mikethebike' suggested the following procedure to restart the queue :
1) omoff -d 0 -s unix
2) ps -ef | grep unix ; and then kill off all unix.out processes.
3) Use omqdump to move all the messages to the error queue
4) omon -s unix
5) omscan -A -q -f
6) Now use omqdump to move messages back in batches to the unix queue
This procedure has worked for me the last 3 or 4 times this happened, but now I just can't get the UNIX queue to start processing mail.
Does any one have any idea how to solve this problem - and prevent it reoccurring ?
Just as an indication, there are currently only 450 messages in the outbound queue so it can't be a case of the machine being overloaded.
Many thanks in advance,
Regards
Arif
We have a problem with the UNIX queue (Internet Mail gateway) on out Scalix 10.0.5 server. This problem keeps reappearing every so often so I'm inclined to think there is some other underlying cause.
Basically, every so often all outbound mail gets stuck in the UNIX queue (which is displayed as Internet Mail Gateway when you run a 'service scalix status').
Previously, 'mikethebike' suggested the following procedure to restart the queue :
1) omoff -d 0 -s unix
2) ps -ef | grep unix ; and then kill off all unix.out processes.
3) Use omqdump to move all the messages to the error queue
4) omon -s unix
5) omscan -A -q -f
6) Now use omqdump to move messages back in batches to the unix queue
This procedure has worked for me the last 3 or 4 times this happened, but now I just can't get the UNIX queue to start processing mail.
Does any one have any idea how to solve this problem - and prevent it reoccurring ?
Just as an indication, there are currently only 450 messages in the outbound queue so it can't be a case of the machine being overloaded.
Many thanks in advance,
Regards
Arif