By default, emails through Pyn are sent from email@example.com. In this article, we have instructions on how to update your sender to be an email or alias from a company domain. We recommend configuring a Custom Sender or connecting your Gmail account to better engage your employees.
Configuring and authenticating a Customer Sender will allow you to use your company domain to send emails and keep them out of spam or promotion folders.
Before you start
Here are some things to know before you begin.
You'll need to verify an email address on the domain, so we know you receive emails there. You can verify any email address on a domain to start the authentication process.
To send from a custom email address, you first need to authenticate your domain so we know you have permission to send email from it.
While email verification is very easy (entering a code we send you), authenticating the domain requires updating records for your domain, and may require assistance from another team.
How to set it up
To authenticate your domain, you'll need to do the following:
Verify an email address on your domain.
Copy and paste information from Pyn into your domain's records (see below for instructions).
Wait for your domain to propagate the information (it can take about 15 minutes for us to see the updated CNAME entries).
Authenticate the new entries on Pyn.
To complete these steps in Pyn, do the following:
Log into your Pyn account, select "Settings" and then "Domains".
Click "Add a domain" in the top right.
First you will need to verify an email address you can read message at on your domain. Enter your name and the email address, and click "Verify Email".
You will be sent a code to that address - once you receive it, enter it on Pyn.
Next, authenticate the domain by clicking the "Authenticate" button.
You will then be given a list of entries to update your domain with. Once you have updated these entries on your domain (instructions below), wait around 15 minutes, and then click the "Authenticate" button to have Pyn check for them.
If Pyn is able to see the entries, your domain is now authenticated and you can start using custom senders. If not, we will continue to retry the authentication for the next 3 hours. If after this time your domain is still not authenticated, please restart the authentication process once your DNS entries propagate.
Here is a detailed video on how to configure a custom sender:
Edit DNS Records with common domain providers
Here are some instructions for editing DNS records with popular domain providers. If your service isn't listed here, log in to your provider's site and search their help documents, or contact their customer support team.
Bluehost Bluerock: Manage DNS Records
Bluehost Legacy: DNS Management
Dreamhost: DNS Overview
GoDaddy: Add a CNAME Record
Google Domains: DNS Basics
Hostgator: Manage DNS records
Hover: Edit DNS Record
IONOS: Configuring CNAME Records
Namecheap: SPF & DKIM
Squarespace: Advanced DNS Settings
Stablehost: How do I get to cpanel?
Wordpress: Adding Custom DNS Records
Siteground: Create CNAME Records
Didn't receive the verification email?
Allow up to 5 minutes after requesting the verification.
Check your spam folder.
Make sure the email address is correct.
You can re-request the verification email from the verify screen for the domain.
Trying verifying a different email address you or your team have access to.
Can't authenticate the domain?
Make sure you set up the keys correctly - different domain providers treat CNAME configurations differently.
The 3rd CNAME listed will be shorter as it does not include "_domainkey."
Depending on your DNS settings, it could take up to a day or more for the fields to propagate.
For additional support please contact firstname.lastname@example.org.