# Why DMARC is p=reject

> EmailPal sets DMARC p=reject on sending domains so unauthenticated mail is refused. Why we do not offer p=none for hosted sending.

Source: https://emailpal.io/help/why-dmarc-is-p-reject

## The policies

- `p=none` — monitor only
- `p=quarantine` — treat failures as suspicious
- `p=reject` — refuse failures

EmailPal hosted sending uses **reject**. Cold email from a domain that will not defend its From: header is easy to spoof and easy for filters to ignore.

## FAQs

### Will reject block my legitimate mail?

Only mail that fails SPF/DKIM alignment. That is the point. If a second platform sends as this domain without being in SPF/DKIM, it will fail — use a dedicated sending domain per stack.

### Can I start on p=none for a week?

Not on EmailPal-managed DNS. Monitor mode is how domains stay useful to spammers.

## Need More Help?

[SPF, DKIM, DMARC and MX](/help/spf-dkim-dmarc-and-mx).