[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

554 5.4.4 SMTPSEND.DNS.MxLoopback Error for multiple email domained site.

Posted on 2013-11-24
2
Medium Priority
?
1,687 Views
Last Modified: 2013-12-18
I'm in the process of merging an office with SBS2003 with one with SBS2008. The SBS2003 device has been decomissioned and the data and users have been sucessfully moved to the SBS2008 machine.

The old SBS2003 users still wish to use their old email addresses so I've set up Exchange 2007 on the SBS 2008 box with multiple email domains and this is working fine for sending emails to or from external email addresses.

However they get

#554 5.4.4 SMTPSEND.DNS.MxLoopback; DNS records for this domain are configured in a loop ##

when attempting to send an email from the new email address to the existing one.

Unfortunatley to complicate things further, the sbs2008 companies MX record points to a third party email provider and the existing users are using POP3 to collect the emails from there (I know, I know).

The obvious fix is to dump the third party email provider and move everything onsite but the users are particualarly computer phobic and some of them including the director are extremly resistant to changing the setup they have and wants me to 'leave things as they are' for the original SBS2008 users.




So the details...
Company 1: Office closing down and users being moved to Company 2's offices.
Lets call them  users@company1.com
Used Outlook 2007 and Exchange 2003 for emails

Company 2:
Lets call them  users@company2.com
Uses Incredimail with POP3 for their emails. Uses Incredimal Email app.
SBS 2008 setup with POP3 connectors to collect the mail
Sending currently using DNS and not a smarthost for sending.

I've added the users of Company1 to the SBS2008 box and configured the users to send and receive via DNS using user@Company1.com email address.

People from Company2 can still send and receive from their accounts, including to company1.com
People from Company1 can now send/receive emails using their user@company1.com email address on Company2's server but cannot send to Company2.com due to MxLoopback Error.

Are there any additional setting I need to do to make this work?

On company2's SBS2008 server I've...

Gone into EMC >> Org Conf >> Hub Transport >> Accepted Domain and added the Company1.com Email domain as an 'authoritive'. Company2.com is currently set to 'External Relay' due to POP 3 connectors maybe???
The default authoritive setting is company2.local

In EMC >> Org Conf >> Hub Transport >> Email Address Policies, the 'SBS Email Address Policy'has Priotiy 1, the Company1.com entry is at Priority 2
They're both current using default settings for the policies themselves.

In EMC >> Recipient Configuration, the new users with Company1.com email addresses have had their user@company1.com entry 'Set as Reply'
In EMc >> Recipeint Configuration, the exisiting users with Company2.com emails addresses have had their user@company2.com entry 'Set as Reply'

Is there anything else I need to do?
0
Comment
Question by:Dale303
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 6

Accepted Solution

by:
donnk earned 2000 total points
ID: 39672632
you need to set the sbs box to be non-authoritive for company 2 as the pop host is the mail server not your sbs box

http://blogs.technet.com/b/sbs/archive/2008/09/25/how-to-configure-non-authoritative-accepted-domains-in-sbs-2008-exchange-2007.aspx
0
 

Author Comment

by:Dale303
ID: 39677475
Yeah, that's how it was set up already. I think I've cracked it though. These were/are the Accepted Domains settings..

Company1.com, Authoritive, Default:False
Company2.com, External Relay, Default:False
Company1.local, Authoritive, Default:True


E-mail Address Policies was set like this...

Company1.com, Priority:1, Applied:True
Company2.com, Priority:2, Applied:True
Default Policy, Priority:Lowest, Applied:True

Those didn't work. Changing them to this...

Company2.com, Priority:1, Applied:True
Company1.com, Priority:2, Applied:True
Default Policy, Priority:Lowest, Applied:True

didn't work either, but

Company1.com, Priority:1, Applied:True
Default Policy, Priority:Lowest, Applied:True


Seems to have fixed things.

I'm still wondering why swapping the priority order didn't work but hey.

Thanks for your help.
0

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The core idea of this article is to make you acquainted with the best way in which you can export Exchange mailbox to PST format.
With so many activities to perform, Exchange administrators are always busy in organizations. If everything, including Exchange Servers, Outlook clients, and Office 365 accounts work without any issues, they can sit and relax. But unfortunately, it…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
Suggested Courses

649 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question