How to Troubleshoot Email Delivery Problems and Rejected Messages Print

  • email delivery, email blacklist, email not sending, spam folder, DKIM, email not receiving, Microsoft Outlook, lagrange point media, cpanel email, Gmail, rejected email, SMTP errors, DMARC, Hotmail, email deliverability, email bounce, SPF
  • 0

How to Troubleshoot Email Delivery Problems and Rejected Messages

Email problems can interrupt business communications, prevent customers from contacting you, and cause important notifications to go missing.

Sometimes an email account stops receiving messages. Other times, outgoing messages are rejected, delayed, or delivered to spam folders.

These problems can have different causes, including incorrect DNS records, mailbox configuration, email authentication, server reputation, or restrictions imposed by the recipient's email provider.

Lagrange Point Media (LPM) provides several tools through cPanel to help customers investigate email delivery issues.

This guide explains how to identify common email problems, interpret delivery errors, and determine what steps to take.

1. Identify the Type of Email Problem

Before changing any settings, determine exactly what is happening.

Common email problems include:

  • You cannot send email.

  • You cannot receive email.

  • Messages are being delivered to spam.

  • Emails are rejected by certain providers.

  • Messages are delayed.

  • Your email application cannot connect.

  • Website contact form notifications are missing.

  • You receive delivery failure or bounce messages.

Each problem requires a different troubleshooting approach.

Important: Avoid changing multiple email settings at once. Making unnecessary changes can create additional problems and make the original issue harder to identify.

2. Determine Where Your Email Is Hosted

Your website hosting provider and email provider do not have to be the same company.

For example, your website might be hosted with LPM while your email is handled by Microsoft 365 or Google Workspace.

If your email is hosted through cPanel, you can investigate mailbox settings and delivery information through your LPM hosting account.

If your email is hosted externally, many of the relevant settings and diagnostic tools will be located with that provider.

To identify your email provider, review your domain's MX records.

MX records identify the servers designated to receive email for your domain.

Important: Do not assume that your email is hosted by LPM simply because your website is hosted with LPM.

3. Check Whether Webmail Works

If you use a cPanel-hosted mailbox, webmail is a useful starting point.

To test your mailbox:

  1. Sign in to the LPM Client Portal.

  2. Navigate to Services > My Services.

  3. Select your active hosting service.

  4. Open cPanel.

  5. Select Email Accounts.

  6. Locate your mailbox.

  7. Click Check Email.

  8. Open the available webmail application.

Try sending a test message to an external email address.

Then send a message from that external address back to your mailbox.

If webmail works but Outlook or your phone does not, the problem may involve your email application's configuration.

If webmail also fails, investigate the mailbox or email service itself.

4. Troubleshooting Email That Won't Send

If you cannot send email, begin with the following checks:

  1. Confirm that your mailbox password is correct.

  2. Verify that your email application uses the correct outgoing SMTP server.

  3. Check the SMTP port and encryption settings.

  4. Confirm that SMTP authentication is enabled.

  5. Test sending through webmail.

  6. Review any error messages.

  7. Determine whether the problem affects all recipients or only certain addresses.

For cPanel-hosted email, you can find the appropriate connection settings under:

Email Accounts > Connect Devices

Tip: If email sends successfully through webmail but fails through your email application, check the application's SMTP settings before modifying DNS records.

5. Troubleshooting Email That Won't Arrive

If you are not receiving messages:

  1. Confirm that the mailbox exists.

  2. Check its storage usage.

  3. Review your spam or junk folder.

  4. Verify the domain's MX records.

  5. Review the Email Routing configuration.

  6. Check for email filters that may redirect or discard messages.

  7. Test delivery from another email provider.

If your mailbox has reached its storage limit, it may be unable to accept additional messages.

Important: Incorrect MX records or email routing settings can prevent incoming messages from reaching the intended email provider.

6. Using Track Delivery in cPanel

cPanel includes a tool called Track Delivery that can help investigate email delivery activity processed by the hosting server.

To access it:

  1. Open cPanel.

  2. Search for Track Delivery.

  3. Open the interface.

  4. Enter a recipient email address if you want to narrow the results.

  5. Run the report.

  6. Review the available delivery events.

Depending on the server configuration, you may see information about successful deliveries, failures, deferred messages, or other delivery events.

The detailed report can provide information about how the server handled a message.

Important: Track Delivery reports on mail activity handled by the cPanel server. It does not provide a complete history of messages processed entirely through external providers such as Microsoft 365 or Google Workspace.

7. Understanding Email Bounce Messages

A bounce message is a notification that an email could not be delivered.

Bounce messages may contain:

  • The recipient's address.

  • The destination mail server.

  • An SMTP error code.

  • A description of the failure.

  • Information about whether the failure is temporary or permanent.

For example, you might see an error beginning with:

550 5.7.1

The meaning depends on the complete message and the receiving provider.

Important: Never diagnose a delivery problem based only on a short error code. The full rejection text often identifies the actual reason.

8. Understanding Common SMTP Error Codes

SMTP error codes provide information about delivery problems.

