---
metadata:
  - name: generator
    content: Diplodoc Platform v5.47.3
alternate:
  - https://yandex.com.tr/support/tracker/en/user/email-filtering.md
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.com.tr/support/tracker/en/llms.txt

# Filtering incoming emails

<!-- source: en/_assets/style/image.md -->

<!-- endsource: en/_assets/style/image.md -->

Email notifications in Tracker contain service headers that can be used for processing messages. You can set up header filters to move notifications to a separate folder, mark emails with a specific label, or delete unwanted messages.

The list of headers is provided in the [Header descriptions](#headers) table.

For more information about viewing email properties and headers, see [Yandex Mail Help](https://yandex.ru/support/yandex-360/customers/mail/ru/tech-glossary#mail-titles).

## Creating a rule for processing emails {#mail-setup}

Let's examine how to set up a rule for filtering emails in [Yandex Mail](https://mail.yandex-team.ru/#setup/filters). For example, to move notifications about comment replies to a separate folder, set up a rule for filtering emails by the `X-Startrek-Answer` header.

1. In the top right corner of the Yandex Mail interface, click <svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" fill="currentColor" aria-hidden="true" class="yc-icon"><svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24"><path fill="currentColor" fill-rule="evenodd" d="m4.929 4.93.001-.002.002.001.527-.528a.575.575 0 0 1 .786-.025l1.21 1.061a1.856 1.856 0 0 0 3.115-1.291h.004l.105-1.607a.575.575 0 0 1 .574-.537h.746V2v.002h.747c.303 0 .554.235.574.537l.105 1.607h.005c.019.484.223.92.544 1.24a1.854 1.854 0 0 0 2.584.039l1.196-1.05a.575.575 0 0 1 .786.026l.528.528.002-.002v.002l-.001.002.528.527a.575.575 0 0 1 .026.786l-1.06 1.212a1.85 1.85 0 0 0-.492 1.258c0 .515.21.98.548 1.317.32.318.753.52 1.235.539v.004l1.606.105c.303.02.538.271.538.574V12H22v.002h-.002v.746a.575.575 0 0 1-.537.574l-1.607.107v.001c-.484.02-.92.223-1.24.544a1.854 1.854 0 0 0-.05 2.572h-.002l1.062 1.211c.2.228.188.572-.026.786l-.528.528v.002h-.001l-.528.527a.575.575 0 0 1-.785.026l-1.168-1.021a1.851 1.851 0 0 0-1.302-.534 1.86 1.86 0 0 0-1.857 1.786h-.004l-.105 1.607a.575.575 0 0 1-.54.536h-1.56a.575.575 0 0 1-.54-.536l-.105-1.607h-.004a1.851 1.851 0 0 0-.545-1.244 1.851 1.851 0 0 0-1.31-.542c-.504 0-.96.2-1.295.526l-1.177 1.03a.575.575 0 0 1-.785-.027l-.528-.528-.001-.001-.528-.528a.575.575 0 0 1-.026-.786l1.062-1.21-.001-.001a1.85 1.85 0 0 0 .493-1.26c0-.515-.21-.98-.548-1.317a1.85 1.85 0 0 0-1.236-.539v-.001l-1.607-.107a.575.575 0 0 1-.537-.574v-.746H2V12h.001v-.747c0-.303.235-.554.538-.574l1.606-.105v-.004a1.851 1.851 0 0 0 1.242-.545 1.854 1.854 0 0 0 .043-2.577L4.376 6.244a.575.575 0 0 1 .026-.786l.528-.527-.001-.002zM16.286 12a4.286 4.286 0 1 1-8.572 0 4.286 4.286 0 0 1 8.572 0z" clip-rule="evenodd"/></svg></svg> → **All settings**.
1. Select **Rules for processing emails**.
1. Click **Create rule**.
1. Under **Apply to**, select the type of email to which you want to apply the rule.
1. Under **If**, select the **Header** condition and enter `X-Startrek-Answer` in the window that opens.
1. Select **Matches** and enter `yes`.


1. Under **Take the following action**, choose what you want to do with the email: move to folder.
1. Enable the **Ignore other filters** option if needed.
1. If you want to name the rule, click the **enter a name** link.
1. Click **Create rule**.

For instructions on how to create rules, see [Yandex Mail Help](https://yandex.ru/support/yandex-360/customers/mail/ru/web/preferences/filters/create-filter).


## Header descriptions {#headers}

| Header | Comment | Example |
----- | ----- | -----
| X-Startrek | This header indicates a message received from Tracker | Yes |
| X-Startrek-Key | Issue key | TEST-1 |
| X-Startrek-Priority | Priority | Normal |
| X-Startrek-Reporter | Issue author | cheshire.katze@yandex-team.ru |
| X-Startrek-IssueType | Issue type | Task |
| X-Startrek-Assignee | Assignee | cheshire.katze |
| X-Startrek-EntityType | [Entity](../api-ref/entities/about-entities.md) type: Project, portfolio, or goal | Portfolio |
| X-Startrek-EntityId | ID of an [entity](../api-ref/entities/about-entities.md) (project, portfolio, or goal) | 655f328da834c763******** |
| X-Startrek-EntityShortId | Short ID of an [entity](../api-ref/entities/about-entities.md) (project, portfolio, or goal), optional | 12345 |
| X-Startrek-Tags | Tags | Relocation |
| X-Startrek-From | The user who initiated sending the notification (for example, the one who updated the issue last) | cheshire.katze@yandex-team.ru |
| X-Startrek-Cc | Issue followers | cheshire.katze@startrek-cc |
| X-Startrek-Component | Issue components | 5075543ae4b03135cc676db1@startrek-component |
| X-Startrek-QA-Engineer | **QA engineer** field value. Only available if the field is not empty. | cheshire.katze |
| X-Startrek-Changed | Updated fields. Only available if the field values were edited. Not available when creating an issue | Followers,Type,Queue,Key,Tags |
| X-Startrek-Fix-Version | **Fix in versions** field value | Release_05.07.2016 |
| X-Startrek-Affected-Version | **Affected version** field value | 0.1.2 |
| X-Startrek-FingerPrint | Backend MAC address hash | 2b953364 |
| X-Startrek-Old-Status | Old issue status | Testing |
| X-Startrek-New-Status | Current issue status | Testing |
| X-Startrek-Summon | Present if a message is a notification about an invitation to comments | Yes |
| X-Startrek-Answer | Present if a message is a notification about a comment reply | Yes |
| X-Startrek-Queue | Key of the issue queue | TEST |
| X-Startrek-Voted | Present if you voted for this issue | Yes |
| X-Startrek-Favorite | Present if the issue is in your favorites | Yes |