> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/guides/marketing/email-deliverability/what-are-spam-traps-and-how-to-avoid-them.md). # What Are Spam Traps (and How to Avoid Them) A spam trap is an email address used to identify senders who are not following proper email practices. These addresses do not belong to real users. ### **Types of Spam Traps** #### **Pristine Spam Traps** * Never used for real communication * Designed to catch bad list practices #### **Recycled Spam Traps** * Old email addresses that were abandoned * Repurposed to identify outdated lists ### **Why This Matters** Sending to spam traps can: * Damage your sender reputation * Reduce deliverability * Lead to blacklisting ### **How to Avoid Spam Traps** * Use confirmed, permission-based contacts * Regularly clean your contact list * Avoid purchased lists * Remove inactive users --- # 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://help.rechat.com/guides/marketing/email-deliverability/what-are-spam-traps-and-how-to-avoid-them.md?ask=&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.