Disable Indexing for Specific File Types: Difference between revisions
m (* Command Line */ - spell it out :]) |
m (→Create LDIF: - remove EOL spaces in case people copy and paste) |
||
Line 63: | Line 63: | ||
# some clients will send binaries as application/octet-stream type | # some clients will send binaries as application/octet-stream type | ||
dn: cn=application/octet-stream,cn=mime,cn=config,cn=zimbra | dn: cn=application/octet-stream,cn=mime,cn=config,cn=zimbra | ||
cn: application/octet-stream | cn: application/octet-stream | ||
objectclass: zimbraMimeEntry | objectclass: zimbraMimeEntry | ||
zimbraMimeIndexingEnabled: TRUE | zimbraMimeIndexingEnabled: TRUE | ||
zimbraMimeType: application/octet-stream | zimbraMimeType: application/octet-stream | ||
zimbraMimeFileExtension: vsd | zimbraMimeFileExtension: vsd | ||
zimbraMimeFileExtension: dwg | zimbraMimeFileExtension: dwg | ||
zimbraMimeHandlerClass: UnknownTypeHandler | zimbraMimeHandlerClass: UnknownTypeHandler | ||
description: Disabled application/octet-stream extensions | description: Disabled application/octet-stream extensions | ||
Revision as of 18:28, 3 December 2007
Introduction
It may be necessary to disable attachment indexing for specific mimetypes if conversion is unable to process the attachments due to size or other error. When disabled, conversion will be bypassed for only specified mimetypes. Attachment indexing can be disabled for all types if desired. Zimbra Collaboration Suite for Mac OS X currently does not support attachment indexing. Attachment indexing is only supported on ZCS Network Edition.
Errors
If conversion (convertd) is unable to process certain attachments, messages containing those attachments will queue in the MTA deferred queue. Here are some relevant errors.
MTA
/var/log/zimbra.log
Nov 27 01:26:12 ubu03 postfix/lmtp[32013]: D3058C9F40: to=<admin@zmb.moc>, relay=ubu03.zmb.moc[192.168.5.63], delay=34, status=deferred (host ubu03.zmb.moc[192.168.5.63] said: 451 4.0.0 Temporary message delivery failure try again (in reply to end of DATA command))
Mailbox
/opt/zimbra/log/mailbox.log
2007-11-27 01:26:12,533 WARN [LmtpServer-1] [] ParsedMessage - Message had parse errors in 1 parts (Message-Id: <44BB8AB2-8BDE-4AE1-96DC-6A7A2C029924@zmb.moc>, Subject: attachment) 2007-11-27 01:26:12,586 WARN [LmtpServer-1] [] ZimbraLmtpBackend - Exception delivering mail (temporary failure) com.zimbra.common.service.ServiceException: system failure: failed to analyze part ... Caused by: com.zimbra.cs.convert.ConversionException: Communication with convertd timed out ... Caused by: java.net.SocketTimeoutException: Read timed out
Bugs
- 15990 attachment crashes convertd
- 16454 Convertd failing on attachments - messages sent to deferred queue
- 17611 refine attachment handing for non-document types and large file sizes
Disabling Attachment Indexing
All Attachments
All attachment indexing can be disabled at the class of service (COS) or account level. Check "Disable attachment viewing from web mail UI" on the advanced tab of the COS or account you wish to disable indexing.
Command Line
COS
$ zmprov modifyCOS default zimbraAttachmentsIndexingEnabled FALSE
Account
$ zmprov modifyAccount user@zmb.moc zimbraAttachmentsIndexingEnabled FALSE
Specific Mimetypes
Disabling indexing for certain mimetypes requires direct modification to the Zimbra directory. The goal is to map the desired file extension and mimetype to UnknownTypeHandler as opposed to DefaultHandler. To configure, create an LDIF file, then use ldapadd to apply the changes to LDAP. The following example disables indexing on Visio and AutoCad attachments.
Create LDIF
/tmp/mimedisable.ldif
# application/acad, mime, config, zimbra dn: cn=application/acad,cn=mime,cn=config,cn=zimbra zimbraMimeType: application/acad cn: application/acad objectClass: zimbraMimeEntry zimbraMimeIndexingEnabled: TRUE zimbraMimeHandlerClass: UnknownTypeHandler zimbraMimeFileExtension: dwg # application/vnd.visio, mime, config, zimbra dn: cn=application/vnd.visio,cn=mime,cn=config,cn=zimbra zimbraMimeType: application/vnd.visio cn: application/vnd.visio objectClass: zimbraMimeEntry zimbraMimeIndexingEnabled: TRUE zimbraMimeHandlerClass: UnknownTypeHandler zimbraMimeFileExtension: vsd # some clients will send binaries as application/octet-stream type dn: cn=application/octet-stream,cn=mime,cn=config,cn=zimbra cn: application/octet-stream objectclass: zimbraMimeEntry zimbraMimeIndexingEnabled: TRUE zimbraMimeType: application/octet-stream zimbraMimeFileExtension: vsd zimbraMimeFileExtension: dwg zimbraMimeHandlerClass: UnknownTypeHandler description: Disabled application/octet-stream extensions
Apply LDIF
$ ldapadd -x -h `zmhostname` -D uid=zimbra,cn=admins,cn=zimbra -W -f /tmp/mimedisable.ldif
A service restart is not required after applying the changes.
Verify
Verify bypassed attachment types are deliverable.
Revert Attachment Indexing
To remove custom handling of a specified mimetype, use the ldapdelete command with an LDIF file.
Create LDIF
This file contains one DN entry per line
/tmp/mimeremove.ldif
cn=application/acad,cn=mime,cn=config,cn=zimbra
Delete Entry
$ ldapdelete -x -h `zmhostname` -D uid=zimbra,cn=admins,cn=zimbra -W -f /tmp/mimeremove.ldif
Keywords: conversion, attachment, indexing, kvoop, verity, mime