#EXCHANGE 2010 SMTP RELAY HOW TO#

Here are the steps to create an authoritative domain. Following are the steps to create a primary domain using Exchange Administration Center.Р”В«efore allowing multiple authoritative domains to receive emails through Exchange server, users need to create a primary domain first.

#EXCHANGE 2010 SMTP RELAY HOW TO#

How to Configure Exchange Server for Multiple Authoritative DomainsР”Р„n authoritative domain can be set using either Exchange Management Console or Exchange Management steps. Again, the send connector is setup Exchange to relay emails. All the incoming emails need to be routed to some other server.

External Relay: This implies that all the mailboxes under a particular domain are saved on an external server.

A Send Connector is used to relay messages of those email ids that are not found on the domain. The internal relay is used to route emails to appropriate receiver. Or there is more than one email id under same domain that needs to be properly addressed. Some mailboxes are saved on an external server like Google mail server.

Internal Relay: This kind of domain is used when some of the email addresses of an organization are not on Exchange.

Additional settings are required to configure Exchange 2010 to relay email for an additional domain. It is the only server responsible for sending or receiving emails. Then only one domain can be entered, which becomes the default address to relay emails. This is the domain configured in the Setup Internet Address wizard asks for an email address.

Authoritative Domain: This is the primary domain which is set up during the time the organization Exchange server is configured.

There are mainly three types of Domain that can be accepted by Exchange to relay messages. In this post, these steps have been described in detail to perform the configuration process. To configure Exchange 2010 To relay email for an additional domain additional steps needs to be performed. If it is not able to find the username, a non-delivery report is sent to the sender. Since Exchange Server treats each organization server as a single SMTP account and relays emails according. This creates an issue is receiving emails as the Exchange Server can not differentiate between different subdomains. Employees may need to configure more than one subdomain on the same email client. Often companies have different internet domains or different subdomains.

When looking at the certificates itРІР‚в„ўs easier to maintain only one SSL certificate with an additional SAN entry then an additional SSL certificate with just one domain name.Ashwani Tiwari ~ Published: T10:31:48+00:00 ~ Tips When using one or two Exchange 2010 servers it doesnРІР‚в„ўt make sense, but I also have a customer that has 28 Exchange 2010 servers running with 40,000 mailboxes, and here we want to separate Office 365 SMTP traffic from regular SMTP traffic. Why do you want to use this in the first place? More information regarding certificate requirements for hybrid deployments can be found here: (v=exchg.141) So, in contrast to my previous belief you donРІР‚в„ўt need a separate SSL certificate for an additional FQDN but you can also use an additional SAN entry on your existing SSL certificate. The validation process again succeeds successfully, but now uses the FQDN (and SAN entry on the SSL certificate) for mail flow from Office 365 to Exchange 2010:

I would expect the new FQDN here, but apparently the HCW does not reconfigure the Office 365 Receive Connector on my Exchange 2010. When validating the connector it succeeds successfully, but when you look closely it still uses the old FQDN. When running the Hybrid Configuration Wizard again on my Exchange 2010 server I select the proper SSL Certificate:Р”Р„nd entered the additional FQDN : It was time to renew my SSL certificate, so I added an additional SAN entry. During the HCW I entered and selected the proper certificate. Originally I had a Digicert SSL certificate with Common Name CN=, and a Subject Alternative Name entry. After a previous blogpost there was an interesting discussion (see the comments of this particular blogpost) about this, so now itРІР‚в„ўs time to do some testing. I was always under the impression that mutual TLS can only use the Common Name of the certificate, which in my scenario is CN=. A proper 3 rd party SSL certificate is needed on your Exchange server. SMTP communication between Office 365 and Exchange in a hybrid scenario is an example of mutual TLS or domain security. If you need to configure domain security (mutual TLS) on Exchange, you need a proper 3 rd party SSL certificate for this. Exchange 2010 uses opportunistic TLS, so the self-signed certificate will do in this scenario. For SMTP you can use the self-signed certificate. On every Exchange server you need SSL certificates for authentication, validation and encryption purposes.

Exchange 2010 smtp relay