<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Verify Microsoft Online Services Transport Layer Security (TLS) E-mail Delivery</title><link>http://blogs.technet.com/msonline/archive/2008/10/23/how-to-verify-ms-online-tls-message-delivery.aspx</link><description>To secure e-mail message delivery between your on-premise and Online environments first, follow the steps on how to configure your on-premise messaging environment . Next, determine whether Transport Layer Security (TLS) was used during Message Delivery.</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: How to Verify MS Online TLS Message Delivery</title><link>http://blogs.technet.com/msonline/archive/2008/10/23/how-to-verify-ms-online-tls-message-delivery.aspx#3147695</link><pubDate>Wed, 05 Nov 2008 08:19:45 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3147695</guid><dc:creator>joshmaher</dc:creator><description>&lt;p&gt;This is great that TLS will be supported.&lt;/p&gt;
&lt;p&gt;I am curious though, why won't the MTLS features take effect if a customer has Exchange 2007 on-site? &lt;/p&gt;
&lt;p&gt;Also for those customer's who want to have private certificates, is there anything on the roadmap to allow private certs between the on-site email system and Exchange Online?&lt;/p&gt;
</description></item><item><title>re: How To Verify Microsoft Online Services Transport Layer Security (TLS) E-mail Delivery</title><link>http://blogs.technet.com/msonline/archive/2008/10/23/how-to-verify-ms-online-tls-message-delivery.aspx#3158887</link><pubDate>Mon, 24 Nov 2008 23:50:27 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3158887</guid><dc:creator>Ryan J. Phillips</dc:creator><description>&lt;p&gt;Hi Josh, EHS does not require a client (sending server) certificate, so we wouldn't do MTLS. &amp;nbsp;EHS provides it's certificate, which is a commonly used certificate, which is trusted by ALL Windows machines. &amp;nbsp;As a result, the sending server is able to successfully able to establish a TLS connection and deliver the message.&lt;/p&gt;
&lt;p&gt;When EHS attempts to deliver a message to an On-Premise Messaging server (Coexistence), it will attempt a TLS connection and if enabled on the receiving server AND is using a certificate that can be validated (Not expired, on a CRL and the Common Name matches), then EHS will deliver using TLS.&lt;/p&gt;
&lt;p&gt;So that end, private certificates cannot be used when receiving mail from an EHS endpoint over TLS.&lt;/p&gt;
&lt;p&gt;I hope this helps&lt;/p&gt;
&lt;p&gt;....Ryan&lt;/p&gt;
</description></item></channel></rss>