10to8 sends thousands of email and SMS messages every day. Delivery issues are unusual, but can sometimes occur. This guide provides information about the processes behind 10to8's messaging and recommends various troubleshooting steps.
SECTIONS:
How to troubleshoot Email delivery issues
- AWS Simple Email Service (SES)
- SPF
- DKIM
- DMARC
How to troubleshoot SMS delivery issues
- Recognizing SMS delivery or failure
- Reasons your SMS may have failed to deliver
How to troubleshoot Email delivery issues
Most emails sent from 10to8 are delivered successfully. Delivery issues may be more common in corporate environments with enterprise IT.
This section outlines 10to8's email delivery process and provides troubleshooting steps for your IT team.
AWS Simple Email Service (SES)
We use Amazon's SES with AWS to deliver all of our emails. Many of our emails come from IP addresses managed by AWS, which have the following ranges:
- 199.255.192.0/22
- 199.127.232.0/22
- 54.240.0.0/18
- 69.169.224.0/20
- 76.223.176.0/24
- 76.223.180.0/23
- 76.223.188.0/24
- 76.223.189.0/24
- 76.223.190.0/24
We also use dedicated IP addresses for many of our emails:
- 23.249.217.229
- 23.249.217.230
- 23.249.221.54
- 23.249.221.55
- 23.249.221.56
- 23.249.221.57
- 23.249.221.58
- 23.249.221.59
Note: these IP addresses are subject to change. SPF makes IP address filtering redundant, so we strongly advise against it.
All of 10to8's emails are delivered from addresses in this format:
reply-aXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX@comms.10to8.com
The long code uniquely identifies the message.
SPF
SPF is an email standard designed to prevent email spoofing by allowing domains to announce which IP addresses are allowed to send emails for that domain.
This announcement is done with a DNS TXT record, so uses the authority of the DNS system.
A bad actor attempting to send fraudulent emails from what looks like the 10to8 domain, would fail. These emails would not originate from an IP address approved by 10to8, so recipient email systems could then reject the email.
All modern email systems support SPF verification. SPF is defined in rfc7208.
When one system receives an email from another server, claiming to be from a particular domain, the receiving system can query the DNS TXT records for the domain, read the SPF details and verify the sending server is permitted to send that email.
10to8 has SPF DNS TXT entries for all outbound emails. Our setup differs from the default AWS SES SPF configuration so that we can support DMARC.
DKIM
DKIM is an email authentication system designed to prevent email spoofing by allowing domains to publish encryption keys that can be used to verify that an email is from the person it claims to be from.
These encryption keys are public, and are shared as TXT records in the DNS system. A bad actor attempting to send phishing emails would fail this test because they would not be able to generate a valid digital signature for the email.
All modern email systems support DKIM verification. DKIM is defined in rfc6376.
When a system receives an email, the email will contain a digital signature in the DKIM header. The receiving system then queries the sending domain's TXT records to find the public key against which the digital signature is verified.
10to8 uses DKIM verification, with AWS's SES standard configuration.
You can read more about SPF and DKIM here.
DMARC
DMARC is a mechanism for domains to set policies and report on email deliveries. This means that recipient email systems send daily reports back to 10to8 about emails that they have received, apparently from 10to8.com, so that 10to8 can monitor attempted fraudulent behavior by bad actors.
As with SPF and DKIM, these are configured with a DNS TXT entry. Using these policies, a domain such as 10to8.com can specify:
1) What should happen to emails that fail SPF and DKIM tests - 10to8 requests a report.
2) Which email address reports on failures and deliveries should be sent to.
DMARC isn't as widely supported as SPF and DKIM, but is still a vital tool in identifying delivery issues.
10to8 fully supports DMARC. Our DMARC feedback email address is dmarc@10to8.com. We monitor these reports to identify email delivery issues early on.
Things to check
While 10to8 makes every effort to guarantee delivery, there can still be problems, especially with email servers that predate modern anti-spam techniques. Several things that your IT team might be able to check are:
1) Do you use SPF and DKIM for verifying inbound emails?
2) Does your system report on errors regarding SPF and DKIM?
3) Do you have auto-forwarding set up for inbound emails? We have seen cases where forwarding an email damaged the DKIM cryptographic signature.
4) Does your system support DMARC delivery reporting? If so, it is possible that your system could report back to us automatically when there are delivery issues, reducing the complexity of fixing the problem.
How to troubleshoot SMS delivery issues
Recognizing SMS delivery or failure
10to8 uses Twilio and some other providers to send SMS messages to your customers.
SMS failure is rare, but it's important to know how to recognize it. This section will help you with that.
Your message records can be found by clicking on the relevant booking within your calendar. This will open a sidebar to the right. Your message history will be visible within the activity window.
You'll find a record of all messages here - both SMS and Email.
SMS messages are labeled with a speech bubble icon:
Whilst Emails are labeled with an envelope icon:
When an SMS message has been successfully sent and delivered to your customer, you'll see a double tick underneath the message.
If the message has been successfully sent but not yet delivered, you'll see a single tick underneath the message. This means the message hasn't yet come through to the customer's phone, and they won't have received it yet.
This can happen if the customer's phone is off or out of signal range.
The message will usually be delivered eventually, once the customer's phone is back on and receiving a signal.
When an SMS message hasn't been sent or delivered, you'll see a red 'X' symbol underneath the message, notifying you that the message has been rejected.
Reasons your SMS may have failed to deliver
1) The most common cause of failed SMS delivery is an incorrect phone number. The customer's number might have changed, they might have made a mistake when entering it, or accidentally included a space or extra character.
Spaces might not be obvious, but might be included at the beginning or end of the number, which could stop the message from being successfully sent.
2) Very occasionally, SMS messages cannot be sent due to mobile network limitations or carrier content filtering.
3) Rarely, our SMS provider could be down, meaning we can't connect to them to get your messages sent.
4) SMS messages can temporarily fail to deliver due to the mobile being out of range or powered off.
Things to check
If 10to8 isn't showing that the message has been rejected, wait a couple of hours or until you see the rejected symbol, before doing the following:
1) Check for any obvious errors in the mobile number, and that it's definitely a mobile number. 10to8 can't send SMS messages to landline numbers.
2) Check with the customer that their mobile number hasn't changed and if possible, whether or not they have recently had their mobile phone powered off or out of range.
3) Check our service status page for any general issues by clicking here.
Need More Help?
We hope this guide has been useful! If you need further help, reach out to our support team who will be happy to assist.