Allow INKY signatures to be suppressed per message using an email header

INKY currently supports the following message header for controlling its email protection and banner processing:

X-IPW-Ignore: True

However, this header does not prevent INKY Signatures from applying a signature to the message.

Even when X-IPW-Ignore: True is present, the INKY signature processing operates separately and can still append the sender’s configured signature.

Requested feature

Please add a supported message header that instructs INKY Signatures not to apply a team or personal signature to a specific email.

For example:

X-INKY-Signature-Ignore: True

The exact header name can be determined by INKY.

When this header is present, the expected behaviour would be:

• Do not append an INKY team or personal signature.

• Apply the exclusion only to the individual message containing the header.

• Continue any other applicable INKY processing normally.

• Do not require the sender or mailbox to be excluded from INKY.

• Ideally remove the control header before the message is delivered externally.

Existing behaviour

An Exchange Online mail flow rule can currently add:

X-IPW-Ignore: True

This provides a way to exclude a particular message from applicable INKY protection or banner processing.

There is currently no equivalent header for INKY Signatures.

Importantly, adding X-IPW-Ignore: True does not solve this requirement because the signature is still applied. The signature component needs its own supported message-level exclusion mechanism.

Example use case

We sometimes need to forward selected emails to another system for automated processing, such as a ticketing, document-processing, accounting or workflow platform.

These messages need to arrive without an email signature being appended. The signature may:

• Become part of the content being processed.

• Interfere with automated parsing.

• Add unrelated contact details or branding.

• Cause the receiving system to incorrectly identify the end of the original message.

• Be repeatedly included when a message passes between automated systems.

An Exchange Online mail flow rule could identify messages being sent to the processing address and add the signature-exclusion header:

Recipient: processing@example.com Add header: X-INKY-Signature-Ignore Value: True

The intended flow would be:

1. A message is sent or forwarded to the processing system.

2. Exchange Online adds the signature-exclusion header.

3. INKY processes the message normally.

4. INKY Signatures detects the header and does not append a signature.

5. The external system receives the original message content without additional signature content.

Desired outcome

This would provide granular control over signature application without having to:

• Exclude the entire user or mailbox from INKY.

• Disable the user’s signature globally.

• Change the signature configuration temporarily.

• Route the message around INKY.

• Rely on X-IPW-Ignore, which does not affect signature application.

The feature would be particularly useful for messages sent to automated systems, application-generated emails and other workflows where a normal user signature is unwanted or may interfere with processing.