# EML_RX_SELFECHO: Incoming e-mail recognised as our own outgoing message

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

## What happened

An incoming e-mail was identified as a copy of a message the organisation sent itself (it came from one of the organisation's own sender addresses, carried our tracking and was not a reply to an issue). It was marked as not spam and skipped classification. Repeated entries suggest a mail loop; check the recipients or forwarding rules that send our outgoing mail back to the inbox.

## When it is logged

- A copy of an e-mail you sent arrived back in your own inbox, for example via a forward or BCC rule.
- The message was skipped by classification and no ticket was created.

## What to do

1. No action needed for occasional entries.
2. If entries are frequent, review the forwarding chain that sends your outbound mail back into the inbox.

## Related codes

- EML_RX_QUOTEHIT: Inbound e-mail carries our tracking pixel but was NOT short-circuited
- EML_RX_LOOP_DUP: Inbound reply dropped as autoresponder loop echo
- 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
