# EML_RX_CROSSORG: Reply linked to an issue in a different organisation

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

## What happened

An incoming reply referenced an issue that belongs to a different organisation than the inbox that received it, usually because a notification was forwarded from one organisation to another's support inbox. To keep organisations separated, the reply was not added to that issue and a new ticket was created in the receiving organisation instead. If this keeps happening between the same two organisations, review the forwarding setup.

## When it is logged

- A reply to a ticket notification arrived in another organisation's inbox, usually because it was forwarded.
- The reply was opened as a new ticket in the receiving organisation instead of being added to the original.

## What to do

1. No action needed for occasional entries.
2. If it repeats between the same organisations, review the mail forwarding rules involved.

## Related codes

- EML_RX_TKN_LEGAC: Reply matched to issue by scanning the message text
- 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
