|
|
re:For Q2:An ob...
|
For Q2:<br>
<br>
<br>
<br>
An obvious solution would be to run store AV scanning, which would mean that anything which was submitted to the back end server (which is ultimately responsible for rendering OWA anyway) would get checked for viruses.If you don't run AV on the backend server, there may be 3rd party options that can scan the attachments during upload (IE some firewalls can do in-line attachment AV scanning etc). For more information please refer follow knowledge base article: <br>
(KB 328841)Exchange and antivirus software<br>
<a target=_blank href=http://support.microsoft.com/kb/328841/>http://support.microsoft.com/kb/328841/</a> <br>
<br>
The scenario might be that a remote user sends an email using OWA from a PC, and submits a virus-infected attachment into OWA. If the remote PC doesn't have reliable anti-virus software, there's a risk that an infected attachment could be introduced into the Exchange store.<br>
<br>
OWA 2003 gives you the option of restricting which attachment types can be viewed at the client (so that executable attachments can't be inadvertently downloaded, refer (KB555001) Outlook Web Access - Configure Attachment Blocking) and you can also restrict that external clients - ie PCs connecting from outside your network, through a front end server - can't download or upload attachments, whereas internal clients (which connect over the internal network) can continue to use attachments in OWA.<br>
|
|