Nope, there are no 0 byte files in outgoing or spool. Outgoing stays empty
----- Original Message ----- From: "Eric Weidner" <[EMAIL PROTECTED]> To: "James Users List" <[EMAIL PROTECTED]> Sent: Thursday, February 14, 2002 11:57 AM Subject: Re: spooling problem > Look to see if there might be a 0 byte file hanging around in the outgoing > or spool directories. This used to happen to me a lot on the 1.2.1 version > and still occasionally in the 2.0 version (but much more rare). > > Delete the 0 byte file and the rest should start to process again if this is > the case. > > Eric > > ----- Original Message ----- > From: "Lucas Gonze" <[EMAIL PROTECTED]> > To: "James Users List" <[EMAIL PROTECTED]> > Sent: Thursday, February 14, 2002 10:53 AM > Subject: Re: spooling problem > > > > I suspect this the same bug I reported before -- that mails which don't > > get sent immediately never go out. > > > > On Thu, 14 Feb 2002, Shal Jain wrote: > > > > > Yes it does.. > > > I'm not using James to send outbound emails. Its being used strictly > for > > > processing inbound emails. > > > If I can process the email, it gets ghosted. If I can't process the > email > > > then it gets sent to a local account 'unfiled@localhost' > > > In case of failure, the mail state is set to 'Error'. The processing is > > > done via a custom mailet and the passthrough flag is set to false > > > > > > What I have noticed is that in certain cases (working on narrowing these > > > down), the email that's received in James, even though its processed > > > correctly by the > > > mailet, still hangs around in the spool. If I manually clear out the > spool > > > folder, emails seem to get processed. However, if I let > > > the spool folder buildup, then James stops passing the email to my > mailet. > > > I then restart James, causing the emails to be processed > > > and then I manually clear the spool folder out again > > > > > > I'm digging through the mailet code but would appreciate any hints on > what > > > to look for > > > > > > ----- Original Message ----- > > > From: "Serge Knystautas" <[EMAIL PROTECTED]> > > > To: "James Users List" <[EMAIL PROTECTED]> > > > Sent: Thursday, February 14, 2002 10:02 AM > > > Subject: Re: spooling problem > > > > > > > > > > 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]> > > > > > > > > > > > > > -- > > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
