# EML_RX_LOOP_DUP: Inbound reply dropped as autoresponder loop echo

- Module: EML. Internal e-mail subsystem (queue, dispatch, inbox)
- Severity: Warning
- 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_LOOP_DUP

## What happened

An inbound e-mail resolved via BKH-ISSUE reply token to an existing issue, but its normalized body was identical to the most recent comment on the same issue (added within the last 30 minutes). This is the autoresponder loop signature: the sender keeps mailing us the same template body quoted together with our outbound. The row is auto-marked `is_spam=true` so no comment is appended and the loop can neither grow the issue nor keep the classifier queue busy. A persistent stream against one issue × sender pair should trigger a mail-forwarder-side investigation at the originating address.

## Likely causes

- An autoresponder kept replying to a ticket notification with the same text.
- The reply body matched the latest comment on the ticket, so it was marked as spam and dropped.

## How to resolve

1. Identify the sender address on the affected ticket.
2. Ask the sender to disable the autoresponder or adjust the mail rule that causes the loop.

## Related codes

- EML_RX_RATELIMIT: Incoming reply exceeded the issue comment limit
- EML_RX_SELFECHO: Incoming e-mail recognised as our own outgoing message
- EML_BOUNCE: E-mail bounce or delivery failure detected
- EML_DKIM_WARN: DKIM not configured for sender (deprecated)
- EML_FALLBACK: Outbound e-mail re-routed via system mailer
- EML_FORCE_FAIL: Immediate e-mail send failed, left in queue
