Why couldn't you use Outlook web access instead of IMAP. The design can be much more secure with mail access from the internet than would be IMAP. More functionality also. -----Original Message----- From: Jason Davis [mailto:JDavis@xxxxxxxxxx] Sent: Tuesday, March 01, 2005 11:08 AM To: [ExchangeList] Subject: [exchangelist] Exchange 5.5 and remote access using IMAP4 http://www.MSExchange.org/ Hello all, Recently, I setup remote access to our Exchange Server for IMAP4 by opening port 143 on our Cisco box. Although this is tremendously convenient for our users to access their office email from home, I'm concerned about the security risks. Most of our users are using Outlook Express from home to access their mail from the Exchange Server. I noticed that there is an option for "My Server Requires Authentication" for Outgoing Mail. Is there anything I need to setup on Exchange Server 5.5 to increase the security and require that the users authenticate for Outgoing Mail? Any other words of wisdom, in terms of securing Exchange Server 5.5 for remote email access? Thanks in advance. --Jason Davis ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this MSEXchange.org Discussion List as: plapatra@xxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to listadmin@xxxxxxxxxxxxxx