none
on-premises mailboxes cannot receive emails from 365 Hybrid deployment RRS feed

  • Question

  • Hi

    I have an exchange 2013 and I tried to set up a hybrid environment with Exchange 2013 for Office 365. After the hybrid wizard, on-premise mailboxes cannot receive emails from users Office365.

    this is the error

    the message keep in pending

    Motivo: [{LED=450 4.7.320 Certificate validation failed};{MSG=UntrustedRoot};{FQDN=owa.mydominio.com};{IP=77.240.116.238};{LRT=5/9/2016 9:09:56 PM}]. OutboundProxyTargetIP: 77.240.116.238. OutboundProxyTargetHostName: owa.mydominio.com

    regards

    Monday, May 9, 2016 10:52 PM

All replies

  • Thank you !!!the connector was wrong, after i  reconfigured and fixed it!!!

    Friday, May 20, 2016 5:26 PM
  • Thank you !!!the connector was wrong, after i  reconfigured and fixed it!!!

    What did you change the connector to? we used the HCW on Exchange 2013 and created both connectors for us, we have same issue.
    Thursday, May 11, 2017 6:09 PM
  • Relevant: https://xkcd.com/979/

    Seriously... what was wrong with the connector?  :-(


    Brian Dagan brian@briandagan.com

    Sunday, June 4, 2017 7:44 PM
  • Yeah, seriously, ZERO POINTS FOR Sidartha_007!!!!!
    Wednesday, September 13, 2017 3:51 PM
  • as a workaround you can change on connector settings to use any digital certificate instead use a certificate issued by a trsuted CA.
    this can made your mailflow work again and after that you can investigate if the CRLs inside your network are being consultedf with success because it seems it cannot find all the certificate chain about this error, so i will try to browse the CRLs in internal network to see.
    Friday, November 24, 2017 7:31 PM
  • Hi. Not to dig up an old thread but I thought it worth mentioning that we discovered that because we had other custom connectors, one of them had the subnet IP address of our load balancer in it so it was using that one rather than the default. The custom connector was using the Exchange self signed cert. This was discovered using checkTLS.com.
    Thursday, October 31, 2019 9:57 PM