All emails pass through the spool, so it's not a question of why they're getting dumped to the spool but rather why they're not leaving the spool.
I would guess that the threads of the spool manager are getting killed or hung, so eventually you run out of threads and messages just stay there. I'm not sure what would be killing/hanging the threads. Does restarting the server process those messages? Serge Knystautas Loki Technologies - Unstoppable Websites http://www.lokitech.com/ ----- Original Message ----- From: "Shal Jain" <[EMAIL PROTECTED]> To: "James Users List" <[EMAIL PROTECTED]> Sent: Wednesday, February 13, 2002 10:32 AM Subject: spooling problem > I'm running James ver. 2.0a1 with a custom mailet whose sole job is to catch > all emails that come in and either process (set state to GHOST) or file them > into a james defined account. > > What I have noticed over the last couple of days is that after startup, any > email received to James gets processed right away > but after N hours of running, the mails start getting dumped to the spool > directory. > > Any clues as to what would cause incoming mails to go to the spool folder -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
