Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Emails sent by my app land in spam

Short answer

Mail providers judge app emails on proof that you are allowed to send for your domain (SPF, DKIM and DMARC), on complaint rates, and on how the mail looks. Missing or wrong DNS records are the most common cause. A developer or whoever manages your domain has to set them up.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Customers say they never got the password reset email.
  • Receipts and notifications are in the junk folder.
  • It works with one mail provider but not another.
  • I send from a free email address through the app.

Why does this happen?

  1. The domain does not prove the mail is yours

    Google requires all senders to set up SPF or DKIM for their domain, and bulk senders of over 5,000 messages a day to Gmail must use SPF, DKIM and DMARC.

  2. The records are missing or wrong

    Authentication lives in DNS records at your domain. A new email service, or a changed host, can leave them out of date.

  3. People mark it as spam

    Google asks senders to keep the spam rate in Postmaster Tools below 0.30%, and ideally below 0.10%. Unwanted or unexpected mail pushes it up.

  4. Marketing mail has no easy unsubscribe

    For bulk marketing and subscribed messages Google requires one-click unsubscribe and a visible unsubscribe link in the message.

  5. The app sends through a weak route

    The server's built-in mail function is often rejected, where a proper email service is not.

What can I do about it today?

  1. Send a test to yourselfSend one real email from the app to a Gmail and one other address, and check where it lands.
  2. Find out which service sends your mailAsk your developer which service or server sends the app emails and from what address.
  3. Ask whoever manages your domain for the DNS recordsThey can show the SPF, DKIM and DMARC records, or tell you they are missing.
  4. Do not send the same email again and againRepeats of one message raise complaints and can harm your sending reputation.
  5. Check that mail to customers is expectedOnly send what they asked for, and make unsubscribing easy for marketing mail.

When should I bring someone in?

  • Password reset or order mails do not arrive.
  • You are unsure who controls the domain records.
  • Mail was fine and suddenly is not.

How do I handle it?

  1. Read the headersI send test mail and read the headers to see whether SPF, DKIM and DMARC pass.
  2. Correct the recordsI write the exact DNS records for your sending service and check them after they spread.
  3. Use a proper sending routeI move app mail to a reputable email service if the app sends through a plain server.
  4. Separate transactional and marketing mailI keep receipts and resets apart from newsletters, so a complaint on one does not harm the other.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Can you promise the inbox?

No. Mail providers decide. I can make sure authentication passes and the setup follows their published guidance.

Do I need all three: SPF, DKIM and DMARC?

Google requires SPF or DKIM for all senders and all three for bulk senders. Setting up all three is sensible either way.

Is it my app or my domain?

Often both. The headers of a test email show which one.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.