session log on MercuryE will show why aol.com drops the connection. My guess is that the maildrop is full.

<p>Hey Guys,</p><p>I've a problem with sending out emails with a big attachment (15 MB):</p><p> </p><p>This is the error i received:</p><p> </p><p>The attached message has failed delivery and has been referred to you as postmaster. The following error report or reports were given to explain the problem:       --- Problems not related to specific addresses in the message: Network failure during DATA with 85.13.XXX.XX</p><p>Network failure during DATA with 85.13.XXX.XX</p><p>Network failure during DATA with 85.13.XXX.XX</p><p>Network failure during DATA with 85.13.XXX.XX</p><p>Network failure during DATA with 85.13.XXX.XX</p><p>Network failure during DATA with 85.13.XXX.XX</p><p>Network failure during DATA with 85.13.XXX.XX</p><p>Network failure during DATA with 85.13.XXX.XX</p><p>Network failure during DATA with 85.13.XXX.XX</p><p>Network failure during DATA with 85.13.XXX.XX</p><p>Network failure during DATA with 85.13.XXX.XX</p><p>Network failure during DATA with 85.13.XXX.XX</p><p>Network failure during DATA with 85.13.XXX.XX</p><p>Network failure during DATA with 85.13.XXX.XX</p><p>Network failure during DATA with 85.13.XXX.XX</p><p>Network failure during DATA with 85.13.XXX.XX</p><p>Network failure during DATA with 85.13.XXX.XX    *** XYZ@aol.com </p><p> </p><p>Any ideas?</p><p>Thanks in advance</p><p>Asgard </p>

<p>Some hosts perform virus checking and other conformance verification before completing the SMTP transaction, which means that SMTP timeout may need to be increased if transmitting big messages. Another possible explanation is packet fragmentation, which can happen if Windows sends bigger network packets than your router accepts. <a href="http://www.speedguide.net/downloads.php%20" target="_blank" mce_href="http://www.speedguide.net/downloads.php ">SG TCP Optimizer</a> is a good tool for checking and correcting this.</p><p>/Rolf </p>