Skip to content
Email deliverability · Australia

Emails going to spam? SPF, DKIM and DMARC set up properly

Check every sender, write the records, test with real mailboxes, then tighten safely.

Your business emails land in spam, bounce, or a customer says they never arrived. Often the cause is how your domain tells the world which systems may send mail for it. This page explains why business email lands in spam, what we check, the three records in plain words and how we move to enforcement without blocking your own mail. True North Innovations is a Melbourne-based team that works with businesses across Australia. This page is for sending problems. If you are moving to a new mail system, see Google Workspace migration. We cannot promise inbox placement, because the receiving mail provider makes that decision.

Check every sender · Write the records · Test · Step towards enforcement

Melbourne based.
Australia-wide delivery.

Melbourne · Sydney · Brisbane · Perth · Adelaide · Canberra

Why business email lands in spam

The usual reasons

Mail providers check whether a message really comes from the domain it claims. When the checks fail or are missing, they may send it to spam or refuse it.

01

No sender records, or incomplete ones

The domain does not list all the systems that send for it, such as your mailbox, your newsletter tool and your booking system.

02

Records that clash

Two SPF records, or a record that lists too many systems, can break the check.

03

A system sending in your name that you forgot

An old tool or a website form that still sends as your domain but is not on the list.

04

No signing

Your mail is not signed with DKIM, so the receiver cannot see that it was not changed.

05

No policy

Without a DMARC record, receivers have no instruction on what to do with mail that fails the checks.

06

Reasons outside the records

The content of the message, the sending history, or a very new domain can also affect where mail lands. We say so when the records are not the cause.

The three records in plain words

SPF, DKIM and DMARC

01

SPF: who may send

A list on your domain of the systems allowed to send mail for it.

02

DKIM: a signature

A digital signature added to each message, so the receiver can check it is really from your domain and was not changed on the way.

03

DMARC: what to do when checks fail

A policy that tells receivers whether to watch, put in spam or reject mail that fails, and where to send reports.

These records are set in the DNS panel of your domain. A person must check them before they go live, because a mistake can block your own mail.

What we check

What we look at first

  • The domain's current SPF, DKIM and DMARC records, and whether they are correct.
  • Every system that sends mail for your domain, such as your mailbox provider, newsletter tool, invoicing, booking and website forms.
  • Whether each system signs its mail and whether the signature matches your domain.
  • Bounce messages and any spam complaints you can show us.
  • Test messages sent to real mailboxes at several providers, with the results read.
How we move to enforcement safely

From watching to rejecting, step by step

Setting the policy straight to reject can block your own mail if one sender was missed. We go in steps.

  1. 01

    Check and list senders

    We find every system that sends for the domain and write the list down.

    Output: A sender list

  2. 02

    Write the records

    We write the records out for you to place, or place them ourselves when you give us access. A named person checks them before they go live.

    Output: Checked records

  3. 03

    Test with real mailboxes

    We send tests and read the results at several mail providers.

    Output: Test results

  4. 04

    Watch

    DMARC starts in watch mode. Reports show who sends as your domain, and we read them for you.

    Output: Report readings

  5. 05

    Tighten

    When the reports are clean, we move the policy up a step, then to reject, after 2 to 4 weeks of reports.

    Output: A stronger policy

  6. 06

    One-page report

    A short report of what was found, what was set and what to keep right.

    Output: A one-page report

What you need to give us

What you give us to start

  • Access to the DNS panel of your domain, or the person who places DNS records for you.
  • Admin access to the mail systems that send for your domain.
  • A list of the tools you know send mail in your name.
  • A few examples of mail that landed in spam or bounced, if you have them.
  • A contact who can approve a record before it goes live.
What is not included and the scope

What is not included and what affects the scope

We do not send marketing campaigns, set up cold-email sending or host mailboxes. This job is about the records and the checks. We cannot promise that every message reaches the inbox, because each receiving provider decides.

What changes the scope: how many systems send for the domain, how tidy the current records are, and whether we place the records ourselves or write them for your team to place. The first records are ready within 3 working days after we have access. Enforcement comes after 2 to 4 weeks of reports. After that you have 30 days of support while we read the reports with you.

If you are changing mail provider as well, see Google Workspace migration. If the website form is the sender, see website maintenance for ongoing care of the site.

Common questions

Email deliverability (SPF, DKIM, DMARC): good to know

Why do my emails go to spam?

There are several reasons. The most common one we can fix is missing or wrong sender records. We check them first and tell you if the cause is somewhere else.

What are SPF, DKIM and DMARC?

SPF lists who may send for your domain, DKIM signs each message, and DMARC says what to do when the checks fail and sends reports.

Can you promise my mail will reach the inbox?

No. Each receiving mail provider decides. Correct records remove a common cause, and we test with real mailboxes to see the result.

Do you need access to my DNS?

Either that, or a person who places the records for you. We write them out in plain steps for the second case.

Could this block my own emails?

A wrong record can. That is why a named person checks each record before it goes live and why we start DMARC in watch mode.

Why not set DMARC to reject straight away?

If one sender was missed, its mail would be blocked. We read reports for 2 to 4 weeks first, then tighten step by step.

Which systems do you check?

Your mailbox provider and every tool that sends in your name, such as newsletters, invoicing, booking and website forms.

Do you send my newsletters?

No. We do not send campaigns, set up cold email or host mailboxes.

How fast are the first records ready?

Within 3 working days after we have access.

What do I get at the end?

The checked records, test results, a monitored move to enforcement and a one-page report, with 30 days of support reading reports.

I am moving to Google Workspace. Is this the same?

Related, not the same. See Google Workspace migration for the move. This page covers sender records and deliverability.

Explore more

Related services

Google Workspace migration →

Moving mailboxes to a new system, with the sender records in mind.

Website maintenance →

Ongoing care of the site, including its enquiry forms.

WordPress repair →

When a website form fails to send.

CRM development →

Where system emails are sent from a business system.

Contact →

Tell us what is going to spam.

WooCommerce repair →

When shop order emails are not arriving.

See all services

Tell us about your business

Tell us where your email is going wrong

Share your domain and what you notice. A person from our Melbourne team will reply by email. Please do not send passwords.

Call 03 4158 4444info@truenorthinnovations.com.au

Every job is scoped before work starts.

We use your details to respond to your enquiry. Read our Privacy Policy.