I have had some situations recently where the spool queue has gotten
clogged and has grown to ~4000 messages. I'm still trying to track down
what is happening and what might be causing it. I can recycle mySQL and
James and the spool starts clearing out.
I'm sure I'll ultimately figure out what is happening. But in the
meantime, I don't want it to back up for 8-10 hours with no mail going
in/out until one of my clients calls and complains and lets me know it's
doing it again.
I've written a monitor app that wakes up every five minutes and looks at
the size of the queue. If the queue ever goes over a threshold, the app
sends a text message email to my cell phone.
However, there is an obvious problem with this solution... if the spool
queue is backed up, the text message email to my cell phone will be
backed up right along with everything else. I could use another smtp
server someplace (non-trivial to find some 3rd party smtp that will let
me use it). Or I could set up a second James smtp server that is only
used by the monitor. However, all the servers in one instance of James
all use the same spool queue, right? So I would literally have to
install James twice, each as its own service, with two different config
files and two different data stores and different ports for the servers,
right?
I figure I can do this. But I would like a sanity check on this.
Again, all I want to do is to have a 2nd (private) spool queue with
another smtp server on a private port that can get a message out of the
primary spool is clogged. Is what I described the best way to do this?
Thanks.
Jerry
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
