Why do my emails go to spam, for a company in Algeria (2027): our quotes and invoices end up in junk although the mail service is set up, reading the headers, finding who really sends, reputation, the website's messages, bulk mail

“Our quotes and invoices go out, but our customers find them in junk, or do not find them at all. Our IT person assures us the mail service is set up properly. The website's order confirmations do not arrive either, and since our last mailing to all customers, it has got worse. Why do our emails go to spam, and how do we get out?” A message is judged three times: on its proofs, on the reputation of whoever sends it, and on what recipients do with it. When the mail service is set up, the culprit is almost always another sender: the website, or the bulk mailing.

Symloop13 min read
Why my emails go to spam and how to get outRead the headers, find who really sends, repair the proofs, separate the streams, keep your reputationBUSINESS EMAIL · ALGERIA · 2027Why my emails go to spamand how to get outRead the headers, find who really sends, repair the proofs,separate the streams, keep your reputationQUOTE IN JUNKthe customer never sees itINBOXthree proofs, one reputationsymloop.com

Short answer. A message is judged three times: on its proofs (SPF, DKIM, DMARC), on the reputation of the domain and server sending it, and on what recipients do with it. If the mail service is set up and your emails still land in junk, look for another sender: the website, which often sends through the host's server without being authorised, or the bulk mailing, sent from the ordinary mailbox. The diagnosis is read in the headers of a message that went to spam. The remedy: declare each sender, give each use its own path, and stay far from 0.3% of complaints. Four weeks in the example.

This page is for the manager whose quotes, invoices or website messages do not arrive, and for the founder based in France whose customers in Algeria, or the reverse, do not receive their messages. The rules quoted come from public sources: Google's email sender guidelines, the best practices published by Yahoo, and encyclopaedia definitions. The company, its two messages, its three streams and its calendar are a constructed example. This page does not go back over setting up SPF, DKIM and DMARC, explained in the guide to business email, and does not cover the legal rules on prospecting by email: see your adviser.

Getting out of junk: diagnosing in six steps

The first step is accented: recover a message that went to spam.

Figure 1 · The accented step is the first: recover a message that landed in junk, whole, with its headers. Without it, fixes are guesses. The next four steps are read from it; the last is the repair.

Start from evidence. You do not diagnose from a story, but from a message: ask a customer to forward you, as an attachment, a message that landed in junk. Its headers say which server sent it and what the customer's server concluded. Do the same for three messages: a quote written by hand, a confirmation from the website, a bulk mailing. Three questions. Who sent it? Do the proofs pass? And if they pass, what is the sender's reputation worth?

Spam, seen from the other side. Email spam refers to unsolicited messages sent in bulk. Your customer's server does not read your intentions: it compares your message with what it has already seen, and with what its users have reported. Published rules. The large mailbox providers publish their requirements: Google lists them for all senders, and adds more for those who send more than 5,000 messages per day to Gmail accounts. A small company is far from that volume; the same checks nevertheless apply to each of its messages.

01

Two messages, the same sender shown

The figure compares the headers of two messages received by the same customer.

Figure 2 · Two messages received the same day by the same customer, with the same sender address. The quote leaves from the mail service: the three proofs pass. The confirmation leaves from the website’s server, which the domain never declared: they fail. Constructed example, fictitious names.

Where it is written. A header field named Authentication-Results lets the receiving server record the results of the checks it carried out. In the recipient's mail program, the menu “show original” or “view source” displays it. Look for three words, spf, dkim, dmarc, followed by pass or fail. Who sent it. The Received line names the server the message left from. In the example, the order confirmation did not leave from the mail service: it left from the server that hosts the website.

Why the website fails. A website sends messages, confirmations, forms, forgotten passwords, most often through its host's server. If the domain does not declare that server, SPF fails; if the website does not sign, DKIM is missing; and DMARC, which requires these proofs to apply to the domain shown, fails in turn. Google sums it up: all senders, SPF or DKIM; bulk senders, SPF, DKIM, and DMARC. The form. That is also why a form's acknowledgement does not arrive, as described in the guide to online forms.

