RE: Accessing Exchange 2000 Remotely

From: Boyce Ezell (boyceezell@yahoo.com)
Date: 08/17/01 

From: "Boyce Ezell" <boyceezell@yahoo.com>
To: <focus-ms@securityfocus.com>
Subject: RE: Accessing Exchange 2000 Remotely
Date: Fri, 17 Aug 2001 09:46:10 -0400
Message-ID: <000501c12722$f9b737b0$8065a8c0@porcupine>

 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have never been big on granting POP/IMAP access to remote users on
my Exchange installations. My main reason for disliking this
solution is backups: users never backup their .pst files. My other
reason is that when they leave the company, users retain the
information, some of which may be privileged. If you have to do it,
secure it with a certificate. IPSEC/PPTP VPN is an alternative, but
it is easier to add your SSL certificate to POP3 and close port 110
to force the issue. Outlook supports using SSL for POP3. Using RRAS
can be a headache, especially when you don't need it. Pay $100 and
get a certificate for a year, sleep well.

Boyce Ezell
SysAdmin-At-Large

- -----Original Message-----
From: Stephen K. Watling [mailto:steve.watling@neumark.com]
Sent: Thursday, August 16, 2001 6:47 PM
To: focus-ms@securityfocus.com
Subject: Accessing Exchange 2000 Remotely

We are running a MS Exchange 2000 server behind our firewall. We do
not
have any problems with our users accessing it from within our LAN (of
course), however, we do have a number of employees who work remotely,
at
least part of the time. In order to accommodate them, we enabled
Outlook Web Access across an SSL connection. Our remote users have
requested that we go a step further and enable POP3 access to the
system. Now, I am against doing this, because I question the
security
aspects of this. I have suggested we enable IMAP4 over SSL to allow
remote access. However, our users are sticking to their guns on POP3
access. We are working on implementing VPN access, but due to
logistical constraints, we will not be able to implement it for a few
months. We would like to find an interim solution as soon as
possible.
Question: What is the most secure/flexible method of accessing an
Exchange 2000 server from across the Internet? Is there a more
secure
option that I just don't see?

Thank you in advance for your assistance,

Steve

Systems Engineer

Systems Engineer
Neumark Technology Group, Inc.
Phone: 630-505-3721
Fax: 630-505-4999
Mobile: 847-366-9088
steve.watling@neumark.com
www.neumark.com

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBO30gIlFH1oF9Bg0QEQKUEgCgima7wT2X1IxFI4yQMu5GL5vJ9EEAoMz9
6j+X92jqw1dhNFkjIDHIz654
=O7+e
-----END PGP SIGNATURE-----


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Relevant Pages

  • SBS w/exchange SP2 Set up Email to pop3 with same domain.
    ... We have exchange setup and everyone but 2 have outlook 2003. ... and send it to the pop3, and he then can get the mail from web based. ... the remote email from the internal company web page. ...
    (microsoft.public.windows.server.sbs)
  • RE: Accessing Exchange 2000 Remotely
    ... Subject: Accessing Exchange 2000 Remotely ... What about secure-pop (over ssl) until you get the VPN up? ... Our remote users have ...
    (Focus-Microsoft)
  • Re: Diagnosing client connection problems
    ... And, I see that the remote routers were set to 1500, which should ... and was able to get onto Exchange remotely on the first try (first ... Remote offices ...
    (microsoft.public.exchange.connectivity)
  • RE: Accessing Exchange 2000 Remotely
    ... Subject: Accessing Exchange 2000 Remotely ... web servers in the same DMZ with it. ... perhaps a better alternative would be to put your exchange server ... Our remote users have ...
    (Focus-Microsoft)
  • Re: Errors after a clean install of SBS2K3
    ... I meant Exchange 2K3 SP1. ... > I had to reinstall SBS 2K3 because of a faulty motherboard. ... > The following settings were successfully configured by the Remote Access ... > server provided with Windows Small Business Server 2003. ...
    (microsoft.public.windows.server.sbs)