How do I configure my receive connector to work with MX Logic

Posted on 2014-12-05
Medium Priority
Last Modified: 2015-04-13
We have configure our MX Logic Console and our MX records for spam filtering through MX Logic.  All emails are being rejected by the server with the message:host no unauthenticated relaying permitted.

I added a new receive connector with the above IP address in the Receive mail from box on the network tab.  The "Use Local IP address" is set to (all available).

Authentication is set to Transport Layer Security (TLS); Basic authentication; integrated windows authentication

Permission group is set to: Anonymous users

I also have the default receive connector set as follows
Local IP address:  (all available) Port 25
Receive mail from remote servers (
Authentication: TLS; Basic authentication, other basic authentication only after starting tls; integrated windows authentication.
Permission groups: anonymous users; exchange users; exchange servers; legacy exchange servers.

Any help would be most appreciated.
Question by:Nancy Villa
  • 2
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40483491
The default one will allow anyone to connect to your server. Therefore if you are following best practises then you should change that connector configuration.

HOWEVER, the true best practise is to limit the traffic to port 25 at your firewall, not on the Exchange server. I would only change the connector if the firewall isn't up to doing that.

Don't forget to restart the Transport service after making any changes.

Although looking at your message again, I am pretty sure that isn't an Exchange error. Turn on logging and see whether you are actually seeing connections from MXLOGIC.


Expert Comment

ID: 40483686

Accepted Solution

Nancy Villa earned 0 total points
ID: 40713694
It was an issue with MX Logic that they resolved.

Author Closing Comment

by:Nancy Villa
ID: 40720416
Because their answers did not correct the issue.

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

This article describes Top 9 Exchange troubleshooting utilities that every Exchange Administrator should know. Most of the utilities are available free of cost. List of tools that I am going to explain in this article are:   Microsoft Remote Con…
Exchange database can often fail to mount thereby halting the work of all users connected to it. Finding out why database isn’t mounting is crucial and getting the server back online. Stellar Phoenix Mailbox Exchange Recovery is a champion product t…
how to add IIS SMTP to handle application/Scanner relays into office 365.
Watch the video to know how one can repair corrupt Exchange OST file effortlessly and convert OST emails to MS Outlook PST file format by using Kernel for OST to PST converter tool. It can convert OST to MSG, MBOX, EML to access them. It can migrate…

627 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