2.1.9: relayed to a system without tracking
A message tracking status: the address was valid and the message was passed on to a system that does not support tracking, so no later status is available.
- Standard
- Provider
- Success (2xx)
- Class
- Sources checked
- Author
At a glance
- Code
- 2.1.9
- Provider
- Standard SMTP codes
- Temporary or permanent
- SuccessThe server accepted the command or the message.
- Who has to act
- The sender. The fix is on the sending side: your domain, your server or your list.
- What the server says
2.1.9 Message relayed to non-compliant mailer
What it means
2.1.9 comes from RFC 3886, which defines message tracking (MTRK) status reports. It reports a success: the message was relayed onward, but to a server that does not speak the tracking protocol, so the trail ends there. RFC 3886 requires it to be used only with the action relayed, in the success class, which is why it is listed here as 2.1.9. Few mail systems implement message tracking, so the code is rarely seen outside environments that do. If a message whose trail ended with 2.1.9 never arrived, the next server on the path is the place to ask.
Common causes
- A tracking query reached a server that handed the message to another server without MTRK support.
- A tracking report in an environment that uses RFC 3886 message tracking.
How to fix it
- 01Treat it as information: the message left that server successfully.
- 02If delivery is in doubt, ask the administrator of the next server on the path to search their logs.
- 03Use the Received headers of a delivered copy, or the recipient's logs, to trace the rest of the route.
Sources
What this page rests on, checked on 20 Oct 2026. The explanation is ours; the reply text is the server's.
Related codes
All 105 standard codesEvery code in the wikiPaste your own bounce