Mail Security Inital Setup

First Steps with Securepoint Mail Security

Last adaption: 04.2025

New:

Article fundamentally revised

notempty

This article refers to a Beta version

-

Introduction

Integration into the existing email data stream requires an active internet connection and a separate email domain that is hosted on a mail server or by a provider and can be accessed from the internet. In order for all email traffic to be redirected via Securepoint Mail Security, the MX records of the corresponding domain must be adjusted accordingly. It must also be ensured that the receiving mail server or provider can be configured to receive and send emails via Securepoint Mail Security. Communication takes place exclusively via SMTP port 25.

Registration in the portal

Fig.1

In the reseller portal, the

or https://my.securepoint.de/mail-security

must be opened using the Assign role button.

to the right of the search bar

to open the dialog for assigning roles.

Fig.2

In the dialog, a

Caption	Description
Admin	User with all rights for their own organization and customers
Technician	Administrative user for technical settings and customer management; has all rights except the User Management role for their own organization
User	Administrative user for the specific customer
Read-only User	Read-only user for this specific customer

in ‘'Mail Security’' can be assigned to a selected user. All roles except ‘'Admin’' restrict the use of the portal.

Only the main user (recognizable by the crown symbol ) of the respective company can assign roles for Mail Security.

Only after entering a search in the user field, users are suggested

Fig.3

Authorized users can access the Mail Security portal via the Log in button under

Basic setup

Fig.1

Under mail.security Domains a new domain can be added via the button.
A new TXT record in the provider's domain settings is required for validation.
- The required value for the TXT record must be copied and pasted from the Mail Security Portal.
- For some providers, a name is also required, this is usually ‘’@.
- A low TTL (e.g. 1 minute) can also speed up the process.
As soon as the entry is set at the provider, the domain can be added in the portal with the Confirm button.

Fig.2

Under , a new inbound route can be created using the button.

To do this, enter a name for the route in the window that appears, select the previously added domain and specify a destination server.

When using Microsoft 365 (Office 365), the corresponding MX entry from the Microsoft 365 domain settings must be used (e.g. test-en.mail.protection.outlook.com)

Fig.3

Under , a new outbound route can be created using the button.

A name for the route is assigned in the window that appears and a verification option is selected.

When using a local mail server with a fixed IP, the option Default with the corresponding IP should be selected.
Alternatively, the option SMTP authentication is available.
If Microsoft 365 (Office 365) is used, the option Relay option must be selected and the route linked to the incoming domain.

Configuration of the mail server

The configuration of your own mail server is explained below; if Office 365 is used, this article will help.

As a rule, no additional adjustments are required to receive emails. However, to increase security, receipt can be restricted to the Mail Security IP subnet ‘'91.212.136.0/24’'.
In order to send outgoing mails via Mail Security, the send connector of the mail server must point to Smarthost: relay.mymailwall.com. Depending on the selected route option, optionally with authentication.

Configure DNS entries

The MX must be changed to ‘'mx.mymailwall.com’'. There can only be one MX. If, when changing the MX, you are informed that other entries will be removed by the change, it is advisable to make a note of these first. Especially when using Microsoft 365 (Office 365), TXT entries such as ‘'autodiscover’' or similar may be required and should be added again after customization.
The TXT record for the SPF entry must be extended by ‘'include:mymailwall.com’' to ensure correct email authentication.
A CNAME entry is required for DKIM. The name (first value) is set to ‘'mailsecurity._domainkey’'. The content (second value) is mailsecurity._domainkey.mymailwall.com.