|Email Plug-in (Reporting):||1.0.1-048|
|Email Plug-in (Encryption):||1.0.0-036|
We are using IronPort C350 ASyncOS Version: 6.5.3-007
We have been using this IronPort for several years as outbound mail server. We found mails are being queued up for long time and found following error messages.
Fri Oct 22 19:50:38 2010 Info: Connection Error: DCID: 220131165 domain: nets.com IP: 22.214.171.124 port: 25 details: [Errno54] Connection reset by peer interface: 206.XX.XX.XX reason: network error
Fri Oct 22 19:50:38 2010 Info: Delayed: DCID 220131165 MID 341927191 to RID 0 - 4.4.0 - Other network problem ('000', ['[Errno 54] Connection reset by peer']) 
Fri Oct 22 19:50:43 2010 Info: Connection Error: DCID: 220130796 domain: columbia.edu IP: 126.96.36.199 port: 25 details: [Errno 60] Operation timed out interface: 206.XX.XX.XX reason: network error
Fri Oct 22 19:50:43 2010 Info: Delayed: DCID 220130796 MID 341956009 to RID 0 - 4.4.0 - Other network problem ('000', ['[Errno 60] Operation timed out']) 
Sat Oct 23 09:30:51 2010 Info: Connection Error: DCID: 220178402 domain: yahoo.com IP: 188.8.131.52 port: 25 details: [Errno 54] Connection reset by peer interface: 206.XX.XX.XX reason: network error
Sat Oct 23 09:30:51 2010 Info: Delayed: DCID 220178402 MID 342019082 to RID 0 - 4.4.0 - Other network problem ('000', ['[Errno 54] Connection reset by peer']) 
Sometime, it is able to deliver few messages after several attempts. But most of the times messages are bounced after maximum attempts tried.
Any help to resolve this issue will be highly appreciated.
looks like the delivery timeout of five minutes that occurs here. Means every message to be send out needs to be completed within five minutes, otherwise a timeout error will occur and the IronÜprt will close the connection. Check these DCIDs from them moment the log/tracking states "New SMTP DCID" and "Delivery sstarted MID XXXX DCID XXXX" Or post the whole output here. If you run into that problem then most likely a bandwith issue is the case, if that happens a common thing to do is to decrese the number of outbound concurrent connections.
the same issue.
4.4.0 - Other network problem ('000', ['[Errno 54] Connection reset by peer']
version of AsynOS 6.5.2-101 (c150)
Please check your DNS record whether you have implemented a SPF record for ipv4 and/or for IPv6.
You can do a check here, if your dns already have an SPF record and for ipv4 and ipv6
We've got the same problem.
For some messages, different destinations we get these errors:
Info: Delivery start DCID 447xxxx MID 1224xxxx to RID 
Info: Delayed: DCID 447xxxx MID 1224xxxx to RID 0 - 4.4.0 - Other network problem ('000', ['[Errno 54] Connection reset by peer']) 
Info: MID 122xxxxxxx to RID  pending till Tue Oct 30 16:34:30 2012 [Default]
This mail arrived yesterday and it is still the queue. Every try for delivery fails.
At hte same time other message to the same destination were delivered successfully.
SMTPPING or telnet to the destination server works fine.
We are using two c350 (AsyncOS v7.6.1-022) at different locations. Both of them have these problems.
The problem occurs to other destinations as well. Maybe depending on the message itself???
What's the message size of these stuck messages compared to those getting trough? And what's the time difference between DCID start and failure?
The problem is solved. I opened up a case and they gave me the hint. The resaon for this behaviour was the esmtp inspection at the firewalls. After disabling this feature globally at our firewalls, everything works fine now and the queued messages were delivered.
I also have this problem BUT only when sending mail to cisco.com (!!) via IPv6.
4.4.2 - Bad connection ('000', ['TimeoutError'])
4.4.0 - Other network problem ('000', ['[Errno 60]
We can send to other sites with IPv6 without any issues.
Im running two IronPort C170/160 in a cluster with version v7.6.2-014 on them
Same issue, aync OS 8.0
Reason: 4.4.0 - Other network problem ('000', ['[Errno 60] Operation timed out']
We will check the firewall and update the post.
other network problem ('000',errno 54] connection reset by peer')
I use the Meraki MX80 just recently purchased by Cisco and one of our clients using the Ironport was getting above message as well. I turned off the "Layer 7 blocking" on the Meraki appliance which was blocking all PtoP, video streaming, and the like and emails started coming through...
we get these errors too, just adding our company to the list, strength in numbers, I have a case opened for Reason: 4.4.0 Errno 54 but will ask them about Errno 60 as well
oh snap didn't realize you posted this 5 years ago, nice, and still no answer / solution from Cisco
Generally with "Errno 60" and a 4.4.0 - this is indicative of a firewall between the ESA and the destination mail server.
The 400 series of codes indicate non-fatal errors or responses in the SMTP conversation. Such errors are often referred to as soft-bounces, as unless otherwise instructed, the transmitting mail server will re-attempt delivery to the intended receiver at a later time.
Try to manually telnet to the smtproute for this, and then manually send an email.
If there is a Cisco PIX firewall between these two MTA's, the FW may still have the fix-up protocol enabled.