MailGuard is more than a spam filter. It combines the reputation infrastructure that gets your outbound mail delivered with the filtering layer that stops inbound mail before it reaches your users — all on one platform.
About the cPanel / WHM module ↗A message with a malicious attachment was rejected before connection.
Filtering outbound traffic is the most overlooked yet most critical part of the job. A customer's compromised WordPress install or a stolen email password can destroy deliverability for every domain on your server within hours.
| Domain / User | Hourly quota | Usage | Status |
|---|---|---|---|
| example.com | 5.000 | Normal | |
| example.org | 2.000 | Normal | |
| example.net | 1.000 | Limited | |
| tanitim@example | 500 | Normal |
When you point your MX record to us, all inbound traffic passes through us first. The cost of filtering — connections, disk, CPU — stays with us; only clean mail reaches your server.
[SPAM] and leave filing to the user, or simply add a header and let it through. Thresholds are set per domain.The most common mistake an intermediate relay makes is altering the message and invalidating its existing DKIM signature. MailGuard solves this with three rules.
d=yourdomain.com, keeping DMARC alignment.Our outbound IPs are spread across several independent network blocks. Even if one block lands on a list, the others keep working.
| Pool | Use |
|---|---|
| Warm-up | New customers start here; volume is increased gradually. |
| Standard | A shared pool for customers with an established history. |
| Priority | Clean-history corporate traffic, mostly transactional mail. |
| Isolated | A tenant that exceeds complaint or bounce thresholds is moved here; the main pools are protected. |
Each domain is assigned a fixed IP within its pool. Reputation models on the receiving side reward consistency; random IP rotation hurts.
On every outbound IP, forward and reverse DNS records match (FCrDNS) and the server name in the SMTP session matches too — this is the first thing large providers check.
Every step of your email traffic is logged; you don't guess why a message was rejected — you see the remote server's response exactly as given.
| Time | Sender | Recipient | Status |
|---|---|---|---|
| 14:26 | bilgi@example.com | alici@... | delivered |
| 14:12 | satis@example.com | musteri@... | delivered |
| 13:58 | destek@example | info@... | delivered |
| 13:40 | spam@phish.ex | x@... | rejected |
Secure transport, redundant gateway architecture and consistent authentication.
| Component | Detail |
|---|---|
| Architecture | Redundant gateway setup; if one node goes down, traffic flows through another |
| Outbound IPs | Multiple network blocks, reputation-based management |
| Transport security | STARTTLS, with DANE and DNSSEC validation on delivery |
| Authentication | SMTP AUTH (587 / 465) or authorization by registered source IP |
| Location | Turkey |
Start using MailGuard without changing your existing infrastructure. Manage the whole server from WHM; connect any platform with SMTP Relay / Smarthost support in a few settings.
Let's talk through your servers and volume and put together a realistic migration plan.