Error General Meaning
421 Service temporarily unavailable
450 Requested action temporarily unavailable
451 Temporary processing failure
452 Insufficient system resources or another temporary condition
550 Requested action rejected or mailbox unavailable
551 User not local or forwarding-related issue
552 Storage limit exceeded or another size-related failure
553 Mailbox name or addressing problem
554 Transaction rejected

These are general interpretations. Providers may use the same primary code for different situations.

Codes beginning with 4 usually indicate temporary failures.

Codes beginning with 5 usually indicate permanent failures.

Important: Enhanced status codes and accompanying text provide more specific information than the three-digit SMTP code alone.

9. Understanding Temporary Delivery Failures

Temporary failures may occur because of:

  • A receiving server outage.

  • Rate limiting.

  • Temporary network problems.

  • Resource limitations.

  • Greylisting.

  • Temporary reputation restrictions.

A sending server may retry delivery automatically after a temporary failure.

However, retry behavior and expiration periods depend on the sending system.

Tip: If a message is delayed rather than permanently rejected, review its delivery status before repeatedly resending it.

10. Understanding Permanent Delivery Failures

Permanent failures generally indicate that the receiving system has rejected the message without requesting another attempt under the same conditions.

Possible causes include:

  • An invalid recipient address.

  • A nonexistent mailbox.

  • A blocked sending server.

  • Authentication or policy restrictions.

  • A message rejected as spam.

  • A prohibited attachment.

  • Recipient-specific restrictions.

The full bounce message should help identify which explanation applies.

Important: A permanent rejection may require correcting the underlying issue before sending the message again.

11. Troubleshooting Emails Going to Spam

If your messages are being delivered to spam folders, several factors may be involved.

Receiving providers evaluate:

  • SPF authentication.

  • DKIM signatures.

  • DMARC alignment.

  • Sending IP reputation.

  • Domain reputation.

  • Message content.

  • Sending frequency.

  • Spam complaints.

  • Recipient engagement.

Start by verifying your domain's email authentication.

Then review whether the problem affects one provider or multiple providers.

Important: Correct SPF, DKIM, and DMARC records improve authentication but do not guarantee inbox placement.

12. Checking SPF, DKIM, and DMARC

For cPanel-hosted email:

  1. Open cPanel.

  2. Search for Email Deliverability.

  3. Select your domain.

  4. Review the available SPF and DKIM information.

  5. Investigate any warnings.

You can also inspect DNS records through Zone Editor or your external DNS provider.

Remember:

SPF identifies authorized sending systems.

DKIM verifies cryptographic signatures.

DMARC evaluates authentication and alignment with the visible From domain.

Important: If you send email through an external service, your authentication records must reflect that service's requirements.

13. Understanding IP Reputation and Blocklists

Email providers maintain systems that evaluate the reputation of sending IP addresses.

A sending server may be blocked or restricted because of:

  • Previous spam activity.

  • Suspicious sending patterns.

  • Spam complaints.

  • Compromised accounts.

  • Activity associated with other senders using the same IP address.

  • Provider-specific reputation policies.

A message can pass SPF, DKIM, and DMARC and still be rejected because of its sending IP reputation.

Important: Changing SPF or DKIM records will not necessarily resolve an IP reputation or blocklist rejection.

The correct response depends on the receiving provider's rejection reason.

14. Troubleshooting Gmail Delivery Problems

If Gmail rejects or filters your messages:

  1. Review the complete bounce message.

  2. Check SPF, DKIM, and DMARC.

  3. Verify that the sending system is authorized.

  4. Review the sending server's reputation.

  5. Check for unusual sending activity.

  6. Review Google's published sender requirements.

Gmail applies different requirements depending on the sender's volume and circumstances.

Important: A message appearing in Gmail's spam folder is different from Gmail rejecting the message during SMTP delivery. The two situations may require different troubleshooting steps.

15. Troubleshooting Outlook, Hotmail, and Microsoft Email Delivery

Microsoft operates email services including Outlook.com and Hotmail.

Microsoft also provides business email services through Microsoft 365.

If a Microsoft destination rejects your message:

  1. Review the full rejection message.

  2. Identify the sending IP address.

  3. Check whether the rejection mentions reputation or blocking.

  4. Verify email authentication.

  5. Investigate unusual sending activity.

  6. Follow the appropriate Microsoft sender support or remediation process.

Some Microsoft rejection messages contain provider-specific codes identifying the type of restriction.

Important: If Microsoft blocks a sending IP address, correcting DNS authentication alone may not remove the block.

The sending provider may need to investigate the IP reputation and request remediation through the appropriate Microsoft process.

16. Understanding Shared Sending IP Addresses

Some hosting environments use shared IP addresses for outgoing email.

This means multiple domains or customers may send email through the same public IP address.

Receiving providers can evaluate that IP address's overall sending reputation.

As a result, reputation problems may affect multiple senders.

Important: A blocklist or reputation issue does not automatically mean your individual mailbox has been compromised or that you personally sent spam.

The sending infrastructure must be investigated to determine the cause.

17. Troubleshooting Website Contact Form Emails

