Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


For email not syncing on your phone or computer, start by comparing the mail app with the provider's webmail. If a message exists on the website but not on one device, the mailbox is intact and the problem is probably the app, account connection, or device. If the website is also missing the message, investigate the sender, mailbox rules, storage, or provider instead of repeatedly resetting the device.
Key Takeaways
- Treat webmail as the server-side reference before changing an app.
- Separate sending, receiving, folders, accounts, devices, and networks.
- Check time, free storage, sync frequency, background activity, and account type.
- Preserve messages and drafts before removing an account or clearing app data.
- Escalate with timestamps and test results instead of a vague “mail is broken” report.
For a reusable troubleshooting order, start with the device and app troubleshooting guide. The method below narrows one mail path without mixing it with calendar, contact, cloud-file, spam, or phishing problems.
Open the provider's official webmail site in a browser and sign in by typing the address yourself or using a trusted bookmark. Do not follow an unexpected sign-in link from a message. Check the same mailbox, folder, and conversation that appears stale in the app.
Create a harmless test message with a unique subject such as “sync check 14:35.” Send it from another trusted account to the affected address, then reply from webmail. Record whether each message appears in webmail and whether sending succeeds. This creates a server reference without exposing passwords, verification codes, customer data, or confidential attachments.
| Observation | Most useful next branch |
|---|---|
| Webmail is current; one app is stale | App sync, account authorization, background activity, or local storage |
| Webmail and every app are stale | Provider status, mailbox quota, rules, sender delivery, or administrator |
| Receiving works but sending fails | Outgoing account, authentication, provider restriction, or attachment |
| Sending works but receiving fails | Folder rules, blocked sender, quota, fetch schedule, or provider delivery |
| Only one folder is stale | Folder subscription, visibility, rule, or account-type limitation |
Apple recommends checking the provider for an outage and verifying the account password when Mail cannot receive messages. It also warns users to confirm that mail exists on the provider's website or elsewhere before deleting an account from a device.[1] Google similarly suggests comparing Gmail on a computer and checking whether the account itself can load current mail before treating the Android app as the only source of truth.[2]
If webmail is current, test the phone on its normal Wi-Fi and then on a permitted mobile-data connection. A result that changes with the connection points to a local network or data-use policy; a result that stays the same points back to the account or app. Do not disable security controls broadly—one short comparison is enough.
Open the phone's account or mail settings and confirm that the affected account is enabled for Mail. Then check whether the app is allowed to use mobile data, refresh in the background, and run without an extreme battery-saving restriction. Menus vary by operating-system version and manufacturer, so follow the current device help rather than a screenshot from an old guide.
Review the sync schedule. Push can deliver changes when the server supports it, while Fetch checks on an interval and manual mode may wait until the app opens. Apple documents Push and Fetch as separate choices, says an account falls back to Fetch when Push is unavailable, and notes that background fetching may run only while the device is charging and on Wi-Fi.[1] A ten-minute delay can therefore be a schedule result, while a mailbox that never updates after a manual refresh needs a different branch.
Check free device storage and mailbox quota. A phone that cannot write its local mail index or download attachments may show old headers, repeated download errors, or messages without content. Free a modest amount of space using known files; do not install a “cleaner” or delete the mail app's data as the first experiment.
Start with the same browser comparison, then close and reopen only the mail application. Confirm that the computer's date, time, and time zone are correct, because authentication tokens and certificate checks depend on time. If other account-backed features are also failing, the wrong computer date and time guide provides a separate clock-focused path.
Look for an Offline, Work Offline, Paused, or disconnected status in the app. Confirm that the correct profile and account are selected, especially after a migration or work/personal profile change. If a single folder is missing, check whether that folder is subscribed, hidden, or excluded from the local synchronization window.
On Outlook for Windows, Microsoft provides a profile Repair flow for connection errors and recommends restarting Outlook after the wizard. It also recommends applying current Office updates.[3] Repair is narrower than deleting a profile: use it only after the server copy is verified, and record any error text before starting.
Security software, a managed proxy, or an organization policy can affect a desktop mail client while webmail still works. Do not permanently disable a firewall, endpoint agent, certificate check, or device-management profile. If a brief administrator-approved comparison identifies a managed control, give the evidence to IT rather than bypassing it.
Identify the account type before changing server fields. IMAP and Exchange normally synchronize server folders and state; POP may download mail with different retention behavior and is not a full multi-device synchronization model. A local-only folder, archive, or draft cannot be expected to appear on another device unless the app saves it on the server.
Check the displayed account address and provider, not only the friendly account name. After a password change, the app may need a fresh sign-in or provider authorization. Complete that flow only in the operating system, mail app, or provider page you opened yourself. Repeated password prompts can also indicate an expired organizational token, revoked app access, or a provider-specific app-password requirement.
Do not copy incoming and outgoing server names from a random forum. Use the provider's current documentation or automatic account setup. A typo in a hostname, port, encryption mode, username, or authentication method can make receiving and sending fail differently. Capture the current non-secret settings before changing them so that one experiment does not erase the starting point.
Rules and aliases can create misleading symptoms. Check whether a server rule moved the test message to Archive, Spam, Trash, or a custom folder. Confirm whether the address is an alias, shared mailbox, delegated mailbox, or group whose delivery rules differ from the primary inbox. This article does not decide whether a suspicious message is legitimate; use dedicated security guidance for that question.
Add the same address on both devices through the provider's own app or the automatic account setup, and pick IMAP or Exchange when the app offers an account type. Those types keep folders, read status, moves, and deletions on the server, so each device mirrors one mailbox instead of keeping its own copy.
Then check three settings that often break the match. Sent mail and drafts should save to server folders, not to a folder stored only on the device. Deleted messages should go to the server Trash. If one device still uses POP, switch it to IMAP when the provider supports it, but back up any mail that exists only on that device first.
Use a reversible sequence and stop when the mailbox becomes current:
Google places clearing Gmail storage after update, restart, connectivity, sync, account, and device-storage checks, and warns that drafts, signatures, ringtone choices, and other settings may be erased.[2] Treat any clear-data action as destructive. If unsent drafts or local folders do not appear in webmail, export or copy them before continuing.
For a work or school mailbox, stop before removing management profiles, certificates, or enrollment. An administrator can check licensing, account state, conditional-access results, server logs, and organization-wide incidents that a local user cannot see.
Escalate when webmail also fails, the mailbox is over quota, authentication is rejected on every trusted client, multiple users are affected, or a provider status page reports an incident. Provide the provider, account type, approximate failure time and time zone, send/receive direction, affected folders, device and app versions, and a sanitized error message.
Avoid sending a password, recovery code, session token, full message content, or sensitive attachment in a support ticket. A message ID or delivery trace can help an administrator, but share it only through the organization's approved support channel.
If webmail is current and only one device remains stale after safe repair, the remaining problem is local to that app, profile, storage, or policy. If no client—including webmail—has the message, changing local sync settings cannot create server data that never arrived.
The server copy exists, so focus on the affected app's refresh state, authorization, folder visibility, background activity, and local storage. A server outage is less likely when webmail is current.
Incoming and outgoing mail can use different authorization or server paths. Test a small message without an attachment, record the error, and verify the provider's outgoing-account guidance rather than changing unrelated inbox settings.
The folder may be hidden, unsubscribed, local-only, or excluded by a synchronization window. Confirm the exact account and compare the same folder in webmail before changing the whole application.
Yes. Push depends on provider support, while Fetch runs on a schedule and manual fetching may wait for the app to open. A predictable delay is different from a mailbox that never refreshes.
Yes. The device or app may be unable to update its local index or download message content. Check both device storage and the provider's mailbox quota.
Only after simpler checks and after confirming that important mail, drafts, and folders exist on the server or in a backup. Removing an account can delete local-only data and settings.
Not necessarily. POP is commonly designed around downloading messages, while IMAP and Exchange provide broader server-state synchronization. Confirm the configured account type and provider behavior.
Contact them when webmail also fails, authentication is rejected everywhere, several users are affected, or a managed policy or server-side trace is needed. Include timestamps and sanitized errors, not credentials.
Use webmail to establish what the server actually holds, and preserve local messages and drafts before reconnecting the account. A VPN cannot create a message absent from the server or recover a deleted local draft; those are data-state problems, not proof of a connection fault.
Sources checked 4 October 2026.
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.





