# EML_RX_TKN_LEGAC: Reply matched to issue by scanning the message text

- Module: EML. Internal e-mail subsystem (queue, dispatch, inbox)
- Severity: Info
- Impact: No impact. Bookkeeping only. Nobody is affected.
- Retry: Not retryable. Retrying will not help until the cause is fixed.
- Reference: https://docs.bizkithub.com/en/system-codes/EML_RX_TKN_LEGAC

## What happened

The issue reference for an incoming reply was not stored when the e-mail was received, so it had to be found by searching the message text instead. This is expected only for e-mails received before 30 September 2026. If it continues for newer e-mails, extracting the reference on receipt is broken and should be investigated.

## When it is logged

- A reply to a ticket was matched using a slower fallback lookup, typical for older messages.

## What to do

1. No action needed. Contact support@bizkithub.com only if new replies are no longer attached to their tickets.

## Related codes

- EML_RX_CROSSORG: Reply linked to an issue in a different organisation
- EML_CLS_TICK: Inbound e-mail classification run summary
- EML_DAEMON_TICK: Outbound e-mail sender run summary
- EML_DISPO: Disposable e-mail domain list sync
- EML_MX: MX-record contact scan
- EML_RX_QUOTEHIT: Inbound e-mail carries our tracking pixel but was NOT short-circuited
