Thanks, that clears some things up. I just ran a sizeable test and sent
~4000 messages to my James server. The spool indeed got filled up but
went down in size pretty quickly. The outgoing messages folder then got
filled up accordingly and is slowly (very slowly) processing messages.
It took abo
> Thanks for the reply. I've included the
> element of my config as well as the thread manager element.
> Please let me know if there's anything else I need to
> include. As for the outgoing mail folder, I can stop the
> cron job from cleaning out the messages but how are messages
> that g
Thanks for the reply. I've included the element of my
config as well as the thread manager element. Please let me know if
there's anything else I need to include. As for the outgoing mail
folder, I can stop the cron job from cleaning out the messages but how
are messages that get stuck in /var/
We use 4 spool threads and 2 x 30 outgoing threads (there are two
RemoteDelivery mailets in use).
After experimenting I found that in our set up, the system slows down a
factor two with more spool threads. 4 turned out to be the optimum. You
may want to run some tests in your environment, thoug
> Could anyone out there that's using James in a production
> system give me an idea of what parameters they use for their
> config file? At any given time, our production applications
> send out approximately 5000 emails a day. Currently, our
> config file is set to have 100 outgoing threads
Could anyone out there that's using James in a production system give me
an idea of what parameters they use for their config file? At any given
time, our production applications send out approximately 5000 emails a
day. Currently, our config file is set to have 100 outgoing threads and
75 spool