> For the complete documentation index, see [llms.txt](https://help.stringeex.com/stringeex-tong-dai-cham-soc-and-quan-ly-khach-hang/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.stringeex.com/stringeex-tong-dai-cham-soc-and-quan-ly-khach-hang/en/ii.-system-features/9.-settings/9.7-campaign-management/9.7.3-email-campaign/do-not-send-email-list.md).
# Do-not-send email list
## Interface of do-not-send email list
* **Email:** email address
* **Block the entire portal:** enable/disable blocking the whole portal to not allow sending out
* **Block by campaign:** enable/disable block by campaign, users can still send to this email in other email sending parts other than email campaign
* **Block sending by client:** Block sending by client
* **Action:**
* **Edit:** fix blocked email info
* **Delete:** delete the corresponding email
## Block emails on the system
On the screen of the list that does not send email, the admin clicks "Add email". The adding email screen opens, the admin enters the necessary information as shown in the picture:
* **Add words:** choose whether to add each email or add it in bulk from an excel file
* **Block the entire portal:** enable/disable to block the whole portal to not allow sending out
* **Block by campaign:** enable/disable to block by campaign, users can still send to this email in other email sending parts other than email campaign
* **Campaign list:** enter the list of campaigns you want to block
**Note: If the customer receives an email and chooses to Unsubscribe or put it in spam, the customer's email will be automatically added to the do not send email list. Admin can't edit, delete this email in the list.**
---
# 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://help.stringeex.com/stringeex-tong-dai-cham-soc-and-quan-ly-khach-hang/en/ii.-system-features/9.-settings/9.7-campaign-management/9.7.3-email-campaign/do-not-send-email-list.md?ask=&goal=
```
`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.