Core → CommunicationChannel → MIMEBase
Prev Appendix B. Configuration Options Reference Next

Core → CommunicationChannel → MIMEBase

Ticket::Article::Backend::MIMEBase::ArticleDataDir

Specifies the directory to store the data in, if "FS" was selected for ArticleStorage.

This setting can not be deactivated.

Default value: 

--- <OTRS_CONFIG_Home>/var/article

Ticket::Article::Backend::MIMEBase::ArticleStorage

Saves the attachments of articles. "DB" stores all data in the database (not recommended for storing big attachments). "FS" stores the data on the filesystem; this is faster but the webserver should run under the OTRS user. You can switch between the modules even on a system that is already in production without any loss of data. Note: Searching for attachment names is not supported when "FS" is used.

This setting can not be deactivated.

Default value: 

--- Kernel::System::Ticket::Article::Backend::MIMEBase::ArticleStorageDB

Ticket::Article::Backend::MIMEBase::CheckAllStorageBackends

Specifies whether all storage backends should be checked when looking for attachments. This is only required for installations where some attachments are in the file system, and others in the database.

This setting can not be deactivated.

Default value: 

--- 0

Ticket::Article::Backend::MIMEBase::IndexAttachmentNames

Specifies whether the (MIMEBase) article attachments will be indexed and searchable.

This setting can not be deactivated.

Default value: 

--- '1'

Prev Up Next
Core → CommunicationChannel Home Core → CommunicationLog