Third Party Encryption: smarshEncrypt

To enable your smarshEncrypt service with Redtail's hosted email services, you will want to provide Redtail Support with the Outbound Relay information provided to you by Smarsh. Once Redtail has completed the setup enabling smarshEncrypt for your domain, we will notify you and provide you with an archive address. The archive address will need to be provided to Smarsh if you wish to have responses to secure emails archived within Redtail CRM.  

When using such an encryption service, recipients of the encrypted emails that you send will receive an email stating that they have a secure email waiting for them and will usually have to register/sign onto a website (provided by the encryption service) to retrieve.

It is important to note that when sending an encrypted message, your outbound message will be archived here at Redtail, since it originates from our servers. Replies from the recipient of an encrypted message, in most cases however, cannot be archived by our servers, as the encryption services server handles their receipt. The exception to this is if a subscriber uses smarshEncrypt. There is a special setup to allow for secure emails sent via smarshEncrypt to be archived. 

If you are a pre-existing smarshEncrypt and Redtail hosted email subscriber and you wish to have your secure emails archived, please contact Redtail Support to request this be setup for you. 

We recommend that you contact Smarsh and add Redtail Email Support to your Smarsh Account as approved to report issues with the encryption service.  This allows us to contact Smarsh directly on your behalf if we notice an error or disruption in the service, as well as to provide them log information regarding the issue. If we are not listed on your account with Smarsh, in the event of this type of issue we will have to provide those details to you directly for you to provide to Smarsh in order for Smarsh to accept them as an issue to look into. In those cases where we might encounter a delay in reaching you, this could mean a delayed resolution of the error or disruption being reported.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk