> For the complete documentation index, see [llms.txt](https://help.smartrr.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartrr.com/docs/support/admin-portal/dmarc-authentication-for-emails.md).

# DMARC Authentication for Emails

Contact us at support\@smartrr.com to provide you with the DNS records and to help verify the changes on our end to complete the DMARC setup for you. Minimize bounced emails today!

To ensure high deliverability rates and ensure DMARC checks will pass, the following CNAME record can be implemented in your email server.

## Steps to Implement

1. Open your email server (i.e. MailChimp, GoDaddy, etc.)
2. Navigate to the **relevant domain** > **DNS Records** > **Add a new record**
3. Enter the following values below:
   1. Type: **CNAME**
   2. Name: **smartrr.mail.\<ShopName>.com** (e.g. smartrr.mail.smartrrsnacks.com)
   3. Value: **\<ShopName>.vendoremail.smartrr.com**
   4. TTL: **1/2 Hour** (or whatever the default setting is)
4. Contact us to complete the verification on our end.
5. Have emails sent from you, and minimize failed notification deliveries.


---

# 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.smartrr.com/docs/support/admin-portal/dmarc-authentication-for-emails.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.