Business Email Going to Spam? How SPF, DKIM and DMARC Fix It
Quotes and invoices sent from your company address landing in spam? What SPF, DKIM and DMARC are, how to check you have them, and what else may be wrong.
Published Updated 10 min read
You send a quote. The client doesn’t reply, and a week later you find out the message sat in their spam folder. When this happens often, the cause is usually technical, not the wording of the message. The client’s mail servers can’t verify that the message really comes from your company. Below you’ll find what SPF, DKIM and DMARC are, how to set them up without cutting off your company’s email, how to check the result, and the other causes that push messages into spam.
Why it matters more now
Gmail, Yahoo and Outlook are checking senders more and more strictly. Since 1 February 2024, Gmail requires every sender to have at least SPF or DKIM set up, valid forward and reverse DNS records for the sending server, and encrypted (TLS) connections. Anyone sending more than 5,000 messages a day to Gmail addresses must have SPF, DKIM and DMARC.
Microsoft followed. Since May 2025, Outlook.com requires domains sending more than 5,000 messages a day to Outlook.com, Hotmail and Live addresses to pass SPF and DKIM and to publish DMARC, at least with a p=none policy. Messages that don’t meet the requirements go to Junk.
A small business won’t reach those volumes, but messages without these settings are treated with more suspicion. Filters don’t only look at volume: an unauthenticated message from a domain with no history, carrying an invoice attachment, looks a lot like a fraud attempt. In practice, these three records have become the minimum for any domain that sends invoices and quotes.
SPF: who is allowed to send
SPF is a line in your domain settings (a TXT record in DNS) that says which servers are allowed to send email for your company. It looks something like this:
v=spf1 include:_spf.provider.ro ~all
What the parts mean:
v=spf1marks the record as SPF;include:adds a provider’s servers, as that provider publishes them;ip4:adds a specific IP address, for example your hosting server’s;~allat the end says all other servers aren’t authorised, but their messages should only be flagged, not rejected;-allasks for them to be rejected.
The usual mistake happens when a company sends from several places: the mail server, an invoicing program, a newsletter platform. If one is missing from SPF, its messages look fake. A domain must have a single SPF record, and every service goes into it.
Each include: triggers extra DNS lookups, and the standard caps how many there can be. An SPF record with services added over the years can exceed that limit and fail completely. When you add a new service, remove the ones you no longer use.
DKIM: the message’s signature
DKIM adds a digital signature to every message. The receiving server checks the signature against a key published in DNS. If it matches, the server knows the message wasn’t altered on the way and comes from the domain it claims. You turn it on in your email panel, which also gives you the record to add to DNS.
The public key sits at an address like selector._domainkey.company.ro. The selector is a name chosen by the provider, so several services can each have their own key on the same domain without getting in each other’s way. In Plesk, DKIM is turned on under Mail, in the domain’s settings, and if DNS is managed on the same server, the record is added automatically.
Every service that sends on your company’s behalf (the invoicing program, the newsletter platform) should sign with DKIM on your company domain. Otherwise DMARC will see it as an unauthorised sender.
DMARC: what happens to fake messages
DMARC tells receiving servers what to do with a message that fails SPF and DKIM: let it through, put it in spam or reject it. It also sends you reports on who is sending as your domain, including services you’d forgotten about, such as an old invoicing program or the form on your website.
A starter record looks like this, at the address _dmarc.company.ro:
v=DMARC1; p=none; rua=mailto:dmarc@company.ro
The rua address receives daily reports, in XML format, from the big email providers that send them. They’re hard to read directly, but there are services that turn them into tables. Use a separate address so the reports don’t fill up someone’s inbox.
Start with a monitoring policy, p=none, and read the reports for a few weeks. Once you can see all your legitimate services passing, move to p=quarantine and then to p=reject. That way nobody can easily send fake emails in your company’s name.
One detail many people miss: DMARC requires the domain in the sender’s address to match (align with) the domain checked by SPF or DKIM. An invoicing program that sends “on behalf of” your company but signs with its own domain passes DKIM for its domain, not yours, and fails DMARC.
The order to set them up in
To avoid cutting off your company’s email along the way:
- List every service that sends from @company.ro addresses: the mail server, the invoicing program, the online shop, the website form, the newsletter platform, the printer that emails scans.
- Put them all in SPF, in a single record, with
~allat the end. - Turn on DKIM for every service that supports it and publish the keys.
- Publish DMARC with
p=noneand a reporting address. - Read the reports for a few weeks and add any services you’d forgotten.
- Tighten gradually to
p=quarantine, then top=reject.
Before changing anything, copy the existing records into a file. What each type of DNS record does and where to find your domain’s zone are covered in our article on DNS explained.
How to check whether you have them
Send an email from your company address to a Gmail address. Open the message, click the three dots and choose Show original. Gmail shows the result for SPF, DKIM and DMARC there. All three should say PASS. If you see FAIL or one is missing, you know where to start.
You can also check the records directly from Windows. Open Command Prompt (Windows + R, type cmd) and run:
nslookup -type=txt company.rofor SPF;nslookup -type=txt _dmarc.company.rofor DMARC;nslookup -type=txt selector._domainkey.company.rofor DKIM, using the selector your provider gave you.
If SPF shows softfail, the message left from a server that isn’t on the list. If DKIM shows fail, the key in DNS doesn’t match the one the server is using, usually after a migration or a key regeneration. If DMARC fails even though SPF and DKIM pass, the problem is domain alignment, explained above.
Repeat the Gmail test for every service that sends on your company’s behalf, not just the main server. The invoicing program is usually the one that fails.
Other causes
If all three are fine and messages still land in spam, check these too:
- Blacklists. If your server has sent spam in the past, for example from a hacked account, its address may be on a blacklist. There are free websites that check this.
- A hacked account. An email account with a weak password can be used to send spam without you knowing. Change passwords and turn on two-factor authentication wherever you can. The signs of a compromised account and of trap messages are covered in our article on how to spot phishing emails.
- Content. Messages that are just an image, shortened links, or password-protected zip attachments look suspicious.
- The sender address. If you send from a program, check that the sender address is on your company domain.
- The website form. Many forms send messages from the web server with the visitor’s address as the sender. To the receiving server, that looks like a forgery. Set the form to send from a company address over authenticated SMTP and put the visitor’s address only in “Reply-To”.
- No reverse DNS for the server’s IP. Gmail requires the sending server to have a reverse DNS (PTR) record, meaning the IP address leads back to a name and that name leads to the same address. This is set by whoever owns the IP address, usually your hosting provider, not in your domain’s zone.
- A shared server with noisy neighbours. On shared hosting, several customers may send from the same IP address. If one sends spam, the address’s reputation drops for everyone. Ask your provider how they monitor outgoing mail and what they do when an address ends up on a blacklist.
- Recipient complaints. If you send newsletters and many recipients mark them as spam, your domain’s reputation drops for your everyday messages too. Only send newsletters to people who subscribed, and include a visible unsubscribe link.
Newsletters and everyday email
If your company also sends campaigns, it’s worth keeping them apart from day-to-day correspondence. A common approach is a dedicated subdomain, such as news.company.ro, with its own SPF, DKIM and DMARC. If a campaign damages the subdomain’s reputation, quotes sent from company.ro aren’t hit to the same degree.
Gmail also requires high-volume senders to offer one-click unsubscribe on marketing messages. Reputable newsletter platforms add it automatically. Check that it’s switched on.
Frequently asked questions
How long after setting up SPF and DKIM will I see a difference?
New records become visible once the old ones’ TTL expires, usually within a few hours. Your domain’s reputation recovers more slowly, depending on how badly it was damaged. Keep an eye on the results in message headers and DMARC reports for a few weeks.
Can I go straight to p=reject to be safe?
You can, but you risk blocking legitimate messages from services you’ve forgotten about, such as your invoicing program. Start with p=none, read the reports, and only then tighten the policy.
Why do my messages go to spam for some clients only?
Each email provider has its own filters, and large companies often have internal filters too, with rules you can’t see from outside. If the problem is with one client only, ask them to check the message headers or add you to their safe senders list. If it happens with many, the cause is on your side.
What if someone is sending fake emails in my company’s name?
Clients tell you they’ve received invoices from “you” with a different bank account, or messages with strange links. First make sure none of your company accounts has been hacked: change passwords and look for unknown forwarding rules. Then move DMARC towards p=quarantine or p=reject, once you’re sure your legitimate services pass, and tell clients to confirm any change of bank details by phone.
Do I need SPF, DKIM and DMARC if I use Microsoft 365?
Yes. Microsoft 365 gives you the values to put in DNS, but it doesn’t publish them on your company domain by itself if your DNS is with another provider. Check them with the test above. The same goes for any other email service.
If you want to understand the options for hosting email on your own domain from scratch, read our guide to email on your own domain. For the basics, our page on whether web hosting is easy explains which steps need the most care.
If you’d rather not touch DNS yourself
Wrong DNS settings can stop your company’s email altogether, so they’re worth doing carefully. On our web hosting we set up SPF, DKIM and DMARC for your company domain, and if your email is with another provider, we help through IT maintenance.