Hi,

 This is my situation, i've an Exchange 2013 Server On-Premises, and i'd like to create a Send Connector that would use Office 365's EOC as SmartHost.
I've read about how to do this, but i keep getting an error from the EMC that says:

error

No se puede hacer coincidir el nombre de identificador rblSmartHostAuthMechanismNone con un nombre de enumerador vlido. Especifique uno de los siguientes nombres de enumerador e intntelo de nuevo: None, Verbose 
 
 
Which roughly translated would be something like...

 The identifier's name "rblSmartHostAuthMechanismNone" won't match any valid enumerator's name. Specify any of the following enumerator names and try again: None, Verbose.

(I've posted this message on the Office 365 forum and they told me to try here...)  -i tried to add a link, but the site wouldn't let me-

Just in case it is not clear, i did all the necessary steps on the Office 365 EAC, and it went smoothly. That error message occurs when i try to create (or modify) a Send Connector in my on-premises server.

Can you think of any suggestions for me?

Thanks!

Hi Diego,

Thank you for your question.

Messages sent from on-premises recipients are always sent to directly to Internet recipients using DNS regardless of which of the above choices you select in the Hybrid Configuration wizard.

We could refer to the following link:

https://technet.microsoft.com/en-us/library/jj659050(v=exchg.150).aspx 

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Ok... i've read the info on that link, but i'm still not sure if i'm getting this right...

You're telling me that i can't use a smart host? There is no way for me to deliver a mail except through my own smtp server? If this is the case, then why is there an option for the smart host?

Thanks!

Diego.

Hi Diego,

If we want to send email from on-premise to office 365, we could refer to the Part 2 in the following link:

https://technet.microsoft.com/en-us/library/dn751020(v=exchg.150).aspx 

Please post the command which you create smart host to us for troubleshooting, we could also check if there is a confilect send connector.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Hi!

Nevermind... It fixed itself... At some point my on-premises server let me create the connector... I can't edit it now, since the error came back... But the connector is up and running...