# Headers

'Headers' allows you to append additional parameters to your messages relayed to the receiving server. This added information helps the server to interpret the message as not spam properly and to qualify the type of email to the correct folder. 

The Headers option will also allow you to specify the type of your sent emails, which, as a result, will aid providers such as Gmail or Yahoo in better understanding the character of the messages.

<figure><img src="/files/2hQY2Kem0u16ss5PoaUY" alt="headers"><figcaption></figcaption></figure>

1. Go to the **SMTP Accounts tab > Settings > Headers**.
2. Select the **“Turned on”** option to activate the Headers application.
3. Choose the type of your sent messages. There are three types available:
   * **No type:** the system will not add a "precedence" header in this case. It is an option for general emails.
   * **Transaction 'list':** this kind of email targets one recipient only and has a transactional type. Examples are registration confirmations or password reminder messages.
   * **Marketing 'bulk':** this email targets many recipients simultaneously; it can be a newsletter or other sales offer.
4. Select the proper option based on the type of messages that you send from your account.
5. In this article, you can find [the most important differences between marketing and transactional emails.](https://emaillabs.io/en/what-kind-of-emails-can-be-sent-using-emaillabs/)
6. Make sure to save the changes by clicking the **“Create button”.**

**⬅️ Detailed instructions for each panel section under the 'Functionalities' tab can be found in the drop-down menu on the left.**


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.emaillabs.io/en/analytics-panel/functionalities/headers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.