Running BES 4.0 sp1 for Exchange. Majority of our devices are 7520. I am trying to find away to block certain attachments (ie .tif) either at the BES or on the actual device. Any suggestions?
This might help. Found on the RIM KB - article KB-04757
To exclude TIFF images from being processed by the Attachment Service
On the desktop, click Start > Programs > BlackBerry Enterprise Server > BlackBerry Enterprise Server Configuration.
Click the Attachment Server tab.
In the Format Extensions field, delete the .tiff, .tif extensions.
Note: Format Extensions is an editable field that lists all the extensions that the Attachment Service will open. A colon is used as a delimiter.
Click Apply, then click OK.
In Microsoft Windows® Administrative Tools, double-click Services.
Right-click BlackBerry Attachment Service, then click Stop.
Right-click BlackBerry Attachment Service, then click Start.
Close the Services window.
You may also need to stop and start the dispatcher service for changes to take effect.
Even though the .tiff and .tif extensions have been removed from the list of supported file types, the Attachment Service may automatically detect a TIFF file with a renamed extension and attempt to process the file. Administrators may need to disable the image attachment distiller.
To disable the image attachment distiller
On the desktop, click Start > Programs > BlackBerry Enterprise Server > BlackBerry Enterprise Server Configuration.
On the Attachment Server tab, select Attachment Server from the Configuration Option drop-down list.
In the Distiller Settings section of the window, clear the Enabled check box for Image Attachments.
Click Apply, then click OK.
In Administrative Tools, double-click Services.
Right-click BlackBerry Attachment Service, then click Stop.
Right-click BlackBerry Attachment Service, then click Start.
Close the Services window.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.