About this article
|
To enhance the security of our Email Signature Server we have added a feature to validate the authenticity of the sender.
With this feature, the Email Signature Server only processes emails that are sent by the tenant's Exchange Online server.
This feature is disabled by default since it requires the generation of a new security key which needs to be provided as an environment variable in the deployment.
Prerequisites
|
Changes required in the Exchange Online Admin center
- Go to [Exchange Online Admin Page] (https://outlook.office365.com/ecp/?rfr=Admin_o365 )
- Select mail flow
- On the rules tab select the templafy email signatures rule
- Click the pencil Edit icon; the Rule window will appear
- On the Rule window under the *Do the following... section click the
[add action]
button - Select Modify the message properties... -> set a message header
- Set the header name to
Templafy-EmailSignatureServer-Secret
- Set the header value to the new GUID value that was created above.
- Click the
[Save]
button
|
Changes required in the Kubernetes deployment for Client Hosted
- Navigate to the Resource group containing the templafyemailsignatureserver Kubernetes service
- Select the Workloads (preview) item under the Kubernetes resources section of the left hand panel
- Click the email-signature-server-deployment in the main panel
-
Select the YAML item in the left hand pane of the email-signature-server-deployment Overview
-
Select the JSON tab of the main panel
- Add the following as an environment variable in the
env
section, you can place this afteroffice365SmtpServerHostname
block:
{ "name": "templafyEmailSignatureServerSecret", "value": "<Your GUID>" },
- Replace the "<Your GUID>" with the the GUID you configured in the Exchange rule above
-
Click the
[Review + Save]
button -
Check the ☑Confirm manifest changes checkbox
-
Click the
[Save]
button
|
Comments
0 comments
Article is closed for comments.