MX gateway and relay server integration for Haraka environments

Pitbull integration with Haraka

In environments using Haraka, 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: Outbound traffic is forwarded to the Pitbull relay via Haraka smtp_forward plugin.

Relay Server Configuration

In Haraka, host, port and auth are defined in config/smtp_forward.ini. Add smtp_forward to the plugins file to relay all outbound traffic.

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

# config/smtp_forward.ini
host=relay.pitbull.com.tr
port=587
enable_tls=true
auth_type=login
auth_user=tenant@pitbull.com.tr
auth_pass=RELAY_TOKEN

# config/plugins
smtp_forward

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.