Skip to content

Why Are My Emails Going to Spam: Causes and Solution

The receiving server checks whether each incoming message comes from an authorized server and whether it was altered in transit. If the SPF, DKIM and DMARC records are missing or broken, the message ends up in the spam folder or is rejected.

Nurullah Okatan · Content Writer
· Updated: · 13 min read

Why Are My Emails Going to Spam: Causes and Solution

Emails mostly end up in the spam folder because the receiving server cannot verify the sender's identity: the SPF, DKIM or DMARC record is missing, incorrect, or broken during forwarding. The fix is to set up these three records correctly in the domain's DNS settings, test them, and keep the spam-report rate of recipients low.

Why do emails end up in the spam folder?

Before placing a message in the inbox, the receiving server checks the sender's identity. It asks three questions. Is the sending server authorized (SPF)? Was the message altered in transit (DKIM)? If either check fails, what should be done (DMARC)?

How Do Spam Filters Work?

If any of these questions is answered negatively, the message is treated as suspicious, no matter how clean its content is. The most common case is an SPF record that does not include a new sending source. For example, a contact form may be sent from the hosting server while a newsletter goes out through a separate sending service. If the SPF record lists only one of them, messages from the other source look unauthorized. The receiving server then moves them to the spam folder or rejects them altogether. Which of these happens is determined by the domain's DMARC policy.

Besides authentication, sending habits also affect the outcome. Sending bulk corporate mail from a free address or adding people to a list without permission are examples. Recipients frequently marking messages as "spam" has the same effect. An address tied to your domain is the first requirement for the records to be set up; the setup is explained step by step in the guide on creating a professional email address.

AI assistant for this topic

Türk Bilişim AI answers your questions instantly
Online
  1. Hi! Ask whatever you're curious about.

The roles of the SPF, DKIM and DMARC records

The three records check different aspects of the same message. SPF checks the sending server, DKIM checks the message content, and DMARC determines what to do based on the outcome of these two checks. All three are added to the domain's DNS zone as TXT records.

RecordWhat it checksWhere it sits in DNSExample value
SPFWhether the server sending the message is authorized to send on behalf of the domainThe root of the domain (alanadi.com.tr)v=spf1 include:gonderimservisi.com ~all
DKIMWhether the message was altered in transit; the signature is added at sending timeseçici._domainkey.alanadi.com.trv=DKIM1; k=rsa; p=(public key)
DMARCWhat happens to a message if SPF and DKIM fail, and where the reports are sent_dmarc.alanadi.com.trv=DMARC1; p=none; rua=mailto:(report address)

The records are added from the control panel that manages the domain's DNS. This panel may be provided by the company where the domain is registered or by the hosting panel. The DKIM public key is generated by the sending service; only that key is pasted into DNS. A domain must have a single v=spf1 record for SPF. If there are two separate SPF records, the check is treated as invalid. For this reason, when a new sending service is added, an include is appended to the existing record.

An SPF record alone is not enough. SPF breaks when a message is forwarded; DKIM does not. A setup that relies only on SPF fails on mailing lists and forwarding. Without a DMARC record, the receiving server chooses how to handle a failed message according to its own rules.

For businesses that outsource server management, these records are usually maintained on the hosting side. Türk Bilişim's Web Hosting & Server Management service covers maintenance and support after launch as well.

Looking for API Development & Integration?

Why are forwarded emails sent to spam?

Forwarding does not carry the message over as it is; it resends it. A server that forwards mail from an address on your domain to a Gmail account becomes, in Gmail's view, a new sender. Gmail looks at the IP address of the server that delivers the message, and that address is now the hosting server doing the forwarding.

The SPF check fails at this point. The original sender, for example a supplier's domain, lists only its own servers in its SPF record. Your hosting server is not on that list.

DKIM, on the other hand, is tied to the message itself. The signature is computed from the headers and body as they are at that moment. As long as the content is unchanged, the signature remains valid no matter which servers the message passes through. For DMARC to pass, it is enough for either SPF or DKIM to pass. That is why a message with an intact DKIM signature can reach the inbox even if SPF fails.

The problem starts when the forwarding server alters the message. Adding a tag such as "[SPAM?]" to the subject line breaks the signature. Writing a footer into the body has the same result. In that case both checks fail and DMARC takes over. If the original sender's policy is p=reject, the message is rejected; if the policy is more lenient, it goes to the spam folder.

