You send a quote from info@your-company.ch. Three days later the client chases you up: nothing has arrived. They eventually find it in their spam folder, or never do.
When your emails go to spam, the wording of the message is not necessarily to blame. The big email providers now check three settings on your domain name for every single email. If one of them is missing or wrong, your quote sets off at a disadvantage, and nobody tells you.
What Gmail, Yahoo and Outlook require
In October 2023, Google announced, with Yahoo's backing, new rules for bulk senders. Since February 2024, Gmail's guidelines and Yahoo's have distinguished between two categories.
All senders, including the tradesperson who sends ten emails a day, must:
- authenticate their messages with SPF or DKIM;
- send from a server whose address has a valid reverse DNS record;
- keep their spam complaint rate below 0.3%.
Gmail also requires an encrypted connection during transmission. It warns that unauthenticated messages may be marked as spam or rejected.
Bulk senders, roughly 5'000 messages or more in 24 hours to personal Gmail addresses, must have SPF and DKIM, publish a DMARC policy (at least "none") and offer one-click unsubscribe in their marketing emails. The count is per domain: your emails, your newsletter and your online shop all add up. According to Google's FAQ, a domain that crosses the threshold just once stays classified as a bulk sender, with no expiry date.
Microsoft followed in April 2025 for its consumer addresses: outlook.com, hotmail.com and live.com. Above 5'000 emails a day, SPF, DKIM and DMARC are required. Microsoft first planned to send non-compliant messages to the junk folder. In an update on 29 April 2025, it announced that it would reject them from 5 May 2025.
A small business rarely reaches those volumes. The minimum, however, applies to everyone.
SPF, DKIM and DMARC explained simply
Your domain name carries, in its DNS zone, lines of text that any mail server can read. Three of them matter here.
SPF, the list of authorised couriers. Picture a list, pinned up at the counter, of the couriers allowed to drop off post in your name. The server receiving your quote checks that whoever delivered it is on the list. Your email service usually is. The invoicing software that sends on your behalf is not necessarily.
DKIM, the seal on the envelope. Each message gets an encrypted signature. The recipient checks it against a key published in your DNS. If it matches, the message comes from a server you have set up, and nobody has altered it on the way.
DMARC, the instruction left at the counter. This is your instruction to email providers: what to do with an email in your name that fails the checks. Let it through ("none"), put it in spam ("quarantine") or refuse it ("reject"). DMARC is also used to receive reports: the providers that receive your emails send you, usually once a day, the list of servers that have sent mail using your domain, and the results of their checks.
Alignment fits in one sentence: the domain validated by SPF or DKIM must be the one shown in the "From" field your client reads, as Microsoft's documentation explains. A tool that passes SPF with its own domain but sends under yours fails DMARC, unless it signs with DKIM using your domain.
Four common reasons emails go to spam
The contact form on your website. Some forms pass on a visitor's message as if it came from them: "From: john.smith@gmail.com", but sent by your website's server. Gmail explicitly asks senders not to impersonate its "From" headers. Another variant: the form sends "From: info@your-company.ch" from the web server, which your SPF does not list.
Tools that write in your name. Invoicing software, newsletter tool, online shop, booking diary: each one sends emails with your address, from its own servers. If it is not listed in your SPF and does not sign with DKIM using your domain, its messages fail DMARC. Microsoft puts this case first among the alignment failures it describes.
Two SPF records instead of one. Every new tool comes with its own SPF line "to add", and someone adds it alongside the old one instead of merging them. But a domain is only allowed a single SPF record. With two, the check returns a permanent error, according to Microsoft. Same result when the list grows too long: beyond ten DNS lookups, SPF fails.
No DMARC at all. Below the 5'000 threshold, none of the three providers requires it. Yahoo nevertheless recommends that all senders publish one. Without DMARC you receive no reports: you do not know who is sending with your domain or what is failing.
The test. Send an email from your business address to a Gmail address. Open it in Gmail on a computer and click the small arrow below the sender's name. According to Google, an authenticated message shows the "Mailed by" and "Signed by" lines with the sending domain. Repeat the test with an invoice sent by your software and with your contact form. A missing line, or a domain other than yours, points to a tool that needs checking.
Without DMARC, someone can invoice in your place
The address shown in the "From" field is declared by the sender themselves. DMARC exists precisely to verify it: Microsoft presents it as protection against the spoofed senders used in business email compromise fraud.
The Federal Office for Cyber Security (FOCS) describes two scams aimed at businesses. In CEO fraud, a forged email in the name of a senior manager demands an urgent payment. In business email compromise, where a business mailbox is hacked, invoices already sent are resent with a different IBAN. Among its recommendations: verify any unusual request by phone or in person.
With DMARC set to "quarantine" or "reject", a fake email using your exact address fails the checks at providers that apply your policy. Two blind spots remain. DMARC does not protect against a domain that looks like yours, such as your-cornpany.ch. Nor does it protect against a mailbox that has actually been hacked, since the fraudster is then writing from your real email account. Against that risk, the FOCS recommends enabling two-factor authentication wherever possible. Let your clients know, too, that you never change your bank details by email.
The flip side: a DMARC that is too strict blocks your own invoices
Going straight to "reject" is tempting. But the invoice sent from software you have not declared will then be refused at the client's end, and you will not know. Microsoft recommends a gradual approach, precisely to avoid legitimate messages being rejected, and warns that a few false positives are almost unavoidable. Google likewise advises starting with "none", then tightening over time.
The process has three stages:
- "none", with reports. Nothing changes for your emails. The reports reveal the services sending in your name; you fix them one by one.
- "quarantine". Failing messages are usually filed as spam, where they can still be retrieved. You can apply it to only a share of messages at first.
- "reject", once the reports show no more failures on your legitimate mail.
There is no official duration for each stage. Reports arrive as XML files that are hard to read as they are. Microsoft advises receiving them in a dedicated mailbox and naming one person to follow them.
The test. Open the Check MX tool in the Google Admin Toolbox and type in your domain name, no account needed. Google recommends it itself for validating a DMARC record. If a DMARC record exists, note the policy shown: none, quarantine or reject.
Setting up SPF, DKIM and DMARC: who to call, what to ask
Do not change your DNS yourself unless you know exactly what you are doing: one mistake can cut off all your email. Microsoft in fact advises anyone unfamiliar with these settings to ask their domain registrar for help. The person to contact is whoever manages your DNS zone: your hosting provider, the domain reseller or your IT person. Send them these questions in writing:
- Which services currently send emails using our domain? Email, website, invoicing, newsletter, online shop, online diary.
- Does our domain have a single SPF record, and does it cover all these services?
- Does each of these services sign with DKIM using our domain, rather than its own?
- Does the website form send from an address on our domain, with the visitor's address in the "Reply-to" field?
- Do we have a DMARC record? With which policy, and to which address do the reports go?
- Who reads these reports, and what timetable do you suggest for moving from none to quarantine, then to reject?
- Is two-factor authentication enabled on all our mailboxes?
Finally, ask for a written record of the resulting configuration. The day you add a tool that sends emails in your name, that is the document that will need updating. Then run the Gmail test again.