> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/help/help-center-en-es/email-security/blocklist.md).

# Lista de bloqueo

Bloquea tú mismo a un remitente o a todo un dominio, sin contactarnos. Úsalo cuando un remitente siga enviando correos no deseados, o para detener todos los correos de un dominio, sea cual sea el remitente.

## Añadir una regla

1. En Stoïk Protect, ve a `Correos sospechosos` > `Configuración` y abre la `Lista de bloqueo` .
2. Haz clic en `+ Añadir`.
3. Elige qué bloquear: un `Remitente` o un `Servidor`, e introdúcelo.
4. Elige los inquilinos a los que se aplica la regla.
5. Opcionalmente, añade una nota para recordar por qué lo bloqueaste.
6. Guarda la regla.

La regla solo se aplica a los inquilinos que seleccionaste.

## Qué le sucede a un correo bloqueado

* Se envía a cuarentena, con un banner genérico de sospecha añadido.
* No se genera ninguna alerta en Stoïk Protect.

## Editar o eliminar una regla

Edita o elimina una regla en cualquier momento desde la `Lista de bloqueo` pestaña. Cada regla muestra los inquilinos a los que se aplica y, si añadiste una, la nota que explica por qué existe.

Si un correo que esperabas que se bloqueara sigue llegando a tu bandeja de entrada, escríbenos a <protect@stoik.io>.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stoik.io/help/help-center-en-es/email-security/blocklist.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
