Knowledge Base

How to add signatures to calendar messages


You would like to add signatures to calendar messages (e.g. meeting requests).


Currently, calendar messages, including meeting requests, are not officially supported by CodeTwo Email Signatures for Office 365. It means that with the default program configuration, no signature will be added to your calendar message, even though:

  • the email address you use to send the message is included in the scope of senders;
  • you’ve configured conditions and exceptions (e.g. a special keyword or a chosen group of recipients) which trigger a signature rule when you send the message.

If you still need to enable signatures in calendar messages, you can use the workaround described below.


This solution might not always work. The signatures may not look as intended or some other unexpected changes may occur. Also, if you use the Sent Items Update (SIU) feature, it will not work for meeting request messages. Use this workaround at your own risk and be ready to revert the changes, if necessary.

To turn on signatures for calendar messages, you need to reconfigure the program's transport rule:

  1. Open the Exchange admin center, and go to Mail flow > Rules. The CodeTwo Exchange transport rule should be visible on the list of rules (Fig. 1., item 2).

The list of Exchange transport rules.
Fig. 1. The list of Exchange transport rules.

  1. Double-click this rule or use the Edit icon (Fig.1., item 3) to modify it.
  2. Remove the following exception: The message type is... Calendaring (Fig. 2.) and wait a few minutes for the changes to propagate to the CodeTwo services.

The exception to be removed.
Fig. 2. The exception to be removed.

Calendar messages, including meeting requests, should now be stamped with signatures.


Since CodeTwo Email Signatures for Office 365 does not officially support calendar messages, remember to check if everything works and looks as expected. Be ready to revert the changes anytime by adding the exception again (alternatively, you can remove the connectors and configure them again in CodeTwo Admin Panel - this will restore the default configuration of the program's transport rule and connectors).

Was this information useful?