⌘ K

Search

Search portal content

AI customer support in one tabAI customer support in one tab
⌘ K

Search

Search portal content

AI customer support in one tabAI customer support in one tab
  • Create an inbox
  • Choose inbox channels
  • Forward your support address
  • Forward from Google Workspace
  • Forward from Gmail
  • Forward from Microsoft 365
  • Send from your own domain
  • Sender names and signatures
  • Fix email problems
  • Connect WhatsApp
  • Use WhatsApp templates
  • Connect Telegram
  • Set up auto-reply
  • Choose ticket numbering
  1. Home
  2. Inboxes & channels

Fix email problems

Find your symptom: missing tickets, a stuck verification email, forwarding bounces, duplicates, failed inbound checks, and DNS records that won't verify.

On this page
  • Fix email problems
  • Email isn't becoming tickets
  • If a test email never shows up
  • If Gmail's verification message never arrives
  • If Gmail is verified but nothing arrives
  • If the sender gets a bounce from Microsoft 365
  • If some email is missing
  • If you get two tickets for each email
  • If tickets show your teammate as the customer
  • If a ticket's sender looks suspicious
  • Domain verification
  • If a record shows Missing or Mismatch
  • If you see "DNS check needs attention" or "We could not check the DNS records."
  • If you see "The DNS check took too long. Your records may still be propagating; try again shortly."
  • If you see "DNS checks are temporarily limited. Wait a moment and try again."
  • If DMARC is Missing but everything else is Found
  • If you see "Verification was lost"
  • If you see "Enter a domain your organization owns and has not registered already."
  • Company email address
  • If you can't turn on sending
  • If the address is rejected
  • If you see "Inbound checks are temporarily limited. Wait a moment and try again."
  • If the inbound check fails
  • If replies come from an initdesk address
  • If replies land in spam or fail authentication
  • If you still need help
  • Related

Fix email problems

Find your symptom: missing tickets, a stuck verification email, forwarding bounces, duplicates, failed inbound checks, and DNS records that won't verify.

Find your symptom below. Receiving problems (email doesn't become a ticket) usually come from forwarding at your email provider. Sending problems (replies come from the wrong address, or the domain won't verify) come from the Company email address setup.

A diagram of email going from the customer to your provider, then to the initdesk inbox address, then into a ticket
Email can stop at any of these steps. Find the step, then fix it.

Email isn't becoming tickets

If a test email never shows up

  1. Send the test from an account outside your company. Mail to yourself from the same account can skip the path customers use.
  2. Check that your forwarding destination is exactly the initdesk inbox address under Settings > Inboxes, your inbox, Email. If you changed the Address prefix, update the rule.
  3. Look in the mailbox you forward from. Spam or a filter there can catch the message first.
  4. Admin routing at Google can take up to 24 hours. Give it time, then test again.
  5. Ask the sender whether they got a bounce. Microsoft 365 sends the bounce to the sender, not to you.

If Gmail's verification message never arrives

Gmail sends it to your initdesk inbox address, where it becomes a ticket. Check that you typed the address exactly, then look in the inbox and in spam. Repeat Add a forwarding address in Gmail to send a new one. If Gmail won't let you add an address at all, an admin has probably turned off forwarding. See Forward from Gmail.

If Gmail is verified but nothing arrives

Verifying the address doesn't turn forwarding on. In Gmail, select Forward a copy of incoming mail to, choose the address, and select Save Changes.

If the sender gets a bounce from Microsoft 365

The bounce says 5.7.520 Access denied, Your organization does not allow external forwarding. Microsoft blocks forwarding to outside addresses by default, and an admin has to allow it. See Forward from Microsoft 365. It doesn't mean initdesk rejected the email.

If some email is missing

Gmail doesn't forward mail it marks as spam, and Google routing rules skip it unless you check Bypass spam filter for this message. In Gmail, a filter with Never send it to Spam helps.

If you get two tickets for each email

Two methods are forwarding the same address, such as a routing rule plus a Gmail filter, or an Outlook rule plus the forwarding setting. Keep one.

