MX gateway and relay server integration for hMailServer environments

Pitbull integration with hMailServer

In environments using hMailServer, Pitbull integration works on two channels:

• Inbound: DNS MX records point to the Pitbull gateway; Rspamd-based filtering, quarantine and policy engine secure inbound traffic.
• Outbound: All outbound traffic is directed to the Pitbull relay via hMailServer SMTP relay route settings.

Relay Server Configuration

In hMailServer Administrator go to Settings > Protocols > SMTP > Delivery of e-mail > Smart host and enter the relay server (relay.pitbull.com.tr), port (587) and SMTP AUTH credentials. Per-domain relay can be configured via Routes.

Inbound MX Gateway

• Point domain MX records to the Pitbull gateway address (priority 10)
• Rspamd spam, phishing and malware filtering at the gateway layer
• Malicious attachment scanning via ClamAV / Avast REST
• SPF, DKIM and DMARC checks + score breakdown
• Suspicious messages isolated in quarantine; admin-approved release workflow

Outbound Relay Settings

To route outbound traffic to the Pitbull relay on hMailServer:

hMailServer Administrator:
  Settings > Protocols > SMTP > Delivery of e-mail
    Smart host: relay.pitbull.com.tr
    Port: 587
    Connection security: STARTTLS
    Authentication: ✓
    Username: tenant@pitbull.com.tr
    Password: RELAY_TOKEN

  Routes (per-domain optional):
    Domain: example.com
    Target: relay.pitbull.com.tr:587

This configuration passes outbound traffic through the Pitbull outbound filtering engine. SMTP Abuse Radar, per-tenant rate limits and Emergency Outbound Lockdown are activated.

Authentication

• Add Pitbull include to SPF
• Enable DKIM signing from Pitbull panel and publish DNS TXT record
• Start DMARC at p=none and monitor reports

Operational Visibility

Monitor delivery rates, reject reasons, queue status and GeoIP/ASN distribution on NOC screens. Deliver periodic security summaries to management teams with executive PDF reports.