Your stationery layouts can include specific user information obtained from your Active Directory. Provided Mimecast has access to your Active Directory, you can use attributes to your stationery layouts, that are populated with the relevant user information. This requires you to:
- Query the Active Directory using the Directory Browser to return the list of attributes in use.
- Create a list of the attributes in the Administration Console. See the Managing Attributes page for further details.
- Run a directory synchronization to return the attribute data to Mimecast. See the Directory Synchronization page for further details.
To add an attribute to a stationery layout:
- Log in to the Administration Console.
- Click on the Administration menu item.
- Select the Stationery | Layouts menu item.
- Open a Stationery Layout.
- Add the HTML tags in the HTML Editor (see below).
- Add the HTML tags in the Plain Text version of the same stationery layout (see below).
- Click the Save button.
It is important to test that the attributes display correctly after you have added the tags to the stationery layout. Although the HTML tags may be added correctly, the attribute data may not have been populated resulting in the attribute data not being displayed.
As a cloud service, Mimecast does not apply signatures and disclaimers to internal emails.
All attributes are added to a stationery layout using the following HTML Tag syntax:
<MC Type="Variable" Source="From" Attribute="cn">
MC Type="Variable"= The Mimecast HTML tag for attributes.
Source="From" or Source="To"= The attribute's source (i.e. FROM the sender or TO the recipient).
Attribute="cn"= The attribute's common name in your Active Directory from which the data needs to be returned.
|Adds the sender's name.|
|Adds the sender's department name.|
|Adds the sender's telephone number.|
|Adds the sender's job title.|
|Adds the sender's full name.|
|Adds the recipient's promotion code.|
Your directory is unlikely to have details for the recipient. Therefore source="to" is not likely to be valid.
You can also add attributes derived directly from a user's email address. They do not need to be created as an attribute in Mimecast, as this data is already present. In this case, the
attribute="email" value changes to
variable="email". Take the following examples:
|Adds the sender's email address. Including the |
|Adds the recipient's email address. Adds the sender's email address. Including the |
|Adds the sender's domain name.|
|Adds the recipient's domain name.|
|Adds the sender's distinguished name.|
|Adds the recipient's distinguished name.|
|<mc type="variable" variable="subject">||Adds the email's subject.|
|<mc type="variable" variable="messagedate">||Adds the email's sent date.|
|<mc type="variable" variable="date" format="dd-MM-yyyy">|
Adds the current date in the format dd-MM-yyyy. The supported date formats are YYYY-MM-DD, DD-MM-YYYY, or MM-DD-YYYY.
|<mc type="variable" variable="time">||Adds the current time.|
|<mc type="variable" variable="datetime">||Add the current date and time.|
If an email user doesn't have an attribute populated in the email directory, you can add a condition to the HTML tag. For example, a user may not have a company mobile. In these cases the signature caters for this by not including any text indicating a mobile number. There are two methods of accommodating this:
- Do not display an attribute if it is not populated in the email directory. In the example below if a user has no mobile telephone number, the “Mobile” text is not included.
<cc type="conditional" source="from" attribute="mobile" condition="notempty">
<mc type="variable" source="from" attribute="mobile">
- Display a default telephone number. In the example below, if a user has no mobile telephone number, the default number (0876876876) is used.
<mc type="variable" source="from" attribute="mobile" default="0876876876">