FolioQ12AnswerLast checked 22 Nov 2026
As at
Sun 22 Nov 2026
Entries
8
Not yet
12
Page seal 0DBB, 259°04′. Drawn from the SHA 256 of this page’s source text0DBB
Page seal0DBB, 259°04′

Why are my emails going to spam?

Short answer. Most often, the receiving mail service cannot prove the message really came from you. Gmail and Outlook.com check three public DNS records: SPF, DKIM and DMARC. If they are missing, broken, or do not match the domain in your From line, mail goes to spam or is refused. Complaint rates and content matter too. Fix the records first.

The three records, in one line each

  • SPF is a DNS record that lists the servers allowed to send mail for your domain (RFC 7208).
  • DKIM is a signature added to each message. The receiver checks it against a public key in your DNS (RFC 6376).
  • DMARC is a DNS record that tells receivers what to do when a message fails, and asks them to send you daily reports (RFC 9989, published May 2026, which replaced RFC 7489).

A message passes DMARC when SPF or DKIM passes and the domain that passed matches the domain in the visible From line. That match is called alignment. Microsoft's guide puts it plainly: a message fails DMARC only if both the SPF and the DKIM alignment checks fail.

Steps you can do yourself, free

Step 1 needs only your inbox. Steps 2 to 6 are for whoever manages your domain; you can send them this page.

  1. Read the verdict on one of your own messages.

    Send a message from your business address to a personal Gmail account. Open it on a computer, choose More next to Reply, then Show original. Look for the lines that report spf, dkim and dmarc as pass or fail. Microsoft 365 writes the same results into a header called Authentication-Results.

  2. Check you have exactly one SPF record.

    It must start with v=spf1. Two SPF records on one domain is an error: RFC 7208 says the check then returns "permerror", which counts as a failure.

  3. Count the lookups in SPF.

    Each include, a, mx, ptr and exists term, and the redirect modifier, costs one DNS lookup. RFC 7208 caps the total at 10. Past 10, the result is again "permerror". Old includes for tools you no longer use are the usual cause. Remove them.

  4. Turn on DKIM in every service that sends as you.

    That means your mailbox provider and also your invoicing tool, CRM, helpdesk and newsletter tool. Each one gives you a record to publish, usually at selector._domainkey.yourdomain. Gmail requires a key of 1024 bits or longer for mail to personal Gmail accounts. In Google Workspace and Microsoft 365, DKIM is switched on in the admin console.1

  5. Make sure each sender signs with your domain.

    If a tool signs with its own domain, DKIM passes but DMARC still fails, because the domains do not match. Most tools have a "custom domain" or "authenticate your domain" setting for this.

  6. Publish a DMARC record at watch level.

    A starting record looks like this:

    _dmarc.yourdomain   TXT   "v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain"

    p=none changes nothing about delivery. It asks receivers to send you reports, so you can see every service that sends as you.

  7. Check your complaint rate if you send in volume.

    Google asks all senders to keep the spam rate shown in Postmaster Tools, Google's free dashboard for senders, below 0.3 percent, and recommends staying below 0.1 percent.

  8. If you run your own mail server,

    give its sending IP a reverse DNS (PTR) record that matches, and send over TLS. Gmail lists both as requirements for all senders.

Do the big mailbox rules apply to you?

  • Gmail. Google counts you as a bulk sender if you send close to 5,000 messages or more in 24 hours to personal Gmail accounts. Mail from all subdomains counts toward the main domain. Cross that line once, and you stay a bulk sender. Bulk senders must have SPF, DKIM and DMARC, with p=none as the minimum, and the From domain aligned. Google said enforcement would ramp up from November 2025, with temporary and then permanent rejections.
  • Outlook.com. Since 5 May 2025, Microsoft sends mail from domains that send more than 5,000 messages a day to Junk if SPF, DKIM and DMARC (at least p=none, aligned) are not in place. It has said rejection comes later, on a date to be announced.
  • Everyone else. Gmail requires SPF or DKIM from all senders, even small ones.

If all three pass and mail still goes to spam

Ask a customer who got it to mark it 'Not spam'. Check that your sending address is not on a public block list. Send from your own domain, not a free webmail address. Avoid sending to lists people did not sign up for.2

What it costs to have it done

The records themselves cost nothing. What costs money is finding every service that sends as you, getting each one signed, and checking the result.

Market prices we found, with sources, read 22 Nov 2026:

SellerWhat it statesSource
Fiverr gigs for SPF, DKIM and DMARCnear 50 USDS25, a search result3
O365HQ monitoring95 USD per monitored domain a month; monitoring only, for a domain already set up; setup is a separate projectS24, search result 22 Nov 2026, not yet opened4
O365HQ setup and ramp450 USD per domain plus a 950 USD tenant fee, about 4 weeksS24, page reread
DMARC Report managed tierA fixed one time price per domain, given on request; enforcement within 90 days in writingS23, search result 22 Nov 2026, not yet opened4

Marsadel's own price. This question is answered by Mail Alignment, which is Stage A of our Domain and Mail Gap Closure unit. At launch every job runs in runbook mode: AI agents check your setup, write each step for you and test the result. You, or whoever runs your website, apply each step; we do not log in to your systems. A second AI model and a named reviewer will check the work.5 These are our own prices, Tier 1 list, in US dollars:

  • Mail Alignment: 232 USD at launch, where you apply each change from our written steps. Full price, once we can make the changes ourselves: 290 USD.
  • Full Domain and Mail Gap Closure, both stages, through to reject: 312 USD at launch. Full price: 390 USD.
  • Agencies and IT firms buying for a client pay wholesale: at launch 152 USD and 200 USD; full price 190 USD and 250 USD.

