You can arrange for email notifications sent from Safelink to appear to come from your company's normal email address, eg. notifications@bondcastle.com, instead of the default sender, noreply@safelinkhub.com.
There are two ways that this can be achieved.
-
Allow Safelink to send emails directly to the recipients' email servers.
-
Allow Safelink to relay emails via your email servers, which can pass them on to the recipients' email servers.
Approach 1. Allowing Safelink to send emails directly to the recipients' email servers
Under this approach, the Safelink application will send emails via our email infrastructure, with the 'from' header set to the custom address you choose.
You will need to set up SPF and DKIM records in order to authorise our application's email servers to send emails from your domain. This authorisation does not extend to the email servers used by our staff to send emails, so our staff are not able to send emails purporting to be from you or your domain. The application itself is limited to only sending emails from the specific address you provide.
Approach 2. Allow Safelink to relay emails via your email servers, which can pass them on to the recipients' email servers
Under this approach, the Safelink application will send emails to your email infrastructure, which can relay it to the final recipient. The 'from' header of the email will be the custom address you choose, as for the first approach.
Your email servers will need to be configured to allow our email servers to relay emails through them. We will provide a list of hostnames of our email servers to enable them to be whitelisted so that other parties are not able to relay emails through the same mechanism. This is known to work well with Mimecast, but should be possible for any type of email server. Your email system may also enable you to implement other controls, like checking the sender address or archiving the sent email.