I am attempting to create a partner send connector for our third party encryption. The third party uses a smart host with opportunistic tls. However, the option to choose smart host is greyed out. Microsoft was less than helpful. Any ideas?  Thank you.

Please describe the exact and complete steps you're taking.

Please describe the exact and complete steps you're taking.

Hi,

As per the information and details provided by you, please follow these steps to solve the issue: -

• The third-party host must use SMTP for transport. If it does not, you should use a Foreign connector or Delivery Agent Connector.

• Use the EAC to create a Send Connector to route outbound email through a smart host.

I hope this information will be helpful for you.

Thanks and regards

Shweta@G 

Hi,

As per the information and details provided by you, please follow these steps to solve the issue: -

• The third-party host must use SMTP for transport. If it does not, you should use a Foreign connector or Delivery Agent Connector.

• Use the EAC to create a Send Connector to route outbound email through a smart host.

I hope this information will be helpful for you.

Thanks and regards

Shweta@G 

The steps I am take are. Logging in to EAC, creating a send connector, selecting Partner. That's as far as I can get as the Smart Host option is not selectable.

That's is what I am trying to do. Put smart host is not selectable.

My system exhibits the same behavior.  I wasn't familiar with it since I always use PowerShell to create connectors.  Consider using New-SendConnector to create the connector.

Agree with Ed; my system also behaves the same (smart host) option grayed out with a new partner send connector.  I can't find any MS documentation stating you can't use a smart host when creating the send connector through shell.  As Ed said, try using the 'New-SendConnector' cmdlet and see if it works or use a "custom" connecto

I will raise the issue as best as I can.  It looks like a bug to me.

Thank you all for your help. I have tried the custom connector but to no avail. In theory that should work as opportunistic tsl is enable by default in exchange 2013. I have created a new connector from command line with the same results. Definitely seems like a bug that MS wont acknowledge to me. I am on site at the moment awaiting a call from Smarsh to see if we can create a work around. I will let you know of the progress.

Thank you all for your help. I have tried the custom connector but to no avail. In theory that should work as opportunistic tsl is enable by default in exchange 2013. I have created a new connector from command line with the same results. Definitely seems like a bug that MS wont acknowledge to me. I am on site at the moment awaiting a call from Smarsh to see if we can create a work around. I will let you know of the progress.

Thank you all for your help. I have tried the custom connector but to no avail. In theory that should work as opportunistic tsl is enable by default in exchange 2013. I have created a new connector from command line with the same results. Definitely seems like a bug that MS wont acknowledge to me. I am on site at the moment awaiting a call from Smarsh to see if we can create a work around. I will let you know of the progress.

Thank you all for your help. I have tried the custom connector but to no avail. In theory that should work as opportunistic tsl is enable by default in exchange 2013. I have created a new connector from command line with the same results. Definitely seems like a bug that MS wont acknowledge to me. I am on site at the moment awaiting a call from Smarsh to see if we can create a work around. I will let you know of the progress.