Route the outbound mail of your standalone Postfix servers to the MailGuard smarthost, so it is delivered DKIM-signed from reputation-managed IP pools. Set it up in just a few lines with relayhost + SASL.
When you send directly from your own Postfix server, IP reputation, the PTR record and SPF/DKIM/DMARC compliance are critical. If any one of these is missing, large providers reject the connection or push the mail to spam. When you set MailGuard as the relayhost, this entire burden shifts to MailGuard.
relayhost = [relay.mailguard.com.tr]:587smtp_sasl_auth_enable = yes, smtp_sasl_password_maps = static:USER:PASSWORD, smtp_sasl_security_options = noanonymoussmtp_tls_security_level = encrypt ; then postfix reload.For detailed, copy-paste configuration, see the docs. To test your domain, use the SPF/DKIM/DMARC tool and the mail test.
| MailGuard | Directly from the server | Doing nothing | |
|---|---|---|---|
| DKIM signature on outbound mail | Automatic (MailGuard signs) | You have to set it up yourself | None |
| IP reputation management | Fixed, monitored pool per domain | Single IP — everyone shares the same risk | None |
| Inbound spam / virus filter | Yes (MX redirection) | Depends on the server | None |
| Risk of being blacklisted | Minimal (isolated pool) | High | High |
| Delivery visibility / logs | Real-time panel + API | Limited | None |
Thanks to MailGuard, we now hardly ever get the “mail didn't arrive” complaint from our customers.
The amount of our mail landing in the spam folder dropped noticeably. It met our expectations.
The spam-filtering results exceeded our expectations. Unnecessary traffic dropped significantly.
Together with SPF, DKIM and the other settings, our delivery performance improved noticeably.
Because the integration steps were clear, our technical team completed it quickly.
Thanks to the technical documentation and integration guides, the setup was completed quite quickly.
Let's go over your current setup, volume and delivery issues, and draw up a migration plan tailored to you.
Get a QuotePostfix is the most widely used MTA in the Linux world and gives you full control. But that control also puts the delivery responsibility on you: IP reputation, reverse DNS (PTR) and the entire SPF/DKIM/DMARC and TLS configuration must all be correct. A single missing piece is enough for your outbound mail to be rejected by large providers.
Defining a smarthost hands off that responsibility. By adding a few lines to main.cf, you route Postfix's outbound mail to MailGuard. MailGuard signs the mail with DKIM, runs it through content and rate inspection, and delivers it from a reputation-managed IP with the correct PTR/HELO. You are freed from the burden of tracking your own IP's reputation, blacklist entries and rDNS settings.
Optionally, you can also add inbound spam/virus filtering by pointing your MX record to MailGuard. This way your standalone Postfix server gains enterprise-grade delivery and security.