Sending domains and DNS

Before you can send from an address such as noreply@example.com, you add example.com as a sending domain and publish its DNS records. Yeap Cloud then signs every message with your domain's DKIM key, so receivers can check that the mail really comes from you.

#Add a sending domain

1. Open Email sending, click the stream, and go to the Sending domains tab.
2. Click Add domain.
3. Enter the domain that will appear after the @ in your From address, such as example.com. A subdomain such as mail.example.com also works and keeps your sending reputation separate from your main domain.
4. Select Shared by all streams if every stream on your account should be able to send from this domain. Leave it clear to bind the domain to this stream only.
5. Click OK. The domain is added and its DNS panel opens.

The counter next to Add domain shows how many domains the stream uses out of its plan limit. When the limit is reached, the button is disabled.

Keep in mind:

• A domain belongs to one account. If another Yeap Cloud account has already verified the domain, you can't add or verify it. The console shows already verified by another account. If you believe this is wrong, contact support.
• Platform domains (yeapcloud.net and yeap.cloud) can't be used as sending domains.
• You send from verified domains only. The From address of every message must be at a verified domain that the stream can use. Otherwise the message is refused.

#Shared or bound to one stream

You can change this later with the Shared by all streams switch in the domain's DNS panel. A shared domain is marked Shared in the list. Making a domain shared fails if any of your streams has no room left in its domain limit.

#DNS records

The DNS panel lists the records for your domain with their exact values. Copy them from the console: the DKIM key is unique to each domain.

• DKIM is the record that matters for sending. The domain becomes verified as soon as this record is live, and every message is signed with it, so DMARC passes through DKIM alignment.
• SPF: a domain can have only one SPF record. If example.com already has a v=spf1 record (for example for Domain Mailbox or another sending service), add include:_spf.tm.yeapcloud.net to that record instead of creating a second one.
• DMARC: if the domain already has a DMARC record, keep it. The suggested p=none value only starts monitoring. Move to p=quarantine or p=reject once you've confirmed that all your legitimate mail passes.

#One-click DNS (Yeap Cloud DNS)

If the domain is hosted in Yeap Cloud DNS, the panel shows Hosted in Yeap DNS and compares each record with what's in your zone:

1. Check the plan: records that are missing are marked as new, an existing SPF record is shown with the merged value, and an existing DMARC record is left alone.
2. Click Add in one click and confirm. The records are written to your zone.
3. About three seconds later, verification runs automatically.

If the domain's name servers don't point to Yeap DNS yet, the panel warns you. The records only resolve once the name server change has taken effect.

#Manual DNS (other providers)

If the domain is hosted elsewhere, the panel shows Add these at your domain's DNS provider:

1. Sign in to your DNS provider and create the records exactly as shown. Some providers want only the host part in the name field, for example tm1._domainkey instead of tm1._domainkey.example.com.
2. Wait for the records to propagate. This usually takes a few minutes, but depends on your provider and TTLs.
3. Click Check public DNS to see what the public DNS returns, then click Verify.

#Verification status

Next to the status, the DKIM, SPF, Return-Path and DMARC tags turn green when the matching record is found. Last checked shows when the domain was last checked.

Verification runs when you click Verify. If you remove or change the DKIM record and verify again, the domain goes back to Unverified and you can no longer send from it.

#Delete a domain

On the domain's row, click Delete and confirm. You can't send from the domain afterwards. If you add it again later, a new DKIM key is generated and you must update the DKIM record in DNS.

#Related

• Transactional & Marketing Mail overview
• SMTP and HTTP API
• Yeap Cloud DNS