BizKitHub
EML_RX_QUOTEHIT

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

InfoEMLRetry: not retryable
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. 1

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

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_QUOTEHIT] [eml] …