---
title: "How to send a #debug email"
slug: "how-to-send-a-debug-email"
description: "Send a #debug email to Opensense support from the affected mailbox, so engineering can trace missing, incorrect, or badly formatted signatures."
updated: 2026-07-16T15:58:27.000Z
canonical: "https://help.opensense.com/docs/how-to-send-a-debug-email"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.opensense.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to send a #debug email

## Overview

If a signature isn't working as expected, send a #debug email. It gives Opensense support the diagnostic data to trace and fix the problem quickly.

## What is a #debug email?

A #debug email is a diagnostic tool. It flags one specific mail flow event in the Opensense backend for engineering review. The subject line holds `#debug` and 5 random digits. This unique identifier lets the engineering team find your exact mail flow event and gather the technical data tied to it.

## When to send a #debug email

Send a #debug email for any of these signature issues:

<dl class="kb-insights-summary">
  <div><dt>Missing signatures</dt><dd>A user's signature does not appear at all.</dd></div>
  <div><dt>Incorrect signatures</dt><dd>The wrong signature is applied.</dd></div>
  <div><dt>Placement problems</dt><dd>The signature appears in the wrong place while composing.</dd></div>
  <div><dt>Formatting issues</dt><dd>Signature elements are misaligned, distorted, or display incorrectly.</dd></div>
  <div><dt>Wrong signature data</dt><dd>Incorrect information, such as a name, title, or contact details, appears in a signature.</dd></div>
</dl>


## Sending a #debug email

:::caution[Send it from the affected mailbox]
The #debug flag works only when you send it from the affected user's mailbox, in the email client where the issue happens. If you send it from a different account or client, it does not capture the diagnostic data.
:::

1. In the affected user's email client, compose a new email. Do not reply to or forward an existing message.
2. Address the email to <help@opensense.com>.
3. In the subject line, type `#debug`, a space, and any 5 random digits, for example `#debug 67890`.
4. In the body, add the details listed below.
5. Send the email.


### What to include in the body

The more context you give, the faster support can find the cause.

<dl class="kb-insights-summary">
  <div><dt>Email type</dt><dd>Whether the issue happens on new emails, replies, or forwards.</dd></div>
  <div><dt>Email client and device</dt><dd>The platform and device, for example Outlook on Windows, Gmail in Chrome, or Apple Mail on iPhone.</dd></div>
  <div><dt>Affected users</dt><dd>The names or email addresses of the users with the issue.</dd></div>
  <div><dt>Timeline</dt><dd>When the issue was first noticed.</dd></div>
</dl>


## After you send it

The Opensense engineering team uses the diagnostic data tied to your #debug email to investigate. Support follows up with findings or next steps.

## What's next

- [Signature management and deployment FAQ](https://help.opensense.com/docs/signature-management-deployment-faq): answers to other common signature questions.