> For the complete documentation index, see [llms.txt](https://docs.emaillabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emaillabs.io/en/analytics-panel/administrator/general-settings/bounce-number-before-blocking.md).

# Bounce Number Before Blocking

Select the number of hardbounces the email address shall receive before being blacklisted.

<figure><img src="/files/N7iEdOGOdlsflOw4yY1t" alt="bounce-number"><figcaption></figcaption></figure>

**The possible options are:**

* **1-3 bounces:** An email address can be blacklisted after getting 1,2 or 3 hardbounces. It is set to 1 bounce by default.

{% hint style="info" %}
**Important!** The selected number of bounces refers only to activating the blocking mechanism. Even when choosing 2 or 3 bounces before blocking, after the first hardbounce, the system will put an email address on the Blacklist, but the messages will not be stopped yet.
{% endhint %}

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.emaillabs.io/en/analytics-panel/administrator/general-settings/bounce-number-before-blocking.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.