What I think is happening though is the other server that james is trying to send to is not allowing for such a large message and is just terminating the connection.
It appears that james takes the termination as a network error and retries immediately (and gets itself into a loop). Has anyone else seen this type of issue? Any solutions? I'm even willing to work through some of the james code if I could get a pointer or two with which classes to start with in my debugging attempts.
What version are you running? I can't think of how our error handling would try to immediately resend without incrementing the attempt counter. Maybe it's an old version with a bug that's since been fixed.
-- Serge Knystautas Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
