Skip to content
novasean.

Knowledge base

Email reporting

Interpret email authentication reports without over-reading one result.

Search all articles
Email reporting

Interpret a DMARC aggregate report safely

Read DMARC XML intervals, counts, aligned results and four dispositions before investigating a sender or changing policy.

Read the guide →
Email reporting

Diagnose mail rejected despite SPF passing

Use the remote rejection and received headers to distinguish SPF pass from DMARC alignment or other policy failures.

Read the guide →
Email reporting

Check why a mailbox can receive but not send

Separate an SMTP 535 login failure from connection, queue and recipient errors when a mailbox receives but cannot send.

Read the guide →
Email reporting

Check why a mailbox can send but not receive

Trace one external message through MX routing, server delivery, filtering and client retrieval.

Read the guide →
Email reporting

Set up an email client securely

Configure IMAP or POP and authenticated SMTP with the real provider's TLS settings; test both directions.

Read the guide →
Email reporting

Trace an email forwarding cycle without disabling protection

Map authorised forwarding rules, remove the returning edge and test one final delivery while preserving loop checks.

Read the guide →
Email reporting

Why mail lands in spam despite passing SPF and DKIM

Inspect recipient headers and filtering evidence when authenticated mail is accepted but placed in Spam or Junk.

Read the guide →
Email reporting

Why a forwarded email fails DMARC and how to diagnose it

Compare original and forwarded SPF, DKIM and DMARC results to find the broken alignment path.

Read the guide →
Email reporting

Resolve an IMAP or SMTP certificate name mismatch

Check the mail endpoint and certificate name before changing settings; keep TLS verification on and involve the operator when the correct server presents the wrong certificate.

Read the guide →
Email reporting

Fix an email rejected because the message is too large (552 5.3.4)

Read a 552 5.3.4 size bounce, identify which mail server rejected the message and choose a safe way to send the content.

Read the guide →