The Mobile Device Signatures dialog is opened by clicking the Mobile Device Signatures button on the Configuration page in the Configuration backstage of the main application window.
This dialog controls how the signatures for mobile devices are managed in your organization. There are two approaches available:
•Injection into emails sent from mobile devices as they are delivered through Exchange Server and Office 365.
•Distribution of mobile signatures to the users in your organization by email.
The signature that is either injected or sent via email is specified using the Mobile Device Signature setting on the Manage Deployment dialog.
Inject Signatures
Signature injection works by using a set of rules to identify where in an email the mobile device signature should be inserted. The text specified by the rule is replaced by the pre-generated signature content, resulting in the signature being injected into the email. Signatures can be injected into emails sent through On-Premises Exchange Server using the Email Signature Manager Transport Agent and through Office 365 using our cloud-based Signature Injection Service for 365 (if your license is enabled to use it).
To enable signature injection, on the Inject Signatures tab, select the Inject signatures into emails sent from mobile devices using rules option, which will have the following effect:
•When using Exchange Server, the Transport Agent will inject the pre-generated signatures by the Email Signature Manager Service.
•When using Office 365, the Signature Injection Service for Office 365 will inject the pre-generated signatures uploaded by the Email Signature Manager Service to the cloud.
To check if your license is enabled for the Signature Injection Service for Office 365, and configure your Office 365 tenant to use it, click the Office 365 Integration... button to open the Office 365 Integration dialog. This button is only available when Office 365 is configured in the Environment Configuration dialog.
By default, most mobile devices send new emails in plain-text format. Selecting the Convert plain-text emails sent from mobile devices to HTML option will cause the plain-text emails to be converted into HTML format and and the HTML signature to be injected.
Note When a plain-text email is converted to HTML, the rules applicable to HTML format emails will be applied, not those applicable to only plain-text emails. Further, an email is only converted if a plain-text rule matches.
The Injection Rules are used to define how signatures are injected and the order in which they are evaluated:
The following actions can be performed:
•To create a new rule, click the Add... button, which opens the Manage Signature Injection Rule dialog.
•To edit an existing rule, select it in the grid and click the Edit... button, which opens the Manage Signature Injection Rule dialog.
•To delete an existing rule, select it in the grid and click the Delete button; you will be prompted to confirm this action before the rule is deleted.
•To move a rule higher in the list (so it is evaluated earlier), select it in the grid and click the Move Up button.
•To move a rule lower in the list (so it is evaluated later), select it in the grid and click the Move Down button.
Send Signatures
Email Signature Manager can be configured to send mobile device signature via email to the users in your organization. When users receive the email, they can open the signature attachment and copy and paste the signature into their mail app. This feature is primarily intended for when there is no possibility to use the signature injection features.
To enable distribution by email:
•Select the Send new and updated signatures by email to users hosted on Office 365 option to send mobile device signatures via email to users who have their mailbox hosted on Office 365.
•Select the Send new and updated signatures by email to users hosted on Exchange option to send mobile device signatures via email to users who have their mailbox hosted on Exchange Server.
The email that is sent to each user is configured in Email Configuration:
The email has the following properties:
Name |
Description |
Sender's Display Name |
The display name for the sender of the email sent to each user. |
Sender's Email Address |
The email address for the sender of the email sent to each user. |
Email Subject |
The subject for the email sent to each user. |
Email Body (Plain-Text) |
The plain-text body of the email; the body is parsed in the same way as signatures and you can therefore make use of the same fields (refer to this appendix for details). |
From the configuration shown above, the following email would be delivered to the appropriate users in your organization:
For more information about distributing signatures via email, please refer to this topic.
When the configuration has been completed as required, click the Save button to save your changes. Click the Close button to close the dialog; if you have made any changes, you will be prompted to save before the dialog is closed.