Transactional emails are the ones your customers wait for: the login code, the password link, the order confirmation, the invoice. When they arrive late or in spam, you get support tickets, abandoned purchases and lost trust. Three things matter for these emails: speed, deliverability and transparency.
Separate from newsletters
ridu sends transactional email and broadcasts through separate IP pools. A newsletter that draws complaints can never damage the reputation your password emails rely on. Newsletter unsubscribes don't affect transactional email either – invoices still arrive.
Delivered securely
- DKIM signature with your domain's key, SPF and DMARC alignment via the return path.
- Encrypted delivery via STARTTLS; where the recipient publishes MTA-STS or you enable “enforce TLS”, the certificate is verified.
- Retries with increasing intervals on temporary errors, for up to 72 hours.
- Immediate suppression of non-existent mailboxes to keep the bounce rate low.
You see what happens
Every email has a timeline in the dashboard: accepted, delivered, delayed, bounced – with the receiving server's response. The same events reach your application as signed webhooks, for example to show in your support tool whether an invoice arrived.
Safe against duplicates
Network errors happen. With one Idempotency-Key per operation – the order number, say – a repeated request creates no second email. That holds for the API and for SMTP.
Templates for every case
Create templates for welcome, password reset or invoice emails, test them with sample values in the live preview and publish them. Your application only sends the variables; copy changes need no deployment.