You have i7.com configured as an authoritative accepted domain, meaning that Exchange is responsible for all mail to that domain. However, you have a send connector for i7.com, i7_Domino_Outbound, which sends unresolved i7.com mail somewhere else. Those two are incompatible. You might want to change accepted domain i7.com to ExternalRelay if it's relayed through the Edge server, or InternalRelay if it's relayed directly by the hub transport server.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi ED, here i would like to update that when ever i am sending an email to change request@i7.com and checking the queues then the message is gng to submission queue the stuck there for a while and then getting the NDR pls find the below Identity: EDGE01\Submission\440312 Subject: test message Internet Message ID: <6B67B54EF023514286231115A1DCD6220C55AA72@IN1PRDMBXVS1.abc.corp.local> From Address: james.bond@abc.com Status: Retry Size (KB): 6 Message Source Name: SMTP:Default internal receive connector EDGE01 Source IP: 10.104.0.216 SCL: -1 Date Received: 10/5/2011 1:21:50 PM Expiration Time: 10/7/2011 1:21:50 PM Last Error: A local loop was detected. Queue ID: EDGE01\Submission Recipients: ChangeRequest%i7Tech@i7.com

What are you trying to do with mail to that address?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Thanks Ed, on your reply .. and all effort. here i just want to update that while digging into more about the change request SMTP address found that change request is an application which does not support email integration so that's the issue. Thanks to Rich as well.

Are those aliases defined in your accepted domains? Do you have send connectors configured for those domains that routes the mail to the appropriate application host or hosts? Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Nothing one user is getting the email from Changerequest@i7.com email address so when he is replying back to that email he is getting the bounce back message which i mentioned above. apart from this the target address is some sort of address which i am not able to find anywhere ? Just added as an External SMTP address.

On Sat, 1 Oct 2011 04:52:08 +0000, amit79 wrote: >Ed, what would be the troubleshooting steps to figured it out , but as i am suspecting it's a issue with mail looping so is any tools where i can check the same ??? If you have the NDR, and the NDR includes the headers of the message that failed (which it does), the "Received:" headers should reflect the loop. The "cashub1" machine thinks the message should be handled by the "maileme" machine. The "maileme" machine think it should be handled by the "cashub1" machine. cashub1 -> maileme -> cashub1 -> maileme -> etc. Are "maileme" and "edge2" the same machine with two NICs installed? Here are the "Received:" headers (stripped down to just show the loop):. Read them from the bottom, up: Received: from Edge1.abc.com (192.168.1.2) by cashub1.abc.corp.local (10.10.1.2) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 14:29:25 +0100 Received: from cashub1.abc.corp.local (10.10.1.2) by maileme.abc.com (192.168.1.2) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 14:28:40 +0100 Received: from edge2.abc.com (192.168.1.1) by cashub1.abc.corp.local (10.10.1.2) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 14:29:24 +0100 Received: from cashub1.abc.corp.local (10.10.1.2) by maileme.abc.com (192.168.1.1) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 14:28:22 +0100 Received: from MBXVS1.abc.corp.local ([fe80::ccc8:f0bb:a3f7:6237]) by cashub1.abc.corp.local ([fe80::1df1:2e66:80b7:8a5e%10]) with mapi; Thu, 29 Sep 2011 14:29:24 +0100 From: James Bond <james.bond@abc.com> To: ChangeRequest <changerequest@i7.com> Date: Thu, 29 Sep 2011 14:27:30 +0100 Subject: RE: Business Owner Approval for: To install the MS patches at Saturday 11:00 PM CST to Sunday 01:00 AM CST Thread-Topic: Business Owner Approval for: To install the MS patches at Saturday 11:00 PM CST to Sunday 01:00 AM CST Thread-Index: Acx+q2CMOT+8SfVxSEeDklVzVDCrrwAAAVdQ Message-ID: <18A1710691464148B5906CEA8CECEF6E023D17C602@MBXVS1.abc.corp.local> References: <OF26AAED8C.691D5771-ON8625791A.0049C5BB@i7.com> In-Reply-To: <OF26AAED8C.691D5771-ON8625791A.0049C5BB@i7.com> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Return-Path: James.bond@abc.com --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

You have i7.com configured as an authoritative accepted domain, meaning that Exchange is responsible for all mail to that domain. However, you have a send connector for i7.com, i7_Domino_Outbound, which sends unresolved i7.com mail somewhere else. Those two are incompatible. You might want to change accepted domain i7.com to ExternalRelay if it's relayed through the Edge server, or InternalRelay if it's relayed directly by the hub transport server.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Your Edge server thinks the recipient is internal to your organization or your connectors are fouled up.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

