I'm running 2.2.0 (I'm assuming that's the latest stable version).
I'm just guessing at the reason for the loop based on my observations. I actually did not have time to try and research the issue today as my ISP wanted me to resolve it quickly (3Mbps is a bit of bandwidth to consume for about 4 hours continuously). I have the var/mail/outgoing files that relate to the message if there could be anything in them that would help.
If I figure anything else by looking at the code Stefano pointed me to, I'll report back.
Thanks, Chris....
Serge Knystautas wrote:
Chris Hane wrote:
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.
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.9.7 - Release Date: 4/12/2005
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
