{"id":952,"date":"2021-07-23T12:41:58","date_gmt":"2021-07-23T12:41:58","guid":{"rendered":"https:\/\/ssdsunucum.com\/blog\/email-routing-configuration\/"},"modified":"2021-07-23T12:41:58","modified_gmt":"2021-07-23T12:41:58","slug":"email-routing-configuration","status":"publish","type":"post","link":"https:\/\/ssdsunucum.com\/blog\/email-routing-configuration\/","title":{"rendered":"Email Routing Configuration"},"content":{"rendered":"<\/p>\n
\n
\n
\n

Valid for versions 96 through the latest version<\/em><\/p>\n<\/div>\n

\n

Version:<\/h4>\n

96<\/h4>\n<\/div><\/div>\n
\n

Overview<\/h2>\n

The Email Routing Configuration<\/em> interface allows you to configure the entry for each destination mail server.<\/p>\n

How to edit MX entries<\/h2>\n

A mail exchanger (MX) entry determines which server receives mail for a domain name. To edit your server\u2019s MX entries, perform the following steps:<\/p>\n

    \n
  1. In the Choose a Domain to Edit<\/em> section, find the name of the domain in the list for which you wish to configure MX entries.<\/li>\n
  2. Click Edit<\/em>. A new interface will appear.<\/li>\n
  3. Select an Email Routing<\/em> setting for the domain.<\/li>\n
  4. Enter the desired settings for each MX entry in the MX Entries<\/em> section.<\/li>\n
  5. Click Save<\/em>.<\/li>\n<\/ol>\n

    Email Routing<\/h3>\n

    After selecting a domain to edit, you can choose one of the following Email Routing<\/em> settings:<\/p>\n

    Automatically Detect Configuration<\/h4>\n

    The recommended Automatically Detect Configuration<\/em> setting lets the system choose the most appropriate Email Routing<\/em> setting, based on a query of the MX record. The system queries the MX record and uses the following criteria to determine the Email Routing<\/em> setting:<\/p>\n

      \n
    • If the lowest priority mail exchanger points to an IP address on this server, the system selects the Local Mail Exchanger<\/em> setting.<\/li>\n
    • If a mail exchanger with a higher priority points to an IP address on this server, the system selects the Backup Mail Exchanger<\/em> setting.<\/li>\n
    • If there are no<\/strong> mail exchangers that point to an IP address on this server, the system selects the Remote Mail Exchanger<\/em> setting.<\/li>\n<\/ul>\n
      \n
      Important:<\/div>\n
      \n
        \n
      • The system cannot perform automatic detection for the Remote Mail Exchanger<\/em> setting if the MX entry does not<\/strong> resolve (for example, if you mistype a domain name or enter one that does not exist). Instead, the system generates a warning and defaults to the last known Email Routing<\/em> setting.<\/li>\n
      • For the Automatically Detect Configuration<\/em> setting to treat additional IP addresses as local, you must add them to the list of local IP addresses. Add IP addresses to the list in WHM\u2019s Configure Remote Service IPs<\/em> interface (WHM >> Home >> IP Functions >> Configure Remote Service IPs<\/em>).<\/li>\n<\/ul><\/div>\n<\/div>\n

        Local Mail Exchanger<\/h4>\n

        The Local Mail Exchanger<\/em> setting causes the server to always<\/strong> accept mail for the domain.<\/p>\n

        Backup Mail Exchanger<\/h4>\n

        The Backup Mail Exchanger<\/em> setting causes the server to accept mail for the domain and store it until a higher priority mail server becomes available.<\/p>\n

        Remote Mail Exchanger<\/h4>\n

        The Remote Mail Exchanger<\/em> setting causes the server to never<\/strong> accept mail for the domain. The system will always assign the lowest<\/strong> priority value to servers with this setting.<\/p>\n

        MX Entries<\/h3>\n

        You can configure the following values for each MX entry:<\/p>\n

          \n
        • TTL<\/em> \u2014 This integer value specifies the time to live (TTL). TTL indicates how long a particular record remains in memory, in seconds, before it refreshes. This value defaults to 14400.<\/li>\n
        • Priority<\/em> \u2014 This integer value represents the priority order of the mail server, in relation to other MX entries. The lower the Priority<\/em> value, the higher the server\u2019s priority. This value defaults to a value that is 10 higher than the highest existing MX entry\u2019s priority.\n
          \n
          Note:<\/div>\n
          \n
            \n
          • Servers with the lowest<\/strong> Priority<\/em> values act as the primary mail servers.<\/li>\n
          • Servers with higher<\/strong> Priority<\/em> values act as secondary mail servers.<\/li>\n
          • If multiple mail servers have the same Priority<\/em> value, the system distributes mail at that Priority<\/em> value to those servers randomly.
            \n<\/li>\n<\/ul><\/div>\n<\/div>\n<\/li>\n
          • MX Destination<\/em> \u2014 Enter the name of the mail server (for example, mail.example.com<\/code>).<\/li>\n<\/ul>\n

            Add and delete MX entry text boxes<\/h3>\n
              \n
            • To add a new MX entry text box, click Add Another MX Entry Field<\/em>. A new row will appear in the table with the (new)<\/em> label in the right column.<\/li>\n
            • To delete a row, click Delete<\/em> next to that MX entry.<\/li>\n<\/ul><\/div>\n","protected":false},"excerpt":{"rendered":"

              Valid for versions 96 through the latest version Version: 96 Overview The Email Routing Configuration interface allows you to configure the entry for each destination mail server. How to edit MX entries A mail exchanger (MX) entry determines which server receives mail for a domain name. To edit your server\u2019s MX entries, perform the following …<\/p>\n","protected":false},"author":1,"featured_media":953,"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\/952"}],"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=952"}],"version-history":[{"count":0,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/952\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media\/953"}],"wp:attachment":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media?parent=952"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/categories?post=952"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/tags?post=952"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}