Mail Alignment gives you written steps to set your three mail records and match them to your domain, lock the domain, and remove old records that point at nothing. You apply them, and we retest. Stage A is done within 72 hours of the day you send what we ask for. In runbook mode, we retest each change within 72 hours of you telling us it is applied; time you take to apply a step does not count toward the 72 hours or the 10 day refund point.6

Not on sale yet. This unit opens after its quality test (target Sat 5 Dec 2026), once our company and checkout are live. At launch you apply each change yourself from our written steps.7

Details: Mail Alignment and Domain and Mail Gap Closure.

How to check it worked

Send the same test message again and read Show original. You want spf=pass, dkim=pass and dmarc=pass, with the DKIM domain equal to your own. Then wait a day and read the first DMARC aggregate report. Every source in it should be one you recognise.

What we have measured. Our first four read only Stage A runs, on domains the founder owns, were sealed on 22 Nov 2026, with no change applied and checked by the rule based inspector only. Four runs on our own domains are too few to print a rate, and human minutes are not measured yet.8

Facts on this page

FactSourceRead
SPF: one record per domain; more than one gives "permerror"; 10 DNS lookup limit; record starts with v=spf1datatracker.ietf.org/doc/html/rfc7208 (sections 3.2, 4.5, 4.6.4)22 Nov 2026
DKIM keys sit at selector._domainkey.domain; d= names the signing domaindatatracker.ietf.org/doc/html/rfc6376 (sections 3.5, 3.6.2.1)22 Nov 2026
DMARC is RFC 9989, May 2026, Proposed Standard, obsoletes RFC 7489 and RFC 9091datatracker.ietf.org/doc/rfc9989/22 Nov 2026
A message fails DMARC only if both SPF and DKIM alignment faillearn.microsoft.com/en-us/defender-office-365/email-authentication-dmarc-configure22 Nov 2026
Gmail rules for all senders: SPF or DKIM, PTR, TLS, spam rate below 0.3 percent (0.1 percent recommended), DKIM key 1024 bits minimumsupport.google.com/a/answer/8112622 Nov 2026
Gmail bulk sender: close to 5,000 a day to personal accounts, counted by primary domain, permanent once crossed; DMARC required; enforcement ramping from November 2025support.google.com/a/answer/14229414 (S14)22 Nov 2026
Outlook.com: over 5,000 a day, non compliant mail to Junk from 5 May 2025, rejection latertechcommunity.microsoft.com/blog/microsoftdefenderforoffice365blog/strengthening-email-ecosystem-outlook%E2%80%99s-new-requirements-for-high%E2%80%90volume-senders/4399730 (S15)22 Nov 2026
Gmail full headers: More, then Show originalsupport.google.com/mail/answer/2943622 Nov 2026
Market pricesDMARC Report dmarcreport.com/managed-compliance/ (search result 22 Nov 2026, not yet opened4); O365HQ o365hq.com/services/dmarc-dkim-spf-email-authentication (read 22 Nov 2026); Fiverr fiverr.com/devops_dmytro/fix-spf-dkim-dmarc-for-better-email-delivery-and-reduce-spam and www.fiverr.com/wordpressmgc/setup-all-dns-records-spf-dkim-dmarc-for-email-inbox-deliverability (search result 22 Nov 2026, not yet opened9)22 Nov 2026

Rows without an S number were read by the page writer and are not yet in the firm's source table.10

Questions people ask next

Is p=none enough to stop spam placement? It meets the Gmail and Outlook.com floor for bulk senders. It does not stop someone forging your domain, because p=none asks receivers to change nothing. To stop forgery you move to quarantine and then reject, step by step. See how to put DMARC at reject without losing email.

My SPF passes but DMARC fails. Why? The service that sent the message uses its own domain as the return address, so SPF passed for its domain, not yours. Microsoft's guide gives two fixes: have that service sign DKIM with your own domain, or change its MAIL FROM address (the return path) to your domain or a subdomain of it.

Do I need DMARC if I send only a few emails a day? Gmail requires only SPF or DKIM from small senders. DMARC is still the only record that lets you see who sends as you, and the only one that lets you ask receivers to refuse forgeries. It costs nothing to publish at p=none.

How long until the change works? DNS changes usually show within the record's time to live (TTL, how long other servers may keep an old copy), often an hour or less. Placement can take longer to recover, because receivers also weigh your past complaint rate.

If I order, do you train AI models on my data? No, unless you tick a consent box that allows it.


Written by AI agents and checked against the sources above. Last checked 22 Nov 2026. No named human has reviewed this page yet.11 No partner is signed in any country yet.12

Not yet in place12

Nothing is on sale yet; each numbered mark on this page points to a condition below. Every condition, with its state, is on the status board.

  1. 1Google and Microsoft DKIM setup pages read and linked with read date
  2. 2each point checked against Google's sender guidelines page and cited
  3. 3gig pages read in full
  4. 4page read in full
  5. 5second model vendor connected; two contracted reviewers, target Mon 30 Nov 2026
  6. 6runbook clock rule confirmed in the terms
  7. 7Stage A Bench passed; company formed and checkout live; cover that includes AI agent work bound
  8. 8own property Stage A results from the week 1 runs, with n, labelled own property, for example "of n own and test domains checked on date, k failed SPF or DMARC"
  9. 9pages read in full
  10. 10each such row added to the plan source table with an S number and status
  11. 11named human reviewer under contract
  12. 12first partner agreements signed

Each item is also marked where it stands on this page.