Authentication built in
DKIM signing, SPF include and DMARC guidance for every domain you add.
SMTP relay service
An SMTP relay you never have to think about.
Point your app at one hostname. We authenticate, sign, route and deliver, then tell you exactly what happened to every message.
Drop-in
Works with everything that sends email
SMTP is the one email protocol every framework, CMS and SaaS tool already speaks. Swap your current host for smtp.mailerace.com, add a credential, and your existing code keeps working. No SDK, no vendor lock-in.
- WordPress, WooCommerce, Ghost and other CMSs
- Laravel, Django, Rails, Spring, .NET, Node.js
- Self-hosted tools: Gitea, Nextcloud, Grafana, Jira
- Network devices and printers with SMTP settings
SMTP settings
- Host
- smtp.mailerace.com
- Port
- 587 (STARTTLS) · 465 (TLS)
- Auth
- PLAIN / LOGIN
- Username
- your credential
- Encryption
- required
Security
Credentials that cannot be abused
Every credential is scoped. Limit it to the domains it may send from and the IPs it may connect from. Rotate passwords with an overlap window so deploys never break, and revoke instantly when something leaks.
- Per-credential domain and IP restrictions
- Zero-downtime password rotation
- Immediate revocation, enforced on the next message
- Rate limits per credential
swaks --server smtp.mailerace.com:587 --tls \
--auth-user "$SMTP_USER" --auth-password "$SMTP_PASS" \
--from [email protected] --to [email protected] \
--header "Subject: Hello from MailerAce"Delivery
Routing that protects your reputation
Mail leaves from IP addresses with established reputation and matching reverse DNS. Transactional and bulk mail travel on separate pools, so one customer's newsletter never slows down another's password reset. Need full control? Bring your traffic to a dedicated IP.
- Shared pools monitored for reputation
- Dedicated IPs with guided warm-up
- TLS to receiving servers when they support it, DANE where published
- Automatic retries with back-off
Message trace
- received
- 09:41:02.118
- policy
- accepted · 1 recipient
- dkim
- signed d=yourdomain.com
- route
- shared pool · warm IP
- delivered
- 250 2.0.0 OK · 1.4s
Bounce and complaint handling
Hard bounces and spam complaints are suppressed so you stop retrying bad addresses.
Webhooks for every outcome
Delivered, bounced, deferred and complained events, signed and retried.
No server to maintain
Forget Postfix tuning, queue monitoring, blocklist checks and TLS renewals.
Workspaces for every project
Separate domains, credentials and logs per project or client.
Coming soon
Delivery analytics
Volumes, bounce rates and per-message timelines.
FAQ
SMTP relay questions
What is the difference between an SMTP relay and an SMTP server?
An SMTP server is any program that speaks SMTP. An SMTP relay is a hosted service that accepts mail from your applications and delivers it onward, handling IP reputation, authentication, retries and bounces so you do not have to run and maintain your own mail server.
Which SMTP port should I use?
Use port 587 with STARTTLS. If your client only supports implicit TLS, use port 465. Port 25 is not offered for submission because most cloud providers block it outbound. The host is smtp.mailerace.com.
Do you support SMTP AUTH PLAIN and LOGIN?
Yes, both, always over an encrypted connection. Authentication without TLS is refused.
Can I restrict a credential to my server IPs?
Yes. Each SMTP credential can have an allowlist of IP addresses or CIDR ranges. Connections from anywhere else are refused even with the right password.
What happens if a message cannot be delivered right away?
Temporary failures are retried automatically with back-off. Permanent failures (hard bounces) are recorded and the address is suppressed to protect your reputation.
Is there a limit on message size?
Messages up to 10 MB on the Free plan and 25 MB on paid plans, including attachments.
Switch your SMTP host today
Keep your code, change five settings, and get better delivery with full visibility.