{"id":97073,"date":"2020-10-16T02:42:25","date_gmt":"2020-10-16T00:42:25","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/fortimail-konfiguracziya-dlya-bystrogo-zapuska"},"modified":"2020-10-16T02:42:25","modified_gmt":"2020-10-16T00:42:25","slug":"fortimail-konfiguracziya-dlya-bystrogo-zapuska","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/fortimail-konfiguracziya-dlya-bystrogo-zapuska","title":{"rendered":"FortiMail \u2014 configuration for quick deployment","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"FortiMail
\n
\nWelcome! Today we will discuss how to perform the initial setup of the mail gateway. FortiMail<\/a><\/noindex> \u2013 solutions from Fortinet for email protection. In this article, we will examine the layout we will be working with, and perform the configuration. FortiMail<\/a><\/noindex>, necessary for receiving and checking emails, and we will also test its functionality. Based on our experience, we can confidently say that the process is very simple, and even after minimal configuration, results can be observed. <\/a><\/noindex><\/p>\n

Let's start with the current layout. It is presented in the figure below.
\n\"FortiMail
\n
\nOn the right, we see the computer of an external user from whom we will send mail to a user in the internal network. In the internal network, there is a user computer, a domain controller running a DNS server, and a mail server. At the network boundary is the firewall \u2013 FortiGate, whose main feature is the configuration of SMTP and DNS traffic forwarding.<\/p>\n

We will pay special attention to DNS.<\/p>\n

Two DNS records are used for routing emails on the Internet \u2013 an A record and an MX record. Usually, these DNS records are configured on a public DNS server, but due to layout constraints, we simply forward DNS through the firewall (that is, for the external user, the DNS server address is set to 10.10.30.210).<\/p>\n

An MX record is a record that contains the name of the mail server servicing the domain and the priority of this mail server. In our case, it looks like this: test.local -> mail.test.local 10.<\/p>\n

An A record is a record that translates a domain name into an IP address; in our case, it is: mail.test.local -> 10.10.30.210.<\/p>\n

When our external user tries to send an email to the address an@test.local, they will request the MX record of the domain test.local from their DNS server. Our DNS server will respond with the name of the mail server \u2013 mail.test.local. Now the user needs to obtain the IP address of this server, so they again query DNS for the A record and receive the IP address 10.10.30.210 (yes, again this one :) ). They can send the email. Thus, they attempt to establish a connection to the obtained IP address on port 25. Through the rules on the firewall, this connection is forwarded to the mail server. <\/p>\n

Let's check the functionality of the mail in its current layout state. For this, we will use the swaks utility on an external user's computer. This tool allows us to test SMTP functionality by sending a message to a recipient with a set of various parameters. Previously, a user with the mailbox an@test.local has already been set up on the mail server. Let's try sending him an email:<\/p>\n

\"FortiMail
\n
\nNow let's move to the internal user's machine and confirm that the email has arrived:<\/p>\n

\"FortiMail
\n
\nThe email has indeed arrived (it's highlighted in the list). This means that the layout is functioning correctly. It's time to turn to FortiMail. Let's add to our layout: <\/p>\n

\"FortiMail
\n
\nFortiMail can be deployed in three modes:<\/p>\n