Hi Mike,

Nice to see another .co.za!

I've experienced the same problem. James was busy with a batch of mails that
had failed previously, and were being tried for the last time before being
removed from the spool. At a certain point, James stopped going through the
spool, for a least one hour. Eventually, I restarted and things proceeded
normally again.

I would also be interested to hear of anything more conclusive in solving
this.

In terms of logging, you can check out the mailet logs for entries from the
RemoteDelivery mailet, and increase the logging level in
SAR-INF/environment.xml.

cheers,
craig


----- Original Message ----- 
From: "Mike Morris" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, October 17, 2003 11:28 AM
Subject: Stuck outgoing mail


> Hi all,
>
> New to James, and still thrashing about figuring out how things work...
>
> I have a couple of mails stuck in the "outgoing" directory, one for over
> a day now, that "should" have been delivered.  Both destination domains
> have valid MX's listed and active, and I have had James succesfully
> delivering mail to other destinations (including, hopefully, this one
>
> Any suggestions on how I can give these a kickstart to resubmit them or
> retry delivery.
>
> BTW, I have delivery retry time set to 1 hour = 3 600 000ms, so that's
> not it...
>
> Is there any way to log/monitor delivery attempts in a fairly detailed
way?
>
> Thanks in adv. for any suggestions/help.
>
> -- 
> mike morris     ::   mike.morris (at) cocosoft . co . za
> cOcO software   ::   mike.morris (at) coco-technologies . co . za
>                       www . cocosoft . co . za
>
> ----- A day without chillies is a day wasted ------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to