MX gateway and relay server integration for Qmail environments

Pitbull integration with Qmail

In environments using Qmail, 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 or per-domain relay is configured through Pitbull via the Qmail smtproutes file.

Relay Server Configuration

For global relay in Qmail, add :relay.pitbull.com.tr:587 to /var/qmail/control/smtproutes. For per-domain routing use example.com:relay.pitbull.com.tr:587 format.

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 Qmail:

# /var/qmail/control/smtproutes
# Route all outbound to Pitbull relay
:relay.pitbull.com.tr:587

# Per-domain (optional)
example.com:relay.pitbull.com.tr:587

# SMTP AUTH requires patch (netqmail + TLS)

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.