Outbound Email Delivery & Bounces

Created by Curtis Hammock, Modified on Sun, 15 Nov at 7:22 PM by Curtis Hammock

When you send an email through Purelymail, our mail delivery servers immediately connect to the recipient's mail server over SMTP. If the recipient server cannot accept the message right away, Purelymail manages retries automatically.


Temporary Deferrals vs. Permanent Bounces

  • Temporary Delivery Failures (4xx SMTP Codes): Occur when the destination server is temporarily unreachable, experiencing high traffic, enforcing greylisting, or suffering temporary DNS issues. Purelymail holds the message in an active queue and continues retrying delivery.
  • Permanent Bounces (5xx SMTP Codes): Occur when an address does not exist (e.g., 550 User unknown), the remote server blocks your domain, or a policy restriction fails. The message is dropped immediately and a Non-Delivery Report (NDR) bounce notice is returned to your inbox.

Purelymail Outbound Retry Schedule

If an outbound email encounters a temporary delivery failure:

  1. Automatic Retry Window (5 Attempts Over ~1 Hour): By default, Purelymail automatically retries delivery up to 5 times with increasing delays (5 seconds, 1 minute, 10 minutes, 20 minutes, and 30 minutes, totaling roughly 1 hour). If you are forwarding inbound mail to your own custom server using Relay mode, you can configure up to 64 retry attempts under Domains (see Custom Domain Delivery Modes).
  2. IP Rotation Across Cluster: If a remote server refuses connections from a specific IP address due to temporary provider throttling, Purelymail rotates subsequent retries across different clean outbound server IPs in our cluster.
  3. Missing MX Fallback (RFC 5321): If the recipient domain lacks mail exchange (MX) DNS records, our mail delivery system follows standard RFC 5321 rules and attempts delivery directly to the domain's root A record.

What to Do If an Email Bounces

If all delivery retries are exhausted, or if the destination server returns a permanent 5xx rejection code:

  • Delivery Stops: Purelymail ceases all further transmission attempts and delivers a final delivery failure notification to your inbox.
  • Manual Resend Required: Purelymail does not automatically retry bounced messages once the final failure report is issued. After verifying that the recipient address is valid or after the receiving provider resolves their server outage, you must compose or forward the email to send it again.
  • Inspect the Rejection Code: The bounce notification in your inbox contains the exact error message and SMTP status code returned by the destination server (such as 550, 451, or a DNS resolution timeout). Reviewing this diagnostic text will explain why the receiving server rejected the email.

Still Need Help?

If you've followed these steps and are still running into trouble, check our Purelymail Support guide.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article