When setting up an Email-to-Case routing address or an Apex Email Service address in Salesforce, it's a best practice to type the values directly into the fields rather than copy and paste them from other sources, such as a Word document or email.
Copying and pasting from formatted sources can introduce hidden characters that cause inbound emails to these addresses to bounce with errors, even though case creation and email processing otherwise work as expected.
This article explains why "is not a valid address" bounce errors occur on Email-to-Case routing addresses and Apex Email Service addresses, and how to recreate these addresses cleanly for Email2Apex, Email2Case, and Email2Salesforce.
Because Salesforce stores configuration data in an XML-based format internally, content copied from sources with extra spaces, line breaks, or HTML formatting can embed hidden characters in the backend tables. These hidden characters are parsed by backend code but are not visible in the setup UI.
For Email-to-Case specifically, emails sent to a routing or service address can bounce with errors such as 'badaddress@185tpneup8unr1zgmcf530kspwcxe2fx3b9q1kp8ohzxmoxyci.xx-9xxxxxxxxx.naXX.case.salesforce.com is not a valid address', and cases are not created because the emails aren't accepted at that address. Similar errors can also occur for Apex Email Service addresses that contain hidden characters.
If copy and paste is the only option when supplying values in routing address setup, paste from a low-level text editor such as Notepad, TextPad, or Notepad++ instead of pasting directly from a formatted source.
For Email-to-Salesforce, no manual address creation is needed — addresses are generated automatically on the backend.
000393407

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.