Quick troubleshooting view
Messages sent by the domain are frequently classified as unwanted.
- Check SPF
- Check for DKIM
- Check DMARC
- Correct SPF/DKIM/DMARC
- Reduce behaviors of send and Similar to spam
- Use a service of mail adapted to mass campaigns
Contextual technician plan
Check I, SPF record and authorized sources.
Resolve-Dns Name example.fr -Type TXTThe command should complete without an unexpected error and return data consistent with the intended service.
If the result is normal, keep this layer lower in the hypothesis ranking and continue with the next discriminating check.
If the result is abnormal, preserve the output and investigate this layer before making broader changes.
Confirm that messages are signed and that the DNS key is correct.
Resolve-Dns(1) _dmarc.example.fr -Type TXTThe command should complete without an unexpected error and return data consistent with the intended service.
If the result is normal, keep this layer lower in the hypothesis ranking and continue with the next discriminating check.
If the result is abnormal, preserve the output and investigate this layer before making broader changes.
Control the alignment and policy.
“Check DMARC” should produce an observation that clearly confirms or rules out “Content assimilated to spam”.
If the observation is normal, lower “Content assimilated to spam” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “Content assimilated to spam” first. Related action: Use a service of mail adapted to mass campaigns.
Analyze Augustation-2011s and any possible scores.
“Examine headers” should produce an observation that clearly confirms or rules out “Mailing lists not well managed”.
If the observation is normal, lower “Mailing lists not well managed” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “Mailing lists not well managed” first.
If the problem is widespread, check the indicators available from the supplier.
“Checking the reputation” should produce an observation that clearly confirms or rules out “Volume or behaviour of unusual shipment”.
If the observation is normal, lower “Volume or behaviour of unusual shipment” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “Volume or behaviour of unusual shipment” first.
Repeat the same validation test after the correction and confirm the original symptom is gone. Validate stability before closing the incident.
Before changing configuration, record the current value and a way back.
Escalad to the courier provider if the authentication is correct but reputation is deteriorating.
Messages sent by the domain are frequently classified as unwanted.
Causes probables
- Incomplete FPS/DKIM/DMARC
- IP reputation or domain
- Content assimilated to spam
- Mailing lists not well managed
- Volume or behaviour of unusual shipment
Diagnostic étape par étape
- 1
Check SPF
Check I, SPF record and authorized sources.
- 2
Check for DKIM
Confirm that messages are signed and that the DNS key is correct.
- 3
Check DMARC
Control the alignment and policy.
- 4
Examine headers
Analyze Augustation-2011s and any possible scores.
- 5
Checking the reputation
If the problem is widespread, check the indicators available from the supplier.
Commands utiles
Resolve-Dns Name example.fr -Type TXTResolve-Dns(1) _dmarc.example.fr -Type TXTSolutions possibles
- Correct SPF/DKIM/DMARC
- Reduce behaviors of send and Similar to spam
- Use a service of mail adapted to mass campaigns
Escalad to the courier provider if the authentication is correct but reputation is deteriorating.