Email addresses are not case sensitive. dean@scaledmail.com, DEAN@SCALEDMAIL.COM, and Dean@ScaledMail.Com all deliver to the same inbox. You can type an email address in any combination of upper and lowercase and it will land correctly on every major mail provider.
That's the practical answer. The technical answer has a footnote worth knowing, but it changes nothing about how you should actually be thinking about your email setup.
What the Email Spec Actually Says
RFC 5321, the specification that governs how email works, says that the local part of an email address (everything before the @) is technically case sensitive. The domain part (everything after the @) has always been case insensitive, since DNS itself is case insensitive.
So by the letter of the spec, Dean@scaledmail.com and dean@scaledmail.com could be two different addresses. A mail server would be within its rights to treat them as distinct mailboxes.
In practice, no major mail provider does this. Gmail, Google Workspace, Microsoft 365, Outlook.com, Yahoo Mail, and every other provider you're likely to encounter treats the local part as case insensitive. They normalize everything to lowercase internally before routing. The spec is technically permissive, but the industry settled on case insensitivity years ago.
How the Big Providers Handle It
Gmail and Google Workspace
Gmail treats the local part as completely case insensitive and also ignores dots. dean.fiacco@gmail.com, deanfiacco@gmail.com, and Dean.Fiacco@Gmail.com all route to the same inbox. Google normalizes everything before delivery. This is true for both consumer Gmail and Google Workspace business accounts.
Microsoft 365 and Outlook
Microsoft 365 treats the local part as case insensitive. Dean@company.com and dean@company.com go to the same mailbox. Unlike Gmail, Microsoft does treat dots as significant in some configurations, but case is always normalized.
Yahoo Mail
Yahoo Mail normalizes the local part to lowercase. Any case variation reaches the same inbox.
Other providers
Virtually every consumer and business email provider follows the same pattern: case insensitive in practice regardless of what RFC 5321 technically permits.
The Edge Cases Worth Knowing
There are scenarios where case sensitivity can technically matter:
- Legacy mail servers: Very old or highly customized mail server software may enforce case sensitivity on the local part. This is rare and getting rarer. If you're sending to an organization running genuinely ancient infrastructure, you might theoretically hit this. For any volume of modern cold outreach or marketing sending, this will not be a factor.
- Self-hosted mail servers: Some organizations running their own mail servers with custom configurations could enforce case sensitivity if they specifically configured it. This would be a deliberate choice, not a default behavior, and is uncommon.
- Case-sensitive subaddressing: Some providers support subaddressing (also called plus addressing or tagged addresses):
dean+newsletter@scaledmail.com. The tag portion after the plus can sometimes be case sensitive depending on implementation. The base address itself is still case insensitive.
For practical purposes: send to email addresses in whatever case they appear. The address will land correctly.
What Actually Determines Whether Your Email Lands
If you're asking about email case sensitivity, you're probably troubleshooting deliverability. The variables that actually determine inbox placement have nothing to do with capitalization.
Domain reputation
Your domain reputation is the primary signal mail providers use to evaluate your email before they ever read the content. Every bounce, spam complaint, and unsubscribe affects it. A domain with good reputation lands in the inbox. A domain with poor reputation filters to spam regardless of what you're sending or how you're capitalizing the addresses.
For cold outreach, this is why secondary sending domains matter. Run outreach off your primary business domain and any reputation damage from campaigns bleeds into your transactional mail, your client correspondence, your invoices. Keep cold email sending on dedicated domains with isolated reputations.
IP reputation
Your sending IP carries its own reputation score separate from your domain. On shared IPs, other senders affect you. On dedicated IPs, you control your own history but start with no established trust. Spam filter services like Talos and SenderScore aggregate complaint and bounce data at the IP level. A flagged IP makes deliverability hard regardless of how clean your domain is.
Email warmup
New sending domains and inboxes have no reputation. Mail providers treat zero-history senders with suspicion by default. Email warmup builds that history gradually: low volumes at first, real engagement signals, increasing send counts over 2–4 weeks before you touch any real campaign volume. Skip warmup and you're sending from an inbox that mail providers have no reason to trust.
This is one of the most commonly skipped steps in cold email setup and one of the most expensive mistakes to make. New domains that go straight into high-volume sending get flagged fast, sometimes within days.
Authentication: SPF, DKIM, and DMARC
Authentication records tell receiving mail servers that your sending infrastructure is legitimate. SPF lists the servers authorized to send from your domain. DKIM cryptographically signs your messages so receiving servers can verify they haven't been tampered with. DMARC tells receiving servers what to do when SPF or DKIM checks fail.
Missing or misconfigured authentication is one of the fastest ways to tank email deliverability. Mail providers are tightening requirements every year. Google and Microsoft now require proper authentication for bulk senders, and that threshold keeps dropping. If your DNS records aren't set correctly, your emails fail at the authentication layer before a spam filter ever evaluates the content.
Sender reputation
Your sender reputation is the composite score that mail providers assign to your sending domain and IP based on observed behavior over time. High engagement (opens, replies, forwards) builds it. Bounces, spam complaints, and sudden volume spikes damage it. Reputation affects where you land in the inbox hierarchy (primary, promotions, spam) across every recipient on that provider.
List quality and bounce rates
Hard bounces from invalid addresses signal to mail providers that you're sending to unverified lists. Keep bounce rates below 2% — ideally below 1% for cold outreach. Email verification before sending is standard practice for any serious outreach operation. Clay, BounceBan, Scrubby, and similar tools let you validate lists before they hit your sending infrastructure.
The Actual Checklist Before Your First Send
If you're setting up cold email infrastructure or troubleshooting deliverability problems, work through this in order:
- Secondary sending domains configured (never your primary business domain)
- Google Workspace or Microsoft 365 inboxes on those domains (real provider accounts, not cheap SMTP relays)
- SPF record set correctly for each sending domain
- DKIM configured and key published in DNS
- DMARC policy set (start with
p=nonefor monitoring, move top=quarantineonce you've confirmed alignment) - Email warmup completed before campaign sending begins
- List verified before importing to your sequencer
- Bounce rate monitoring active from day one
Email case sensitivity is nowhere on this list because it has no meaningful effect on any of these outcomes.
At ScaledMail
The infrastructure questions that actually affect whether cold email campaigns succeed are the ones most teams underinvest in: domain configuration, authentication records, warmup, and ongoing monitoring. At ScaledMail, we provision Google Workspace and Microsoft 365 inboxes on dedicated sending domains with SPF, DKIM, and DMARC configured correctly from day one, warmup built into the setup process, and continuous monitoring so problems get flagged before they turn into burned domains.
If you've been sending and your deliverability is poor, start with the checklist above. The answer is almost never the case of the letters in an email address.
