Oops..that is a 40MB attachment..
Chris Hane wrote:
I have a little more information on an issue that crops up every once in a while. Basically, james gets in a loop with another email server and consumes all of the bandwidth we have (3Mbps) until I shut james down and remove the outgoing emails.
The loop happened again today and this time I was able to isolate the email message that was causing the issue. The email has a large attachment and is about 40GB large (yes I have to allow for large attachments as one of my clients is a graphics firm...). I actually saved it for some further testing....
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.
Should I ask on the dev list instead.....
Thanks in advance, Chris....
Chris Hane wrote:
I have been running james for a couple of months now without incident. We send/receive around 50MB / day of email through james. All of a sudden we spiked to around 1.2 GB / hour (that is correct 1.2 GB / hour) and it was steady traffic over days.
We measured this using ntop and the ISP confirmed with measurements at their switch. I finally tracked it down to James. When I stopped James, the traffic stopped. When I started James, the traffic started again.
I set all of the logging to DEBUG. When I started the James server and the traffic picked back up (instantly), none of the logs were growing. The entries being added were in the 1-2 message / minute and not enough to account for 1.2GB/hour.
After a some experimenting, I found there were about 20-30 messages in the /var/mail/outgoing directory. The oldest one had a date of 3 days ago and most were from today. Also, the largest outgoing email was less than 100Kb.
When I deleted these messages and restarted James, the traffic did not pick back up and remained at normal levels (at least for the last two hours).
I know I'm probably not providing enough information to troubleshoot this effectively. I have a couple of questions though to try and help me track this down if it occurs again:
0. Actually, does anyone have any suggestions?
1. Is there logging I can turn on for the outgoing retries?
2. Rather than delete the outgoing emails again, is there some other action I should take to try and isolate this?
3. I installed James because we are a java shop. If someone can point me to a section of code that deals with the outgoing email directory I can try to look through the code the next time it happens and even install a debug version of james to try to catch the error.
Thanks for your help/suggestions in advance. Chris....
P.S. Here is my configuration info: James 2.2.0 Using the file system store Usage Mysql 4.1 for JDBCVirtualUsers JDK 1.5.0-b64 Linux 2.4.28 Dual PIII
------------------------------------------------------------------------
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.8.1 - Release Date: 1/27/2005
-- 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]
