{"id":450,"date":"2021-07-23T12:30:08","date_gmt":"2021-07-23T12:30:08","guid":{"rendered":"https:\/\/ssdsunucum.com\/blog\/how-to-keep-your-email-out-of-the-spam-folder\/"},"modified":"2021-07-23T12:30:08","modified_gmt":"2021-07-23T12:30:08","slug":"how-to-keep-your-email-out-of-the-spam-folder","status":"publish","type":"post","link":"https:\/\/ssdsunucum.com\/blog\/how-to-keep-your-email-out-of-the-spam-folder\/","title":{"rendered":"How to Keep Your Email Out of the Spam Folder"},"content":{"rendered":"<\/p>\n
\n
<\/div>\n
\n

Overview<\/h2>\n

This article contains helpful information to make sure that other servers or network do not mark your email as spam. You do not<\/strong> want to send spam from your server. For more information on how to make sure that you do not send spam, read our How to Prevent Email Abuse documentation.<\/p>\n

Use email authentication<\/h2>\n

DKIM and SPF<\/h3>\n

DKIM (DomainKeys Identified Mail) and SPF (Sender Policy Framework) authentication can help verify that email comes from a trusted sender. DKIM is a validation system that detects email spoofing. It allows your mail server to check whether a domain\u2019s administrators authorized email from a domain. The email includes a digital signature that your mail server uses to verify the sender\u2019s public key in their DNS record.<\/p>\n

SPF uses DNS records to prevent email spoofing. If an email message uses falsified sender addresses, SPF uses the DNS record for the sender\u2019s domain to detect the modification in the email\u2019s header.<\/p>\n

\n
Note:<\/div>\n
\n

On servers that run CentOS 7, CentOS 8, or AlmaLinux 8, you may see a named<\/code> warning about the absence of SPF resource records on DNS.<\/p>\n

    \n
  • This warning is not relevant on CentOS 7, CentOS 8, or AlmaLinux 8 servers because RFC 7208 deprecated SPF records. CentOS 7 and 8 servers use TXT records instead of SPF records.<\/li>\n
  • Red Hat 7.1 and CentOS 7.1 both contain bind-9.9.4-23.el7<\/code>, which is an updated version of BIND that complies with RFC 7208. To resolve this issue, update your operating system to a version that contains the updated version of BIND. For more information, read the Red Hat Bugzilla case about SPF record errors.<\/li>\n<\/ul><\/div>\n<\/div>\n

    For more information, read our Email Deliverability documentation.<\/p>\n

    DMARC<\/h3>\n

    DMARC (Domain-based Message Authentication, Reporting & Conformance) is a technical specification to help reduce the potential for email-based abuse. A DMARC policy uses DNS to confirm that an email message uses a valid DKIM and SPF record, and that the From:<\/code> header matches those records.<\/p>\n

    Many large email networks require that you use a DMARC policy to help protect their users from spam email. To prevent email rejections or spam flags within these networks, your server must<\/strong> use a DMARC policy.<\/p>\n

    Configure the server PTR record<\/h2>\n

    A PTR record resolves an IP address to a domain name. A PTR record resembles a reversed A record. Configure the PTR record of the primary IP address of your server to use the hostname of your server. If you have configured Exim to use a different IP address, ensure that the PTR record of that IP address uses the hostname of your server.<\/p>\n

    A record resemble the following example:\n<\/p>\n

    \n
    \n\n\n
    \n
    1\n<\/span>2\n<\/span>3\n<\/span><\/code><\/pre>\n<\/td>\n
    		\n
    server<\/span>:~<\/span> root<\/span>$<\/span> dig<\/span> mx1<\/span>.cpanel<\/span>.net<\/span> +<\/span>short<\/span>\n208.74.121.68<\/span>\nserver<\/span>:~<\/span> root<\/span>$<\/span><\/code><\/pre>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<\/div>\n
    PTR records resemble the following example:\n<\/p>\n
    \n
    \n\n\n
    \n
    1\n<\/span>2\n<\/span>3\n<\/span><\/code><\/pre>\n<\/td>\n
    		\n
    server<\/span>:~<\/span> root<\/span>$<\/span> dig<\/span> -<\/span>x<\/span> 208.74.121.68<\/span> +<\/span>short<\/span>\nmx1<\/span>.cpanel<\/span>.net<\/span>.\nserver<\/span>:~<\/span> root<\/span>$<\/span><\/code><\/pre>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<\/div>\n
    Spam and other networks<\/h2>\n
    If email networks such as Gmail\u2122, Yahoo, or Outlook mark your server\u2019s email as spam, you must<\/strong> identify the reason and resolve the problem. If you have recently resolved an issue with spam on your server or you received a new IP address which previously sent spam, you must<\/strong> notify the remote network. Make certain<\/strong> that you review the bulk sender policy of large email networks.<\/p>\n
    \n
    Note:<\/div>\n
    \n
      \n
    • In most cases, Google automates their spam flagging system and requires you to wait for their system to restore your domain\u2019s reputation. For more information, read Google\u2019s Troubleshooting for bulk email senders documentation.<\/li>\n
    • We recommend that you read Google\u2019s Bulk Senders Guidelines.<\/li>\n
    • For more information, read our Blacklisting & IP Address Reputation documentation.<\/li>\n<\/ul><\/div>\n<\/div>\n
      Bulk email best practices<\/h2>\n
      We recommend that you adhere to the following best practices:<\/p>\n
        \n
      • Use the same IP address to send all bulk email.<\/li>\n
      • Use the same email address in the From: header of your emails.<\/li>\n
      • Ensure that your email complies with RFC 5322.<\/li>\n
      • If your email uses HTML, ensure that it complies with HTML standards.<\/li>\n
      • Ensure that the contents of your email relate to the subject of your email.<\/li>\n<\/ul><\/div>\n","protected":false},"excerpt":{"rendered":"
        Overview This article contains helpful information to make sure that other servers or network do not mark your email as spam. You do not want to send spam from your server. For more information on how to make sure that you do not send spam, read our How to Prevent Email Abuse documentation. Use email …<\/p>\n","protected":false},"author":1,"featured_media":451,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/450"}],"collection":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/comments?post=450"}],"version-history":[{"count":0,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/450\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media\/451"}],"wp:attachment":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media?parent=450"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/categories?post=450"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/tags?post=450"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}