SRVO Send

SRVO Send sends email from your own domain through an email API or SMTP. Manage domains, Send keys, email delivery and suppressed addresses in the Send module. Our email infrastructure is in the EU, in Frankfurt.

Add and verify a domain

1. Open Send → Domains and add your sending domain, such as mail.example.com.
2. Copy the DNS records SRVO shows into your DNS provider’s settings. Copy the exact values for your domain.
3. Add both DKIM CNAME records, srvo1._domainkey and srvo2._domainkey.
4. Add the bounce CNAME, send, pointing to mf-eu.srvo.app. If you chose a different return-path label, use that label.
5. Add the recommended _dmarc TXT record if your domain has no DMARC policy. Keep an existing policy.
6. Save the records, then select Verify in SRVO. Verification usually takes minutes. If it stays pending, check the record names and values at your DNS provider.

Some DNS providers append your domain to record names. Avoid adding it twice. On Cloudflare, use DNS only for these CNAMEs. Sending requires a verified domain.

Automatic DNS setup through Domain Connect is coming soon. Add the records manually for now.

Create a Send key

Open Send → API keys and create a named key.

• Sending access (sending_access) is for applications that send email. You can restrict it to selected domains.
• Full access (full_access) also allows Send administration. It does not grant access to other SRVO modules.

Copy the secret when it appears. SRVO shows it only once. Store it in your application’s secrets and revoke keys you no longer need. These are Send keys, separate from the general SRVO API keys in Settings.

For integration examples, see Send API and SMTP.

Check email delivery

Open Send → Emails to see the email log. Filter by status, then select a message to open its details. The details show the recipient, message type, creation time, delivery attempts and available delivery events. Failed messages also show a reason.

Queued means SRVO accepted the message for sending. It does not mean it reached the recipient. Check the later delivery status when investigating a missing email.

Manage the suppression list

SRVO skips recipients on your workspace’s suppression list. Other workspaces have their own lists. Reasons include a permanent delivery failure, called a hard bounce, a spam complaint, an unsubscribe or a manual block.

Soft-bounce suppression after three temporary delivery failures within 72 hours is coming soon. Temporary failures do not currently add an address to the list.

To remove an address:

1. Open Send → Suppressions and search for the email address.
2. Select Remove next to the address.
3. Read the confirmation and confirm removal. Sending to this address becomes possible again.

Remove an address only after resolving the delivery problem or confirming that the recipient wants your emails. Full-access Send keys can also manage suppressions through the Send API.

Sending limits and warm-up

Each recipient in To, Cc and Bcc counts as one email. Suppressed recipients do not count. A message can have up to 50 recipients in total.

New workspaces start with a warm-up ramp, based on the workspace’s age:

• First 7 days: up to 200 recipients per rolling 24 hours and 50 per hour.
• From day 7 until day 30: up to 2,000 recipients per rolling 24 hours.
• After 30 days: the warm-up ramp ends. Other sending limits still apply.

Contact our team to request an earlier lift of the ramp. High bounce or complaint rates can pause sending; contact SRVO support if this happens. Request limits also apply; see Send API and SMTP.

Coming soon

Broadcasts, Audience and contacts, and Templates are coming soon. Use the API or SMTP to send your application’s emails today.