Gmail wants a DMARC record on your domain and you’re staring at a DNS panel wondering which policy won’t reject your own newsletter.

You’ve read three explanations of p=none, p=quarantine and p=reject and copied a record from a forum thread.

None of them told you whether your own SPF and DKIM pass first, which is the thing the policy acts on.

The next five minutes walk through what DMARC does, why setups go wrong, and the steps InboxStack takes you through to set it up and watch the results.

If you’re reading this because a client asked for “that DMARC thing” by Friday, you’re in the right place.

Start your 14-day trial → — full access from day one, no card required.

What DMARC does

DMARC (Domain-based Message Authentication, Reporting, and Conformance) stops your domain being used for phishing and fraud. It lets Gmail and other receivers check a message against your SPF and DKIM records, and it tells them what to do with mail that fails: nothing, quarantine it, or reject it. For how the three records work together, see the DMARC, DKIM and SPF walkthrough.

Why DMARC setups go wrong

Setting it up means editing DNS, understanding SPF and DKIM, and knowing which services send mail as your domain. Smaller teams often skip it for that reason, or publish a record and never look at the reports again.

What InboxStack does

  1. A guided setup. The dashboard walks you through the DMARC steps in order, so you don’t need to read the RFC.
  2. DNS records written for you. InboxStack creates the DMARC record, which removes the most common source of typos.
  3. Results after you publish. Once the record is live, InboxStack shows SPF, DKIM and DMARC results per message so you can see what’s failing and fix it before tightening the policy.
  4. Free, for now. At the time of writing there is no charge, so a small team can set DMARC up without a budget line.

The walkthrough

  1. Create an account on InboxStack. It takes a minute.
  2. Look around the dashboard so you know where the DMARC section and the results live.
  3. Follow the DMARC setup. It tells you which DNS records to create and confirms when they resolve.
  4. Check the results after publishing. Watch for messages failing SPF or DKIM, fix the sending service that’s causing them, and only then move the policy from p=none to p=quarantine or p=reject.

That order — records first, results second, policy last — is what keeps your own mail out of the reject pile.