Sending From Your Own Email Address: SPF/DKIM Setup and Suppressed Addresses
You add SPF and DKIM records to your domain, the panel verifies them for you; addresses that bounce or report spam are suppressed automatically and…
Where to find it: Left menu → Integrations → Email section → Email health, Sender domain authentication and Suppressed addresses cards Who it is for: Anyone sending from their own domain (like
orders@mystore.com) who wants those emails to actually arrive. In short: You add SPF and DKIM records to your domain, the panel verifies them for you; addresses that bounce or report spam are suppressed automatically and never bothered again.
Why is this needed?
When a mail server receives an email claiming to come from your domain, it asks: "Was this really sent by the owner of this domain?"
DNS records answer that question. If the records are missing, the receiving server either drops your email into the spam folder or rejects it outright. This is not something Treyza controls — you must add the records to your domain's DNS settings yourself.
There are three records:
| Record | What it does | Required? |
|---|---|---|
| SPF | A list saying "these servers may send on my behalf". | Yes |
| DKIM | Cryptographically signs the email, proving it was not altered in transit. | Yes |
| DMARC | Tells receivers what to do when SPF/DKIM fail, and sends you reports. | Recommended |
Tip: If you use the Treyza infrastructure (you have not configured your own SMTP/Resend account), you can skip this section. The records are already in place on the Treyza side.
Setup steps
- First configure your SMTP or Resend account from the Email sending chain card and enter your sender address.
- Go to the Sender domain authentication card.
- Pick the account you want to verify from the Provider list.
- Press Verify. The panel queries your domain's DNS records and reports SPF / DKIM / DMARC separately.
- If records are missing, look at the DNS records to add list at the bottom of the card. Copyable values have a copy button next to them.
- Add the records wherever you manage your domain (GoDaddy, Cloudflare, Namecheap, etc.).
- Wait 15 minutes to 24 hours and press Verify again. DNS changes do not propagate instantly.
If you use Resend
Resend generates the DKIM key specifically for you. The panel therefore cannot give you the DKIM value; it only tells you which name to add it under.
- Open Domains → your domain in the Resend panel.
- Add the records listed there to your DNS (usually SPF and MX for a
send.subdomain, plus DKIM forresend._domainkey). - Confirm the result with the Verify button in the Treyza panel.
You can leave the DKIM selector field empty; resend is tried by default.
If you use your own SMTP server
The include: value in the SPF record depends on your provider; take the correct value from your SMTP provider's documentation. The panel gives you the template:
v=spf1 include:YOUR-PROVIDER-SPF-DOMAIN ~allCaution: If your domain already has an SPF record, do not add a second one. A domain may have only one SPF record; add the new include: value inside the existing record.
For DKIM your provider gives you a selector (such as default, selector1, mail). Enter it in the DKIM selector field and press Verify. The panel also tries common selectors on its own, but entering the correct one makes the result definitive.
DMARC
The DMARC record is provided as copyable and can be added directly:
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.comp=none means "monitor only, do not block anything". After collecting reports for a few weeks and confirming that all of your sending sources pass SPF/DKIM, you can move to p=quarantine and then p=reject.
Caution: Do not set p=reject before SPF and DKIM are fully in place; it will cause your own email to be rejected.
I see "Not verified" — has sending stopped?
No. Treyza does not block sending from an unverified domain. You only see a warning badge.
The reason: DKIM selectors vary from provider to provider and the panel cannot know every possibility. Cutting off a working store's email because of a false "not verified" result would do more harm than leaving the setup incomplete.
But be aware: until the records are complete your deliverability stays low — a significant share of your email lands in spam.
Email health card
This card shows the delivery picture for the last 30 days:
| Metric | Meaning |
|---|---|
| Delivered | Emails confirmed as delivered to the recipient's mailbox. |
| Bounced | Emails that could not be delivered. Split into hard (address does not exist) and soft (mailbox full). |
| Complaints | Emails where the recipient pressed the "spam" button. |
| Suppressed addresses | Number of addresses currently not being emailed. |
Tip: The card warns you if the complaint rate goes above 0.1%. That is a critical threshold in the email world; once crossed, your domain reputation drops quickly. If you see such a warning, review your campaign lists and consent process.
What does "Not measured" mean?
For the rates to be calculated, your provider has to report delivery information back to Treyza.
- Resend: all data fills in once you set up the webhook (see below).
- SMTP only: the SMTP protocol does not report bounces that arrive later. In that case only addresses the server explicitly rejects at send time can be captured; the rates stay "not measured".
This is not a bug but a limit of the technology you use — the panel says plainly what it cannot measure instead of inventing numbers.
Resend webhook setup
For bounce and complaint information to reach Treyza, you must define a webhook in Resend.
- Open Integrations → the Resend card. Above the form you will see a Webhook URL specific to your store; copy it.
- In the Resend panel go to Webhooks → Add Webhook and paste the URL.
- Select these events:
email.sent,email.delivered,email.bounced,email.complained,email.delivery_delayed. - Resend gives you a Signing Secret (starting with
whsec_). Copy it. - Paste it into the Webhook Signing Secret field on the Resend card in Treyza and save.
Caution: If you do not enter the signing secret, incoming webhook requests are rejected. This is a deliberate security measure: without signature verification anyone could send fake requests and get your customers' addresses suppressed.
Suppressed addresses
When an address bounces or reports spam, Treyza adds it to the suppression list and stops sending to it. This keeps you from bothering your customer and protects your domain reputation.
Which case blocks what?
This is the most important rule of the list — not every suppression blocks every email:
| Case | Order, shipping, password reset | Campaign, automation |
|---|---|---|
| Hard bounce (address does not exist) | Blocked | Blocked |
| Soft bounce (below threshold) | Sent | Sent |
| Soft bounce (5 consecutive) | Blocked (7 days) | Blocked (7 days) |
| Spam complaint | Sent | Blocked permanently |
| Unsubscribed | Sent | Blocked permanently |
| Manual suppression | Per the scope you choose | Per the scope you choose |
The critical row here is the spam complaint. When a customer marks your campaign email as spam, that means "stop sending me marketing" — not "I do not want to know where my order is". So a complaint blocks marketing email only; order confirmations and shipping notifications keep going out.
A hard bounce is different: the address genuinely does not exist. Since nothing will ever reach it, both classes are blocked.
Why are soft bounces time-limited?
The mailbox may be full or the recipient's server temporarily down. A single soft failure is not grounds for suppression; a counter is kept. After 5 consecutive soft bounces the address is suppressed for 7 days, then the suppression lapses on its own and sending is retried.
If an email is delivered successfully in between, the counter resets.
Using the list
The list uses the same toolbar as the panel's other lists (products, orders).
- Search: search by address or detail. The search applies on its own once you stop typing.
- Reason filter: show only hard bounces, or only complaints.
- More actions → Refresh: reload the list.
- More actions → Download CSV: download the whole list as a spreadsheet.
- More actions → Customize Columns: hide the columns you do not need.
- Suppress address: add an address manually. You choose the scope (all emails / marketing only).
- Remove suppression: open the ⋮ menu at the end of the row, choose Remove suppression and confirm.
- Pagination: page navigation buttons and a Rows per page selector sit below the list; your choice is remembered in the browser.
Caution: Before removing a suppression, make sure the address is genuinely fixed. Continuing to send to a non-existent address raises your bounce rate and lowers deliverability for your whole store.
Who does the list belong to?
The suppression list is specific to your store. If the same address is suppressed in another store, your sends are unaffected; and your list does not affect other stores.
Frequently asked
Do suppressed addresses consume my quota when sending a campaign? No. Suppressed addresses are removed from the campaign audience before sending starts; no quota is spent on them.
A customer did not receive an order confirmation — what could be the reason? Search the address in the suppressed addresses list. If the reason is "Hard bounce", the address may have been mistyped; get the correct address from the customer, update their record, then remove the suppression.
What happens to customers in an email flow (drip)? If there is a permanent suppression, the customer exits the flow. If it is a temporary one, only that step is skipped and the flow continues.
Can I add addresses to the list myself? Yes. Use the Suppress address button. If you choose "Marketing only", the customer stops receiving campaigns but keeps receiving order emails.
Related topics
- Email Sending Chain — configuring, ordering and testing SMTP and Resend
- Managing Integrations
Was this page helpful?
Email Delivery Chain (Send From Your Own Address)
You define SMTP and Resend at the same time and set an order between them; your emails go out through the first working service in the order, and if…
Social Login (Google / Apple)
You enter your own Google/Apple keys; the matching buttons then appear automatically on your storefront's login and register pages. A provider whose…