Fix Signature Integrations with INKY

 

  1. Navigate to the Microsoft Admin Console: admin.microsoft.com

  2. Select the Exchange Admin Console in the bottom left corner

  3. Go to Mail Flow → Rules

  4. Select the “IOC Strip Markup” rule then hit Edit

  5. Select “add exception”

    1. Choose “A message header… matches these text patterns”

    2. FOR EXCLAIMER (DON'T COPY THE QUOTES & CASE SENSITIVE)

      1. Select “Enter text…” and add ‘X-ExclaimerHostedSignatures-MessageProcessed’ then OK

      2. Select “Enter text patterns…” and add ‘true’ hit the + button then ok

    3. FOR CODETWO (DON'T COPY THE QUOTES & CASE SENSITIVE)

      1. Select “Enter text…” and add 'X-CodeTwoProcessed' then OK

      2. Select “Enter text patterns…” and add ‘true’ hit the + button then ok

    4. FOR CROSSWARE (DON'T COPY THE QUOTES & CASE SENSITIVE)

      1. Select “Enter text…” and add 'X-CWesigProcessed' then OK

      2. Select “Enter text patterns…” and add ‘true’ hit the + button then ok

    5. FOR SENDERGEN (DON'T COPY THE QUOTES & CASE SENSITIVE)

      1. Select “Enter text…” and add 'X-SG-Signature' header OK

      2. Select “Enter text patterns…” and add ‘true’ hit the + button then ok

  6. Save the rule and wait for propagation

 

We have seen an increase in reports of this issue recently with Exclaimer and they have discussed this with Microsoft. Previously, the expected behavior with Out Of Office emails was that they were not routed to Exclaimer's service, as they currently cannot add signatures to them, and they follow the route any standard email within your environment would if you were not using our service. Recently, Exclaimer had reports that these emails have been routing to their service and, unfortunately, due to the way the messages are formed, they are unable to identify the tenant and these are routed directly to Microsoft/Internet to deliver via routing based on MX records. This has led to these emails following less standardized routes and being delivered to SPAM folders or quarantine. They have confirmed that the below steps will resolve this issue.

  1. Log into Office 365 and navigate to Exchange Admin Center

  2. Navigate to Mail Flow

  3. Edit the Identify Messages to Send to Exclaimer Cloud transport rule

  4. Change the Message Type exception from Calendaring to Automatic Reply

Please note that the Calendaring exception is no longer required for emails routed to Exclaimer Cloud. There will be no other changes required, so save this and allow for up to an hour for the change to replicate across Microsoft 365. This will force the Automatic Reply messages to no longer route to our service as expected.