Ricardo Kleemann wrote:
Basically I have a mailq which is backed up tremendously. It takes more than 24 hours for mailq to run itself out, spitting all of the messages that are backed up. Last time I let it run itself out, there were more than 160,000 messages in the queue!!!
You mentioned that you have a courierfilter program. Is it possible that this filter is injecting messages into the queue in responce to incoming messages, including its own? If so, the filter would inject messages into the queue as fast as the machine allows.
I'd suggest stopping courier, moving its queue directory aside, creating a new one, and starting courier back up. Take the opportunity to examine the queue that's too full to determine what source and destination addresses are most common. You will probably find that some common source has been injecting message that you don't care about. Once you find out what that is, you can remove it from the old queue and re-inject the remaining messages into courier's queue.
Once you fix that, you can also adjust the settings in module.esmtp and module.local to increase the MAXDELS. I suggest raising each by 25% and watching the load on your system to make sure it can handle the increased load. Also watch 'vmstat 2' and 'iostat -x 2' to make identify bottlenecks in your system. These tools will show you how much cpu use, memory use, swap use, and disk bandwidth your system is subject to.
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
