Transactional email
Messages a customer is waiting for, delivered in seconds.
- Order receipts and invoices
- One-time passwords and sign-in codes
- Password resets
- Shipping and account alerts
RichSMTP is the SMTP service provider for businesses whose email carries revenue: dedicated SMTP servers and IPs, warm-up managed for you, a secure email relay with TLS on every connection, and a strict sender policy that keeps spammers off your infrastructure.
RichSMTP is the SMTP service provider for teams that have outgrown shared infrastructure. You keep your code, your templates and your From addresses; we run the dedicated IPs, the warm-up and the reputation work behind them.
Your mail leaves from IP addresses no other sender uses, so the reputation mailbox providers judge you on is yours alone. Start with a dedicated IP, or a private pool sized to your volume.
TLS on every connection, separate credentials for every application, and only verified domains you own allowed to send. A drop-in SMTP relay: change the host and credentials, nothing else.
New IPs and domains are warmed for you, provider by provider. Volume rises only while complaint and bounce data stay clean.
Every message is DKIM-signed for your domain with 2048-bit keys and aligned with SPF and DMARC.
Authentication-Results: spf=pass dkim=pass dmarc=pass
Bounces and complaints are suppressed automatically, and every sending domain is checked against blocklists before mail goes out.
Every delivery, deferral, bounce, complaint, open and click is recorded as it happens and can be pushed to your own systems by webhook.
| Time | Event | Recipient | Detail |
|---|---|---|---|
| 12:04:31 | delivered | maya@example.org | 250 OK |
| 12:04:33 | deferred | liam@example.net | 451 try later · retrying |
| 12:04:38 | bounced | old.address@example.com | 550 no such user · suppressed |
| 12:04:41 | opened | maya@example.org |
Messages a customer is waiting for, delivered in seconds.
Large sends to people who opted in, paced for every provider.
Five things happen to every email you hand to RichSMTP. None of them needs a line of code from you.
235 Authenticated
Your app connects over TLS and signs in with its own SMTP credential.
DKIM-Signature: d=yourdomain.com
The message is DKIM-signed for your domain, so receivers can prove it is yours and unaltered.
451 → retry
Mail is paced for each mailbox provider. Temporary failures are retried with backoff instead of being dropped.
250 OK
The relay hands the message to the recipient’s mail server, encrypted whenever that server supports TLS.
event: delivered
Delivered, deferred, bounced or complained about — each outcome becomes an event you can read or receive by webhook.
Email deliverability comes down to what mailbox providers such as Gmail, Outlook and Yahoo check on every message: whether it is authenticated, how the sending domain and IP have behaved before, and how recipients react. RichSMTP is designed around those signals, and on dedicated IPs your reputation is built by your mail alone.
Every message leaves authenticated. SPF, DKIM and DMARC line up with the domain in your From address, which is what the large mailbox providers now expect from bulk senders.
New domains and new IPs start small. Sending volume grows step by step as providers see healthy mail, which is what IP and domain warm-up means in practice.
Addresses that hard-bounce or complain are suppressed automatically. Mailing dead addresses again and again is the fastest route to the spam folder.
RichSMTP is built for permission-based email: receipts, alerts and newsletters that people expect to receive.
| Record | What it tells a receiving server | DNS type |
|---|---|---|
| SPFSender Policy Framework | “These servers are allowed to send email for my domain.” | TXT |
| DKIMDomainKeys Identified Mail | “This message was signed by my domain and has not been altered.” | TXT |
| DMARCDomain-based Message Authentication, Reporting and Conformance | “If SPF and DKIM fail, do this with the message — and send me reports.” | TXT |
You publish these once on your sending domain. Your MX records and incoming email are not touched.
There is no SDK to install and no template language to learn. Use the mail library you already have and change three settings.
Node.js
import nodemailer from "nodemailer";
const transport = nodemailer.createTransport({
host: process.env.RICHSMTP_HOST,
port: 587, // STARTTLS
auth: {
user: process.env.RICHSMTP_USER,
pass: process.env.RICHSMTP_PASS,
},
});
await transport.sendMail({
from: "Acme Receipts <receipts@yourdomain.com>",
to: "maya@example.org",
subject: "Your receipt",
text: "Thanks for your order.",
});
Python
import os, smtplib
from email.message import EmailMessage
msg = EmailMessage()
msg["From"] = "Acme Receipts <receipts@yourdomain.com>"
msg["To"] = "maya@example.org"
msg["Subject"] = "Your receipt"
msg.set_content("Thanks for your order.")
with smtplib.SMTP(os.environ["RICHSMTP_HOST"], 587) as smtp:
smtp.starttls()
smtp.login(os.environ["RICHSMTP_USER"], os.environ["RICHSMTP_PASS"])
smtp.send_message(msg)
PHP
use PHPMailer\PHPMailer\PHPMailer;
$mail = new PHPMailer(true);
$mail->isSMTP();
$mail->Host = getenv('RICHSMTP_HOST');
$mail->Port = 587;
$mail->SMTPSecure = PHPMailer::ENCRYPTION_STARTTLS;
$mail->SMTPAuth = true;
$mail->Username = getenv('RICHSMTP_USER');
$mail->Password = getenv('RICHSMTP_PASS');
$mail->setFrom('receipts@yourdomain.com', 'Acme Receipts');
$mail->addAddress('maya@example.org');
$mail->Subject = 'Your receipt';
$mail->Body = 'Thanks for your order.';
$mail->send();
Premium sending starts with a plan, not a sign-up form. This is how a new RichSMTP account goes live.
Your sending domains, your mail streams (transactional, marketing or both) and the volume you expect. Your account and sending plan are reviewed before anything is sent.
Dedicated IPs or a private pool are assigned to you, with a warm-up plan for each mailbox provider.
Add the SPF, DKIM and DMARC records for yourdomain.com. They prove every message is yours.
Point your app at the relay. Volume rises with the warm-up while deliveries, bounces and complaints come back as events.
Twelve terms that cover most conversations about sending email.
An SMTP relay service is an outgoing mail server run for you by a specialist provider. Your application hands each email to the relay over SMTP, and the relay delivers it to the recipient’s mail server, handling authentication, queuing, retries and sender reputation along the way.
Businesses that send high volumes of important email and cannot afford for it to go missing: software platforms sending sign-in codes and alerts, online shops sending receipts and shipping updates, subscription and financial services, and marketing teams mailing large opted-in lists.
Cheap and free SMTP services put many unknown senders on the same IP addresses, so one spammer can damage everyone’s delivery. RichSMTP works the other way round: dedicated IPs, warm-up managed for you, accounts reviewed before they send, cold email and purchased lists refused outright, and an uptime commitment backed by service credits.
Yes, on every plan. RichSMTP has no shared IPs: your mail is sent from dedicated IP addresses or a private pool, so the reputation it is judged on belongs only to you. New IPs are warmed up gradually before they carry full volume.
Mailbox providers distrust new IP addresses that suddenly send large volumes. During warm-up RichSMTP raises your sending limits step by step, separately for each provider such as Gmail, Outlook and Yahoo, and only while complaint and bounce rates stay clean.
Yes. Connections are encrypted with TLS, every application signs in with its own credentials, messages are DKIM-signed with 2048-bit keys, and only verified domains you own can send. Mail is delivered over TLS wherever the receiving server supports it.
Port 587 with STARTTLS is the recommended port. Port 465 with implicit TLS is also available, and port 2525 is offered as an alternate for networks that block the standard ports.
Yes, you add a few records to your sending domain: SPF to authorise the sending servers, DKIM so receivers can verify the signature on each message, and DMARC to say what should happen when those checks fail. Your MX records and incoming email are not affected.
Plans start at $99 a month for 100,000 emails, sent from your own dedicated IP. Every plan includes dedicated IPs, the full platform and the 99.9% uptime SLA, and Enterprise plans are built around volumes of 10 million emails a month and more.
RichSMTP targets 99.9% monthly uptime for the SMTP relay. If a month falls short, you can claim service credits as set out in the Terms and Conditions.
Yes. Anything that can send through an external SMTP server works: web frameworks such as Laravel, Django and Rails, libraries such as Nodemailer, PHPMailer and smtplib, WordPress through an SMTP plugin, and devices such as printers and scanners.
Dedicated IPs, managed warm-up, a secure relay and a strict sender policy: everything an SMTP relay service should be when your email carries revenue.