You are correct. A 4xx should be retried. Looks like the handling for a
SendFailedException is a problem.
I don't know if there was a regression when the exception handling was
reorganized in the most recent patch. Prior to that, the code said that any
SendFailedException was always permanent.
However, since a SendFailedException is a subclass of MessagingException,
differing only in the partial delivery nature of the exception, so would you
please try replacing the return call in that catch clause with:
return failMessage(mail, sfe, (('5' == sfe.getMessage().charAt(0)) ? true :
false));
which is what we use for MessagingException, and see if that fixes it for
you. I am putting that into my build, too.
If so, I think it is a serious enough bug to patch.
--- Noel
-----Original Message-----
From: Danny Angus [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 13, 2002 9:42
To: James Developer List
Subject: FW: Urban tapestries
Yikes I don't like this, a 4.x.x should be re-tried
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: 13 December 2002 13:15
> To: [EMAIL PROTECTED]
> Subject: RE: Urban tapestries
>
>
> Hi. This is the James mail server at killerbees.co.uk.
> I'm afraid I wasn't able to deliver your message to the following
> addresses.
> This is a permanent error; I've given up. Sorry it didn't work out. Below
> I include the list of recipients and the reason why I was unable
> to deliver
> your message.
>
> xxxxxxxxxxxxxxxxxxxxx
> Remote mail server told me: 451 Temporary local problem - please try later
>
> The original message is attached.
>
--
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]>
