Skip to content
Standard SMTP codes · permanent error

5.7.19: ownership check could not be done

The message asked the receiver to check how long the recipient had owned the mailbox, and the receiver could not, because it has no record of that date.

Standard
Provider
Permanent (5xx)
Class
Sources checked
Author

At a glance

Code
5.7.19
Temporary or permanent
PermanentRefused for good: the message comes back to the sender, and resending it gets the same answer.
Who has to act
The sender. The fix is on the sending side: your domain, your server or your list.
What the server says
5.7.19 RRVS test cannot be completed

What it means

RFC 7293 lets a sender require that a recipient address has had the same owner since a given time. If the receiving system never recorded when the mailbox was created or reassigned, and cannot choose a reasonable substitute date, it cannot run the check and refuses the message with X.7.19. The registry gives it a 5xx reply code. RFC 7293 leaves the next step to the sender: reissue the message without the RRVS requirement, or find another way to reach the person.

Common causes

  • The receiving system supports RRVS but has no creation date for this mailbox.
  • An old mailbox created before the system recorded such dates.

How to fix it

  1. 01Decide whether the message is safe to send without the ownership check.
  2. 02If it is, resend without the RRVS parameter or header field.
  3. 03If it is not, reach the person through another channel.

Sources

What this page rests on, checked on 20 Oct 2026. The explanation is ours; the reply text is the server's.

  1. 5.7.17Mailbox owner has changed.The message asked to be delivered only if the recipient address had the same owner since a given date, and the receiving system says it has changed hands.StandardPermanent
  2. 5.7.18Domain owner has changed.Under an RRVS check, the receiving system reports that the recipient's domain has changed owner since the date the sender gave, so the message was refused.StandardPermanent

All 105 standard codesEvery code in the wikiPaste your own bounce

Beat · paid monitoring

A heartbeat for your email.

Beat runs every check on this site on a schedule: 41 checks, 33 blacklists and real inbox placement. The moment something breaks, it tells you what broke, why it matters, and the exact fix.

example.comWatching
  • SPFpass
  • DKIMpass
  • DMARCp=none
  • Blacklists0 of 33

Illustrative. Your domain, every few hours.

Also from us:Pulse: your own sending infrastructureConsulting: $65/hr, no retainer