# EML_RX_QUOTEHIT: Inbound e-mail carries our tracking pixel but was NOT short-circuited

- 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_QUOTEHIT

## What happened

An inbound e-mail contains the tracking pixel URL of one of our own outbound mails (typically because the sender quoted our original notification when replying) but the tightened heuristic (introduced 2026-09-30) correctly declined to short-circuit it because the From: address is not ours AND/OR a BKH-ISSUE reply token is present. This log is a regression tripwire: the count measures how much legitimate reply traffic the OLD naïve pixel-only heuristic would have swallowed. If this signal ever falls to zero without a code change, the new heuristic likely broke and replies are being buried again.

## When it is logged

- A received e-mail quoted one of your own outbound messages but came from an external sender.
- The message was processed normally as a reply instead of being treated as an internal echo.

## What to do

1. No action needed. This entry is a diagnostic signal confirming that replies are processed correctly.

## Related codes

- EML_RX_SELFECHO: Incoming e-mail recognised as our own outgoing message
- 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_CROSSORG: Reply linked to an issue in a different organisation
