Troubleshooting: Missing or Delayed Inbound Emails (Greylisting & Verification Codes)

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

If you are waiting for an incoming message (such as a login verification code, two-factor authentication (2FA) prompt, or password reset email from services like Discord, Steam, online banks, or social networks) and the message does not appear immediately or arrives several minutes late, this guide explains why and how to resolve it.


The Most Common Cause: Greylisting

Purelymail employs greylisting as a frontline defense against automated spam networks and botnets.

How Greylisting Works:

  1. First-Time Evaluation: When an external mail server attempts to deliver an email to your Purelymail address for the first time, our mail cluster checks its reverse DNS (rDNS) and sending profile.
  2. Temporary Deferral (451 Code): If the sending server is unfamiliar or lacks a complete reverse DNS record, Purelymail temporarily defers the message with an SMTP 451 code ("Please try again shortly").
  3. Automatic Sender Retry: Standard, RFC-compliant mail servers (such as Discord, Google, Microsoft, and legitimate transactional email providers) automatically queue the message and retry delivery within 1 to 15 minutes.
  4. Acceptance & Whitelisting: When the server retries, Purelymail recognizes the compliant retry, accepts the email into your inbox, and whitelists that sending server for future deliveries.
Why we use greylisting: Automated spambots send millions of mass messages to random domains and do not maintain retry queues. Greylisting stops over 90% of zero-day spam before it ever reaches your account.

Delayed vs. Bounced: What Happened to Your Email?

Understanding the difference between a delay and a rejection will tell you where the issue lies:

  • Delayed (Greylisted): Purelymail did not reject the message. The email is simply queued at the sending provider awaiting their automatic retry schedule. Once retried, it delivers normally.
  • Bounced (Rejected): If Purelymail rejects an incoming email (for example, if the domain does not exist, the mailbox is full, or the sending IP is on a severe real-time blocklist), our server sends an immediate rejection code back to the sending mail server.
    • The sending service will automatically generate a bounce notification (Non-Delivery Report) back to the sender.
    • Key Rule: If the sender did not receive a bounce notice, Purelymail did not permanently reject the email. The message is either still queued on their mail servers or in transit.

Checklist: How to Troubleshoot Missing Inbound Emails

If an expected email has not arrived after 15 to 20 minutes, perform the following checks:

1. Check Your Spam / Junk Folder

Purelymail's SpamAssassin filter scores incoming mail. Messages scoring 5.0 or higher are delivered straight to your Junk folder (see How Purelymail Spam Protection Works).

  • Log into Webmail (inbox.purelymail.com).
  • Check your Junk folder. If found, move the message to your Inbox so future communications are accessible.

2. Verify Your Domain's MX Records

If you recently connected your custom domain or updated DNS records:

  • Confirm that your domain's only active MX record points to mailserver.purelymail.com (see Setting Up Your Custom Domain DNS Records).
  • If you recently migrated from another host (such as Google Workspace, cPanel, or Microsoft 365), ensure all old MX records have been removed. Senders may continue routing messages to your previous mail host until their DNS cache expires.

3. Confirm Domain Delivery Mode in Purelymail (`535 5.7.1`)

In the Purelymail Account Admin portal:

  1. Navigate to Domains (purelymail.com/manage/domains) and click on your domain.
  2. Verify that Deliver Mail To is set to Purelymail.
  3. If this is set to External server (MX), Purelymail refuses incoming messages for that domain with 535 5.7.1 Purelymail is not configured to accept mail for this domain (see Custom Domain Delivery Modes).

4. Confirm the Recipient User or Alias Exists (`550 5.1.1 Unknown user`)

If a sender receives a bounce stating 550 5.1.1 Unknown user (or User isn't located here):

5. Check Symbolic Subaddressing (`+` or `_` tags)

If you gave a service a tagged address containing a plus sign, underscore, or hyphen (such as alex+discord@yourdomain.com):

  • Ensure that the base mailbox (alex@yourdomain.com) or alias exists.
  • Under Account Admin > Routing, verify that Enable symbolic subaddressing is checked for your domain. See Understanding Symbolic Subaddressing.

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