> For the complete documentation index, see [llms.txt](https://learn.mechanic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.mechanic.dev/platform/email/dmarc.md).

# DMARC

{% hint style="info" %}
DMARC is an email authentication measure, increasingly important for deliverability. [Learn more about DMARC here.](https://postmarkapp.com/support/article/892-what-is-dmarc)
{% endhint %}

By default, Mechanic tasks send email using the domain`mail.usemechanic.com`, which is properly configured for DMARC. If you're using Mechanic's default email configuration, DMARC is handled for you. There are no steps you need to take.

Emails sent using a [custom email address](/platform/email/custom-email-domain.md) move the responsibility for DMARC to the email domain administrator. If you're using a custom email address, make sure that the domain you're using is properly configured for DMARC. (Mechanic can't help with this part.)

## Set up DMARC configuration

We recommend using DMARC configuration and monitoring by Postmark. (They're Mechanic's email provider! We're not paid for this endorsement; we just like what they make.)

* Free (and still very good): <https://dmarc.postmarkapp.com/>
* Premium (i.e. more complete tooling): <https://dmarcdigests.com/>
* Product comparison: <https://dmarc.postmarkapp.com/#comparison>

## Verify DMARC configuration

Once you've got your DMARC policy configured (no matter what strategy or tooling you've adopted), you can use these tools to make sure that it's set up properly.

* <https://dmarcian.com/dmarc-inspector/>
* <https://www.suped.com/tools/dmarc-checker>


---

# 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://learn.mechanic.dev/platform/email/dmarc.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.