«The fault is rarely the mail service: it is a sender nobody declared.»
02

Six causes, their sign, and what is done

The figure gives, for each cause, the sign that betrays it and the fix.

Figure 3 · Six causes, in the order they are checked. The first three are read in the headers of a single message; the next three are read in the way the company sends. Most often, two causes add up.

The shared address. In shared web hosting, many websites reside on one web server, and may share a single IP address. If one of them sends spam, the whole address carries the mark. A DNS blocklist is a service mail servers query to check whether a sending host's IP address is listed for email spam: yours can be on it without your having sent anything. What is done. The website's messages are sent through a sending service whose job it is, and removal is requested afterwards. Changing host is another decision, described in the guide to changing host.

Bounces. A bounce message is an automated message informing the sender that a previous message has not been delivered. A list that produces many of them tells the other server that you write to addresses you do not know. Blind copy. Three hundred customers in blind copy from the manager's mailbox is a bulk mailing with no unsubscribe, sent from the address that also sends the quotes. Content. Plain text, a link to the document rather than a ten-megabyte attachment, no shortened link: a message that looks like those people report is treated like them. Your customers, for their part, are learning to be wary, as the guide to fake emails recalls.

03

What the recipient's server looks at, in five layers

The accented layer is reputation.

Figure 4 · The accented layer is reputation. Proofs are set up in a few days; reputation is built on what recipients do with your messages, and is won back over weeks.

Before the message. The sending server must have a name that checks out both ways: the address leads to the name, and the name leads back to the address. Google asks it of all senders: valid forward and reverse DNS records. Reputation. It attaches to the domain and to the sending address, and is built on what recipients do with your messages. Reports as junk are at its heart: a feedback loop is the mechanism by which a mailbox provider forwards its users' complaints to the sender's organisation.

The threshold. Google asks to keep spam rates below 0.10% and to avoid ever reaching 0.30%; Yahoo sets the same limit of 0.3%. Three complaints per thousand messages are therefore enough. For marketing and subscribed messages, both require one-click unsubscribe, with a clearly visible link in the message. Consent. A list people chose to join, rather than being added to by default, produces few complaints: it is the only lasting protection.

04

Three streams, three paths

The figure shows the same company, before and after its streams are separated.

Figure 5 · Before, quotes, the website’s messages and the newsletter leave from the same place and share one reputation. After, each use has its path, its address and its reputation: complaints about the newsletter no longer touch the quotes. Constructed example.

Three uses. People's mail: quotes, invoices, replies. The website's messages, called transactional: they are triggered by a customer's action, an order, a registration, a password. Bulk mail: newsletter, offers. Why separate them. Google recommends it: if you must send from multiple IP addresses, use a different IP address for each message type; and messages of the same category should have the same From address. In the example, each use gets its sub-domain and its sending service: the newsletter's reputation no longer mixes with the quotes'.

Raise it gently. A new path has no past. Google advises starting with a low sending volume to engaged users, and slowly increasing the volume over time. The right channel. Not everything has to go by email: a sign-in code or an appointment reminder arrives better by SMS or WhatsApp, as in the guide to notifications. On a shop. Order confirmations follow the same rule, described in the guide to creating an e-commerce site.

«A complaint about the newsletter must never cost a quote.»
05

Four weeks to get out of junk, in 2027

Four weeks in the example, the first for the diagnosis.

  • What the manager receives: the diagnosis on three real messages, with headers as evidence; the list of everything that sends in the domain's name; each sender declared and signed; the website connected to a sending service; one path per use; lists cleaned, with unsubscribe; a monthly measure.
  • What the company no longer does: call the customer to tell them to look in junk, write to three hundred people in blind copy, let the website send through a server nobody declared, attach ten megabytes to a quote.
  • What is measured: test messages where all three proofs pass, the complaint rate of bulk mailings, bounces per mailing, presence of the sending address on blocklists, undeclared senders found in the reports.
  • What Symloop does: reading the headers and the diagnosis, the inventory of senders, declaring and signing each one, connecting the website and your applications to a sending service, separating streams by address and sub-domain, cleaning lists, raising volume, then measuring each month.
Figure 6 · Four weeks in the example. The accented period is the first: the diagnosis, on evidence. Proofs are repaired quickly; raising the volume of bulk mail takes the rest of the time. Indicative durations of a constructed example.

The order. In the first week, the diagnosis: three messages, their headers, and the list of everything that sends in the domain's name. A forgotten sender is almost always found: the website, the invoicing software, the copier that sends scans. Proofs are repaired in a few days, provided you control the domain, as the guide to the domain name recalls. Reputation is won back over weeks. Once streams are separated and lists cleaned, bulk mail resumes in small batches.

Measure. Each month: the complaint rate of bulk mailings, the bounces, and three test messages re-read in two mailboxes from different providers, headers included. What makes it hold. One rule: nothing sends in the domain's name without being on the list of senders, and nobody writes to more than twenty recipients from their own mailbox.

Why do my emails go to spam?
For one of three reasons: a sending proof fails, the reputation of the domain or server is bad, or the message looks like those recipients report. The headers of a message that landed in junk say which: look for spf, dkim and dmarc, followed by pass or fail.
How do I find out why an email went to spam?
Ask the recipient to forward it to you as an attachment, then open “show original”. The Received line says which server sent it; the Authentication-Results field says whether SPF, DKIM and DMARC passed. If everything passes, the cause is reputation or content.
SPF, DKIM and DMARC are set up: why does it go on?
Because they are set up for the mail service, not for everything that sends. The website, the invoicing software or a bulk mailing tool often go through another server, never declared. Or the proofs pass, and it is reputation, damaged by complaints, that gets the message filed as junk.
Why do the emails from my website not arrive?
The website most often sends through its host's server, which your domain has not authorised, and without a signature. On shared hosting, it also shares its address with other sites. The fix: send these messages through a declared sending service, under a dedicated address.
What is a blocklist, and how do you get off it?
It is a service mail servers query to check whether a sender's address is listed for spam. You get off it by fixing the cause, then asking the list for removal. If the address is shared with other sites, change the sending path.
Can a newsletter be sent from Outlook or Gmail?
No, not beyond a few recipients. A bulk mailing in blind copy has no unsubscribe link, no measure of complaints, and it leaves from the address that sends your quotes. Use a bulk sending tool, under a separate address and sub-domain.
What complaint rate must not be exceeded?
Google asks to stay below 0.10% of reported messages and never to reach 0.30%; Yahoo also sets 0.3%. That is three complaints per thousand messages. Beyond that, all messages from the same sender risk the junk folder.
Is a sub-domain needed for bulk mail?
It is the safest. A sub-domain and an address per use give each stream its own reputation: a badly targeted campaign no longer drags the quotes and invoices with it. Google, for its part, recommends one From address per category of messages.
Do attachments send emails to spam?
A heavy file, an unusual format or a compressed file contribute, especially from a little-known sender. Prefer a link to the document, or a light PDF, and a text that says clearly what the message contains.
How long does it take to get out of spam?
Four weeks in this page's example. Proofs are repaired in a few days; reputation is won back more slowly, by resuming bulk mail in small batches and keeping complaints well below 0.3%.
Forward us, as an attachment, a message that landed in junk: the diagnosis starts with its headers

Quotes customers cannot find, website confirmations that never arrive, a mailing to all customers followed by a week in junk, or a founder in France whose messages do not reach Algeria: we read, we declare, we separate

Reading the headers, inventory of senders, each one declared and signed, website and applications connected to a sending service, one path per use, lists cleaned, volume raised, a monthly measure. We work from Algiers and Sétif, in French, Arabic and English.