What this code means
The receiving system permanently rejected the message because it could not complete the RRVS evaluation: the required timestamp had not been recorded. Do not retry the same attempt unchanged.
Technical meaning
The X.7.19 pattern is returned when a message contains a Require-Recipient-Valid-Since field or RRVS extension and the receiving system cannot complete the requested evaluation because the required timestamp was not recorded. The message originator must decide whether to reissue the message without RRVS protection. Code 5.7.19 applies this meaning in the permanent-failure class.
Delivery status
The leading digit 5 denotes a permanent failure of the current attempt. The code alone does not explain why the timestamp was not recorded and does not establish that the recipient address is invalid.
- Class
- Permanent failure
- Retry
- Do not retry unchanged
- Suppression
- Check the full context
Retry decision
Operational recommendation: stop automatic and manual retries of the same unchanged attempt. Consider a new, controlled send only after assessing the risk and making an informed decision about whether policy permits sending without RRVS protection; first confirm the recipient and check suppression again.
Suppression decision
Operational recommendation: do not automatically add the address or domain to a suppression list based on 5.7.19 alone. Inspect the complete response, RRVS context, and other delivery events, then make the suppression decision according to the confirmed cause and applicable policy.
Common causes
- The message contained a Require-Recipient-Valid-Since field or RRVS extension, but the receiving system had not recorded the timestamp required to perform the requested evaluation.
Diagnostic steps
- Inspect the raw SMTP response or nondelivery report and confirm the exact 5.7.19 code and a basic reply in the 5xx class; retain the complete response text.
- Correlate the event with the intended message, recipient, attempt time and stage, and the Require-Recipient-Valid-Since field or RRVS extension; do not infer from the code alone that the address is invalid.
- Ask the receiving-system administrator or provider to inspect available logs and confirm that the required timestamp was not recorded. Stop unchanged attempts and check suppression before the originator decides whether to send without RRVS protection.
Actions by owner
Sender
- Do not resend the same unchanged message; confirm the recipient and determine whether RRVS protection is required, then give the sender administrator the complete response.
Sender administrator
- Retain the complete response and RRVS context, stop unchanged retries, check suppression, and coordinate with the recipient administrator or provider on an informed decision about whether policy permits a new send without RRVS protection.
Recipient administrator
- If you manage the system that returned the code, inspect its logs and data used for the RRVS evaluation, confirm that the required timestamp was not recorded, and correct a confirmed recording problem or safely give the sender the result of the analysis.
Provider
- If you operate a system involved in the attempt, inspect RRVS processing and timestamp recording in the managed service, correct a confirmed problem or give administrators the needed context, and do not trigger suppression based on the code alone.
Sources and verification
The standard meaning of X.7.19 and the class-5 application of code 5.7.19 were verified against the IANA registry and RFC 2034, RFC 5248, and RFC 7293 as of July 17, 2026. Retry, suppression, diagnostic, and owner-action guidance is presented separately as operational advice; this record contains no provider-specific practice.
- iana-smtp-enhanced-status-codesT0 source
Enumerated Status Codes / X.7.19
- rfc5248T0 source
Section 2.1: registry fields and non-exclusive Associated Basic Status Code
- rfc2034T0 source
Section 4: enhanced status class agrees with SMTP reply class
- rfc7293T0 source
IANA registry reference for X.7.19
Last verified:
