> ## Documentation Index
> Fetch the complete documentation index at: https://docs.allgoodhq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Email not sending or rendering wrong?

> Work through the common reasons an email is stopped, won't save, or shows blank values.

A stopped send can feel alarming, but it usually means allGood caught a problem before your recipients did. Most email problems fall into three groups: a send that is stopped, a save that is blocked, and values that show up blank. Find your symptom below.

## The send is stopped for a missing unsubscribe link

The email body has no working `{{ send.unsubscribeUrl }}`. Any other spelling, such as `unsubscribe_url`, shows as blank and fails the check.

1. Open the email or its template and find the footer.
2. Replace the unsubscribe placeholder with `{{ send.unsubscribeUrl }}`.
3. Preview the email, then publish it again.

If the problem comes from a shared template, fix it there so later emails inherit the fix. See [Changing an email template](https://docs.allgoodhq.com/mk/content/email/templates/changing-an-email-template.md).

## The send is stopped for a missing postal address

Your postal address comes from **Sender Defaults** in **Settings → Email**. Add it there, then check that the footer uses `{{ sender.postalAddress }}` in both the HTML and the plain-text version. See [Before an email can send](https://docs.allgoodhq.com/mk/content/email/emails/before-an-email-can-send.md#build-the-footer).

## The send is stopped for a weak DMARC policy

Your sending domain's DMARC policy is below `quarantine`, or it has none. This is often inherited from a root domain still at `p=none`. Publish the record shown on the domain's card under **Email Domains** on the sending subdomain itself, then click **Verify All**. See [What allGood requires on your sending subdomain](https://docs.allgoodhq.com/mk/settings/email/authentication.md#what-allgood-requires-on-your-sending-subdomain).

## A greeting or other value shows as blank

Two causes are common.

* **The recipient has no value for that field.** Add a fallback: `{{ person.firstName | default: 'there' }}`.
* **The field name is wrong.** A misspelled or nonexistent field shows as blank with no error. Compare it against [Personalizing an email](https://docs.allgoodhq.com/mk/content/email/emails/personalizing-an-email.md).

Preview a person with complete data and a person with gaps to tell the two apart.

## The save is blocked by a component check

A section of the email no longer matches its approved block. The message names the block and what differs. Restore the section's structure, or ask your marketing ops team to update the block in the library. Changing words, links, or style values doesn't trigger the check. See [Component libraries](https://docs.allgoodhq.com/mk/content/component-libraries.md).

## A template shows as out of date

The brand guideline or component library it was published against has changed. See [Changing an email template](https://docs.allgoodhq.com/mk/content/email/templates/changing-an-email-template.md).

## If none of these fix it

Contact [support@allgoodhq.com](mailto:support@allgoodhq.com). Include the email's name, the exact message you see, and whether the problem appears in preview, in a test send, or only at send.

## Related articles

* [Before an email can send](https://docs.allgoodhq.com/mk/content/email/emails/before-an-email-can-send.md)
* [Previewing and testing an email](https://docs.allgoodhq.com/mk/content/email/emails/previewing-and-testing-an-email.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.