Introduction
This document describes information on how to customize a logo under the envelope of an encrypted email for CRES (Cisco Registered Envelope Sender) service on ESA (Email Security Appliance).
Prerequisites
Requirements
Cisco recommends that you have knowledge of these topics:
- Cisco Email Encryption CRES
Components Used
This document is not restricted to specific software and hardware versions.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
Background Information
The information in this article is based on CRES Email Encryption Configuration at the box and CRES Email Encryption configuration at websafe: res.cisco.com.
Configure
Below there are two options of how to implement this solution:
Branding
For Branding and logo pre-requisites click here.
Step 1. Set Branding
From an active CRES admin account, Log in and select your account, and navigate to Branding tab, as shown in the image:
Step 2. Add Image
Once you have your image with the proper pixels and KBs select Browse to attach it to the portal.
Finally, confirm the Envelope Profile name and select Add Image, as shown in the image:
Warning: The Encryption Profile Name in ESA must match with CRES administrator account. This option is case sensitive.
Template
Configure, export, and import a template from the CRES portal to the ESA.
Step 1. Set Template
Navigate to your Account and select the Templates tab as shown in the image:
The first time the only template that is visible is the Default template.
Note: In order to see a preview of the default template, select the Default template and then identify the Locale Language you want to see and select the icon under the Actions column as shown in the image:
In the section Copy template set fill the Title of a new template set and generate a copy based on the Default Template.
Select Add to generate the template as shown in the image:
Example: Test_Template as shown in the image
Step 2. Verify Template
Select Test_Template
Select the Locale you want to work at.
By default, if you select the Preview button the next text displays as shown in the images:
The format of this template is based on HTML so you can add/edit objects based on the same language. In this case you add a IMG logo at the first part of the template.
For this, please have a public URL where you can gather the image.
Example:
https://yourURL.com/yourImage
Now, in HTML format, create an <img> tag . You can find the "img" tag of the mail Icon and just copy and paste that and change the source.
<img style="display: inline-block" width="200" height="100" alt="Logo" src="https://yourURL.com/yourImage"/
Add this new tag wherever you need it
Warning: Be careful with the start/end of the tags and sections so the format keeps without any corruption
If all is good, on the next preview you check, the image logo you added with the <img> tag is present as shown in the image:
Step 3. Add Text Resource in Profile
Once the final template is ready, go back to the edit page of the HTML and copy ALL the content of the HTML code.
Log in to the ESA appliance and navigate to Mail Policies > Text Resources.
Select Add Text Resource.
Give a name to your new template.
Under the option type, select Encryption Notification Template HTML as shown in the image:
Finally, delete the default content generated and paste the content from the CRES portal.
Submit and commit the changes.
Step 4. Configure Template in Profile
Apply this under ESA Encryption configuration.
Navigate to Security Services > Cisco IronPort Email Encryption.
Select the profile in use to encrypt.
Scroll down to the section of Notification Settings
Under the Encrypted Message HTML Notification select the new template generated.
Submit and commit the changes.
Verify
Send an email with a proper tag to match the encryption profile configured. The final test message shows the custom logo.
Troubleshoot
There is currently no specific troubleshooting information available for this configuration.
Related Information