Blob Export Configuration

Blob Exporting is the mechanism to help James to export a blob from an user to another user. It is commonly used to export deleted messages (consult configuring deleted messages vault). The deleted messages are transformed into a blob and James will export that blob to the target user. This configuration helps you choose the blob exporting mechanism fit with your James setup and it is only applicable with Guice products.

Consult in GIT to get some examples and hints.

Configuration for exporting blob content

localFile: Local File Exporting Mechanism (explained below). Default: localFile
linshare: LinShare Exporting Mechanism (explained below)

Local File Blob Export Configuration

For each request, this mechanism retrieves the content of a blob and save it to a distinct local file, then send an email containing the absolute path of that file to the target mail address. Note: that absolute file path is the file location on James server. Therefore, if there are two or more James servers connected, it should not be considered an option.
The directory URL to store exported blob data in files, and the URL following James File System scheme. Default: file://var/blobExporting

LinShare Blob Export Configuration

Instead of exporting blobs in local file system, using LinShare helps you upload your blobs and people you have been shared to can access those blobs by accessing to LinShare server and download them. This way helps you to share via whole network as long as they can access to LinShare server.

To get an example or details explained, visit

the URL to connect to LinShare
the authentication token to connect to LinShare