Troubleshooting Missing Custom Domain Emails in a Free Help Desk

If emails sent to your custom domain never show up as tickets, start with the most common causes — DNS misconfiguration, missing forwarding, or unverified inbound addresses — and follow the checks and fixes for each.

NNeuraDesk TeamNovember 19 20264 min read
On this page

You’ve configured a custom domain for your support address, but messages sent to that address never appear in your help desk. The symptom is usually the same: the inbox stays empty, no tickets are created, and there’s no error message to explain why.

1. DNS records not propagated or misconfigured

How to confirm

  • Use a DNS lookup tool (dig, nslookup, or an online checker) to query the MX, SPF, DKIM, and any CNAME records for your domain.
  • Verify that the MX record points to the inbound email host supplied by your help desk.
  • Check that SPF includes the help desk’s sending servers and that DKIM selectors match the values shown in the help desk settings.

How to fix

  • Correct any missing or typo‑ridden records in your domain registrar’s DNS console.
  • Allow up to 48 hours for full propagation, though most changes appear within a few hours.
  • Re‑run the lookup until the records match exactly what the help desk expects.

2. Email forwarding not set up in the domain provider

How to confirm

  • Log into your registrar or hosting control panel and locate the email forwarding section.
  • Ensure a forward exists from your custom support address (e.g., support@yourdomain.com) to the unique inbound address provided by the help desk (often something like inbound@helpdesk.io).

How to fix

  • Add the forward if it’s missing, or correct the destination address.
  • Save changes and send a test message to the custom address; it should arrive in the help desk within minutes.

3. Help desk inbound address not verified

How to confirm

  • Open the help desk’s email settings page and look for a verification status next to the inbound address.
  • Many free help desks (including NeuraDesk) require you to click a verification link sent to that address before they accept mail.

How to fix

  • Request a new verification email from the settings page.
  • Check the inbox of the inbound address (or the forward destination) for the verification link and click it.
  • Once verified, the status should change to “Active” and mail will be processed.

4. Spam or filtering rules dropping messages

How to confirm

  • Send a test email from an external address (Gmail, Outlook) to your custom support address.
  • Check the spam folder of the forwarding inbox and the help desk’s internal spam quarantine, if one exists.
  • Review any custom filter rules you may have created in the help desk that could move or delete incoming mail.

How to fix

  • Whitelist the help desk’s inbound domain or IP range in your email provider’s spam settings.
  • Disable or adjust any aggressive filter rules that match legitimate support keywords.
  • Mark a few test messages as “Not spam” to train the filter.

5. Rate limits or quota exceeded on the free plan

How to confirm

  • Open the usage or billing dashboard in the help desk and look for a “messages received” counter or a quota indicator.
  • Some free tiers cap the number of inbound emails per month; once the limit is hit, new messages are silently dropped.

How to fix

  • If you’re near the limit, reduce inbound volume (e.g., consolidate aliases) or upgrade to a paid plan that removes the cap.
  • For NeuraDesk, the free tier includes unlimited email‑to‑ticket conversion, so this issue only appears on platforms with stricter limits.

6. Email client sending from an unauthorized alias

How to confirm

  • Send a test from the exact address you configured as the sender in your help desk (e.g., support@yourdomain.com).
  • If you use an alias or a different “From” address, the help desk may reject the message because it doesn’t match the verified sender list.

How to fix

  • Add any additional sending addresses to the help desk’s authorized senders list.
  • Ensure your email client’s “From” field matches one of those authorized addresses.

What to do if nothing worked

Collect the following information and contact the help desk’s support team:

  • Screenshots of your DNS records (MX, SPF, DKIM).
  • The exact forwarding rule you created.
  • Verification status screenshot from the help desk.
  • A sample of the raw email headers from a test message that didn’t arrive.
  • Any error logs the help desk provides.

With that data the support engineers can trace the message path and identify whether the block occurs at the DNS layer, the forwarding layer, or inside the help desk itself.

If you’re still evaluating options, a free help desk that includes automatic email‑to‑ticket conversion, AI reply suggestions, and a shared inbox can simplify the setup. Try NeuraDesk free.

Found this useful? Share it with your team.

Join teams already using NeuraDesk

Ready to get started?

Create your workspace and try NeuraDesk for free.

Sign up free