WordPress websites commonly send automated notifications from:

  • Contact forms.

  • Appointment systems.

  • E-commerce applications.

  • Membership plugins.

  • Password reset functions.

If these messages are missing:

  1. Confirm that the form submission was recorded.

  2. Review the notification email settings.

  3. Verify the recipient address.

  4. Check the spam folder.

  5. Identify which service sends the email.

  6. Review the sending service's logs, if available.

  7. Check authentication and delivery errors.

Some websites send mail directly through the hosting server, while others use SMTP or an external email API.

Important: A successful form submission does not necessarily mean the notification email was delivered.

18. Understanding WordPress SMTP Plugins

SMTP plugins can help WordPress send messages through a configured email provider.

Depending on the plugin and service, delivery may use:

  • Authenticated SMTP.

  • Microsoft 365.

  • Google services.

  • A transactional email API.

  • Another supported provider.

The plugin must be configured with the correct account and sending method.

Important: An SMTP plugin does not automatically solve problems involving the recipient's spam filters, the sending provider's reputation, or incorrect DNS authentication.

19. Troubleshooting Email Authentication Failures

If your messages fail authentication:

  1. Identify the service that actually sent the message.

  2. Review its SPF requirements.

  3. Check whether DKIM signing is enabled.

  4. Verify the published DKIM records.

  5. Review DMARC alignment.

  6. Check for duplicate or malformed DNS records.

  7. Send a new test message.

  8. Inspect the authentication results.

Avoid making changes until you know which sending system is responsible.

Tip: Businesses using multiple email services should maintain a record of which systems are authorized to send messages using their domain.

20. Troubleshooting DNS-Related Email Problems

DNS configuration can affect both incoming and outgoing email.

Common problems include:

Incorrect MX Records

Incoming messages may be routed to the wrong provider.

Incorrect Email Routing

The hosting server may attempt local delivery when mail should be handled externally.

Missing SPF Records

Receiving systems may be unable to confirm the sending server's authorization.

Incorrect DKIM Records

Signature verification may fail.

Incorrect DMARC Policy

Legitimate messages may be affected by an enforcement policy when authentication alignment is not configured correctly.

Wrong DNS Provider

Changes may be made in a DNS zone that is not authoritative for the domain.

21. Checking DNS Records

You can inspect public DNS records using:

Google Admin Toolbox Dig

To check your configuration:

  1. Enter your domain name.

  2. Select the relevant DNS record type.

  3. Run the lookup.

  4. Compare the results with your provider's required settings.

Common records to review include:

  • MX

  • TXT

  • CNAME

  • A

  • NS

Important: DNS records should match the requirements of your actual email provider. Do not replace existing values with generic examples.

22. Checking for Compromised Email Accounts

Unexpected email activity can indicate unauthorized access.

Warning signs include:

  • Messages in your Sent folder that you did not send.

  • Unexpected password changes.

  • Unfamiliar forwarding rules.

  • Large volumes of outgoing messages.

  • Repeated authentication failures.

  • Complaints about suspicious messages sent from your address.

If you suspect compromise:

  1. Change the mailbox password.

  2. Review forwarding rules and filters.

  3. Check connected devices and applications.

  4. Review available account activity.

  5. Scan affected devices for malicious software.

  6. Contact LPM support if the mailbox is hosted through LPM.

Important: If your domain is being spoofed, attackers may be sending messages that appear to come from your domain without actually accessing your mailbox.

23. When to Contact Your Email Provider

Some problems cannot be resolved through cPanel alone.

For example:

  • Microsoft 365 account restrictions.

  • Google Workspace mailbox configuration.

  • External email provider outages.

  • Provider-specific sending limits.

  • Third-party SMTP service errors.

  • Receiving provider reputation restrictions.

If your email is hosted or sent through an external provider, its administration tools and support team may be needed.

LPM can assist with hosting-related configuration, but external providers control their own email systems and filtering decisions.

24. What Information to Collect Before Requesting Support

Providing accurate diagnostic information can significantly reduce troubleshooting time.

Before contacting support, gather:

  • The affected email address.

  • The recipient email address.

  • The approximate time the message was sent.

  • Whether the issue affects sending, receiving, or both.

  • The complete bounce or rejection message.

  • Whether the issue affects one recipient or multiple recipients.

  • Your email provider.

  • Any recent DNS or account changes.

Tip: A complete bounce message is often more useful than a screenshot showing only that an email failed.

Do not send mailbox passwords or other sensitive credentials.

25. Getting Help from LPM

If you're experiencing email delivery problems involving your LPM hosting service, contact our support team.

Submit a ticket through the LPM Client Portal.

Please describe the problem and include any relevant error messages.

LPM can help investigate:

  • cPanel mailbox configuration.

  • Hosting-related DNS records.

  • Email routing.

  • SPF and DKIM configuration.

  • Available server delivery logs.

  • Hosting-related sending and receiving problems.

Some issues, particularly those involving external email providers or recipient-side filtering, may require action from the provider responsible for the affected service.


Additional Resources:


Was this answer helpful?

« Back