This article explains why emails sent from a Salesforce Case show a "no-reply" From address instead of the customer's original email address, and how to correct the email routing configuration to resolve this.
Scenario: An organization has an Email-to-Case routing address of "support@xyz.com". When a customer sends an email from "John.Doe@gmail.com", the case is created successfully. However, when an agent tries to reply from the Case record, the From address shows "no-reply@xyz.com" instead of "John.Doe@gmail.com", preventing the agent from replying to the correct customer address.
On-Demand Email-to-Case is a Salesforce feature that converts incoming emails into Cases by routing emails from a support address to Salesforce. The routing method — forwarding vs. redirecting — determines what From address is preserved when the Case is created.
This issue occurs because the email server rule is configured to forward incoming emails rather than redirect them. When emails are forwarded, the original sender's From address is replaced with the forwarding address (such as "no-reply@xyz.com"). When emails are redirected, the original customer From address is preserved.
To preserve the original customer email address, configure your email server rule to redirect (not forward) emails to the Salesforce Email-to-Case Service address.
After the change, new cases created from inbound emails show the original customer email address as the From address, and agents can reply directly to the customer.
Note: For detailed steps on creating redirect rules in Microsoft Outlook, see Use rules to automatically forward messages.
Use Rules to Automatically Forward Messages — Microsoft Support
000380554

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.