Why your business emails go to spam: what to check first

Business email hosting

The short answer

First establish whether the message was rejected, delayed, quarantined or delivered to spam. Collect an affected message's headers or bounce details, identify the system that actually sent it and check SPF, DKIM and DMARC for that route. Compare ordinary mailbox mail with website or billing notifications. Authentication is important but does not guarantee inbox placement; recipient filtering, sender reputation, message content and compromised accounts can also affect delivery.

A quote sent from an app and a reply written in webmail can display the same business address while taking different paths. Diagnose the failing path before changing every setting on the domain.

Establish what happened to one affected message

Ask for a concrete example: sending time, recipient domain, sending app and whether there is a bounce or delivery report. A message in spam reached a receiving system. A rejected message may never appear in the recipient's mailbox. A quarantined message may require their administrator to release or inspect it.

Preserve the full error text and headers for the authorized person investigating. A screenshot saying 'not received' is not enough to identify the cause. Redact private content before sharing evidence. If the message is urgent, use another agreed contact method while investigating rather than repeatedly resending the same message and hoping the result changes.

Identify the system that actually sent the email

Compare the failing route with a working route
Message typeWhat to check
Webmail replyMailbox sending service and authentication results.
Phone or desktop emailConfigured outgoing account and actual sender identity.
Website notificationWhether the site generated it and which service sent it.
Quote or invoice emailThe business app's sending route and domain setup.
Forwarded messageThe extra delivery step and resulting authentication checks.

If only one route fails, focus there first. A working mailbox does not establish that an invoice app is authorized to send using the same domain.

Check SPF, DKIM and DMARC without treating them as magic switches

SPF checks whether the sending host is authorized for the relevant envelope domain. DKIM verifies a domain signature over selected message data. DMARC evaluates alignment with the visible From domain using a passing aligned SPF or DKIM result. The FTC gives a small-business overview; the current DMARC standard describes the validation boundary.

Ask the administrator to inspect results from the affected message, not merely whether DNS contains records with familiar names. A signature can pass for a domain that does not align with the visible sender. A DMARC pass validates domain use, not the trustworthiness of every message, and receiving systems can still apply their own filtering.

Inventory legitimate senders before editing authentication

List staff mail, website forms, quoting tools and billing notifications that send using the domain. Use each service's account-specific instructions and have the DNS administrator review the combined setup. Do not paste a new SPF record beside an existing one: the SPF standard prohibits multiple selectable SPF records for the same name.

Do not switch straight to a stricter DMARC policy without understanding current legitimate traffic. Check the authorized senders and alignment first, then agree an appropriate rollout. Incoming MX routing is not a general fix for outgoing spam placement. Keep a record of changes so a new failure can be compared with the previous configuration.

Illustrative example: replies arrive, invoice notifications do not

A fictional business finds that webmail replies reach a recipient, but its invoice notifications go to spam. The notifications display the same From address. Inspection shows the billing app uses a separate sending service whose domain authentication has not been configured for that route.

The administrator follows that app's supported setup, sends a controlled test and reviews the new headers. This identifies a configuration issue worth fixing; it does not prove every future message will reach the inbox. The team also checks the message itself and asks the recipient whether a local policy affected it. No change of website or mailbox provider is assumed necessary.

If authentication passes, inspect content, reputation and account activity

Compare a short expected message with the affected message. Look at unusual links, attachment types, mismatched signatures and unexpected sending patterns. Keep testing limited and relevant to ordinary business correspondence; generating a burst of test mail is not a substitute for diagnosis.

If activity is unfamiliar, treat possible account compromise as a separate security issue. Review authorized access, sending apps and forwarding rules, and follow the service's recovery process. Do not solve it by disabling filtering. A recipient administrator may be able to explain a local rejection or quarantine. Avoid blanket requests to bypass all safety controls or claims that a particular phrase guarantees spam placement.

Bring useful evidence to an email setup discussion

Prepare the affected route, time, recipient domain, error code and sanitized headers. Note whether the problem affects one recipient or several, one app or all apps, and whether it began after a DNS or sending change. This makes a service discussion more useful than 'our email is broken.'

Our business email hosting starts at $5 per mailbox per month with 5 GB each, including webmail, compatible apps and spam and virus filtering. It is optional alongside websites or other business services. We can discuss your mailbox setup and the configuration involved; changing hosting alone is not a guarantee of inbox placement or a substitute for checking the actual sending path.

A few follow-up questions

Does passing SPF, DKIM and DMARC guarantee inbox delivery?

No. They help validate authorized domain use, but receiving systems also evaluate other signals and local policies. Inspect the affected message and route rather than treating a pass as a complete delivery diagnosis.

Should I ask the customer to mark the message as not spam?

That can help them recover an expected message and provide feedback within their service. It does not repair a broken sending configuration or justify bypassing their organization's security policy.

Is a contact-form notification problem always an email-hosting problem?

No. The form may fail before a message is generated, or the website may use a different sender. Check capture, message creation and delivery separately before changing mailbox settings.

Sources and further reading

Check the route behind the missing message

Tell us which app sends the affected mail, when it happened and whether there is a bounce. We can discuss your business email setup; do not send passwords or private message contents.

Discuss your email setup See what our business email hosting service includes
Website by TelosOps