1

I have just added MX record for mail.example.com. Previously there was MX record for example.com. we have default email address-domain @example.com - and it is working fine for send and receive. we need to get some admin-level email addresses working that ends with @mail.example.com, for example:

so we added the MX record and pointing to same server. I tested sending email to [email protected] and [email protected] from inside domain and I am able to receive emails to them. but from outside, I am not able to send email to those address. it says

Message not delivered
Your message couldn't be delivered to [email protected] because the remote server is misconfigured. See technical details below for more information.

The response from the remote server was:

550 5.7.1 Unable to relay

now, i see there are some suggestion to create new receive connector in Exchange. we have Exchange server 2013. what parameters I need to use to create the new receive connector? we already have default receive connector in both exchange servers for example.com and both inbound and outbound emails are working fine.

we have two exchange servers 2013, the servers are on cluster. each server has its own receive connectors as below.

Client Frontend <server-name> - FrontendTransport
Client Proxy <server-name> - HubTransport
Default Frontend <server-name> - FrontendTransport
Default <server-name> - HubTransport
Internal-Relay <server-name> - FrontendTransport
Outbound Proxy Frontend <server-name> - FrontendTransport

any suggestion will be greatly appreciated. thanks.

1 Answer 1

2

You don't need a new Receive Connector at all. Receive Connectors have nothing to do with the domains that the server can receive.

The only thing that you need to do is add the domain to the list of Accepted Domains. mail.example.com and example.com are different domains as far as Exchange is concerned.

Once you have added the domain to the list of Accepted Domains, add the email addresses to the various accounts as required. For a small number of addresses I don't bother with email address policies.

2
  • thanks for your reply. do I also need to create a new DNS zone for mail.example.com in our public DNS server and add the MX record inside it? at present, mail.example.com MX record is present inside example.com DNS zone. will it work after doing what you said and as per current DNS settings?
    – arifr
    Jul 28, 2017 at 4:38
  • A new zone in the public DNS will be required for the same reason - as far as the internet is concerned mail.example.com is a different domain to example.com, requiring its own set of DNS records.
    – Sembee
    Jul 28, 2017 at 8:55

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .