Ever since we have upgraded Ironmail to 6.7.2 we've noticed that IronMail has been dropping a lot of email with attachments, in the case below 9MB.
This only started happening recently, since the 6.7.2 upgrade earlier versions never had this problem. We have 2 backend mail servers that delivery to both has issues. All internal email routes from a seperate postfix server that has no issues delivering any size attachments. I believe this is a Mcafee issue, as all internal mail does not have the same delivery issue, with addition that the system has worked flawless until recent upgrade.
20120217:10:49:32|28327122|9492|Connection Status <status> -|1|
20120217:10:49:32|28327122|4139|-|Sending: EHLO asdf.edu|
250 SIZE 0'|
20120217:10:49:32|28327122|9523|Starting SendSmtpMsg in domain -|asdf.edu|
20120217:10:49:32|28327122|9570|BATV values are DSN_BVP_enable: <IsEnabled> mail_from: <Mail From> mdoutbound <IsOutbound> selfdeliveryMode <Delivery Mode> -|0:firstname.lastname@example.org:0:0|
20120217:10:49:32|28327122|4139|-|Sending: MAIL FROM:<jahern@fdsa> size=9439277|
20120217:10:49:32|28327122|4139|-|Reply: '250 2.5.0 Address and options OK.'|
20120217:10:49:32|28327122|4139|-|Sending: RCPT TO:<email@example.com>|
20120217:10:49:32|28327122|4139|-|Reply: '250 2.1.5 firstname.lastname@example.org OK.'|
20120217:10:49:32|28327122|4139|-|Sending: DATA |
20120217:10:49:32|28327122|4139|-|Reply: '354 Enter mail, end with a single ".".'|
20120217:10:54:34|28327122|9563|Exception occurred: Type=<error type> Exception=<exp> -|<class 'ct_smtplib.SMTPServerDisconnected'>:Socket error sending DATA|
Message was edited by: kollross on 2/22/12 4:08:20 PM CST
on 2/22/12 4:15:58 PM CST
What you are showing there does not appear to be a issue with the IronMail, as the log states that the other server disconnected. It would probably be best to get a packet capture to show what is truly going on. You can run this at the command line, but that is hard to read. The easiest step may to be to call support and have them run the packet capture while the message is retried. This should be fairly straight forward, as the next hop mail server is not supporting TLS, so any errors would be in plain text.