OK, try again... Windows 2003 Enterprise SP2 Exchange 2003 SP 2 - 2 Frontend Servers, 3 Backend Clusters Roaring Penguin Gateway SPAM Filter IronPort Secure E-Mail OK, I have read all the Articles on implementing TLS and I want to make sure I'm doing this right for our needs... We have non TLS Exchange running and working fine and want to keep it that way. We are adding the IronPort Secure E-Mail system to allow users to send optional secure e-mail from Outlook to any user, both internal and external. Otherwise the default is to send non TLS e-mails. So I do not want to set TLS to send secure to any particular domain nor do I want all of our exchange e-mails set for TLS. Per instructions, on one of the Frontend Exchange servers I have added an additional IP address and added a Secure SMTP Virtual Server. Questions... First, do I need to duplicate all this with the second Frontend server using the same IP address? On the routing groups,after I set'Forward all E-Mail through this Connector to the following Smart Hosts' to the primary Frontend Secure SMTP Virtual server I now have listed, does this allow all mail from the other Backend server to route through this or do I need to do more? As stated, I am not trying to send TLS to any one particular domain, we are using the IronPort option that will notify the user he has a secure e-mail and to log into the IronPort website and register, then they will receive the secure e-mail from us. Otherwise all other e-mail traffic is unsecured. Any help on this would be appreciated Don R Hunsinger Systems/Exchange Admin