If tickets show your teammate as the customer

An Outlook rule uses Forward to, which makes the message look like it came from your mailbox. Change it to Redirect to. In Google, use admin routing.

If a ticket's sender looks suspicious

That's a sender verification warning, not a delivery problem. See Sender verification.

Domain verification

If a record shows Missing or Mismatch

Open Settings > Sending domains and select the domain. A record marked Missing isn't published yet. A record marked Mismatch exists with a different value. Compare the Name and Value at your DNS provider with the ones in initdesk, correct them, then select Check DNS. If your provider adds your domain to every name, enter the name without the final .yourcompany.com.

The page also shows "{found} of {required} required records found." DNS changes can take time to spread, so wait a few minutes and check again.

If you see "DNS check needs attention" or "We could not check the DNS records."

Review the records, fix any mismatch, and select Check DNS again.

If you see "The DNS check took too long. Your records may still be propagating; try again shortly."

The records may not have spread yet. Wait and check again.

If you see "DNS checks are temporarily limited. Wait a moment and try again."

You checked too many times in a short period. Wait a minute. initdesk also checks again on its own.

If DMARC is Missing but everything else is Found

That's fine. DMARC is Recommended and doesn't block verification.

If you see "Verification was lost"

A record that was there is gone or changed, so DNS stopped verifying. New tickets send from the initdesk sender until the records are back. Restore the records and select Check DNS.

If you see "Enter a domain your organization owns and has not registered already."

initdesk accepts only a domain your organization owns and hasn't added already. Enter the part after the @ in your address, without www..

Company email address

If you can't turn on sending

You'll see "Complete the sending-domain and inbound checks before enabling." You need a verified domain, a saved address, and Inbound connected.

If the address is rejected

  • "Use an address on the selected sending domain." The address must end with the domain you picked, or one of its subdomains.
  • "Enter an unused address on the selected sending domain." Another inbox already uses it.
  • "This address could not receive a provider check. Try another address."

If you see "Inbound checks are temporarily limited. Wait a moment and try again."

You sent checks too quickly. Wait, then select Send inbound check again.

If the inbound check fails

The page shows what happened to the last check. Match the title:

Title Meaning and fix
Last check did not return in time The check message didn't reach the inbox before it expired. Check automatic forwarding, the destination, and spam or mailbox filters. Keep the original subject and message headers. Send another check.
Delivery status could not be checked The check didn't return, and initdesk couldn't confirm delivery. Same fix as above.
Last check rejected by the receiving server Your mail server rejected the message. Confirm that the mailbox exists and accepts email from initdesk, then send another check. If it's still rejected, contact initdesk support.
Last check blocked by Amazon SES Amazon SES (the service initdesk sends email through) blocked delivery after an earlier rejection or a spam complaint. Confirm that the mailbox exists and the owner wants this email, then contact initdesk support to review the block.
Last check rejected by the email provider Contact initdesk support to review the rejection before sending another check.
Last check could not be sent Try again later. If it continues, contact initdesk support.
The last failure has no recorded cause Send another check. If it fails again, contact initdesk support.

The message describes the last attempt. After you fix the cause, select Send again for a fresh result.

If replies come from an initdesk address

Check that the status is Live and that the ticket is new. Existing tickets keep the sender they started with.

If replies land in spam or fail authentication

Check that the domain is Verified and that all records still show Found. Keep one SPF record per domain. initdesk's SPF record is on a subdomain, so you shouldn't need to edit your main one. Mail forwarded to initdesk can fail SPF on the way in. That's normal and separate from sending.

If you still need help

Select Contact initdesk support under the failure message, or contact us from the help center. Tell us the inbox, your support address, your email provider, and the message you see.

Related

  • Forward your support address
  • Send from your own domain
  • Sender verification
Sender names and signatures

Choose the name customers see on replies, set a signature for each inbox, and let each person on your team add a personal email signature.

Connect WhatsApp

Connect a WhatsApp Business number to an inbox through Meta. Customer messages become tickets, and you reply from initdesk.

Powered by initdesk