Re: Serious bandwidth begin consumed by James

[Chris Hane]

In my case, james was receiving the 552 error correctly.  It then tried 
to bounce the message back to the sender using an internal bounce 
method.  The internal bounce method sends the entire message (as a note, 
the entire message at this step is read into memory).  At this point, 
the message was large enough that I ran out of heap space.

Once the outofmemory exception was generated, effectively the thread 
that was processing the message was abandoned.  However, the message (as 
stored in the spool - using terminology very loosely here) was never 
marked as completed or error ed.  Therefore, the next time the master 
spooler cycled through it saw that the message was ready for delivery.

And here we go with the loop.....
There are three solutions.  One is to increase the heap space (not an 
option for me).  Second is to modify the code to catch the 
OutOfMemoryException.  I would not recommend that option.

The other option is to configure the RemoteDelivery mailet to use a 
different bounceProcessor.  The DSNBounce mailet has an option that will 
not bounce the attachments back to the user.  This is what I used and it 
solved my problem.  A bounce message is generated telling the sender the 
message subject, who the sent it too, and the reason is bounced and does 
NOT attach the attachment.  Hence I no longer have outofmemory exceptions.

Hope this helps explain at least what I was experiencing....
Chris....
Renen wrote:
Hello.
I'm afraid I'm not sure that I got all that. I have been experiencing
exactly the same problem, but as part of implementing this "correction"
I would like to try and understand what I am doing.
So, a couple of questions:
1) What does the DSNBounce mailet do? And why won't the bounce mailet
correctly handle the 552 error?
2) Do I understand correctly that James doesn't know to stop trying to
send the email? Hence the continuous consumption of bandwidth and the
James' the proliferation of mail in the outgoing directory?
thanks.
renen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

 


--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.11.9 - Release Date: 5/12/2005
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]