EML_RX_ROUTE_OTHInbound mail routed to "other" bucket
InfoEMLRetry: not retryable
The pre-classifier router identified the mail as non-human infrastructure noise (DSN bounces, DMARC reports, raw monitoring alerts, prompt-injection attempts). The row is short-circuited as spam and no ticket is created. A persistent stream in a single-sender dimension often means a real notification source should be filtered at the forward-rule layer rather than classified every tick.
When it is logged
- A received e-mail was recognised as automated noise (bounce reports, DMARC reports, monitoring alerts).
- The message was marked as spam and no ticket was created.
What to do
- 1
No action needed. If one sender produces many entries, filter it in your mail forwarding rules.
Where you will see it
The code tags entries in the admin Log viewer, where you can filter by it and open individual occurrences. Codes logged as error or critical can also trigger a technical notification e-mail with the code in the subject:
Notification subject
[EML_RX_ROUTE_OTH] [eml] …