Dear Customer,

We are happy to report that the SpamTitan Backup functionality has been restored. 

We have made some changes to the back up to enhance it’s security so please find all new changes detailed below:

LDAP Recipient Verification:

If you are using LDAP recipient verification then you will need to re-enable this once the back up is imported as this is no longer contained in the back up. Recipient Verification will be set to None when the back up is imported.

SASL Authentication:
If you are using SASL authentication this will be disabled when exporting and importing the back up, you will need to re-enable this. 

Smarthosts:
If you are using a smarthost for outbound mail this will also need to be re-enabled when you have imported the back up.

Outbound TLS Encryption:
If you are using outbound TLS encryption this will be disabled and need to be re-enabled once the back up has been imported

Web Authentication:
If you are using LDAP or SQL Authentication please note this will be changed to Internal authentication when you import the back up and you will need to re-enable your chosen method of Authentication.

SSL Certs and TLS:
SSL certs are not contained in the back up and as such will need to be re-installed or new certs will need to be generated.
TLS encryption will also be disabled and need to be re-enabled.

Active Directory Aliases:
If using AD Aliases you will need to re-insert the password post back up

Rest API and 2FA:
You will need to generate new Rest API Oauth access tokens as these will not be copied over.
2FA will also be disabled and need to be re-enabled.

Schedule Back Up Settings:
This will also need to be re-enabled once the back up has been imported.


Thank you for your patience while we redesigned this feature to enhance it’s security. If you have any questions please feel free to open a support ticket and we will be happy to assist.