asked on

Adding a webmail link to a corporate site

using Server 2003 and Exchange. Please advise on the security issues that would arise from installing a link (however small) on a 'business' website (not heavily traveled by any means) to allow employees Outlook Web Access? Do larger business still practice this? Is their a 'better' way; maybe having http://webmail.business.com point to the Exchange Outlook Web Access page? what is safe and secure?

ASKER CERTIFIED SOLUTION

Sembee

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

72chevy4x4

ASKER

What about letting SBS2003 create its own certificate? I've tried the website in question and it automatically requires https (will not accept the http request).

Sembee

The only problem with using the built in certificate is that it isn't trusted. It will generate errors each time it is used, unless the certificate is installed. It probably isn't a good idea to install the certificates everywhere as this will leave information about your configuration everywhere. Furthermore that certificate has probably been issued in the name of server.domain.com and you might want it to be webmail.domain.com

With FreeSSL doing certificates for some ridiculous sum like US$20/year I just think it looks more professional to have a real certificate that doesn't generate errors and allows the users to verify that it is legimate.

Simon.

72chevy4x4

ASKER

regarding the certificates: that is one error I've run across, when the remote office logs on using https:server.business.com, an error stating the certificate holder's name is server.business.local pops up. guess the original cert was incorrectly named. The public has no knowledge of or use for the cert (no e-business or the likes going on), so I may not pursue the FreeSSL option, but thank you for the information.