Why is Apple Mail showing the email address instead of the name and how to fix?
Published 2 Aug 2025
Updated 24 Oct 2026
12 min read
Summarize with

Updated on 24 Oct 2026: We clarified Smart Addresses behavior and added iPhone and iPad steps for correcting sender names.
Apple Mail shows the email address instead of the sender name when the message has no usable display name, or when its Contacts data or display settings change what you see. On Mac, turning off Use Smart Addresses normally shows the name and address together in message address fields; it does not necessarily remove the sender name from the inbox list. Other causes include malformed From headers, a saved contact with the wrong name, or an outbound account or alias setting.
Start with the raw message because it separates a sending problem from a local display problem. If the delivered From header contains the right name and valid formatting, investigate Apple Mail's settings and contact data. If the name is missing or incorrect in that header, correct the sender configuration. A saved contact can supply a name locally, but it does not change what the sender transmitted.
- Fast answer: on Mac, choose View > Message > Raw Source and inspect the From line, including the display name and encoding.
- Display setting: choose Mail > Settings > Viewing and select Use Smart Addresses to show recognized names without their addresses in message address fields.
- Local fix: correct the matching Contacts card and remove an incorrect Previous Recipients entry.
- Sender fix: set the friendly From name in the sending platform, alias, or account settings.
- Authentication check: investigate SPF, DKIM, or DMARC if there is also an authentication concern. These checks do not set the displayed name.
Start with the raw From header
In Apple Mail on Mac, open the affected message and choose View > Message > Raw Source. Find the top-level From header in the message header area, before the blank line that starts the body. It shows the sender name as delivered to that mailbox, rather than a name substituted from Contacts. An intermediary can rewrite headers, so compare the original sending path if delivered copies differ.
Good raw From headertext
From: "Target Support" <targetinfo@example.com> To: customer@example.net Subject: Account update Date: Fri, 15 Mar 2024 05:30:43 -0600
If Apple Mail shows targetinfo@example.com but the raw header contains a correctly formatted Target Support name, start with the recipient device. If the raw header contains only the address, the sender supplied no friendly name. That is valid email syntax, but a recipient without a matching contact has no sender-supplied name to display.
What to check in raw source
- From should include the intended display name before the angle-bracketed address when the sender wants to supply a name.
- If MIME encoded-word formatting is used, check that its declared charset and encoded text are valid.
- The address should be the intended sender identity, rather than an old alias or test mailbox.
- Duplicate top-level From headers point to a message construction problem that needs sender-side repair.
Character encoding matters for display names too. Non-ASCII names can use MIME encoded-word formatting, or UTF-8 headers when the sending path supports internationalized email. RFC 6532 permits UTF-8 in header fields, so readable non-ASCII text is not automatically an error. Invalid encoding can produce a broken name or an address-only fallback.
For a sending-path check, send a real message to Suped's email tester and compare the received headers and authentication results with the affected Apple Mail copy. The test checks the delivered message; it cannot inspect a recipient's local Contacts data.
Email tester
Send a real email to this address. Suped shows a results button when the test is ready.
?/43tests passed
This test also prevents a common mistake: changing DNS records when the only problem is a stale contact entry on one Mac. DNS affects authentication and delivery trust. It does not force Apple Mail to ignore a local contact name.
Check the Smart Addresses setting
On Mac, Apple Mail's Use Smart Addresses preference controls whether recognized people appear by name alone or with their email address in message address fields. Choose Mail > Settings > Viewing, then select Use Smart Addresses when you want the name without the address. Mail can look up recognized people in Contacts, Previous Recipients, or connected directories.
Apple's Viewing settings guidance documents this option. The inbox message list has its own presentation, so this setting is not a universal fix for an address appearing there. Check an opened message and its raw From header separately.
- Open Mail > Settings > Viewing on the affected Mac. Older macOS versions call Settings Preferences.
- Select Use Smart Addresses, then reopen the affected message and check its address fields.
- If the address remains, verify that Contacts or Previous Recipients has a name for that exact address.
- If the raw From header lacks the intended display name, ask the sender to add it. This preference does not add a name to the transmitted message.
Fix sender names in Mail on Mac

