How does case sensitivity work in email headers?

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

Email header field names (like "From", "To", "Subject") are never case sensitive. The spec is RFC 5322, and it treats From, FROM, and from exactly the same. Every email client honors this. You can't break email by capitalizing a header name differently.

The values inside those headers follow different rules. Domain names are always case insensitive because DNS itself ignores case. captain@tidalmail.com and captain@TIDALMAIL.com are the same address. The local part (the bit before the @ sign) is technically case sensitive according to the spec. Captain@tidalmail.com and captain@tidalmail.com could theoretically be two different mailboxes.

In practice, no major provider actually implements case sensitive local parts. Gmail, Outlook, Yahoo Mail, and everyone else treat them case insensitively. They do this to avoid user confusion (imagine trying to explain to a customer why captain@ and Captain@ are different mailboxes). This is a real world application of Postel's Law: be strict in what you send, liberal in what you accept.

The one place case sensitivity can bite you is custom mail servers. If you're running your own SMTP server with a config that enforces case sensitive local parts, you can create addresses that break user expectations. Don't do this unless you have a very specific technical reason and you're prepared to support the resulting confusion.

Worth knowing: some older systems (mostly Unix-based mail servers from the 1990s) did implement case sensitive local parts. You might still encounter one in a corporate environment or a university. If you're sending to an address that looks case sensitive and bounces keep happening, try the exact capitalization the recipient gave you. But this is rare enough that it's not worth worrying about unless you hit it.

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

Is case sensitivity breaking your delivery?

I just read this Email Almanac entry on case sensitivity in email headers, and I'm wondering if this could be causing issues in my setup. Here's what I'm working with: My email infrastructure: - Platform/ESP: e.g. Mailchimp, custom SMTP, Postmark - Sending domains: list them - Technical access: full server control / ESP dashboard only / limited What's happening: - Are bounces or delivery failures mentioning case issues in the error messages? - Are you importing lists from multiple sources with inconsistent capitalization? - Are you running a custom mail server with case sensitive local parts enabled? - Are recipients complaining that email to one version of their address works but another doesn't? What I want to figure out: - Whether case sensitivity is actually causing my current problem - If I need to normalize address capitalization in my database - Whether my SMTP config is enforcing case sensitivity when it shouldn't - How to test if a recipient's server is case sensitive Give me: 1. Whether case sensitivity is likely the real culprit (or if I should look elsewhere) 2. How to test this specifically for my setup 3. What to fix if it is the issue 4. When to just leave it alone

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