Mailock Outlook Add-In: Sending a Secure Email With Recipient Validation

Recipient validation can now be switched on when sending secure emails via the Mailock web or the Outlook add-in.

 

This option is available for Pro licence users and will prompt a user when they go to send their secure email, to check each recipient, to ensure they have inputted the correct recipient email address. This feature, provides an opportunity to help reduce mis-directed emails. 

 

Mailock OAI: Recipient Validation

 

If you're a company owner and would like to switch on this feature for all of your company users, click here  for further details. 

 

Please note: You'll need to have at least version 1.27 of the add-in installed to use this feature.

 

With recipient validation switched on within Company Admin, all users will see the following screen if they open their add-in settings. The option to untick recipient validation will be disabled:

 

mailock-outlook-add-in-sending-a-secure-email-1-newux-2b

 

Alternatively, with 1.27 installed and 'Recipient Validation' not switched on within Company Admin, a user can turn this feature on manually within the add-in settings, as displayed below:

 

 

mailock-outlook-add-in-sending-a-secure-email-2-newux-2b

 

Once your secure email is composed, example as below, select 'Send' and the next screen you'll see is the recipient validation check:

 

mailock-outlook-add-in-sending-a-secure-email-3-newux-2b

 

Check the recipient address(es) listed are correct and select the tick box. If any are incorrect, click the cross at the top right of the box and amend accordingly. 

 

Once the recipient address(es) have been ticked as correct, the 'Continue' button will be highlighted:

 

Select 'Continue'

 

mailock-outlook-add-in-sending-a-secure-email-4-newux-2b

 

You'll next see the usual challenge screen. If you're sending to a new recipient, a challenge is required, like our example below. Set a challenge and click 'Send':

 

mailock-outlook-add-in-sending-a-secure-email-5-newux-2b

 

If you're sending to a recipient you have sent secure emails to before and they're in your trusted community list, a challenge is optional.