Apple Mail Account Information settings for checking sender names, aliases, and email addresses.
When the raw From header is correct, treat Apple Mail as the display layer. Contacts, Previous Recipients, and connected directories can affect the names Mail recognizes. That is why one colleague can see the proper brand name while another sees an address or an unexpected contact name. Your own account aliases affect outgoing messages and need a separate sender-side check.
Apple's Account Information settings page shows the path Mail > Settings > Accounts > Account Information. Use its Email Address menu to check the name on your own outgoing account or alias. The Description field labels the account inside Mail; changing it does not set the name recipients see.
- Open Contacts and search the exact email address that Apple Mail is displaying.
- Correct the name on the matching card. Check duplicate cards and the account that stores them before merging entries.
- In Mail, choose Window > Previous Recipients, find the exact address, and remove the incorrect entry with Remove From List. Then quit and reopen Mail.
- If the wrong name returns, correct the contact in its source account or shared directory and let the change sync to the affected devices.
The same cleanup also applies when Apple Mail fills the wrong name in the To field while composing. Apple documents Previous Recipients as an address-completion list. Removing an entry does not edit a Contacts card, and correcting autocomplete does not prove that an incoming From header is wrong.
When several colleagues see it overnight
If several Apple Mail users suddenly see the same wrong display name, compare the raw From header on an affected message first. A correctly formatted raw name points toward a shared contact source or client behavior. A wrong raw name points toward the sender configuration or a header rewrite during delivery. Do not change SPF, DKIM, or DMARC to repair a display name.
Fix sender names on iPhone and iPad
The Mac Use Smart Addresses preference is not an iPhone or iPad Mail setting. If a received message shows only an email address, check the contact for that exact address on the affected device. Changing your own Mail account Name field changes your outgoing identity, not the names on incoming messages.
- Open Contacts, tap Lists, and search All Contacts for the exact sender address. Check the relevant account list if there are duplicate or missing cards.
- Edit the matching contact to add or correct the name, or create a contact with the sender's exact address if you want a local name for an address-only sender.
- Go to Settings > Apps > Contacts > Contacts Accounts, select the account that stores the contact, and confirm Contacts is enabled. For iCloud contacts, also check Settings > [your name] > iCloud > See All > Contacts.
- Refresh Contacts by swiping down on its list, reopen Mail, and test with a newly received message. If the contact still does not appear, check that the devices use the same Apple Account for iCloud contacts.
Apple documents these account controls in its contact settings guidance and the refresh steps in its iCloud sync guidance. Settings > Apps > Contacts > Short Name changes how existing contact names appear in Mail; it does not add a missing sender name to a message. On iOS 17 and earlier, Contacts settings are directly under Settings.
For the full From header, open the same original message in Mail on a Mac or in your provider's webmail source view. A forwarded copy has a new outer From header, so use the original message when deciding whether the sender supplied a name.
Fix the sender name at the source
When the raw From header is wrong, the sender system owns the fix. The setting is usually called From name, sender name, friendly name, profile name, alias name, or display name. In a company setup, check the mailbox alias, the sending platform, the CRM integration, and any template-level sender override.
Raw header is correct
- Owner: recipient-side Apple Mail, Contacts, or synced address data.
- Fix: correct the local contact and clear incorrect recipient history.
- Check: compare the affected device with a device that has no matching contact or recipient history.
Raw header is wrong
- Owner: the mailbox, alias, sending platform, or template. Check an intermediary if delivered copies differ.
- Fix: set the proper friendly name before the message is sent.
- Proof: the next delivered raw From header contains the expected name.
Sender name examplestext
With a display name: From: "Target Support" <targetinfo@example.com> Without a display name (valid, but no name supplied): From: <targetinfo@example.com> Address repeated as the display name: From: "targetinfo@example.com" <targetinfo@example.com>
In Mail on Mac, check Mail > Settings > Accounts > Account Information > Email Address > Edit Email Addresses where available. On iPhone or iPad, open Settings > Apps > Mail > Mail Accounts, select the account, and check its Name field if exposed. If the field is unavailable or managed centrally, change the name through the provider or administrator. Confirm the intended account or alias in the From menu before sending.
Use the sending platform's name field or a mail library to handle quoting and character encoding. A comma in a display name needs correct quoting, and a malformed encoded name needs repair in the generated header. Changing the HTML body charset does not repair the From field. Retest the delivered EML after making the change.
Reply-To, Return-Path, and the envelope sender do not set the friendly From name. Apple Mail reads the visible From header and applies its local display rules. A deeper breakdown of sender name display is useful when only some recipients see the wrong name.
If the issue also appears in Gmail, compare the behavior with the Gmail friendly name case. Multiple clients showing an address makes the raw header comparison more useful; it does not by itself prove that the sender configuration is wrong.
Where authentication fits
SPF, DKIM, and DMARC do not choose the friendly From name. SPF checks sending-IP authorization for an envelope domain, while DKIM checks a domain signature. DMARC requires a passing SPF or DKIM result with the required relationship to the visible From domain. None of these checks verifies the human-readable display name or proves that a message is safe.
Suped DMARC dashboard showing email volume, authentication health, and source breakdown
Suped's DMARC reporting supports this separate authentication check. Its reports group authentication results by sending source so teams can compare reported traffic with their approved senders and investigate failures. Aggregate DMARC reports do not contain the sender display name or a recipient's Contacts data.
If there is also an authentication concern, use Suped's domain health check for a DNS check and a real-message test for the actual sending path. Suped's DMARC monitoring tracks reported sources and authentication results over time. Keep name-display testing in the affected mail client.
|
|
|
|---|---|---|
From | Sender-supplied display name and address | Set the display name |
Contacts | Local name lookup | Correct the matching contact |
SPF | Sending-IP authorization for the envelope sender domain | Fix the source or SPF record |
DKIM | Domain signature and integrity of signed content | Fix signing or the DKIM record |
DMARC | Passing SPF or DKIM with the required From domain match | Fix authentication and its domain match |
Use this table to decide whether the issue is display, sending, or authentication.
If DKIM is failing, run a focused DKIM check and verify the signature on a newly delivered message after changing signing or DNS. A passing DKIM result does not force Apple Mail to show a particular name.
How to test the fix
After changing the sender name or cleaning Apple Mail contact data, test with a fresh message. Do not forward an old message because forwarding creates a new outer From header. Send a new message from the same production path that caused the problem, and check the individual message rather than an older conversation entry.
Simple test matrixtext
1. Send to Apple Mail without the affected contact or recipient history 2. Send to an existing affected Apple Mail user, including iPhone or iPad if relevant 3. Send to a non-Apple mail client 4. Compare raw From headers in the delivered original messages 5. Check SPF, DKIM, and DMARC separately if authentication is also in question
If the delivered headers have the intended name but only the affected device shows an address, continue with that device's contact data and display behavior. A newly created Mail profile can still receive the same synced contacts, so it is not automatically an independent test. If new messages still lack the intended name in raw source, revisit the actual production sending path.
Where to investigate
Use raw From evidence, rather than the number of affected users, to choose the next action.
Local evidence
One device
The raw From name is correct, but one device shows the wrong name.
Shared display evidence
Several devices
The raw From name and formatting are correct on affected copies. Check shared contacts and client behavior.
Sender-side evidence
Raw From wrong
New delivered copies contain a missing or incorrect display name in the raw From header.
Choose the fix using the header
Read raw source first, then choose the relevant fix: correct recipient contact data when the header is valid, or repair the sending path when the name is missing or wrong. Confirm the result in a newly delivered message on the affected device.

