We have Exchange 2010 environment with shadow redundency feature enabled on transport server. few of our clients reported that they have been recieving certain emails mutiple times. however when we check the queue status on edge server, the message is still in queue with retry state. As of now we are suspending the queue when such situation occurs however we need a permanent fix to this problem and your input will be appreciated,

Hi Sajjan, Please install the lastest service pack and rollup for Exchange 2010(SP1 rollup 6) first if you didn't do it. These mails are internal mails or external ones? Please run the Tracking Log Explorer in the Toolbox to track the duplicated message and post the result here. Frank

Hi Sajjan, Please could you post the message header of original and duplicate email to track more details. -Srini-

Hi Srinivasan, Please find the Below message Header. Original Message Header X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from Bb.aa.cc.com ([53.32.141.131]) by bell.aa.cc.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 18 Nov 2011 19:46:39 -0600 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_005_01CCA65D.14522980" Received: from out.river.com ([53.32.141.133]) by Bb.aa.cc.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 18 Nov 2011 19:46:38 -0600 Received: from [10.248.226.35] (HELO inbo.river.com) by out.river.com (CommuniGate Pro SMTP 5.3.2) with ESMTP id 614880312 for xyz@xyz.com; Fri, 18 Nov 2011 19:46:30 -0600 Received: by inbo.river.com (CommuniGate Pro PIPE 5.4.1) with PIPE id 215710923; Fri, 18 Nov 2011 19:46:38 -0600 Received: from [110.111.161.1] (HELO Inmuedge01.a4g.port.com) by inbo.river.com (CommuniGate Pro SMTP 5.4.1) with ESMTPS id 215709154 for xyz@xyz.com; Fri, 18 Nov 2011 19:24:18 -0600 Received: from Inmuhub01.a4g.port.com (109.111.0.28) by ongoing.port.com (10.111.10.194) with Microsoft SMTP Server (TLS) id 14.1.339.1; Fri, 18 Nov 2011 22:24:46 +0530 Received: from Inmumailbox10.a4g.port.com ([fe80::32:99fd:c97a:290c]) by Inmuhub01.a4g.port.com ([::1]) with mapi id 14.01.0339.001; Fri, 18 Nov 2011 22:24:43 +0530 Content-Language: en-US Return-Path: <Sss@a4g.port.com> X-OriginalArrivalTime: 19 Nov 2011 01:46:38.0552 (UTC) FILETIME=[140DCD80:01CCA65D] X-Primary: xyz@xyz.com X-Note-Sending-IP: 110.111.161.1 X-Note: Mail Class: ALLOWEDSENDER X-Country-Path: ->->INDIA->UNITED STATES X-Note-Reverse-DNS: mx1.port.com X-Policy: xyz.com X-Virus-Scan: V-X0M0 x-allow: @port.com ALLOWED X-Originating-IP: [10.111.0.90] Accept-Language: en-US X-Note-AR-ScanTimeLocal: 11/18/2011 7:46:35 PM X-Note-AR-Scan: None - PIPE X-Note-Return-Path: Sss@a4g.port.com Content-Class: urn:content-classes:message Subject: RE: Request if possible Date: Fri, 18 Nov 2011 10:54:41 -0600 Message-ID: <BC785792C0FF4948BCF569D684E417420A2C2687@Inmumailbox10.a4g.port.com> In-Reply-To: <6DA1334395E2204587DA5F0BD5DF3ECE03B35281@Bell.aa.cc.com> X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: Request if possible Thread-Index: AcykxkTLFm06Kj7ITcC+nl6kUSYY1ABSZECwAAApvNA= References: <295244FC3900FE41A03741AA281C4F7F20883BBE@Bell.aa.cc.com> <6DA1334395E2204587DA5F0BD5DF3ECE03B35281@Bell.aa.cc.com> From: ss <Sss@a4g.port.com> To: xy xyz@xyz.com Duplicate Message Header X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from bc.aa.cc.com ([53.32.141.139]) by bell.aa.cc.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 18 Nov 2011 21:16:46 -0600 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_003_01CCA669.AB24E300" Received: from out.river.com ([53.32.141.133]) by bc.aa.cc.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 18 Nov 2011 21:16:45 -0600 Received: from [10.241.227.24] (HELO inbo.river.com) by out.river.com (CommuniGate Pro SMTP 5.3.2) with ESMTP id 614890367 for xyz@xyz.com; Fri, 18 Nov 2011 21:16:46 -0600 Received: by inbo.river.com (CommuniGate Pro PIPE 5.4.1) with PIPE id 214459998; Fri, 18 Nov 2011 21:16:02 -0600 Received: from [110.111.161.1] (HELO Inmuedge01.a4g.port.com) by inbo.river.com (CommuniGate Pro SMTP 5.4.1) with ESMTPS id 214458404 for xyz@xyz.com; Fri, 18 Nov 2011 20:55:26 -0600 Received: from Inmuhub01.a4g.port.com (109.111.0.28) by ongoing.port.com (10.111.10.194) with Microsoft SMTP Server (TLS) id 14.1.339.1; Fri, 18 Nov 2011 22:24:46 +0530 Received: from Inmumailbox10.a4g.port.com ([fe80::32:99fd:c97a:290c]) by Inmuhub01.a4g.port.com ([::1]) with mapi id 14.01.0339.001; Fri, 18 Nov 2011 22:24:43 +0530 Content-Language: en-US Return-Path: <Sss@a4g.port.com> X-OriginalArrivalTime: 19 Nov 2011 03:16:45.0664 (UTC) FILETIME=[AAF19E00:01CCA669] X-Primary: xyz@xyz.com X-Note-Sending-IP: 110.111.161.1 X-Note: Mail Class: ALLOWEDSENDER X-Country-Path: ->->INDIA->UNITED STATES X-Note-Reverse-DNS: mx1.port.com X-Policy: xyz.com X-Virus-Scan: V-X0M0 x-allow: @port.com ALLOWED X-Originating-IP: [10.111.0.90] Accept-Language: en-US X-Note-AR-ScanTimeLocal: 11/18/2011 9:16:00 PM X-Note-AR-Scan: None - PIPE X-Note-Return-Path: Sss@a4g.port.com Content-Class: urn:content-classes:message Subject: RE: Request if possible Date: Fri, 18 Nov 2011 10:54:41 -0600 Message-ID: <BC785792C0FF4948BCF569D684E417420A2C2687@Inmumailbox10.a4g.port.com> In-Reply-To: <6DA1334395E2204587DA5F0BD5DF3ECE03B35281@Bell.aa.cc.com> X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: Request if possible Thread-Index: AcykxkTLFm06Kj7ITcC+nl6kUSYY1ABSZECwAAApvNA= References: <295244FC3900FE41A03741AA281C4F7F20883BBE@Bell.aa.cc.com> <6DA1334395E2204587DA5F0BD5DF3ECE03B35281@Bell.aa.cc.com> From: ss <Sss@a4g.port.com> To: xy <xyz@xyz.com>

