Ensure that Messages are Delivered to Email

Ensure that Messages are Delivered to Email

To help ensure that email messages (like invoices and service notices) reach your recipients inbox, we recommend adding RingLogix to your SPF DNS record.

SPF (Sender Policy Framework) DNS records are used by many email providers to identify which mail servers are authorized to send email messages on behalf of your domain.

Any emails sent from a server that is not authorized via an SPF record is likely to be marked as spam and not reach the recipients inbox.

 

Disclaimer.

Managing DNS records is an ADVANCED network function. Only administrators with knowledge on how DNS works should attempt to make these changes. RingLogix does not offer DNS management services.

For more info on SPF you can visit this link: https://en.wikipedia.org/wiki/Sender_Policy_Framework
 
Limitation Details: As outlined in Section 10.1 of the SPF RFC, SPF implementations must adhere to a strict cap on the number of DNS lookups during an SPF check. Specifically, this limit is set at a maximum of 10 lookups. These lookups encompass any queries triggered by the “include” mechanism or the “redirect” modifier.



The Basics.

You’ll need access to change settings with your domains DNS provider.

SPF should be setup with a TXT record.

When making your updates it’s important that you include and or don’t remove any other email service provider that you use or may already exist.

The added entry of "include:spf.simplelogin.net" should be added to your record.

The RingLogix server IPs that should be authorized if firewall IP level is needed are 192.92.8.0/24, 64.52.82.0/24,64.52.83.0/24.

 

Examples of records with our server info:

Single include

  • Record Type: TXT
  • Name: typically left blank
  • Data: v=spf1 include:spf.simplelogin.net -all
Multiple includes
  • Record Type: TXT
  • Name: typically left blank
  • Data: v=spf1 include:spf.simplelogin.net include:example.com -all

Depending on your provider, you may need to add quotation marks around your entire SPF record.

 

Support Center Links for Popular DNS Providers

Amazon Web Services: Configuring DNS, Resource Record Types

Dreamhost: DNS Overview

GoDaddy: Add a CNAME Record

Google Domains: DNS Basics

Hostgator: Manage DNS records

Hover: Edit DNS Record

Namecheap: SPF & DKIM

Squarespace: Advanced DNS Settings

Stablehost: How do I get to cpanel?

1&1: Domain Guidelines

 

Testing your SPF record.

DNS updates can take anywhere from a few minutes to a couple days to apply.

You should test your entries after about 1 hour.

If your first test fails, don’t’ be concerned and just wait a bit longer (up to 48 hours).

We recommend using the SPF Lookup tool from MXToolBox: https://mxtoolbox.com/spf.aspx

If your SPF lookup is failing after 48 hours you will need to contact your DNS admin or provider for assistance.

    • Related Articles

    • HIPPA BAA Request

      Complete this form. We'll send an email with the agreement. RingLogix HIPPA BAA Request Form

    • How Inbound Calling Works

      How Inbound Calling Works The following is a detailed, technical article that explains the inbound calling process. This is an invaluable aid to a technician in troubleshooting inbound calling issues and working with RingLogix Customer Support. 1. ...

    • SIP and TLS

      TLS (Transport Layer Security) and SIP TLS is a common security protocol used for private, and secure communications over the Internet. When enabled, TLS encrypts the signaling of VoIP calls. Why Use TLS? TLS is often used for security purposes and ...

    • Voice Network Details

      RingLogix operates an Active/Active Geo Redundant Infrastructure to best meet the needs of our Partners and your Customers. Below are the addresses and related IPs for different segments of the network. We recommend that you always use auto ...

    • Understanding How NAT and Firewalls Affect UCaaS Services

      What is NAT? NAT (Network Address Translation) is a technology most commonly used by firewalls and routers to allow multiple devices on a LAN with 'private' IP addresses to share a single public IP address. Should I configure specific SIP or NAT ...