Email Errors¶
Use this page to troubleshoot email errors. Save the full error message, bounceback, headers, or mailbox details before contacting Fused support.
Quick Reference¶
| Symptom or error | Usually means | Start here |
|---|---|---|
550 No Such User Here |
The recipient address does not exist on the destination server. | Check spelling in the To, Cc, and Bcc fields. |
Mailbox full or quota reached |
The recipient mailbox is out of space. | Increase quota if it is your mailbox, or contact the recipient another way. |
No Such Domain |
The recipient domain is misspelled or no longer resolves. | Check the domain spelling and try again. |
x.x.x.x is not allowed to send mail from example.com |
SPF does not authorize the sending server. | Review SPF or send the bounce to Fused. |
554 Denied or spam rejection |
The receiving server rejected the message. | Save the bounceback and message headers. |
| Cannot send mail | SMTP authentication, port, password, or connection settings may be wrong. | Check email settings. |
| Cannot receive mail | Password, quota, DNS, client settings, or filtering may be involved. | Check webmail, quota, and client settings. |
| Old messages download again | Mailbox cache or quota issue. | Check mailbox quota. |
If A Message Bounced¶
- Read the bounce message for the recipient address and error code.
- Confirm the recipient address is spelled correctly.
- Check whether the error mentions quota, domain, SPF, reputation, or spam.
- Save the full bounce message.
- If the error is not obvious, send the bounce to Fused support.
If Sending Fails¶
Check:
- Username is the full email address.
- Password is current.
- SMTP authentication is enabled.
- Outgoing server matches the mailbox settings.
- Outgoing port and SSL setting match the mailbox settings.
- The device is not stuck on an old saved password.
If Receiving Fails¶
Check:
- The mailbox can sign in through webmail.
- The mailbox is not over quota.
- The mail app uses the correct incoming server settings.
- Filters or forwarding rules are not moving messages unexpectedly.
- DNS for the domain still points mail to the right provider.
If webmail works but the mail app does not, the issue is usually local to the device or client configuration.
If Support Needs Headers¶
Full message headers show the path an email took and are useful for tracing delivery problems, spam filtering, and authentication failures.
Related Guides¶
-
Bouncebacks
Decode common delivery failures and bounce messages.
-
Common problems
Review quota issues, spam filtering, sending, and receiving problems.
-
Message headers
Find full headers for support and delivery tracing.
-
Email settings
Confirm IMAP, SMTP, SSL, and device settings.