Original Message : Received: from [10.241.227.24] (HELO inbo.river.com) by out.river.com (CommuniGate Pro SMTP 5.3.2) with ESMTP id 614890367 for xyz@xyz.com; Fri, 18 Nov 2011 21:16:46 -0600 Duplicate email : Received: from [10.248.226.35] (HELO inbo.river.com) by out.river.com (CommuniGate Pro SMTP 5.3.2) with ESMTP id 614880312 for xyz@xyz.com; Fri, 18 Nov 2011 19:46:30 -0600 ==== I hope that 10.241.227.24 and 10.248.226.35 are not Exchange Server, Please could you share more details about box which assisgned with that IP address as message was duplicated from the previous hop which sends that email. Please could you verify again and let me know the details. -Srini-

Hi Srinivasan, Please ignore the previous message Header. Original Message Header X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from Bb.aa.cc.com ([53.32.141.131]) by bell.aa.cc.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 18 Nov 2011 19:46:39 -0600 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_005_01CCA65D.14522980" Received: from out.river.com ([53.32.141.133]) by Bb.aa.cc.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 18 Nov 2011 19:46:38 -0600 Received: from [10.248.226.35] (HELO inbo.river.com) by out.river.com (CommuniGate Pro SMTP 5.3.2) with ESMTP id 614880312 for xyz@xyz.com; Fri, 18 Nov 2011 19:46:30 -0600 Received: by inbo.river.com (CommuniGate Pro PIPE 5.4.1) with PIPE id 215710923; Fri, 18 Nov 2011 19:46:38 -0600 Received: from [110.111.161.1] (HELO Inmuedge01.a4g.port.com) by inbo.river.com (CommuniGate Pro SMTP 5.4.1) with ESMTPS id 215709154 for xyz@xyz.com; Fri, 18 Nov 2011 19:24:18 -0600 Received: from Inmuhub01.a4g.port.com (109.111.0.28) by ongoing.port.com (10.111.10.194) with Microsoft SMTP Server (TLS) id 14.1.339.1; Fri, 18 Nov 2011 22:24:46 +0530 Received: from Inmumailbox10.a4g.port.com ([fe80::32:99fd:c97a:290c]) by Inmuhub01.a4g.port.com ([::1]) with mapi id 14.01.0339.001; Fri, 18 Nov 2011 22:24:43 +0530 Content-Language: en-US Return-Path: <Sss@a4g.port.com> X-OriginalArrivalTime: 19 Nov 2011 01:46:38.0552 (UTC) FILETIME=[140DCD80:01CCA65D] X-Primary: xyz@xyz.com X-Note-Sending-IP: 110.111.161.1 X-Note: Mail Class: ALLOWEDSENDER X-Country-Path: ->->INDIA->UNITED STATES X-Note-Reverse-DNS: mx1.port.com X-Policy: xyz.com X-Virus-Scan: V-X0M0 x-allow: @port.com ALLOWED X-Originating-IP: [10.111.0.90] Accept-Language: en-US X-Note-AR-ScanTimeLocal: 11/18/2011 7:46:35 PM X-Note-AR-Scan: None - PIPE X-Note-Return-Path: Sss@a4g.port.com Content-Class: urn:content-classes:message Subject: RE: Request if possible Date: Fri, 18 Nov 2011 10:54:41 -0600 Message-ID: <BC785792C0FF4948BCF569D684E417420A2C2687@Inmumailbox10.a4g.port.com> In-Reply-To: <6DA1334395E2204587DA5F0BD5DF3ECE03B35281@Bell.aa.cc.com> X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: Request if possible Thread-Index: AcykxkTLFm06Kj7ITcC+nl6kUSYY1ABSZECwAAApvNA= References: <295244FC3900FE41A03741AA281C4F7F20883BBE@Bell.aa.cc.com> <6DA1334395E2204587DA5F0BD5DF3ECE03B35281@Bell.aa.cc.com> From: ss <Sss@a4g.port.com> To: xy xyz@xyz.com Duplicate Message Header X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from bc.aa.cc.com ([53.32.141.139]) by bell.aa.cc.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 18 Nov 2011 21:16:46 -0600 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_003_01CCA669.AB24E300" Received: from out.river.com ([53.32.141.133]) by bc.aa.cc.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 18 Nov 2011 21:16:45 -0600 Received: from [10.248.226.29] (HELO inbo.river.com) by out.river.com (CommuniGate Pro SMTP 5.3.2) with ESMTP id 614890367 for xyz@xyz.com; Fri, 18 Nov 2011 21:16:46 -0600 Received: by inbo.river.com (CommuniGate Pro PIPE 5.4.1) with PIPE id 214459998; Fri, 18 Nov 2011 21:16:02 -0600 Received: from [110.111.161.1] (HELO Inmuedge01.a4g.port.com) by inbo.river.com (CommuniGate Pro SMTP 5.4.1) with ESMTPS id 214458404 for xyz@xyz.com; Fri, 18 Nov 2011 20:55:26 -0600 Received: from Inmuhub01.a4g.port.com (109.111.0.28) by ongoing.port.com (10.111.10.194) with Microsoft SMTP Server (TLS) id 14.1.339.1; Fri, 18 Nov 2011 22:24:46 +0530 Received: from Inmumailbox10.a4g.port.com ([fe80::32:99fd:c97a:290c]) by Inmuhub01.a4g.port.com ([::1]) with mapi id 14.01.0339.001; Fri, 18 Nov 2011 22:24:43 +0530 Content-Language: en-US Return-Path: <Sss@a4g.port.com> X-OriginalArrivalTime: 19 Nov 2011 03:16:45.0664 (UTC) FILETIME=[AAF19E00:01CCA669] X-Primary: xyz@xyz.com X-Note-Sending-IP: 110.111.161.1 X-Note: Mail Class: ALLOWEDSENDER X-Country-Path: ->->INDIA->UNITED STATES X-Note-Reverse-DNS: mx1.port.com X-Policy: xyz.com X-Virus-Scan: V-X0M0 x-allow: @port.com ALLOWED X-Originating-IP: [10.111.0.90] Accept-Language: en-US X-Note-AR-ScanTimeLocal: 11/18/2011 9:16:00 PM X-Note-AR-Scan: None - PIPE X-Note-Return-Path: Sss@a4g.port.com Content-Class: urn:content-classes:message Subject: RE: Request if possible Date: Fri, 18 Nov 2011 10:54:41 -0600 Message-ID: <BC785792C0FF4948BCF569D684E417420A2C2687@Inmumailbox10.a4g.port.com> In-Reply-To: <6DA1334395E2204587DA5F0BD5DF3ECE03B35281@Bell.aa.cc.com> X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: Request if possible Thread-Index: AcykxkTLFm06Kj7ITcC+nl6kUSYY1ABSZECwAAApvNA= References: <295244FC3900FE41A03741AA281C4F7F20883BBE@Bell.aa.cc.com> <6DA1334395E2204587DA5F0BD5DF3ECE03B35281@Bell.aa.cc.com> From: ss <Sss@a4g.port.com> To: xy <xyz@xyz.com>

It looks like the issue is happening after the server with IP 10.111.10.194. We need to track the email history from that server to see why problem email was delivered multiple times. Please verify message tracking log and protocol logs to verify more, if it reproducable netmon trace will help you. -Srini-