Email replies synced to Salesforce using Einstein Activity Capture (EAC) or Sync Email as Salesforce Activity are automatically linked to Cases, even when the Email-to-Case routing address is completely removed from the recipient list.
This occurs because Email-to-Case uses header-based matching. When a user or contact replies to an existing email thread, the email client preserves the original message headers, specifically In-Reply-To and References. Salesforce reads these thread headers and automatically attaches the synced email to the corresponding Case record, regardless of whether a routing address is present.
Note: This behavior applies specifically to header-based threading. It does not apply to emails associated through parent record inheritance (where email replies inherit Account and Opportunity associations from the parent message). You can verify if a record was attached via header matching by inspecting the ReplyToEmailMessageId field on the synced EmailMessage record.
This article explains why Salesforce attaches a synced email reply to a Case even after the Email-to-Case routing address is removed, and how to identify which emails were attached through header-based thread matching.
This is expected system behavior when header-based threading is active for Email-to-Case. The Email-to-Case engine prioritizes email thread header parameters (In-Reply-To, References) over the current recipient list to ensure thread continuity on Case records.
Query or inspect the ReplyToEmailMessageId field on the EmailMessage record. A populated ReplyToEmailMessageId confirms that the record was attached to the Case through header-based thread matching rather than parent inheritance.
Make sure users know that replying to an existing Case email thread keeps the email associated with the original Case record, even after the routing alias is removed from the recipient list. This happens because persistent Internet Message IDs remain in the email headers.
005391244

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.