Attached is the patch to fix the exception handling problem. Unfortunately, this has been tested. It works. BellSouth finally got the 552 code it needed to stop attempting to deliver a message > 4MB after 116 attempts today.
Is it just me, or is 116 attempts in 18 hours just a bit excessive? It was
getting 451 errors generated by the JDBC driver until this evening when I
saw the problem occurring, tried to fix it with the maxmessagesize, and had
to create this patch to allow maxmessagesize to return a 552 (BellSouth
doesn't use EHLO). Meanwhile they consumed almost half a gigabyte of
transfer. What are retry policies out there?
--- Noel
MimeMessageInputStreamSource.java
Description: Binary data
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
