> 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/appendix/brokerage-set-up/email-delivery.md). # Email Delivery Emails you send from Rechat have a pretty good chance of being delivered into your recipient's inboxes.\ However there are measures you can take to improve those odds. Let's say your email address is **** and you're sending an email to ****. \ In this case, Rechat has to deliver an email on behalf of your domain (**greenrealty.com**) to gmail.\ When doing so, Rechat will introduce itself as **mail.rechat.com** although it's claiming to deliver an email from **greenrealty.com.**
The discrepancy between your domain (**greenrealty.com**) and Rechat's domain (**mail.rechat.com**) means that email providers (like Gmail in this case) will consider the email less authentic and may treat it as spam.\ The test of passing or not passing this discrepancy test is called **DKIM Alignment**. ### Domain Authorization Fixing this problem requires authorizing Rechat to introduce itself as a subdomain of your domain. In the above example, we'll make Rechat introduce itself as **rechat-mail.greenrealty.com**. Email providers like Gmail will consider **rechat-mail.greenrealty.com** aligned with **greenrealty.com** and will, therefore, consider the email more authentic. ![](https://1031368632-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MJZySovZjoLVT1XAonI%2F-ML_G--kkbNHAxHDt_1H%2F-ML_NKvabjhyuMjEI4Jr%2FEmil's%20Flows%20\(6\).png?alt=media\&token=feddeb2c-67fe-4c71-a27a-2ab578206964) Although the domain authorization process is optional, it's highly encouraged. In order to fix it, feel free to contact us. Fixing this requires some changes to your domain name. The changes will not break anything and will only allow Rechat to add a cryptographic signature ensuring the authenticity of emails. These proposed changes are not unique to Rechat. All email marketing tools like [Mailchimp](https://mailchimp.com/help/about-email-authentication/), Mailgun, Sendgrid offer the same feature. {% content-ref url="/pages/Pk4cvAnkMIjdH0lcBXZa" %} [DNS Self-Service Setup](/appendix/brokerage-set-up/email-delivery/dns-self-service-setup.md) {% endcontent-ref %} {% content-ref url="/pages/oCIz4EvTknBVyDyUwtBJ" %} [Setup DNS Records](/appendix/brokerage-set-up/email-delivery/setup-dns-records.md) {% endcontent-ref %} --- # 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/appendix/brokerage-set-up/email-delivery.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.