How to create and edit a named route in Email Security Cloud
search cancel

How to create and edit a named route in Email Security Cloud

book

Article ID: 277111

calendar_today

Updated On: 06-05-2025

Products

Email Security.cloud

Issue/Introduction

A named route is a collection of your registered default inbound routes. Named routes are used with the Data Protection service to define routing rules that determine how emails are delivered.

This KB article provides steps to create and edit named routes in Email Security.cloud.

Environment

Email Security.cloud

Resolution

Creating a Named Route

To create a named route in Email Security.cloud:

  1. Go to Dashboard > Platform > Inbound Routes.

  2. In the Named Routes section, click Add New.

  3. Under Manage Named Routes, enter a name for the route.

    • The name must start with an alphabetic character.

    • It can contain up to 255 alphanumeric characters and spaces.

  4. Click Add.

  5. In the Registered Inbound Routes section, select the required IP addresses or hostnames by checking the boxes next to them.

    • Only your registered default inbound routes are available.

  6. Click Add to include them in the named route.

  7. Use the priority arrows to arrange the routes in your preferred order.

  8. Click Save.


Editing a Named Route

To edit an existing named route:

  1. Go to Services > Email Services > Inbound Routes.

  2. In the Named Routes section, click Manage Settings next to the route you want to modify.

  3. In the Manage Named Routes section, make the necessary changes. You can update:

    • Route Name

      • Must begin with an alphabetic character.

      • Can include up to 255 alphanumeric characters and spaces.

    • IP Addresses or Hostnames

      • Click Add, select the required entries from the Registered Inbound Routes section, and click Add again.

    • Priority Order

      • Use the arrows to reorder the routes.

  4. Click Save to apply the changes.

 

 

Additional Information

To learn more, refer to the following TechDocs: