Another question: The CPU hogging appears to be a result of mails failing and being retried. As the queue stacks up, the CPU (and our outgoing mail) bogs down.
Anyway, what I have been doing is to stop James, and empty the outgoing queue, which sometimes gets large enough to actually choke the shell (i.e. 'rm *' returns "too many arguments"). Problem is, stuck in there are mails I do want to send which cannot be easily re-created. So, what I've been doing is to rename the outgoing/ directory to "badmail" or such and then create a new outgoing directory and restart james. Now, I can easily identify a "good" mail message by certain telltale text artifacts easily found with grep or awk. My question is, when I identify a "good" message, is there a way to copy it back into the outgoing mail queue so that James will attempt to deliver it? -cwk. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
