Exchange 2007 Queue question - Last Error: A local loop was detected.
Hi,
Got an error with adding a new domain for Exchange receive email for.
We've been using "domain1.co.uk" for a while now, email flows fine, we want to add "domain2.com" to our email address policy so users can receive email for this address.
I've added the domain to our "accepted domains" list on the organisation Configuration --> Hub Transport.
I then update the "Email Address Policy" to add in the new domain "domain2.com" and applied it.
I checked users on Exchange had the new domain under their "email address" tab, which they do.
We have changed the delivery IP on the domain's MX record to point to our server.
I can now see email arriving to the Exchange server, but it is stuck in the "Submission" queue, with an error: "Last Error: A local loop was detected."
I've no idea what this means, or how to fix it - can anyone help please?
Thanks
Got an error with adding a new domain for Exchange receive email for.
We've been using "domain1.co.uk" for a while now, email flows fine, we want to add "domain2.com" to our email address policy so users can receive email for this address.
I've added the domain to our "accepted domains" list on the organisation Configuration --> Hub Transport.
I then update the "Email Address Policy" to add in the new domain "domain2.com" and applied it.
I checked users on Exchange had the new domain under their "email address" tab, which they do.
We have changed the delivery IP on the domain's MX record to point to our server.
I can now see email arriving to the Exchange server, but it is stuck in the "Submission" queue, with an error: "Last Error: A local loop was detected."
I've no idea what this means, or how to fix it - can anyone help please?
Thanks
Amit
http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/0c52a2c1-9248-4c8f-a6ce-9660e99a180f/
This could be caused by the connector on your DR Exchange server. Is that still sending and receiving email?
ASKER
That’s what I was thinking Hypercat, but I'm not sure how to check that?
The error in the queued email is:
So it appears it is receiving it from the Receive Connector correctly? Looking at the receive connector on the main Exchange server, it has its own IP in the "use these local IP addresses to receive email". You can see from the screenie:
The IP's 192.168.60.0 is our dev network.
Ignorance is playing a big part here, I'm not sure how to tell it not to use the other DR Exchange server for any of this?
(Note: Other Exchange server doesn't have anything in its queues)
The
img-1.jpg
The error in the queued email is:
Identity: EXCHANGE\Submission\16945
Subject: TEST2 @ 17:16
Internet Message ID: <1ee801cbefbf$15695e10$403
From Address: me@testdomain.com
Status: Retry
Size (KB): 7
Message Source Name: SMTP:receiveconnector
Source IP: xx.xx.xx.xx1
SCL: 0
Date Received: 31/03/2011 17:47:22
Expiration Time: 02/04/2011 17:47:22
Last Error: A local loop was detected.
Queue ID: EXCHANGE\Submission
Recipients: test.user@newdomain.com
Subject: TEST2 @ 17:16
Internet Message ID: <1ee801cbefbf$15695e10$403
From Address: me@testdomain.com
Status: Retry
Size (KB): 7
Message Source Name: SMTP:receiveconnector
Source IP: xx.xx.xx.xx1
SCL: 0
Date Received: 31/03/2011 17:47:22
Expiration Time: 02/04/2011 17:47:22
Last Error: A local loop was detected.
Queue ID: EXCHANGE\Submission
Recipients: test.user@newdomain.com
So it appears it is receiving it from the Receive Connector correctly? Looking at the receive connector on the main Exchange server, it has its own IP in the "use these local IP addresses to receive email". You can see from the screenie:
The IP's 192.168.60.0 is our dev network.
Ignorance is playing a big part here, I'm not sure how to tell it not to use the other DR Exchange server for any of this?
(Note: Other Exchange server doesn't have anything in its queues)
The
img-1.jpg
ASKER
So in short. Email comes in to our External SMTP server (a Unix box), this forwards it on to Exchange, where it is received by the Receive Connector. The receive connector "should" just dump email into the recipient mailbox? is that correct?
But for some reason it might be trying to deliver it to the DR Exchange server and that is why we are getting the error in the mail that is queues? (Last Error: A local loop was detected.)
Question is, how do I sort out where email is delivered to in the Receive Connector? Because from what I can tell there is no reference to the DR Exchange Server?
(apologies for the text spam - but I’m not so good at explaining myself!!)
But for some reason it might be trying to deliver it to the DR Exchange server and that is why we are getting the error in the mail that is queues? (Last Error: A local loop was detected.)
Question is, how do I sort out where email is delivered to in the Receive Connector? Because from what I can tell there is no reference to the DR Exchange Server?
(apologies for the text spam - but I’m not so good at explaining myself!!)
Here's a guide
http://technet.microsoft.com/en-us/library/aa996314(v=exchg.80).aspx
Here's a video :)
http://technet.microsoft.com/en-us/exchange/cc950455.aspx
http://technet.microsoft.com/en-us/library/aa996314(v=exchg.80).aspx
Here's a video :)
http://technet.microsoft.com/en-us/exchange/cc950455.aspx
ASKER
THansk Sunny, done that as it suggests - think this issue lies outside that with where email is attempted to be delivered. This is the bit I can't figure out. It works perfectly for our main domain, but for the new domain just added it is looping in the mail queue.
Did you restart the services after applying the EAP's ?
Another thought - do you have any antispam software on this server?
If it's only the one domain that is looping, it seems odd. Even if the DR server is still in the "loop" so to speak, it should see the new domain so that shouldn't be a problem. I would try restarting all of the Exchange services on both servers and see if that helps. The thought about anti-spam software was due to the fact that 3rd party antispam software would most likely need to have that new domain added as a valid domain in order to accept the mail as well.
ASKER
Thanks for all the advice guys, I've gone back to basics and re-did the accepted domains and re-updated the email address policy. I then re-started the Transport Service.
I checked a few on the SMTP addresses for some users and noticed an anomaly where some of the users had "firstname.lastname2@domain.com" - this "2" shouldn't have been there (it was also present on the test account.
I realised that some users had "contact" accounts setup in AD, and these were obviously conflicting with the Email Address Policy. Removed contacts from AD, edited SMTP addresses - everything works.
Thanks so much for all your kind assistance.
I checked a few on the SMTP addresses for some users and noticed an anomaly where some of the users had "firstname.lastname2@domain.com" - this "2" shouldn't have been there (it was also present on the test account.
I realised that some users had "contact" accounts setup in AD, and these were obviously conflicting with the Email Address Policy. Removed contacts from AD, edited SMTP addresses - everything works.
Thanks so much for all your kind assistance.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 500 points for hypercat's comment http:/Q_26925200.html#35283560
Assisted answer: 0 points for georgefowler's comment http:/Q_26925200.html#35283803
for the following reason:
With help from Hypercat I noticed the issue on the server.
Accepted answer: 500 points for hypercat's comment http:/Q_26925200.html#35283560
Assisted answer: 0 points for georgefowler's comment http:/Q_26925200.html#35283803
for the following reason:
With help from Hypercat I noticed the issue on the server.
ASKER
Need to accept this question asap please as I need to ask a new question on another subject.