#Zimbra change email server settings professional#
#Zimbra change email server settings series#

all fail All servers that do not match the above rules are not allowed to send mail. +all pass Allows all mails, as if there was nothing configured ( Not recommended ) all: As you can see in the following table, with this we indicate that the rest of the servers are not authorized unless they coincide with the previous rules Mx: indicates that the server with MX record of our domain is also authorizedĪ:: The server whose IP matches the A record of the domain is authorized V=spf1: Indicates that the TXT record is for SPF checkingĪ: indicates that the server with record A is authorized The explanation of the format is simple, first we indicate v=spf1 to indicate that it is an SPF record, and then who is authorized to send mails in which it is configured. Normally we will have the DNS server in a provider that will facilitate this task through a control panel. To carry out this configuration we must create a new record of type TXT in our DNS server. In case the sender is not authorized, the receiving server should reject the mail since it is not authorized to send mails on our behalf. That is, if someone tries to send an email using our domain, the receiving mail server should check whether the sender is allowed to send emails on our behalf. What this system does is take into account the DNS records of our domain to ensure that the sender of an email is authorized to do so. Let's use zmprov ms `zmhostname` -zimbraDNSMasterIP zmprov ms `zmhostname` +zimbraDNSMasterIP zmprov gs `zmhostname` zimbraDNSMasterIPįor communication between mail servers, the use of SPF is very common. So we have to modify it to use a real, production server.

To check the primary DNS you zmprov gs `zmhostname` zimbraDNSMasterIP

Since it is temporary, we need to remove it from the Zimbra configuration and add a real Primary DNS. With this we already have several lists configured so that the detection of spammers is better and there are emails that are automatically rejected.Īs you may remember, in the first post we used a temporary DNS server for the installation. In our Zimbra administration section we will go to Configure → General Settings →MTA and here we will go down to the DNS Checks section, where we will add the following blacklists for each of the sections we see. For the configuration we will go to the administration console of our Zimbra server, going through the web browser to the address, where SERVER is the IP or DNS resolution of our server Basically its operation is to make a list of IPs that are marked as spammers due to different criteria.

#Zimbra change email server settings series#

Therefore, we are going to make a series of configurations, not only at the Zimbra level, that will help us to achieve this purpose, so let's go for it.īlacklisting is an attempt to stop spam in the jungle that is the internet today.

#Zimbra change email server settings professional#

We already have our Zimbra working, but with the basic installation we did not get it to be as professional as our title pretends it to be