Strange behavior Ironport

Unanswered Question
Jul 23rd, 2009

A user has send a e-mail to company x. The user from company x has received the e-mail. But he does get this e-mail now like every hour.

I have checked the message with message tracking on my Ironport. I see in the log that the message keeps retraying. But like before, the message is already deliverd. Somehow the Ironport probley thinks it is not deliverd yet.

Hopefully someone can help me with this.



_____________________________________________________________

21 Jul 2009 12:45:22 (GMT +0200)
Message 10343849 queued for delivery.

21 Jul 2009 12:45:22 (GMT +0200)
SMTP delivery connection (DCID 2495923) opened from IronPort interface 1.2.3.4 to IP address 213.207.102.166 on port 25.

21 Jul 2009 12:45:23 (GMT +0200) (DCID 2495923) Delivery started for message 10343849 to (no recipient data).

21 Jul 2009 12:45:23 (GMT +0200)
(DCID 2495923) Message 10343849 to RID 0 delayed. Reason: 4.4.0 - Other network problem ('000', ['[Errno 54] Connection reset by peer']) []

21 Jul 2009 12:45:23 (GMT +0200)
Message 10343849 to (no recipient data) pending until Tue Jul 21 12:46:23 2009 as per bounce profile Default.

21 Jul 2009 12:46:25 (GMT +0200)
SMTP delivery connection (DCID 2495930) opened from IronPort interface 1.2.3.4 to IP address 213.207.102.166 on port 25.

21 Jul 2009 12:46:25 (GMT +0200)
(DCID 2495930) Delivery started for message 10343849 to (no recipient data).

21 Jul 2009 12:46:25 (GMT +0200)
(DCID 2495930) Message 10343849 to RID 0 delayed. Reason: 4.4.0 - Other network problem ('000', ['[Errno 54] Connection reset by peer']) []

21 Jul 2009 12:46:25 (GMT +0200)
Message 10343849 to (no recipient data) pending until Tue Jul 21 12:48:31 2009 as per bounce profile Default.

21 Jul 2009 12:48:32 (GMT +0200)
SMTP delivery connection (DCID 2495938) opened from IronPort interface 1.2.3.4 to IP address 213.207.102.166 on port 25.

21 Jul 2009 12:48:32 (GMT +0200)
(DCID 2495938) Delivery started for message 10343849 to (no recipient data).

21 Jul 2009 12:48:32 (GMT +0200)
(DCID 2495938) Message 10343849 to RID 0 delayed. Reason: 4.4.0 - Other network problem ('000', ['[Errno 54] Connection reset by peer']) []

21 Jul 2009 12:48:32 (GMT +0200)
Message 10343849 to (no recipient data) pending until Tue Jul 21 12:54:53 2009 as per bounce profile Default.

21 Jul 2009 12:54:54 (GMT +0200)
SMTP delivery connection (DCID 2496007) opened from IronPort interface 1.2.3.4 to IP address 213.207.102.166 on port 25.

21 Jul 2009 12:54:54 (GMT +0200)
(DCID 2496007) Delivery started for message 10343849 to (no recipient data).

21 Jul 2009 12:54:54 (GMT +0200)
(DCID 2496007) Message 10343849 to RID 0 delayed. Reason: 4.4.0 - Other network problem ('000', ['[Errno 54] Connection reset by peer']) []

21 Jul 2009 12:54:54 (GMT +0200)
Message 10343849 to (no recipient data) pending until Tue Jul 21 13:13:59 2009 as per bounce profile Default.

21 Jul 2009 13:14:00 (GMT +0200)
SMTP delivery connection (DCID 2496196) opened from IronPort interface 1.2.3.4 to IP address 80.69.76.190 on port 25.

21 Jul 2009 13:14:01 (GMT +0200)
(DCID 2496196) Delivery started for message 10343849 to (no recipient data).

21 Jul 2009 13:14:01 (GMT +0200)
(DCID 2496196) Message 10343849 to RID 0 delayed. Reason: 4.4.0 - Other network problem ('000', ['[Errno 54] Connection reset by peer']) []

21 Jul 2009 13:14:01 (GMT +0200)
Message 10343849 to (no recipient data) pending until Tue Jul 21 14:11:18 2009 as per bounce profile Default.

21 Jul 2009 14:11:19 (GMT +0200)
SMTP delivery connection (DCID 2496854) opened from IronPort interface 1.2.3.4 to IP address 213.207.102.166 on port 25

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
kyerramr Fri, 07/24/2009 - 03:38

You might want to open a support case on this issue with the version you are currently running. The logs you have retrieved indicate that there was network issue/error while delivering the message and this was re queued for delivery. Support would be helpful in running additional debug and packet captures to trace this issue.

Thanks,
Kishore

jloehler_ironport Fri, 07/24/2009 - 07:26

I saw this behaviour several times in the last year. As far as I remember there was a bug in the AsyncOS. Do you have the latest release on your system?

Regards,

Joerg

dvdlinden_ironport Fri, 07/24/2009 - 08:17

First of all thx for the reply's so far.

At the moment we are ussing version v6.3.5-003.
Just made a ticket aswell. If I know more about this problem, i will update this post.

jloehler_ironport Fri, 07/24/2009 - 09:01

That's what I've found in my mail archive:

Fixed: Messages with Footers Sent Multiple Times
Previously, when the IronPort appliance added a footer to an outgoing HTML message, the message may be sent to the recipient multiple times. This occurred because the IronPort appliance failed to escape leading dots as required by the SMTP protocol, resulting in a partial message being sent. In some cases, the appliance failed to see the response from the remote server and resent the message.
This issue has been resolved. The appliance correctly escapes dots when it adds a footer and outgoing messages are not truncated.
[Defect ID: 41255]

Fixed in 6.3.6

dvdlinden_ironport Fri, 07/24/2009 - 13:41

The feedback from Ironport Support was indeed that this was a know issue. So the advice was to upgrade the AsynchOS.

After the firmware update. Some messages did resolve by themself. Some others I had to manuel delete from the que.

Everything looks ok now. Thx for all the replys.

Best regards,
David

Actions

This Discussion