Creating Email Channels
Learn how to add an Email channel in TextPeak, publish the DNS records your sending domain needs, and confirm that verification has completed.
Creating Email Channels
An Email channel sends transactional and campaign email from a domain you own and receives the replies into the TextPeak inbox. This article walks you through creating the channel on the Channels > Email page, publishing the DNS records the domain needs, and confirming that verification has completed.
NOTEAn Email channel needs a domain you control, such as
example.com. A free mailbox on a provider domain, such as a Gmail address, cannot be verified because you cannot publish DNS records for it.
Opening the Email channel list
- Log in to TextPeak in your browser.
- Click Channels in the main menu on the left, then open the Email card.
- The Email channels page lists every Email channel on the account.
The Email channels page
Creating the channel
- Click Add channel.
- On the Channel details step, enter a Channel name and a Channel description.
- Set Enable IP ACL if you want to restrict which addresses may call the channel, and add any Tags.
- Click Next.
Adding the sending domain and its addresses
The Email settings step is where you name the domain the channel sends from and the addresses on it.
Email settings, with the sending domain and its addresses
- In Sending domain, enter the domain, such as
example.com. - Under Addresses on this domain, enter each address the channel sends from and receives on, such as
[email protected], then click the plus icon. Add at least one address. - Click Save changes.
NOTEBoth halves are required. TextPeak verifies the domain on Amazon SES, and the addresses tell the platform which mailboxes on that domain belong to this channel.
Publishing the DNS records
Saving the domain generates the DNS records it needs. TextPeak lists them under Add these DNS records, and you publish them at your DNS host, such as GoDaddy, Porkbun, or Google Domains.
Add these DNS records, with the verification and DKIM records
The bounce, SPF, and DMARC records
Refer to the following table for what each record does.
| Type | Name | Purpose |
|---|---|---|
| MX | example.com | Routes inbound mail for the domain to the platform, so replies reach your inbox. Priority 10. |
| TXT | _amazonses.example.com | Proves you control the domain. |
| CNAME | Three ._domainkey.example.com records | DKIM keys that sign outgoing mail so receivers can confirm it came from you. |
| MX | bounce.example.com | Routes bounce and complaint notifications back to the platform. Priority 10. |
| TXT | bounce.example.com | The SPF record that authorizes the sending service. |
| TXT | _dmarc.example.com | The DMARC policy for the domain. |
To publish a record, copy it with the copy icon at the end of its row, then add it at your DNS host using the Type, Name, Value, and, for the MX records, the Priority shown here.
Checking each record
Every record carries its own status badge, and that is where you look when a domain will not verify.
| Badge | What it means |
|---|---|
| Verified | The record was found at your DNS host and its value matches. |
| Not Found | No record of that type and name was found. It has not been published, or it has not propagated yet. |
| Wrong Value | A record was found, but its value does not match the one shown here. Copy the value again and replace what you published. |
WARNINGAdd every record. A domain with some of its records published stays unverified, and the channel cannot go live until all of them resolve.
Confirming verification
Verification runs on the DNS side and can take up to 72 hours to complete, depending on how quickly your host propagates the change.
- A Verified badge next to Add these DNS records means the domain has passed.
- To re-check before the badge appears, open the channel and click Show DNS records under Domain records in Channel management.
Domain records in Channel management
TIPIf the badge has not appeared after 72 hours, compare each published record against the row in the table, character for character. A trailing dot or a missing subdomain in the Name field is the usual cause.
Using the channel
Once the domain is verified, select the Email channel in the sender profile you want it to send from, and set its incoming routing so replies reach the right team. See Sender Profiles and Incoming Routing.
For the actions every channel shares, such as the token and the lifecycle controls, see TextPeak Channels Overview.
Updated about 3 hours ago