Send transactional mail from your own domains, DKIM-signed, over SMTP or an API.
Send the mail your application needs — sign-up confirmations, password resets, invoices — from your own domain, through Deutsche Cloud instead of an outside provider. Outbound only: there are no mailboxes and no inbound mail.
- Your domain, signed. Every message is DKIM-signed with a key generated for your domain. With a custom MAIL FROM (the default) SPF passes for your domain too, so DMARC passes on both.
- SMTP or HTTP. Point any SMTP library at the submission endpoint, or call the API.
- Built like SES. Sender identities, a sandbox for new organizations, sending quotas, and a suppression list per organization.
Status. Sender domains, sending over SMTP and the API, the message log, DMARC reports and one-click unsubscribe are available. The relays' addresses are new and are being warmed up (see Delivery and warm-up): until they have a sending history, Gmail and Microsoft may file some mail as spam.
Price: €0.10 per 1,000 recipients (email.message, billed per recipient a message was
accepted for; suppressed recipients are not billed). Sender domains, the message log and the
suppression list cost nothing.
Add a sender domain
In the console: Email → Add domain, or with the CLI:
dcloud email identities create --name example.comA 2048-bit DKIM key is generated for the domain. The domain needs these records:
| Purpose | Name | Type | Value |
|---|---|---|---|
| DKIM (verifies it) | <selector>._domainkey.<domain> |
TXT | v=DKIM1; k=rsa; p=… |
| MAIL FROM | bounce.<domain> |
MX | 10 smtp.de1.mail.apps.platform-development.deutschecloud.app |
| MAIL FROM SPF | bounce.<domain> |
TXT | v=spf1 include:spf.mail.apps.platform-development.deutschecloud.app -all |
| DMARC (optional) | _dmarc.<domain> |
TXT | v=DMARC1; p=none; rua=mailto:dmarc@reports.mail.apps.platform-development.deutschecloud.app — only if you have no policy yet |
The domain page lists them with the real values, ready to copy.
If the domain is in Deutsche Cloud DNS (one of your hosted zones), Create records in Deutsche Cloud DNS writes
them for you; this needs dns:ChangeRecords on the zone as well. A record set that already exists
at one of those names is left alone, and an existing DMARC policy is never replaced (only a DMARC
record Deutsche Cloud wrote itself follows your DMARC settings).
The domain is verified once public DNS answers its DKIM record. Deutsche Cloud checks every five minutes for 72 hours (or press Check now), and verified domains once a day after that: if the DKIM record disappears, the domain goes back to unverified, because mail signed with a key nobody publishes fails DKIM everywhere.
The MAIL FROM records are not needed to send. Without them the bounce address is on the platform's own bounce domain: SPF then passes for that domain rather than yours, and DMARC still passes through DKIM.
Sending
Use an access key whose user may email:SendEmail on the sender domain. Give an application a
user of its own with only that permission, not your own key.
Over SMTP
| Setting | Value |
|---|---|
| Host | smtp.de1.mail.apps.platform-development.deutschecloud.app (shown on the domain page) |
| Port | 587, STARTTLS (required before authenticating) |
| User name | the access key id (EWS1…) |
| Password | the access key secret |
| Auth | PLAIN |
With Nodemailer:
import nodemailer from 'nodemailer';
const transport = nodemailer.createTransport({
host: 'smtp.de1.mail.apps.platform-development.deutschecloud.app',
port: 587,
secure: false, // STARTTLS
auth: { user: process.env.EWS_ACCESS_KEY_ID, pass: process.env.EWS_SECRET_ACCESS_KEY },
});
await transport.sendMail({
from: 'Example <no-reply@example.com>',
to: 'user@example.org',
subject: 'Confirm your address',
text: 'Open this link to confirm: …',
});A refusal comes back as an SMTP error with the reason: 550 5.7.1 for a sender that is not a
verified domain of yours or a key without email:SendEmail, 554 5.7.1 for the sandbox, 452 4.5.3 for the daily quota, 451 4.7.1 for the per-second rate.
Over the API
curl -X POST "https://console.<platform domain>/email/api/send" \
-H "Authorization: EWS-ACCESS-KEY $EWS_ACCESS_KEY_ID:$EWS_SECRET_ACCESS_KEY" \
-H 'Content-Type: application/json' \
-d '{"from":"Example <no-reply@example.com>","to":["user@example.org"],
"subject":"Confirm your address","text":"Open this link to confirm: …"}'or dcloud email messages send --from … --to … --subject … --text …. Fields: from, to, cc,
bcc (at most 50 recipients in all), replyTo, subject, text and/or html, headers (X-…
and List-Unsubscribe only), attachments (filename, contentType, base64 content).
POST /email/api/send-raw takes a whole message you built yourself (raw, base64) and its
recipients. The answer is 202 with the message id and each recipient's state: queued, or
suppressed when the address is on your suppression list (accepted, never sent).
Limits
| Limit | Value |
|---|---|
| Message size | 10 MB including attachments |
| Recipients per message | 50 |
| Recipients per 24 hours | 200 in the sandbox, 50,000 after review |
| Recipients per second | 1 in the sandbox, 14 after review |
| Message log | 30 days |
Sandbox. A new organization can send only to its own verified identities (any address at a
verified domain) until an operator takes it out of the sandbox. Ask on Email → Sending, or
with dcloud email account request-production-access --use-case "…": say what you send, to whom,
about how many a day, and how recipients asked for it. Leaving the sandbox also moves your mail
to the relays' established addresses.
Bounce and complaint rates. Email → Sending shows both over the last seven days. Above 5 % bounces or 0.1 % complaints you are warned; at 10 % or 0.5 % (with at least 200 recipients in the window) sending is paused automatically, because the relays' addresses are shared and one sender's bad list hurts everyone's delivery. An operator resumes it after review.
One-click unsubscribe
For newsletters and other bulk mail, Gmail and Yahoo require a one-click unsubscribe (RFC 8058).
Send with "unsubscribe": true (API), or add the header X-DCLOUD-Unsubscribe: one-click (SMTP
or send-raw; the former X-EWS-Unsubscribe works too; Deutsche Cloud removes it), and every
recipient's copy gets
List-Unsubscribe: <https://console.platform-development.deutschecloud.app/api/email/unsubscribe/<token>>
List-Unsubscribe-Post: List-Unsubscribe=One-Clicksigned with the rest of the message. When the recipient presses Unsubscribe in their mail
program, the address goes on your suppression list
with the reason unsubscribe. The token names your organization and the address and is signed, so
nobody can unsubscribe an address that was not mailed. Opening the link in a browser shows a page
with one button; a plain visit (a link scanner) unsubscribes nobody. A List-Unsubscribe header of
your own is kept as it is.
The link does not expire: its signature uses a key that Deutsche Cloud keeps across rotations of its own encryption keys. Links in mail sent before 2026-11-16 were signed with the platform master key and stop working when Deutsche Cloud rotates it; opening one then offers to mail a fresh link to the address it was sent to (at most twice a day per address), so the recipient can still unsubscribe.
Turn it on for every message of a domain on the domain's page (One-click unsubscribe on every
message, or dcloud email identities update <domain> --list-unsubscribe). Once your organization has
sent 4,000 messages in 24 hours, every message gets it anyway: above 5,000 a day Gmail treats you as
a bulk sender, and bulk mail without it lands in spam for everyone sharing the relays.
DMARC
DMARC tells receivers what to do with mail that claims to come from your domain but fails DKIM and
SPF, and asks them to send a daily report about all mail they saw from it — from Deutsche Cloud and from
anyone else. On the domain's page, or with dcloud email identities update <domain>:
- Policy (
dmarcPolicy):none(report only, the default),quarantine(failing mail goes to spam) orreject.quarantineandrejectneedonlySendsThroughEws: true: if another service (Google Workspace, Microsoft 365, a newsletter tool) also sends as the domain without DKIM for it, its mail would be lost. Gmail and Microsoft trust a domain with an enforced policy more. - Your report address (
dmarcReportAddress): reports go there too. An address outside the domain must publish<domain>._report._dmarc.<its domain>v=DMARC1to accept them.
Saving rewrites the DMARC record in Deutsche Cloud DNS when Deutsche Cloud wrote it; otherwise publish the value shown under the domain's records yourself.
Reports. The DMARC record names Deutsche Cloud's report address, so the reports come to Deutsche Cloud. The domain's
page (dcloud email identities dmarc-reports <domain> --days 30) shows how many messages receivers
saw, how many passed DMARC, each sending IP address (Deutsche Cloud relays are named) with its DKIM and SPF
alignment, and a next step: move to quarantine once every reported message passed for 7 days,
to reject after 30 days of quarantine. Reports are kept 180 days.
Delivery and warm-up
- Over IPv4. The relays deliver over IPv4 only. Gmail and Microsoft judge IPv6 senders more strictly, and an IPv6 address would start without any history of its own.
- Warm-up. A new sending address has no reputation; the big receivers trust it after it has sent a steady, growing volume that people want. Each address of the established pool therefore delivers at most a daily number of messages per receiver (Gmail, Microsoft, Yahoo, everyone else): 50 on its first day, then 100, 200, 400, 700, 1,000, growing by half each day after that, spread over the day, until there is no cap on day 21 (day 28 for Microsoft and Yahoo). The day only advances when the address actually sent and receivers did not push back (under 5 % deferrals and 3 % bounces). Mail over the cap is not refused: it waits in the relay's queue and leaves within the next hours; the message log says so. Email → Sending shows today's caps while the addresses warm up.
- Pace per receiver. Each relay address also sends at a steady pace to any one receiving mail system: 60 messages a minute while it is new (and always from the sandbox pool), rising with the warm-up to 300 a minute for Gmail, 150 for Microsoft and Yahoo and 120 for everyone else; t-online, GMX, WEB.DE, IONOS and freenet stay at 60. No single sender may take a receiver's whole pace: a large burst from one account leaves at its share while other accounts' mail to the same receiver goes out within seconds.
- What you can do. Send from a domain with a DMARC policy (ideally
quarantine), with real content and a realFromname; avoid test-like messages ("test", a lone link). Ask your first recipients to move a message out of spam if it lands there — that teaches the receiver faster than anything else.
Message log
Email → Messages, GET /email/api/messages or dcloud email messages list: every message of the
last 30 days with each recipient's state — queued, delivered, deferred (the receiving server
asked to retry; retried for 24 hours), bounced, complained, suppressed or rejected — and
the receiving server's last answer. dcloud email messages get <id> shows every delivery attempt.
Bounces, complaints and the suppression list
An address that bounces permanently (no such user, no such domain) or whose owner marks a message as spam is put on the organization's suppression list, and nothing is sent to it again until it is removed. Bounces that arrive later by mail are matched to the message through its bounce address, which carries a signed token.
Sending to a suppressed address is not an error: the message is accepted and that recipient is
reported as suppressed. See and edit the list on Email → Suppression list, or with
dcloud email suppressions list|put|delete. Remove an address only when you know it works again —
sending to it while it still bounces counts against your bounce rate.
Permissions
| Action | Allows |
|---|---|
email:ListEmailIdentities |
list sender domains |
email:GetEmailIdentity |
read one, with its records and DMARC reports |
email:CreateEmailIdentity |
add a domain |
email:DeleteEmailIdentity |
remove a domain and its DKIM key |
email:UpdateEmailIdentity |
set the DMARC policy, report address and one-click unsubscribe |
email:VerifyEmailIdentity |
run the DNS check now |
email:PutEmailIdentityDnsRecords |
write the records into Deutsche Cloud DNS (with dns:ChangeRecords on the zone) |
email:SendEmail |
send from a domain (permitted sends are not audited, denials are) |
email:ListEmailMessages |
read the message log |
email:GetEmailMessage |
read one message with its delivery events |
email:GetEmailAccount |
read the quota, sandbox state and rates |
email:RequestProductionAccess |
ask to leave the sandbox |
email:ListSuppressedDestinations |
read the suppression list |
email:PutSuppressedDestination |
add an address to it |
email:DeleteSuppressedDestination |
remove an address from it |
Resource names: rn:ews:de1:<org>:email:identity/<domain>, so a policy can allow an application
to send from one domain only.
Not available
Inbound mail and mailboxes, templates, open and click tracking, dedicated IP addresses, sending
over IPv6, DMARC forensic (ruf) reports, and bring-your-own DKIM keys.