I doubt that is coming from your Exchange. But I really can't tell from the pieces you've posted. If you want further diagnosis, post the complete headers of the message without changing anything, and the exact unchanged output from Get-AcceptedDomain, and Get-SendConnector. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi Ed, Under the accepted domain "i7.com" is configured as an authoritative domain which is set to false by default. Apart from this Under the Send connector there is a send connector configured which is set to disabled; address space is configured with "1" cost and under the network tab i am seeing route mail through the following smart host is there which i a unable to ping the smart host. And Under the source servers are all CASHUB server listed. Do i need to change the the setting under the network TAB to use DNS "MX" record to route email..??? Or do i need to change the setting under the accepted domain from "Authoritative" to "Internal relay Domain." and enabled ??

Apart from this there is only Mail contact in exchange GAL called " changerequest@i7.com" there is no mailbox associated with this kind of email address When we configure an internal relay domain, some or all of the recipients in this domain don't have mailboxes in this Exchange organization as i mentioned above there is no mailbox. Mail from the Internet is relayed for this domain through Hub Transport servers in this Exchange organization. but here I am sending the mail inside the org. As while gng through the below URL for internal mail domain in my scenario Accepted domain is there but set as a Authoritative domain as mentioned above and send connecter is also in place but seems to be disabled so while change the Authoritative to internet relay and enabling the connect will fix the issue http://technet.microsoft.com/en-us/library/bb124423.aspx#RDomains

What is the target address for the mailcontact? Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

On Mon, 3 Oct 2011 05:40:17 +0000, amit79 wrote: > > >Hi Rich, > >Thanks for your reply , here i would like to mention that "mailema.abc.com" are the alias used by application or application groups. Mailema and Edge are the different machines and on Edge machine there is only one NIC installed. Starting at the bottom of the "Received:" headers and working up the list gives some odd results: 1. MBXVS1.abc.corp.local 2. cashub1.abc.corp.local (10.10.1.2) 3. maileme.abc.com (192.168.1.2) **how did the message get to edge2.abc.com (192.168.1.1) 4. cashub1.abc.corp.local (10.10.1.2) 5. maileme.abc.com (192.168.1.2) **how did the message get to edge1.abc.com (192.168.1.2) -- and why does edge1 and how does maileme have the same IP address? 6. cashub1.abc.corp.local (10.10.1.2) There's no "Received:" header showing the transfer of the message from #3 (maileme) to edge2, yet #4 shows the message received from edge2. There's no "Received:" header showing the transfer of the message from #5 (maileme) to edge1, yet 6 shows the message received from edge1. And how did edge1 and maileme get the same IP address? Have you edited these "Received:" headers? If you did, I'm done with this thread. If you haven't, then you have some infrastructure problems to address. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Ed, what would be the troubleshooting steps to figured it out , but as i am suspecting it's a issue with mail looping so is any tools where i can check the same ???

Hi ED, Target address - SMTP:ChangeRequest%i7Tech@i7.com. One more thing i wanted to know like as we are sending a mail to changerequest@i7.com if there will be no mailbox then how the mail will be delivered to that address, or is there any possibility that address is hidden somewhere ??

ED, please find the below and in your first post you pointed out that "our Edge server thinks the recipient is internal to your organization " so here i would like to inform you that this is our internal only , earlier this was the domain i7 and after merging to abc.com @i7.com SMTP address are also in place. But when i am checked the changerequest@i7.com SMTP addres i did not found the mailbox only Mail contact is there which i mentioned as above. So is that the reason whenever i am reply back to changerequest@i7.com address getting NDR ... [PS] C:\Windows\system32>get-accepteddomain Name DomainName DomainTy Default ---- ---------- -------- ------- localtemp localtemp Autho... False corp.local corp.local Autho... False abc.com abc.com Autho... True abc-emea.com abc-emea.com Autho... False i7.com i7.com Autho... False i7-usergroup.org i7-usergroup.org Autho... False [PS] C:\Windows\system32>get-sendconnector Identity AddressSpaces Enabled -------- ------------- ------- EdgeSync - Maryland1 to Internet {SMTP:*;1} True EdgeSync - Inbound to Maryland1 {smtp:--;100} True EdgeSync - Inbound to UnitedKingdom1 {smtp:--;100} True EdgeSync - UnitedKingdom1 to Internet {SMTP:*;1} True EdgeSync - India1 to Internet {SMTP:*;1} True EdgeSync - Inbound to India1 {smtp:--;100} True i7_Domino_Outbound {SMTP:i7.com;1} False Exchg07 to leni7.com {SMTP:lenedi01.leni7.com;1} False

Hi Rich, Thanks for your reply , here i would like to mention that "mailema.abc.com" are the alias used by application or application groups. Mailema and Edge are the different machines and on Edge machine there is only one NIC installed.

