locked
EOP inbound connector required forced TLS for on-premise Exchange? RRS feed

  • Question

  • We purchased EOP spam protection for an on-premise Exchange 2010 environment.  Inbound email is currently flowing through EOP to their exchange just fine, but we don't have them routing outbound email back through EOP due to the TLS certificate setting.  We would like to point their Exchange send connector smarthost to EOP for best practice.  EOP documentation states we must use Forced TLS and a certificate name for the inbound connector.  The documentation falls short here and I need some help getting TLS setup on the on premise exchange.  Is it required to use Forced TLS or can we change to opportunistic TLS like the EOP outbound connector?  We currently only have a SSL certificate for their OWA set to mail.domain.com.  Is that what I use as the TLS certificate name?  Can someone point me in the right direction here?  Thanks.

    Friday, April 4, 2014 5:19 PM

All replies

  • Hi,

    you don't need TLS to send mails over EOP if you use it as smarthost.

    Greetings

    Christian


    Christian Groebner MVP Forefront

    Sunday, April 6, 2014 6:23 PM