Troubleshooting Email Not Sending
When your emails fail to send, it disrupts your business communications. This guide provides a systematic approach to diagnosing and resolving common outgoing email problems. Work through each section in order — most issues are resolved in the first few steps.
Quick Diagnosis Checklist
Before diving into detailed troubleshooting, check these common causes:
- Is your internet connection working? (Try loading a website)
- Are you using the correct SMTP settings? (Server, port, username, password)
- Has your password changed recently?
- Is your mailbox or hosting account suspended?
- Are you getting a specific error message? (Check below for your error)
Step 1: Verify Your SMTP Settings
Incorrect SMTP settings are the most common reason emails fail to send. Verify these settings in your email client:
| Setting | Value |
|---|---|
| SMTP Server | mail.yourdomain.com or your server hostname |
| Port | 465 (SSL) or 587 (STARTTLS) |
| Encryption | SSL/TLS (port 465) or STARTTLS (port 587) |
| Authentication | Required — use your full email address |
| Username | Your full email address (e.g., [email protected]) |
| Password | Your email account password |
Important: Port
25is blocked on most networks and hosting providers. Always use port465or587.
Verifying in Popular Email Clients
Outlook:
- Go to File → Account Settings → Account Settings
- Select your account → Change
- Click More Settings → Outgoing Server tab
- Ensure My outgoing server (SMTP) requires authentication is checked
- Under Advanced tab, verify port and encryption
Thunderbird:
- Go to Account Settings → Outgoing Server (SMTP)
- Select your server → Edit
- Verify the server, port, and security settings
Apple Mail:
- Go to Mail → Preferences → Accounts
- Select your account → Server Settings
- Under Outgoing Mail Server (SMTP), verify settings
Step 2: Test Your Login Credentials
A failed authentication will prevent sending. Test your credentials:
- Log in to webmail at
https://yourdomain.com/webmailorhttps://mail.yourdomain.com - If login fails, your password may be wrong or your account may be locked
- Reset your password through cPanel: Email → Email Accounts → Manage → Change Password
Tip: If you recently changed your password, update it in all devices and email clients. A device with the old password will cause repeated failed login attempts, which can trigger an IP block.
Step 3: Check for IP Blocks
If you entered the wrong password multiple times, your IP address may have been temporarily blocked by the server's firewall (CSF/LFD or Imunify360).
Signs of an IP block:
- Webmail loads but email client cannot connect
- Connection timeout errors
- "Cannot connect to server" messages
Solution:
- Find your public IP at https://whatismyip.com
- Contact {{SUPPORT_EMAIL}} and provide your IP address
- We will check the firewall and unblock your IP if needed
Step 4: Check Your Sending Limits
{{COMPANY_NAME}} hosting plans have per-hour sending limits to prevent spam abuse:
| Plan Type | Approximate Limit |
|---|---|
| Shared Hosting | 100–500 emails/hour |
| Business Hosting | 500–1000 emails/hour |
| Dedicated | Configurable |
If you hit the sending limit, emails will queue and be delivered in the next hour. The error message typically says:
- "Too many connections"
- "Rate limit exceeded"
- "Sending quota exceeded"
Solution: Wait for the next hour or contact support to adjust your limit if your business requires higher volume.
Step 5: Check for Bounced Emails
If the email appears to send but the recipient never receives it, check for bounce-back messages in your inbox. Common bounce errors:
| Error Code | Meaning | Solution |
|---|---|---|
550 5.1.1 | Recipient address does not exist | Verify the recipient's email address |
550 5.7.1 | Rejected — your IP is blacklisted | See blacklist removal guide |
552 5.2.2 | Recipient's mailbox is full | Ask the recipient to clear their mailbox |
421 4.7.0 | Temporary rejection — try later | Wait and resend; the recipient's server is throttling |
554 5.7.1 | TLS required | Enable SSL/TLS encryption in your email client |
553 5.1.3 | Invalid address syntax | Check for typos in the email address |
Step 6: Check DNS Records
Missing or misconfigured DNS records can cause outgoing email to be rejected by receiving servers:
- SPF record — Authorizes your server to send email for your domain
- DKIM record — Adds a digital signature to verify message integrity
- rDNS (PTR record) — Maps your server IP to a hostname (managed by your hosting provider)
Use MXToolbox to check: https://mxtoolbox.com/diagnostic.aspx
Step 7: Test with Webmail
To determine if the problem is with your email client or the server:
- Log in to webmail at
https://yourdomain.com/webmail - Compose and send a test email to a Gmail or Outlook address
- If webmail works but your email client does not — the issue is with your client settings
- If webmail also fails — the issue is server-side; contact support
Step 8: Check Server Status
Occasionally, the mail server itself may have an issue:
- Check the {{COMPANY_NAME}} status page for any reported outages
- If no outage is reported but the issue persists, contact support with:
- Your domain name
- The recipient email address
- The exact error message (screenshot if possible)
- The date and time of the failed attempt
Common Error Messages and Solutions
| Error Message | Cause | Solution |
|---|---|---|
| "Connection timed out" | Firewall block or wrong port | Check port settings; whitelist your IP |
| "Authentication failed" | Wrong credentials | Reset password; update all devices |
| "Relay access denied" | Not authenticated or wrong server | Enable SMTP authentication; verify server |
| "Message rejected" | Content triggered spam filter | Remove suspicious links, attachments, or formatting |
| "Mailbox full" | Your own mailbox is full | Delete old emails or increase quota |
Related Articles
- Troubleshooting Email Not Receiving
- What to Do If Your Email Is Blacklisted
- Understanding SPF, DKIM, and DMARC Records
Still unable to send email? Contact our support team at {{SUPPORT_URL}} or email {{SUPPORT_EMAIL}} with your domain name, the error message, and the recipient address. We will investigate and resolve the issue promptly.