# Email Headers and Message Format



> Message headers, MIME structure, and basic formatting rules help inboxes parse and trust an email.



- Human page: https://mailrith.com/guides/email-headers-and-message-format

- Markdown page: https://mailrith.com/guides/email-headers-and-message-format.md

- Category: Authentication and Deliverability

- Reading time: 7 min read

- Related keywords: Email Headers and Message Format, Email Headers and Message Format guide, Authentication and Deliverability, Authentication and Deliverability guide, email sending guide, email marketing guide, email deliverability guide, Email Editor, RFC 5322 Internet Message Format, One-Click Unsubscribe and Opt-Outs



## AI Agent Notes

- Use this page as plain-language guidance for the specific email sending issue named in the title.

- Preserve the distinction between Mailrith, an email delivery service, DNS, and inbox providers when explaining fixes.

- When a user is running a free tool, pair the tool result with the relevant issue or step section from this guide.



### Email Headers and Message Format

Message headers, MIME structure, and basic formatting rules help inboxes parse and trust an email.

Email is not only the visible design. Every message has headers and a body. Headers carry information such as From, To, Subject, Date, Message-ID, Reply-To, List-Unsubscribe, DKIM signatures, and routing details.

Inbox providers expect messages to follow internet message format rules. If headers are missing, duplicated in the wrong way, too large, or misleading, delivery can suffer even when the design looks fine.

Important headers should be clear and consistent. The From header should identify the sender. The Subject should describe the message honestly. The Date and Message-ID should exist. The Reply-To should point to a real inbox when replies matter.

MIME is the structure that lets one email contain different parts, such as HTML, plain text, images, attachments, and tracking elements. A healthy marketing email usually has a clear HTML body and, where supported by the sending system, a plain-text version.

HTML email should be simple and resilient. Some email clients block images, ignore certain CSS, clip very large messages, or render the same layout differently. That is why testing on desktop and mobile matters.

Message format is not a substitute for permission or authentication. It is a baseline. A well-formatted unwanted email can still go to spam, but a badly formatted wanted email may be rejected or displayed poorly.

1. Use a recognizable From name and From email.
2. Write a subject line that matches the actual message.
3. Use the [Email Editor](https://mailrith.com/docs/email-editor.md) to build a clean body instead of pasting complicated HTML from unknown sources.
4. Keep images useful and avoid putting important text only inside an image.
5. Send a test email and open it in at least one desktop inbox and one mobile inbox.
6. For deliverability troubleshooting, inspect the original headers and check From, Reply-To, Message-ID, SPF, DKIM, DMARC, and List-Unsubscribe results.
7. If an email delivery service reports a message-format error, fix the header, MIME, HTML, or size issue before retrying a large send.

- The visible email is only one part of the message.
- Headers help inboxes understand sender identity, routing, authentication, and unsubscribe behavior.
- Message-ID, Date, From, To, and Subject should be valid and not duplicated incorrectly.
- Subject lines and display names should not mislead people.
- Large or messy HTML can display poorly and may trigger clipping in some inboxes.
- Use [One-Click Unsubscribe and Opt-Outs](https://mailrith.com/guides/one-click-unsubscribe.md) to understand unsubscribe headers.
- Use [From, Reply-To, and Return-Path](https://mailrith.com/guides/from-reply-to-and-return-path.md) to understand sender-related headers.

## Fix Common Issues
### Original Headers Missing

A header analyzer says the pasted text does not contain original email headers.

1. Open the delivered test email in the receiving inbox.
2. In Gmail, open the three-dot menu and choose `Show original`.
3. In Outlook or Apple Mail, look for message source, view source, or internet headers.
4. Copy the header block that includes From, Return-Path, Received, Authentication-Results, and DKIM-Signature if present.
5. Paste the headers into the analyzer again.
6. Remove private body content if you do not need it checked.

### From Domain Not Found

A header analyzer cannot find the visible From domain in the pasted headers.

1. Make sure the pasted content includes a line that starts with `From:`.
2. Send a fresh test email if the original message source is incomplete.
3. Check that the From address is a normal email address such as `name@example.com`.
4. Fix the sender identity in the sending tool or email delivery service if the From header is malformed.
5. Send another test and analyze the new headers.

### Authentication-Results Missing

A header analyzer cannot find the receiver's SPF, DKIM, and DMARC verdicts.

1. Copy headers from the inbox that received the email, not from the draft or sending preview.
2. Look for a header named `Authentication-Results`.
3. If the receiving inbox does not add that header, send the test to Gmail, Outlook, or another inbox that shows original authentication results.
4. Analyze the new headers and compare SPF, DKIM, DMARC, From, Return-Path, and DKIM `d=` domains.

### Email Too Large or Clipped

An HTML size checker says the email is near or above a common clipping threshold.

1. Remove unused layout sections, comments, and pasted template code.
2. Shorten repeated content and move long supporting detail to a landing page.
3. Avoid embedding base64 images in the HTML.
4. Keep only the images that help the reader understand or act.
5. Send a test email to Gmail and confirm the full message, footer, and unsubscribe link are visible.

### Script Tag Found

An HTML checker found a script tag inside the email content.

1. Remove every `<script>` tag from the email HTML.
2. Do not rely on JavaScript for layout, tracking, buttons, forms, countdowns, or personalization inside email.
3. Use email-safe HTML and normal links instead.
4. Send a test email and confirm the content still works without scripts.

### Form Tag Found

An HTML checker found a form inside the email content.

1. Remove the embedded form from the email.
2. Create a hosted form or landing page instead.
3. Link to that page from one clear button or text link.
4. Send a test email and click the link to confirm the form opens correctly.

### Base64 Image Found

An HTML checker found an embedded base64 image in the email content.

1. Upload the image to a reliable HTTPS image host or use your email editor's image upload.
2. Replace the embedded base64 data with a normal HTTPS image URL.
3. Add useful alt text if the image supports the message.
4. Run the HTML size checker again and send a test email.

### Image-Heavy Email

A checker found many images in the email.

1. Remove decorative images that do not help the reader understand the message.
2. Keep important text as real text, not only inside images.
3. Make sure the main call-to-action is visible even when images are blocked.
4. Send a mobile test and confirm the message is easy to read.

> If the email delivery service says the message is malformed, do not keep resending. Fix the format problem first, then test again.

Related resources:
- [Email Editor](https://mailrith.com/docs/email-editor.md): Use Mailrith's editor to build and preview email content.
- [RFC 5322 Internet Message Format](https://www.rfc-editor.org/rfc/rfc5322): The technical standard for internet email message format.
- [One-Click Unsubscribe and Opt-Outs](https://mailrith.com/guides/one-click-unsubscribe.md): Understand List-Unsubscribe headers and body unsubscribe links.



## Related Guides

- [Sender Domains and Email Authentication](https://mailrith.com/guides/sender-domains-and-authentication.md): Your sender domain is the name inboxes learn to trust, and authentication proves that your email delivery service is allowed to send for it.

- [From, Reply-To, and Return-Path](https://mailrith.com/guides/from-reply-to-and-return-path.md): An email has several sender-related addresses, and each one has a different job in delivery and replies.

- [DNS, PTR, and Reverse DNS](https://mailrith.com/guides/dns-and-reverse-dns.md): DNS records identify your domain, while reverse DNS helps inboxes check whether a sending IP has a sensible hostname.
