> 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/why-are-my-emails-going-to-spam.md). # Why Are My Emails Going to Spam? Use this guide to quickly identify and fix common issues. #### **Emails Going to Spam for Most Recipients** **Likely Causes:** * Domain not authenticated * Sending to cold lists **Fix:** * Complete DNS setup * Start with engaged contacts #### **Low Open Rates** **Likely Causes:** * Weak subject lines * Low engagement history **Fix:** * Improve targeting * Send to smaller, more engaged groups #### **First Campaign Performs Poorly** **Likely Cause:** * No warm-up period **Fix:** * Restart with smaller batches * Gradually increase volume #### **Emails Only Going to Spam for Some Recipients** **Likely Cause:** * Recipient-level filtering **Fix:** * Ask recipients to save your contact * Encourage replies --- # 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/why-are-my-emails-going-to-spam.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.