To enhance the security of Email Signature Server there is an optional mechanism to validate the authenticity of the sender.
Prerequisites
|
Enable Secret Key Validation to Email Signature Server
- Use a GUID generator to create a new value: Free Online GUID Generator.
- Navigate to https://admin.exchange.microsoft.com/.
- Go to Mail flow, then Rules.
- Find the Templafy rule, likely named:
templafy email signatures
.- Click Edit.
- Under the Do the following section, click the + button to add another condition.
- Select
Modify the message properties
followed byset a message header
.- Click the first
Enter text
and set the header name toTemplafy-EmailSignatureServer-Secret
. - Click Save.
- Click the second
Enter text
and set the value to the GUID generated in Step 1. - Click Save.
- Click the first
- Navigate to https://portal.azure.com/.
- Open the Kubernetes service containing the Templafy ESS, likely named:
templafyemailsignatureserver
. - Under Kubernetes resources, select Workloads.
- Select the email-signature-server-deployment.
- Select YAML, then JSON in the main window.
- Add the following as an environment variable in the
env
section, you can place this after theoffice365SmtpServerHostname
block:
{
"name": "templafyEmailSignatureServerSecret",
"value": "<GUID>"
}, - Replace
<GUID>
with the value obtained in Step 1. -
Click Review + Save.
-
Check the Confirm manifest changes checkbox and click Save.
NoteIf the secret is not correct or it is not added in Exchange Online, all mail flow will fail. |
Comments
Article is closed for comments.