Spending some time in addition to composing eye-catching email content, configuring our DNS<\/strong> will allow us to maximize the investment required for the implementation of a newsletter or automated communication system with our customers containing alerts. The penalty to pay in the case of not paying attention to these details is that our communication reaches only a part of our contacts because of the recipients mail server’s protection system, which may classify our email as SPAM, depositing them, at best, in the relevant folder. But things could be even worse, in fact by not giving weight to the problem, we will worsen, the “reputation” of our mail server, which will inevitably lead us to be placed on the dreaded black lists. Terrified?<\/strong> Don’t worry, you will soon realize that it is not difficult to prevent the email from ending up in SPAM.<\/p>\n In order to fully understand what various factors come into play in managing email classification, this guide provides both basic instructions, suggested for updating one’s DNS configuration independently, and descriptions of the operation of the systems used in the suggested configurations, useful for making custom configurations suitable for specific needs. If these topics are already known, or you are only interested in the operational part of the guide, you can go directly to the Let’s Configure DNS<\/a> point.<\/p>\n To date, commercial communications take place mainly through email messages. In order to make the service more usable, the mail servers that receive messages very often take charge of detecting so-called SPAM messages, messages from senders who mass forward messages, whether for lawful or unlawful purposes, but with whom you have no relationship whatsoever. L<\/span>he word SPAM originates from “spiced ham” food forcibly offered to patrons of an inn in a <\/span> Before making the necessary optimizations to make your e-mail address more reliable, it is good to take stock of its “deliverability” ( or delivery rate). <\/span>The systems used to classify email messages as SPAM are basically 2: the black lists<\/strong> <\/span>and the methods<\/strong> <\/span>that allow the authenticity of the message to be validated. <\/span> <\/span>The content of the message also contributes to its classification, but this aspect has less of an impact on classification than the first two elements mentioned above.<\/span><\/p>\n DNS<\/span> (Domain Name Server) is the system by which a server’s IP address can be linked to an alphanumeric string. To give a practical example, it is the system that allows us to reach the server where our website is hosted, normally identified by an IP address, by typing into our browser, an easily memorized text string (e.g. Le <\/strong> (Sender policy framework) is a method by which recipients can check the record of your domain where you have authorized your host or sending service to deliver newsletters on your behalf. In other words, it helps your recipients determine whether an e-mail is a scam or not.<\/span><\/p>\n (Domain Keys Identified Email). It is a digitally signed authentication method created to prove the legitimacy of an email sender and the server from which this email is sent. After your message is sent, the destination mail server extracts the digital signature and applies local rules based on the results of the signature test.<\/span><\/p>\n (Domain-based Message Authentication, Reporting and Conformance), is an email standard that confirms the identity of the sender, using SPF and DKIM, tells the recipient’s email service what to do with emails that have failed the check, and asks recipient email services to provide reports on where the email came from.<\/span><\/p>\n To test how reliable our emails are considered to be, it is possible to take advantage of some tools that return a report<\/strong> <\/span>on the quality of the email address we wish to use to send commercial messages to our customers. To illustrate its operation, in this guide we will use the free service Test: how to check how spammy your emails are<\/p><\/div>\n After sending the email to the given address you can return to the site and within seconds we will get a report divided by sections, ending with a global index that we can use to see if our optimizations have been successful.<\/span><\/p>\n All sections of the report provide important information on how to improve the quality of our email with a score that will help define the final one and thus how to prevent the sent email from ending up in SPAM, but for the purpose of this guide we will comment on the most useful ones.<\/span><\/p>\n SPF, DKIM and DMARC authentications.<\/strong><\/span><\/p>\n In the section on authentication we are provided with information on the implementation of the mentioned configurations. Clicking on the down arrow located to the left of the selection title will open a list that will allow us to see what authentication methods are already present or missing in our DNS configuration.<\/span><\/p>\n The email blacklists<\/strong><\/span><\/p>\n The section shows the list of the many black lists that contribute to the classification of mails. For each list is indicated the presence or absence of the email we used and the link to the list useful to take action on that specific list and request its removal. In fact, each list has its own procedure that you can follow by following the directions provided on their site.<\/span><\/p>\n List of sample email blacklists<\/p><\/div>\n <\/p>\n The key to improving the efficiency of sending our emails is to configure the SPF, DKIM and DMARC protocol within the <\/span>DNS of one’s domain<\/span>. Before making the change, it is useful to conduct a check on its configuration status. One method is to resort to a test such as the one shown in Let’s Test the Quality of Our Email<\/a>. <\/span>If of the report shows that one of the SPF, DKIM, or DMARC protocols has not been implemented, it is necessary to proceed to modify the DNS of the domain to which the e-mail corresponds by adding a TXT record or modifying the existing one.<\/span><\/p>\n Normally the SPF string is already present in the standard DNS configuration. If, on the other hand, our tests show that it is not present, it will be necessary to add a dedicated TXT record with the following :<\/span><\/p>\n NB. the text “_spf.aruba.it” is valid only if you use a domain hosted on Aruba servers. for other providers consult available documentation or their service department.<\/span><\/p>\n For details on how to edit the TXT record, it will be sufficient to consult the documentation made available by your service provider. <\/span> Details on advanced DNS configuration are available through an Internet search. Google provides this guide on advanced de SPF configuration setup<\/a>.<\/span><\/p>\n If you use the<\/strong> DMARC is a recently introduced method implemented by many mail handlers to reduce attempts at Phishing<\/a> <\/span>e An example of a DMARC string<\/strong><\/span><\/p>\n In detail: <\/span><\/p>\nHow to prevent your email from ending up in SPAM: Table of Contents<\/strong><\/h3>\n
\n
\n
\n
\n
\n
\n
What is SPAM and how to prevent your email from ending up in SPAM<\/span><\/strong><\/h3>\n
\n sketch<\/a>
\n<\/span> 1970s comedy sketch by <\/span>
\n Monty Python’s Flying Circus<\/a>
\n<\/span> <\/span><\/strong><\/span><\/p>\nWe check the “Deliverability” of one’s email address<\/span><\/strong><\/h3>\n
What are DNS, Black Lists and Control Methods.<\/strong><\/span><\/h3>\n
\n www.vayu.it<\/a>
\n<\/span>). To enable on the entire Internet a rapid conversion from ip to domain name, with defined frequencies the configuration of each server is copied to the other DNS servers scattered around the world. The process is completed within a range of a few hours to 72. <\/span><\/span><\/p>\n![\"dns](\"https:\/\/lh6.googleusercontent.com\/S-F7epY2oKE7468CfRCxoMZSbtODu8rV4PmlJsM0P_393K_mwpt0CO6A4eXwRsFvWwskNb8-cv4V0w8WOXpBZLlundN9sRhSW5C2ef_AQ-5uJe9el-889fvE9vPkCuKeKLHJaj12XbiidzwB2HNJfVKpN3WOQ3Y77pDtVh4vs6WeqJPggTlWRxjSOnnh4yOukgQ\" "\\"DNS:")
\n Black list<\/strong>
\n<\/span> are lists, continuously updated, of IPs or email domains that have been flagged as spam or with harmful content. These lists are used by the anti-spam systems of mail servers, to perform classification of each email we receive. <\/span><\/span>Configurations can be made on each domain that allow the servers to verify the authenticity of received emails. These methods are known as SPF, DKIM and DMARC.<\/span><\/span><\/p>\nWhat is the SPF <\/strong><\/span><\/h4>\n
What is DKIM<\/strong><\/span><\/h4>\n
What is DMARC <\/strong><\/span><\/h4>\n
We test the quality of our email and its spam level<\/strong><\/span><\/h3>\n
\n mail-tester.com<\/strong>
\n<\/span> <\/strong>but there are many others on the net. <\/span> <\/span>Going to the website
\n https:\/\/www.mail-tester.com\/<\/a>
\n<\/span>, on the home page you will get a personalized address to which you can send an e-mail from the address we want to test. <\/span> <\/span><\/p>\n![\"spam](\"https:\/\/lh6.googleusercontent.com\/5g-pO8aYeFeJTPj-4w-NvRTpJFcBW9ey2a-QIS2cUmvWVWd5KulllG1vmX_qHOf48c00Dkctdq-oUjO3QcFG6Q0acPOtw71km5RIO0UPpAFL-2i8387ikvHcEJLs0fkE7p7acAhNACf0XRCIBi2RdJfyPXeNpsHfqhBCbr1a7NtXQTtr3GsNCo0g_jtKozoZAts\" "\\"spam")
The most important sections of the report <\/strong><\/span><\/h3>\n
![\"SPF](\"https:\/\/lh6.googleusercontent.com\/UjMvWY5RXB_WnMN7k5UdBPsMiKrt5u3J4SZ_rVUtG0Pxd-wi7TtrII1anZgho_oXlKD0YK5525RcUbe7AVWHrlw3Fo5dX_dkzQcccyGKG2tSTUbeq-Ho5b08LIIiW_JB_3SMPukjKNqsEZfy2PgKAlTrs1JcWhebBGT5t3G6UMc-lvFnXbF00V8gbiezaXaxwC4\")
Let’s configure DNS.<\/strong><\/span><\/h3>\n
We manage the SPF string<\/strong><\/span><\/h4>\n
\n
\n In case you are using an external server <\/strong>
\n<\/span>a different configuration is required. <\/span> The<\/span>meaning of the string symbols is as follows<\/span>:<\/p>\n\n
We manage the DKIM string<\/strong><\/span><\/h4>\n
\n Aruba mail service<\/strong>
\n<\/span>, that is, you have not changed the MX to “point” to an external service,
\n the DKIM signature is already active by default<\/strong>
\n<\/span> and is automatically included when using Aruba.it outgoing mail servers. <\/span> <\/span>In case you are working with
\n providers that have not implemented the DKIM signature <\/strong>
\n<\/span>by default in the domain, you need to contact technical support for its implementation, which consists of creating the digital signature and entering it into the DNS.<\/span><\/span><\/p>\nWe manage the DMARC string<\/strong><\/span><\/h4>\n
\n Spoofing<\/a>
\n<\/span>. <\/span> <\/span>As we have seen in the
\n definition<\/a>
\n<\/span> DMARC allows you to provide guidance to the recipient server on how to process email and can only be implemented if you have already configured SPF and DKIM. <\/span> <\/span>It also allows you to receive reports from recipient mail servers <\/span>useful for understanding which messages sent from your domain pass SPF and DKIM authentication <\/span>. <\/span>For an in-depth tutorial on DMARC configuration, you can check out Google’s guide this
\n link<\/a>
\n<\/span><\/span><\/p>\n\n
\n “<\/em>
\n<\/span> of the DNS we enter:”_dmarc<\/span>“(.nomedomain if not already present in the configuration)<\/span><\/span><\/li>\n
\n “<\/em>
\n<\/span> of DNS we enter, “v=DMARC1; p=reject; rua=mailto:postmaster@miodominio.it, mailto:dmarc@miodominio.it; pct=100; adkim=r; aspf=r<\/span>.<\/span>“<\/span><\/span><\/li>\n<\/ul>\n\n
\n v<\/strong>
\n<\/span>: mandatory tag, indicates the version of the protocol<\/span><\/li>\n
![\"email](\"https:\/\/lh4.googleusercontent.com\/KJDr1NR3_cZYnBAZnThlZAYqKIehayVL6J3wlUzAYCNv3X1vkY6uJatbYUid8XpbBtF8oFmBDU3yjxdUqOm-_JPauduYn03eUQkcnRPpY6uenxsdC62k2hfqvDp63LdwEO0CP313ytdlROG-91YcIH14_hHXOUFOV0Rst2TXZ3xiG5JHQIvzgagtqsOGpZYsbp0\" "\\"email")
![\"List](\"https:\/\/lh5.googleusercontent.com\/tcVMEw8GN9_nx859hF_rdSPMIR6bnQK41p0D6fWo696kBTkxvCeq17PcJ_ujCSbeqQXxCVzaX81KU_foCgwVYGXRRLqjVxMeAlwaoV1SkVZsaqCOBc1FIu_49sapEU9omEa0HmvXyQl7q85AmMH2v55dStJJfDBL9esiRc8Y575uv6tEvsXwiAqq2l9QOwnwOfk\")