Provider documentation checked on 8 November 2026. Account-generated values, entitlements and current support remain deployment prerequisites.
Caspio's sender-address verification and domain verification are different controls. The first confirms access to an address; the second enables domain DKIM signing. A custom website domain under Deployment is another setting entirely. For email authentication, start with the Email tab in Account settings.
Verify the sender, then the domain
Caspio documents Account, Account settings, Email, Add email address. Enter the sender address, request its verification code and complete the address verification. Next select Verify domain for the owned domain and publish the displayed TXT and CNAME entries. Use Verify and monitor the domain's status. The documented sequence requires verifying an email address before verifying its domain. Email and domain verification
Copy the record values shown by Caspio. Do not use a sample selector or token. Arrange access to the sender mailbox and authoritative DNS with the responsible owners, and retain the exact record names and types. Consumer-provider domains cannot be authenticated as domains you own simply because you can receive mail at one address.
Reconcile SPF and sender replacement
References: RFC 7208 §3.2, RFC 9989 §4.4.2.
Caspio’s troubleshooting guide documents include:_spf.caspiomail.com. Its surrounding inbound-whitelisting language is not a correct general description of SPF. Treat any addition as an outbound authorization decision for the relevant envelope domain, not a recipient allowlist. Preserve other legitimate sources in the single policy at the applicable owner name. Do not treat a domain's SPF authorization as an inbound allowlist or a reason to bypass recipient security filtering. Its usefulness to DMARC still depends on the envelope identity and alignment.
Caspio says unverified sender addresses are replaced at send time with noreply@caspio.app, without changing the stored DataPage, Task or Triggered Action configuration. Therefore the configured From field alone may not be the delivered From identity. Inspect actual received mail rather than assuming that an old configuration screenshot proves branded sending.
Separate application logs from receiver evidence
References: RFC 6376 §6, RFC 9989 §5.3.5.
The Email Logs documentation describes an authenticated security status for successfully DKIM-signed outgoing messages. That is useful producer-side evidence, but not the same as a recipient verifying the signature or evaluating DMARC alignment. Retain both the application log and original received message. Caspio email logs
Original test plan: exercise a harmless DataPage notification, a representative Task and a Triggered Action where each is in use. Record workflow, sender configuration, delivered From, SPF identity/result, DKIM d=/s=/result and DMARC outcome. Use controlled recipients and synthetic application data, not real customer records.
Illustrative failure: a Task is configured with an unverified branded address and the delivered message uses the default Caspio address. It may authenticate as that provider domain, but it does not demonstrate successful branded authentication. Complete the address and domain workflow and repeat the Task test.
Troubleshoot without widening trust
Caspio's troubleshooting guide recommends checking the correct domain, all required DNS entries, authoritative placement and duplicated suffixes when verification remains pending. For delivery issues, its logs help distinguish message generation or sending problems from later receiving behavior. Troubleshooting
The troubleshooting guide says automated daily domain checks stop after a further 72-hour checking period following its pending-verification notice if the domain remains unverified. Do not assume a stalled status will be retried indefinitely; correct the DNS and confirm the verification workflow with the account owner or support.
If a test fails, pause only the affected automation where possible, preserve the logs and restore an approved verified sender if needed. Do not delete or replace a sender across application objects without reviewing the dependent workflows. This guide does not claim live Caspio execution; all test cases are proposed or illustrative, and no customer email was sent.