Guys needs small help seems to be mail looping issue but how can be fixed ??below is the header info. One of the user getting approval requests (patch applications) from ChangeRequest@i7.com. However, when he respond, replies are rejected – see below. --------------------------- From: Microsoft Exchange Sent: 29 September 2011 15:32 To: James bond Subject: Undeliverable: RE: To install the MS patches at Saturday 11:00 PM CST to Sunday 01:00 AM CST Delivery has failed to these recipients or distribution lists: ChangeRequest%i7Tech@i7.com A problem occurred during the delivery of this message. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message later, or provide the following diagnostic text to your system administrator. The following organization rejected your message: maileme.abc.com. _____ Sent by Microsoft Exchange Server 2007 Diagnostic information for administrators: Generating server: cashub2.abc.corp.local ChangeRequest%i7Tech@i7.com maileme.abc.com #554 5.4.6 Hop count exceeded - possible mail loop ##rfc822;changerequest@i7.com Original message headers: Received: from edge2.abc.com (192.168.1.1) by cashub2.abc.corp.local (10.10.1.1) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 15:31:48 +0100 Received: from cashub2.abc.corp.local (10.10.1.1) by maileme.abc.com (192.168.1.1) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 15:15:42 +0100 Received: from Edge1.abc.com (192.168.1.2) by cashub2.abc.corp.local (10.10.1.1) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 15:16:44 +0100 Received: from cashub2.abc.corp.local (10.10.1.1) by maileme.abc.com (192.168.1.2) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 15:00:56 +0100 Received: from edge2.abc.com (192.168.1.1) by cashub2.abc.corp.local (10.10.1.1) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 15:01:39 +0100 Received: from cashub1.abc.corp.local (10.10.1.2) by maileme.abc.com (192.168.1.1) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 14:45:36 +0100 Received: from Edge1.abc.com (192.168.1.2) by cashub1.abc.corp.local (10.10.1.2) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 14:46:06 +0100 Received: from cashub1.abc.corp.local (10.10.1.2) by maileme.abc.com (192.168.1.2) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 14:30:20 +0100 Received: from Edge1.abc.com (192.168.1.2) by cashub1.abc.corp.local (10.10.1.2) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 14:30:31 +0100 Received: from cashub1.abc.corp.local (10.10.1.2) by maileme.abc.com (192.168.1.2) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 14:29:12 +0100 Received: from Edge1.abc.com (192.168.1.2) by cashub1.abc.corp.local (10.10.1.2) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 14:29:56 +0100 Received: from cashub2.abc.corp.local (10.10.1.1) by maileme.abc.com (192.168.1.2) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 14:28:41 +0100 Received: from edge2.abc.com (192.168.1.1) by cashub2.abc.corp.local (10.10.1.1) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 14:29:25 +0100 Received: from cashub1.abc.corp.local (10.10.1.2) by maileme.abc.com (192.168.1.1) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 14:28:23 +0100 Received: from Edge1.abc.com (192.168.1.2) by cashub1.abc.corp.local (10.10.1.2) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 14:29:25 +0100 Received: from cashub1.abc.corp.local (10.10.1.2) by maileme.abc.com (192.168.1.2) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 14:28:40 +0100 Received: from edge2.abc.com (192.168.1.1) by cashub1.abc.corp.local (10.10.1.2) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 14:29:24 +0100 Received: from cashub1.abc.corp.local (10.10.1.2) by maileme.abc.com (192.168.1.1) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 29 Sep 2011 14:28:22 +0100 Received: from MBXVS1.abc.corp.local ([fe80::ccc8:f0bb:a3f7:6237]) by cashub1.abc.corp.local ([fe80::1df1:2e66:80b7:8a5e%10]) with mapi; Thu, 29 Sep 2011 14:29:24 +0100 From: James Bond <james.bond@abc.com> To: ChangeRequest <changerequest@i7.com> Date: Thu, 29 Sep 2011 14:27:30 +0100 Subject: RE: Business Owner Approval for: To install the MS patches at Saturday 11:00 PM CST to Sunday 01:00 AM CST Thread-Topic: Business Owner Approval for: To install the MS patches at Saturday 11:00 PM CST to Sunday 01:00 AM CST Thread-Index: Acx+q2CMOT+8SfVxSEeDklVzVDCrrwAAAVdQ Message-ID: <18A1710691464148B5906CEA8CECEF6E023D17C602@MBXVS1.abc.corp.local> References: <OF26AAED8C.691D5771-ON8625791A.0049C5BB@i7.com> In-Reply-To: <OF26AAED8C.691D5771-ON8625791A.0049C5BB@i7.com> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Return-Path: James.bond@abc.com