If company messages arrive in spam, the cause may relate to domain authentication, sender reputation, content, or sending method. Correct configuration of SPF, DKIM, and DMARC assists with verifying sender identity but does not guarantee all messages land in the inbox.
Quick answer: First, list all services sending on behalf of the domain: regular email, site, invoicing, and communication platforms. Only then modify domain records to avoid blocking legitimate senders.
1. Determine if the message is rejected or classified as spam
A message arriving in spam is different from one rejected by the server or remaining in the sending app. Keep automatic error replies and their codes, if any. Compare recipients across different services and verify the entered address.
Do not repeatedly send dozens of test messages to clients. Use verification addresses you control and record the time, sender, and result of each test.
2. What role does each mechanism have
- SPF (Sender Policy Framework): indicates servers authorized to send for the domain verified during delivery.
- DKIM (DomainKeys Identified Mail): attaches a verifiable signature to the message; the public key is published in DNS, and the private key remains with the sending service.
- DMARC (Domain-based Message Authentication, Reporting and Conformance): checks the alignment of the visible sender domain with SPF or DKIM authentication and allows a policy for handling messages that fail verification.
DNS (Domain Name System) publishes the necessary records. Do not copy values from another domain: these must be provided by your actual services.
3. Check the messages sent by the site
A form may correctly save the request in WordPress but fail to deliver it by email. Check saving, sending, and receiving separately. SMTP configuration must use the server, port, encryption, and authentication specified by the provider.
Do not put the client's address in the From field as if the site is authorized to send on behalf of their domain. Use an authorized sender of the company and, when appropriate, the client's address in Reply-To.
4. Apply changes progressively
- Save existing DNS records and the list of senders.
- Check SPF for the relevant domain; two separate SPF records do not automatically combine into a valid one.
- Enable DKIM at each authorized service and verify the selector indicated by it.
- Configure DMARC after inventory and alignment verification. Assess reports before applying a strict policy.
- Test again the usual messages and those generated by the site.
Do not change name servers or all domain records for a specific email issue.
5. Check sending practices as well
Authentication does not compensate for purchased lists, recipients who did not request messages, sudden volume increases, or problematic links. Keep the list clean and comply with provider requirements for the type of communication used.
iTechServiceTM can check the domain's email and the site's messages online, for clients from Romania and abroad. Send the domain, provider, and error, without passwords or private keys.
Frequently asked questions
Do SPF and DKIM guarantee that the message does not go to spam?
No. They are authentication checks, and filtering also considers other factors.
If the form displays success, did the email arrive?
Not necessarily. Saving the request, server acceptance of the message, and delivery to the recipient must be checked separately.
Can I activate a DMARC reject policy directly?
First check all legitimate senders and alignment. A strict policy applied prematurely can reject legitimate messages.
Documentation and sources
Supplementary guides: Tutorial on how to check if your email was compromised in a data breach · Gmail Tips & Tricks: 15 useful features worth using · what to prepare before creating a website
Discuss your situation with iTechServiceTM
Describe the equipment or project and what you want to achieve. Suitable services, conditions and costs are established before intervention.