Configuration

The Configuration is an account only/private section, which is only accessible post login. The configuration section has the following three options:

The sections below describe the three configurations features/options:

---

Manage Email IDs

The Manage Email IDs allows you to create new private emails for the subdomain(s) of Mail7 or your domain(s). Thus, first of all, you should configure a subdomain of Mail7 or your domain as explained in this document.

Note: You must be logged in to access these sections/features. Please refer to this document for details of the Login and Get Access process.

Once the domain/subdomain is configured, you can proceed with the steps described below to create the private email id(s).

Selecting the Configuration > Manage Email IDs from the left navigation panel displays the following screen:

To create a new private email Id, click the Generate New ID button and the following pop-up appears:

The @mail.mail7.io displayed in the above pop-up is a subdomain configured here. Similarly, clicking the drop-down arrow icon next to it will display the options if you have multiple subdomains or multiple custom domains or both subdomain(s) and custom domain(s) configured.

You need to enter the desired email id, choose the domain/subdomain, and then click the Generate button. The application will display a confirmation message and the created private email id will be displayed on the same screen:

In the same way you can create multiple email ids. If required, you can select an email id by clicking the delete icon available next to it.

---

Routing Rules

The Routing Rules allows you to configure the rules that will be executed on receiving email(s) in the private email id(s). Thus, to check the routing rules, you must have configured email ids as explained in the above section.

Note: You must be logged in to access these sections/features. Please refer to this document for details of the Login and Get Access process.

The following explains how you can create a new routing rule:

Selecting the Configuration > Routing Rules from the left navigation panel displays the following screen:

Click the Create Routing Rule button and the following pop-up will appear:

1. Enter the name in the Rule Name text box. It should be unique for each routing rule.
2. Enter the description in the Description text box.
3. Enter/set the priority (1,2,3 …) in the Priority spinbox. The rule will be executed in the sequence of given priority i.e. if the multiple rules are applicable, the rule with priority 1 will be given priority, and so on.
4. Enabled text with blue color on the toggle button depicts that that rule is enabled if you plan to enable it later, turn it off.
5. Select the condition from the drop-down list as per your requirement. The list and logic of each condition are as follows:
6. All: Select this option, if you want that the rule should be executed only if the configured condition(s) are met.
7. Any: Select this option, if you want that the rule should be executed even if one of the configured conditions is met.
8. Always Match: Select this option, if you want that the rule should always be executed i.e. without checking a condition.

On selecting All and Any condition, the application display a default option to configure the setting as follows:

The first drop-down always displays the Equal condition. From the second drop-down you can select one of the following condition:

To: The email should be equal to the entered text. This is applied to the entire email, for example, [email protected]

Prefix: The email prefix should match with the entered text. For example, if the test is entered and email is received on the [email protected] email, it will fall under this rule.

Suffix: The email suffix should match with the entered text. For example, if the .com is entered and email is received on the [email protected] email, it will fall under this rule.

Next, in the text box, you need to enter the text for the condition. Similarly, you can configure the multiple conditions to complete the rule. To add another condition, click the + icon given next to the condition row. The added condition can also be removed by clicking the - icon given next to the condition.

6. Select an action from the drop-down list. The available action options are as follows:
7. Webhook: If selected, you must enter the endpoint as well. On matching the rule, the email(s) will be posted over the specified endpoint.
8. Email Forwarder: If selected, you must enter the email id. On matching the rule, the email(s) will be forwarded to the specified email id.
9. Delete: If selected, on matching the rule, the email(s) will be deleted.
10. Click the Save button to save the configured rule. Alternatively, click the Cancel button if you do not wish to save the rule.

Note: The configured routing rules will be checked and executed on receiving an email i.e. no waiting time for the action. Also, you can configure multiple routing rules as per your requirements.

For example, if you want that all of the received emails should be forwarded to test/test.com and once forwarded, those should be deleted from the Mail7 private inbox, you can execute it as follows:

1. Configure a routing rule where the condition is Always Match, the action is Email Forwarder (enter the email id forwarding action) and priority is 1.
2. Configure another routing rule where the condition is Always Match, the action is Delete and priority is 2.

As a result, Mail7 will first forward the received email on the mentioned email id and then delete the already forwarded email.

The following displays the list of the configured routing rules:

You can enable/disable a rule by clicking the icon given next to it. Also, you can delete a rule by clicking the delete icon given next to the rule in the list.

API Credentials

---

The API Credentials allows you to view the API Credentials for your account.

Selecting the Configuration > API Credentials from the left navigation panel displays the following screen:

You can copy the API Key and API Secret by clicking the Copy button given next to them.

For the available APIs and their usage, please refer to this document.

Note: You must be logged in to access these sections/features. Please refer to this document for details of the Login and Get Access process.