> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/builder/builder-2021.1/email-mailbox-configuration/incoming-emails-processing-logic/wildcard-routes-for-incoming-bcc-emails.md). # Wildcard Routes for incoming BCC Emails When incoming emails have the relevant Enate email address as the Bcc'd, they do not have a 'To' address visible to the system and so are plaeced in the Unprocessed emails list. To help reduce the ocurrences of such mails landing in 'Unprocessed emails' in this situation, you can configure Wilcard Email Routes which essentially use the knowledge of which email addresses these mails come ***from*** to allow it to be processed. These Routes are set to match with a wildcard '\*' email address (The To address of the incoming mail) and a known email address (or addresses) in the 'Sender List includes' (The From address of the incoming mail). Set in this way, they able to match even a BCC'd email if the from address matches. ### Creating a 'Wildcard' Email Route Wildcard routes are created in the same way non-wildcard routes are created, via the 'Routes' page in the Email section of Builder. Simply click to create a new email route and fill in the email route pop-up information as required. To set this as a Wildcard Route to handle Bcc scenario, when filling out the Routing Rules information users should put a '\*' wildcard asterisk as the 'Email Address', and then in the 'Sender List Includes' field, set the name of the known email address that such mails would be coming from. Multiple such addresses can be added to a single Route, with a ';' semicolon character between.
You should create as many such Wildcard Routes for a single Email Connector as there are different Work Item types you wish to be creating from that connector. #### Ordering of Wildcard Routes with Other Routes When ordering their email routes into a hierarchy, users should always ensure that non-wildcard routes appear above wildcard routes, with overall fallback routes appearing *after* the wildcard routes at the very bottom of the list.
## Rules when setting up Wildcard Email Routes When creating an email route containing a wildcard route, there are some important rules that apply, to keep routing of incoming emails working consistently at runeimt. See the table below for a full list of rules regarding the use of working with Email Routes if wildcard (i.e. '\*') email routes are involved. Note: The system will show error messages when a user attempts an activity which may break these rules.
ActivityRuleRelated API
Updating an Email RouteUpdating a NON-wildcard email route to a wildcard email route is now restricted.Email Route - Update
Updating an Email RouteUpdating a wildcard email route to a NON-wildcard email route is now restricted.Email Route - Update
Creating or Updating an Email RouteThe system does not allow using a wildcard address for the sender list when the route's email address is also a wildcard.Email Route - Create Email Route - Update
Creating or Updating an Email RouteA wildcard route requires a sender list to be included.Email Route - Create Email Route - Update
Ordering Multiple RoutesWhen using a wildcard, a strict routing order exists:
1. Non-wildcard Routes
2. Wildcard Routes
3. Fallback Routes		Email Route - Get All For Connector
Creating an Email RouteWhen a email route is created, whether it is a wildcard or not, its order is based on the criteria is determined by the order (stated above). Route orders can be adjusted accordingly after creation.Email Route - Create
Moving an Email RouteRoutes can only be rearranged within their respective type ranges. For example, if it's a wild card route, the system allows moving it within the wild card order range (min-max). The same applies to non-wildcard routes, where the system permits movement within the non-wildcard order range (min-max). If routes are moved beyond their designated range, the system will generate an error.Email Route - Move Route
#### Example of screen popups to help ensure consistent ordering of such routes: If a user attempts to move a route into an order that does not correspond with the required hierarchy, the route will return to where it was and a error message will be displayed.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.enate.net/enate-help/builder/builder-2021.1/email-mailbox-configuration/incoming-emails-processing-logic/wildcard-routes-for-incoming-bcc-emails.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.