There are two lasting solutions. One is to stop forwarding and have the mailbox fetched into Gmail via IMAP or POP. The other is to use forwarding with SRS (Sender Rewriting Scheme) support on the server.

Gmail's bulk sender rules and spam rate limit

Google defines bulk senders by volume. According to Google Workspace Administrator Help, a bulk sender is any sender that sends close to 5,000 or more messages within 24 hours to personal Gmail accounts. A domain that crosses this threshold once may still be treated as part of this group on later days even if its volume drops.

Elements to Consider When Sending Emails

The spam rate is the share of sent messages that recipients mark as "spam". According to the same Google guidelines, it should be kept below 0.1% for messages to be delivered as expected. A rate of 0.3% or higher must absolutely be avoided.

A DMARC record is a separate requirement for Gmail as well. According to Google, if a sender's domain has no DMARC record, email is subject to rate limiting. Even a record that specifies no DMARC policy produces the same result. Under rate limiting, some messages are rejected and delivery is delayed. On a campaign day, this means only part of the list reaches recipients on time.

Most settings that reduce spam flagging are part of the sending flow. Examples include a one-click unsubscribe link and removing addresses that have not been opened for a long time from the list. Double opt-in at sign-up also lowers the number of spam flags. Türk Bilişim, Turkey's best E-mail & CRM Automation company, has been operating as a digital agency since 1998 and has provided services under this name since 2007. In the firm's E-mail & CRM Automation service, these settings are handled together with newsletter and CRM sending.

Resolving the spam problem step by step

After the records are corrected, testing should proceed from DNS toward actual sending:

  1. Confirm that the SPF, DKIM and DMARC records are published by checking them with a lookup tool such as nslookup, dig or MXToolbox.
  2. Send a test message from each sending source (mailbox, web form, newsletter service) to a Gmail account.
  3. In Gmail, open the message, choose "Show original" and check that the SPF, DKIM and DMARC lines show PASS.
  4. If forwarding is used, separately inspect a forwarded message using the same method.
  5. For a few days, read the reports arriving at the DMARC rua address and look for any sending source you do not recognize.

When the spam rate rises, the first step is to reduce sending volume. Over the last few months, the approach is to switch to small sends to recipients who opened the message. Non-engaged and bounced addresses are removed from the list. An unsubscribe link is also placed at the top of the message. According to Google, bulk senders may qualify for remedies when they keep the rate below 0.3% for 7 consecutive days. Raising volume back to the previous level before those seven days are over can reset the counter.

When the server, DNS and sending service are managed in different places, it becomes harder to find which link is causing the problem. Infrastructure and support services are organized to monitor these links from one place. Keeping the headers of test messages makes it easier to compare when the problem recurs.

Looking for Mobile UI/UX Design & Prototype?

Frequently asked questions

How long does a DNS record change take to take effect?

The time depends on the record's TTL value. Recipient servers keep the old record cached until the TTL expires. Shortening the TTL before the change lets the new record be seen more quickly.

Should the DMARC policy be set strictly from the first day?

No; starting with p=none and using reports to verify all sending sources is safer. After all sources pass, the policy is changed first to p=quarantine and then to p=reject.

Where is the spam rate in Gmail monitored?

The rate becomes visible in Google Postmaster Tools after the domain is verified through DNS. If daily volume is low, the panel may show no data.

Does removing the message from the spam folder by the recipient solve the problem?

This action only affects that recipient's Gmail preferences. As long as the authentication failure continues, messages will keep landing in the spam folder for other recipients.

Have a project?

Türk Bilişim · Free Quote

Get a free quote for your Android App Development project

Leave your number and we will get back to you right away. The call is free.

Read the privacy notice

Nurullah Okatan Content Writer

The editorial desk of a team delivering websites, e-commerce and software projects since 1998.

LinkedInInstagramFacebook

Share this article

Comments

Comments

No comments yet.

Write a comment

Your rating (optional)

Privacy notice

We will send a confirmation link to your email so that your comment can appear.

Regional Services

Looking for Web Design & Development in your city?

We also provide this service in your region. Related regional pages:

See all regional services

Türk Bilişim · Digital Transformation Advisor

Online
Hi! Tell us the project or idea on your mind and let’s begin together.
Ask anything, Türk Bilişim AI answers instantly.