Datasinks can be enabled/disabled in the /fileserver/etc/datasinks/datasinks.cf file. Here you have an entry similar as the following for each supported datasink type:

<configuration>
   <sftp disabled="false" supportsScheduling="true" />
   <ftp disabled="false" supportsScheduling="true" />
</configuration>

The disabled option controls if the datasink is overall enabled or disabled. Further, scheduling via datasinks can be enabled or disabled via the supportsScheduling setting. Note that you can not enable scheduling if the datasink is overall disabled.

Further, you can select a default datasink per type as shown below for email / SMTP datasinks:

<email disabled="false" supportsScheduling="true">
    <defaultDatasinkKey>DEFAULT_EMAIL_DATASINK</defaultDatasinkKey>
</email>

Here, your default datasink is the datasink with the key DEFAULT_EMAIL_DATASINK. You can select the default datasink by key:

<email disabled="false" supportsScheduling="true">
    <defaultDatasinkKey>DEFAULT_EMAIL_DATASINK</defaultDatasinkKey>
</email>

or by id:

<email disabled="false" supportsScheduling="true">
    <defaultDatasinkId>14</defaultDatasinkId>
</email>

For the SFTP/FTPS/SCP datasinks to work, you have to add your SFTP/FTPS/SCP host to your .ssh/known_hosts file (https://en.wikibooks.org/wiki/OpenSSH/Client_Configuration_Files#~/.ssh/known_hosts) in order to verify the identity of the remote host, thus protecting against impersonation or man-in-the-middle attacks. Its location be configured in the /fileserver/etc/security/misc.cf file as follows.

E.g.: Use ssh-keyscan IP >> known_hosts in order to add the given IP to your known_hosts file.

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
   <knownHosts>/path/to/your/machine/.ssh/known_hosts</knownHosts>
</configuration>

For manually adding a public key to the .ssh/known_hosts file, check here: https://en.wikibooks.org/wiki/OpenSSH/Client_Configuration_Files#Manually_Adding_Public_Keys_to_~/.ssh/known_hosts.

E.g.: Use ssh-keyscan IP >> known_hosts in order to add the given IP to your known_hosts file.

The StrictHostKeyChecking setting allows you to enable or disable the host key verification process. This configuration can be applied either globally for all datasinks (default) or individually for specific datasinks (enforced). When enforced for a specific datasink, it overrides the global default for that datasink.

You can configure this setting in the file: /fileserver/etc/security/misc.cf. Below is an example configuration:

<strictHostKeyChecking>
   <default>true</default>
   <enforce>
      <datasinks>
         <datasink>
            <datasinkKey>DEMO_SFTP_DATASINK</datasinkKey>
            <strictHostKeyChecking>false</strictHostKeyChecking>
         </datasink>
      </datasinks>
   </enforce>      
</strictHostKeyChecking>

In this example:

The global default is set to true, meaning host key verification is enabled for all datasinks unless overridden. The DEMO_SFTP_DATASINK is explicitly configured with StrictHostKeyChecking set to false, disabling host key verification for this specific datasink.

Note: It is highly recommended to set StrictHostKeyChecking to true for security reasons. This ensures that the server's host key is verified before establishing a connection, protecting against man-in-the-middle (MITM) attacks. Without verification, a malicious actor could intercept the connection and impersonate the remote server, potentially compromising sensitive data being transferred. Disabling this setting (false) should only be done for specific cases where security risks are fully understood and mitigated.

As of ReportServer 4.7.0, the old, deprecated and insecure mail/mail.cf configuration file is deleted. Please delete it from your system. Instead, Email SMTP datasinks should be used together with a default email datasink, which can be defined in the /etc/datasinks/datasinks.cf configuration file as follows.

<email disabled="false" supportsScheduling="true">
    <defaultDatasinkName>Default Email Datasink</defaultDatasinkName>
    <!-- or access via ID -->
    <!-- <defaultDatasinkId>14</defaultDatasinkId> -->
</email>

You can use the name of the datasink, or use the ID of the datasink, for the assignment. Use one of the two variants above for the configuration.

Note that you can configure a default datasink per datasink type, so this is not limited to email SMTP datasinks.