What are proper header identification practices?

Still have a question, spotted an error, or have a better explanation or a source we should cite?

You've set up your ESP, built your first campaign, and you're about to hit send. But have you checked what's actually in your email headers? Most senders never do, and that's exactly where deliverability problems hide.

Headers are the behind-the-scenes metadata that mailbox providers read before your subscriber ever sees the email. Getting them right isn't optional. It's the difference between landing in the inbox and looking like a spammer.

The core header checklist

  • From address. Use a real, monitored address at a domain you own and have authenticated with SPF, DKIM, and DMARC. Something like hello@harborpost.net, not a throwaway address you'll abandon next month.
  • Friendly From name. Make it recognizable. Your brand name, or "YT at Review My Emails", not "noreply" or a random string. Subscribers decide whether to open based on this name, before they even read the subject line.
  • Reply-To. If you want replies going somewhere different from your From address, set this explicitly. Just make sure someone actually monitors it. An ignored Reply-To is worse than no Reply-To.
  • Message-ID. Should be unique per message and formatted correctly (like unique-id@yourdomain.com). Your ESP handles this automatically, but if you're building on raw SMTP, don't skip it. Missing or duplicate Message-IDs are a spam signal.
  • Date. Should reflect the actual time the message was sent. Backdated or future-dated timestamps are a red flag for filters. Again, your ESP sets this, but worth knowing.
  • List-Unsubscribe. For bulk senders, this is non-negotiable. Both Gmail and Yahoo Mail now require one-click unsubscribe headers for senders above certain volume thresholds. Include both the mailto and the HTTPS version.
  • List-Id. If you manage multiple lists, this header helps mailbox providers identify which list a message came from. It also helps subscribers set up filters without unsubscribing entirely.

The gotchas that trip people up

The biggest one: fake Re: or Fwd: prefixes in the subject line. Some senders think this boosts open rates (and it might, briefly). But mailbox providers have seen this trick for years, and it's a fast track to the spam folder. It also violates CAN-SPAM, CASL, and most ESP terms of service.

Another common mistake is mismatching your visible From address with your authenticated envelope sender. The display name can be your brand. The domain needs to match what your DKIM signature and SPF record cover. When those don't line up, DMARC fails, and that hurts your reputation fast.

Also worth knowing: most ESPs inject their own headers on top of yours. Mailchimp, Twilio SendGrid, and Postmark all add tracking and routing headers automatically. That's fine and expected. What you want to check is whether any of their injected headers conflict with something you've set manually. If you're setting a custom Message-ID but your ESP overwrites it, one of you is going to win, and it might not be you.

If you want to see what headers are actually going out on your emails, our free Email Header Analyzer reads raw header output and tells you what each field means. Worth a look before your next send. If something looks off and you're not sure what to fix, drop us a message and we'll take a look.

Contributors

Who worked on this answer

Every name links to their profile. Every company links to their site. Real people, real accountability.

Ask an AI · tailored to your setup

Get a header checklist tailored to your ESP

I'm setting up email sending for your organization using your ESP, e.g. Mailchimp / SendGrid / Postmark. Can you give me a checklist of exactly what I need to set in my From, Reply-To, Message-ID, and List-Unsubscribe headers? Flag any gotchas specific to my ESP and tell me which headers could cause DMARC or spam filter issues if I get them wrong.

Edit the yellow boxes, then send to the AI of your choice.