Become a Columnist Microsoft Exchange Site Microsoft Support SiteMSDN Exchange Site

   

Subscribe to OutlookExchange
Anderson Patricio
Ann Mc Donough
Bob Spurzem
Brian Veal
Catherine Creary
Cherry Beado
Colin Janssen
Collins Timothy Mutesaria
Drew Nicholson
Fred Volking
Glen Scales
Goran Husman
Guy Thomas
Henrik Walther
Jason Sherry
Jayme Bowers
John Young
Joyce Tang
Justin Braun
Konstantin Zheludev
Kristina Waters
Kuang Zhang
Mahmoud Magdy
Martin Tuip
Michael Dong
Michele Deo
Mitch Tulloch
Nicolas Blank
Pavel Nagaev
Ragnar Harper
Ricardo Silva
Richard Wakeman
Russ Iuliano
Santhosh Hanumanthappa
Steve Bryant
Steve Craig
Todd Walker
Tracey J. Rosenblath
 
   

Blocking Attachments with Outlook Web Access

Page 1 | Page 2 | Page 3 | Page 4

To control whether or not attachments are used at all, create a new DWORD entry named DisableAttachments on each of the backend servers. Depending on how you want attachments to be handled, use:

0          To permit all attachments

1          To permit no attachments

2          To permit attachments from back-end servers (and accepted Front-end servers.)

This last option is important to the rest of this article as it provides the tools we need to provide different attachment handling for different scenarios. This value works hand-in-hand with the “AcceptedAttachmentFrontEnds” string value you can add to identify which Front-end servers should allow attachments (based on the file type rules). Front end servers or namespaces that are not on the list will not allow attachments. Let me explain:

If you don’t want to purchase a new Front-End server (who would) then just add an IP, a new Web Site and certificate.

 

 

Blocking Attachments with Outlook Web Access

Columnist's Index
Page 1 | Page 2 | Page 3 | Page 4

Disclaimer: Your use of the information contained in these pages is at your sole risk. All information on these pages is provided "as is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by Stephen Bryant or Pro Exchange. OutlookExchange.Com, Stephen Bryant and Pro Exchange shall not be liable for any damages you may sustain by using this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages.

Copyright Stephen Bryant 2008