# Your Quotes Keep Landing in Spam? Here's Why (and How to Fix It)
Table of Contents
You send a quote, you wait, and nobody replies. The natural conclusion is that the client wasn’t interested. Often, though, the truth is different: that email never arrived. It landed in the spam folder, or it was rejected before it even reached the inbox. A deal lost without even knowing you lost it.
It isn’t bad luck, and it is almost never about what you wrote. In the vast majority of cases it is a precise, fixable technical problem in how your domain proves its own identity. Gmail, Outlook and the other big providers decide in a fraction of a second whether to trust an email, and if your domain can’t prove it is really you, the default answer is: into spam.
The good news is that this problem can be diagnosed in half an hour and fixed in an afternoon, and it does not require changing email provider. Let’s look at why it happens and how to tell if it affects you too.
Why a legitimate email ends up in spam
Email has a birth defect: the sender is easy to forge. The address shown in the “From” field is like a name written by hand on the back of an envelope, nothing guarantees it on its own. That is why providers filter aggressively, and a sender they can’t verify is, by definition, suspicious.
To decide, they check three public “documents” of your domain: SPF, DKIM and DMARC. If they are missing, broken or not aligned, your email starts at a disadvantage. On top of that comes reputation: the IP address you send from has a history, and if spam went out from there in the past, or if your domain has never been authenticated, filters treat you with suspicion.
Think of customs. A parcel with its paperwork in order goes through; one without a verifiable sender gets opened, set aside or returned. Your email is that parcel, and the three checks are its paperwork.
The three checks that decide whether you get read
Without going technical, here is what each one does:
- SPF declares which servers are allowed to send for your domain. If the email comes from a server not on the list, it is suspicious.
- DKIM adds a signature proving the message really comes from you and wasn’t altered along the way.
- DMARC ties the first two to the address the client actually sees, tells the provider what to do when something doesn’t add up, and sends you reports on who is sending in your name.
Anyone who wants the details will find them in the full guide on what SPF, DKIM and DMARC are. The point for you is a different one: since 2024 Gmail and Yahoo explicitly require them from senders of any real volume, and use them as a signal for everyone. Not having them set up today means sending uphill.
How to tell if it’s your case, without being technical
There are signs it’s time to look under the hood:
- Clients tell you “I never got anything”, when you did send the email.
- Quotes to Gmail, Outlook or corporate addresses go unanswered more than usual.
- Transactional emails from your app or e-commerce (order confirmations, password resets) don’t arrive.
- Years ago someone connected a newsletter platform or a CRM to your domain, and nobody checked the configuration since.
The quick test you can run yourself: send a message to a Gmail address and to an Outlook one, and see if it lands in spam. Then open the received email and look, under “show original” or “details”, for the lines that say spf=pass or spf=fail, dkim=pass or dkim=fail. A “fail” is the warning bell. There are also free online tools that, given your domain, tell you whether the three records exist and are consistent.
What does NOT fix the problem
Worth stating, because these are the wrong turns people try most often:
- Buying more powerful hosting or a bigger server is beside the point: deliverability is a matter of DNS and reputation, not horsepower.
- Rewriting the email text or dropping attachments helps little if the domain isn’t authenticated: the filter decides before it reads the content.
- Adding “this is not spam” in the footer has no effect on filters whatsoever.
A domain’s reputation takes months to build and burns in an afternoon, for example through a compromised mailbox sending spam without your knowledge. That is why the right move is to configure the three checks properly, start DMARC in observe-only mode to learn who really sends in your name, and only then tighten the rules. First you look, then you decide.
In short
Quotes ending up in spam are rarely bad luck: they are your domain failing to prove it is you. The combination of SPF, DKIM, DMARC and reputation decides whether a legitimate email reaches the inbox or gets discarded. It is a problem you can diagnose and fix in an afternoon, without changing provider, and every email that gets delivered again is a deal you were silently losing. If you would rather not handle it yourself, it is exactly the kind of work we do.
