This element controls how x-headers will be provided.

<output mode='inject'/>

The inject mode is probably used most frequently. This mode causes SNFServer to inject the X-headers into the message file it has scanned. This way any processes that handle the file subsequently will be able to evaluate the X-headers provided by SNF. This option only works when messages are scanned by file.

<output mode='file'/>

The file mode is used in situations where the X-headers will be added to the message later or otherwise evaluated by other software after SNF has finished its scan.

The message file itself is not modified by SNFServer. Instead, a new file is created containing the X-headers for the message. The file will be placed in the same directory as the message file with the name: message.file.name.xhdr

It is assumed that the X-headers will be added to the message later along with headers from other sub-systems. This mode is most frequently used in environments where a number of message processing steps will be scripted together. This option only works when messages are scanned by file.

<output mode='api'/>

The api mode causes SNF to make the X-headers available via the API - that is either through function calls or via XCI responses. No files are created or manipulated. This mode is most frequently used when a message processing application will call SNF directly via XCI or function calls.

It is worth noting that the X-header data is available via SNF's api whenever X-headers are enabled.

<output mode='none'/>

The default X-header output mode if none is provided is 'none'. This turns off X-header generation.

Please email support@armresearch.com with any questions.