Send outbound email from any application, framework or server through MailGuard. Standard SMTP over 587/465 SASL, or transactional sending via REST API. We sign DKIM and we manage the reputation.
When you send directly from an application (WordPress, Laravel, Node.js, ERP, CRM…) or a server, delivery is determined by IP reputation and DNS settings. Managing these takes expertise and constant attention. An SMTP relay takes that burden off your hands: you enter standard SMTP settings, and MailGuard handles signing, filtering and reputation management.
POST /api/v1/send on the REST API.For detailed, copy-paste configuration, see the docs. To test your domain, use the SPF/DKIM/DMARC tool and mail test.
| MailGuard | Directly from your server | Doing nothing | |
|---|---|---|---|
| DKIM signature on outbound mail | Automatic (MailGuard signs) | You have to set it up | None |
| IP reputation management | Fixed, monitored pool per domain | Single IP — everyone shares the same risk | None |
| Inbound spam / virus filtering | Included (MX routing) | Depends on the server | None |
| Risk of being blacklisted | Minimal (isolated pool) | High | High |
| Delivery visibility / logs | Real-time panel + API | Limited | None |
The SMTP integration was far easier than we expected. The whole system runs flawlessly.
The SMTP configuration was simple and clear. We have been using it without a hitch from day one.
We clearly saw the improvement in delivery rates, especially on bulk email campaigns.
A great solution I would recommend to anyone dealing with mail delivery problems.
A great email gateway solution that met our expectations on both security and delivery.
The setup documentation was very clear. We got it running on the Plesk side without any issues.
Let's talk through your current setup, your volume and your delivery problems, and map out a migration plan tailored to you.
Get a QuoteAn SMTP relay (forwarding) service is where an application or server sends its outbound email not directly to the recipient, but to an intermediate server whose reputation and infrastructure are managed. That intermediate server signs the mail, inspects it and delivers it from the right IP. The goal: improve delivery, prevent landing in spam and make IP reputation management a specialty.
When you send from your own server, you have to keep every technical requirement — SPF, DKIM, DMARC, PTR and IP reputation — correct at all times. A small mistake can send all of your mail to spam. The MailGuard SMTP relay takes on that responsibility; you only enter standard SMTP settings or use the REST API.
Delivery success is especially critical for transactional emails (sign-up confirmations, password resets, order notifications) and bulk announcements, and it is kept high thanks to reputation-managed IP pools and automatic rate limiting. With real-time logs and suppression management, you can track what happens to every message.