What is case sensitivity in local parts?

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

Technically, yes. RFC 5322 (the standard that defines email address syntax) says the local part (the bit before the @) can be case sensitive. That means Captain@tidalmail.com and captain@tidalmail.com could theoretically point to different mailboxes.

So In practice? No major provider enforces this. Gmail, Outlook, Yahoo Mail, and every other inbox you've heard of treat email addresses as case insensitive. They follow Postel's Law (be liberal in what you accept) to avoid confusing users. If someone types their address with random capitals at signup, it still works.

Why it matters for senders: you don't need to worry about case when validating addresses or matching them in your database. Normalize everything to lowercase for storage and comparison, and you'll never have a problem. If you're building a custom mail server, follow the crowd and treat local parts as case insensitive. Going strict-RFC-compliant here just creates user frustration for no benefit.

The one edge case: some legacy corporate mail systems or custom SMTP servers might enforce case sensitivity. If you're sending B2B and a delivery fails with a "user unknown" bounce, try the exact case they provided at signup. It's rare, but it happens. Bottom line: the spec says case matters, real life says it doesn't. Store addresses in lowercase, send to whatever case your subscriber gave you, and you're covered. For more on what makes an address valid (or not), check out what counts as an invalid address.

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

Ask Claude about your address storage →

I read this on the Email Almanac about case sensitivity in email addresses: "Technically, RFC 5322 says the local part (before the @) can be case sensitive, so Captain@tidalmail.com and captain@tidalmail.com could be different mailboxes. In practice, no major provider enforces this. Gmail, Outlook, Yahoo, and others treat addresses as case insensitive to avoid user confusion." Help me apply this to my situation: 1. Email storage setup: Should I store subscriber addresses in lowercase, keep original case, or both? 2. Address matching: How should I compare addresses when checking for duplicates or unsubscribes? 3. Validation logic: Should my signup form force lowercase, accept any case, or warn users? 4. Edge cases: Are there any industries or mail systems where case sensitivity actually matters? --- My context: - ESP/platform: e.g. Mailchimp, custom Rails app, WordPress - Database: e.g. PostgreSQL, MySQL, spreadsheet - List size: e.g. 5,000 subscribers - Audience type: B2C newsletter / B2B SaaS / ecommerce - Current issue: [e.g. duplicate signups with different cases, validation rejecting mixed-case addresses]

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