Estimated reading time : 6 min · Published
Separate email submission, transfer and reading
Email can pass through several servers. SMTP acceptance does not prove the recipient read it; identify which stage each check observes.
- Creation
The site prepares the message and intended recipient address.
- Submission
The sending service accepts or rejects responsibility.
- Transfer
Servers relay the message or report a problem.
- Recipient mailbox
Check the mailbox, its folders and its rules.
Fictional teaching scenarios to adapt to your system. This page performs no operation on your website.
Open the situation you want to check
The log records SMTP acceptance
- What is known
- A server accepted responsibility for the message at that stage.
- The next check
- Identify the responding server and examine later events; do not present acceptance as evidence of reading.
The notification is missing from the main inbox
- What is known
- Its absence there does not yet locate the cause.
- The next check
- Check the actual address, available rejection notices, spam folders and classification rules in the test mailbox.
Messages arrive, but reach the former team
- What is known
- Transport can work while business handling is wrong.
- The next check
- Confirm active recipients and absence cover, then follow a test enquiry through to ownership.
Failure is reported after acceptance
- What is known
- The first server accepted the message; a later event reports a delivery problem.
- The next check
- Reconcile the events without erasing the initial acceptance. Identify the failing stage and affected recipient before deciding on another send.
- Evidence to retain
- Test message reference, observed servers, times with timezone and available failure reason; no private content.
Technical reference : RFC 5321 · SMTP · Consulted .
Inventory messages and senders
List contact notifications, confirmations, account recovery, invoices and newsletters. For each stream, record its sending service, domain, recipient, expected volume and person responsible for errors. An essential transactional message and a promotional campaign require different decisions.
For a contact form, use a From address on a domain authorised by the sending service. A validated visitor address may be used as Reply-To; using it as From means sending on behalf of a domain you do not control. Provide a monitored address for replies.
Have domain authentication checked
SPF describes authorised senders, DKIM supports signature verification and DMARC evaluates alignment with the domain displayed in From. They complement one another but do not guarantee inbox placement. Requirements depend on the recipient service and sending volume: consult current provider guidance.
Ask the email owner to compare domains used by the website, business tools and automated messages. Adding a sending platform may require DNS changes. Inventory legitimate streams and arrange observation before adopting a rejection policy. Public pages must never contain connection credentials or private keys.
Fictional authentication example: From contains contact@example.com, the message is valid and an applicable DMARC policy exists. To simplify comparison, this scenario uses strict alignment for SPF and DKIM: domains must be identical to example.com. The table starts with authentication results already verified at the receiving side; copying a “pass” line into a message is not that verification.
A positive SPF or DKIM result for example.net does not by itself authenticate example.com in From. Conversely, one successful and aligned mechanism can yield DMARC pass even when the other fails. This does not guarantee inbox placement. RFC 9989, published in May 2026, supersedes RFC 7489 among others; have the email administrator verify actual streams rather than copying these example domains into DNS.
Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.
| SPF result and MAIL FROM domain | DKIM result and d domain | Expected DMARC outcome |
|---|---|---|
| pass · example.net | No valid signature | fail: no successful aligned mechanism |
| fail | pass · example.com | pass: successful aligned DKIM |
| pass · example.com | fail | pass: successful aligned SPF |
| pass · example.net | pass · example.net | fail: both domains differ from From |
- RFC 9989 : DMARC / Identifier Alignment
RFC 9989, consulted 22 October 2026: identifier alignment. These simplified cases are not a DNS configuration to apply.
Test the whole journey
Use consenting test addresses to submit an enquiry on a phone, then check storage, the internal notification, visitor confirmation and the ability to reply. Try several mailbox providers. Inspect spam folders, authentication headers and links; one test with the sender’s own mailbox does not cover other recipients.
Include an invalid address, a temporary refusal, a blocked recipient and a retry after failure. Retain a test reference, time and observed state. Avoid copying private message bodies into logs. Acceptance by the email service must not be described as proof that the message was read.
Handle errors and preserve continuity
Distinguish permanent bounces from temporary incidents using the provider’s returned codes. Define retry handling and a process for invalid destinations. For newsletters, test unsubscribe and its effect on the next campaign. A contact enquiry is not an agreement to join a mailing list.
If an enquiry was recorded but email failed, give the team a way to retrieve it without forcing the visitor to start again. Repeat tests after DNS migration, provider changes or form updates. Deliver an inventory of streams, states, test results and the person responsible for alerts.
Diagnosis case: the request exists but the notification is missing
Synthetic example: a request has a reference in the receiving system, but the team gets no email. Check the sending log against that reference, then distinguish a message never sent, provider rejection and a message accepted but absent from the inbox. Do not ask the visitor to resubmit before establishing whether the request was saved: this can create a duplicate.
For recovery, record reference, time, sending state and the person handling the request. If another send is needed, keep one request and trace the new attempt. Changing mail providers calls for a test separate from form storage. Acceptance must identify how the team retrieves requests when the email channel is unavailable.
Read SMTP codes without confusing acceptance with reading
For diagnosis, record the responding server and relevant command, not just a “sent” label. The codes below belong to SMTP: HTTP 200 from a sending API describes a different layer and does not replace this log.
Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.
| Reply | Meaning at this stage | Next diagnostic step |
|---|---|---|
| 250 after the end of DATA | The server accepts responsibility for the message; this proves neither main-inbox placement nor reading. | Retain the tracking identifier and examine later delivery events. |
| 450 | The mailbox is temporarily unavailable; the exact reason depends on the accompanying text. | Check the service’s retry policy and final outcome instead of multiplying manual sends. |
| 550 | The mailbox is unavailable for reasons such as an unknown address, denied access or receiving policy. | Read the full diagnostic; do not automatically conclude that the address contains a typo. |
- RFC 5321 · 4.2.3 / 4.2.5
RFC 5321 documents these codes and responsibility after DATA. Map a provider’s status to that specific stage.
Identify the DMARC reference and the right type of report
Since May 2026, RFC 9989 has defined the DMARC protocol. RFC 9990 covers aggregate reports and RFC 9991 covers reports on individual failed messages. These three documents supersede RFC 7489.
Use aggregate reports to identify sending sources and alignment problems. When checking a web form, also retain evidence of what arrived in the destination inbox.
Reference documents
- RFC 5321 · SMTP
- Gmail: official email sender guidelines · Source consulted
- Cloudflare: DNS TXT records
- RFC 5321 · 4.2.3 / 4.2.5 · Source consulted
Content updated on
