Home / Docs / Mail server setup
Outbound filtering

Configure your mail server for outbound filtering

Set up your MTA to relay outbound mail through AnitaHost Mail as a smart host, with SMTP AUTH and TLS encryption. No sender-domain verification or DNS records are required.

No domain verification: AnitaHost Mail accepts any authenticated sender domain. Every message still passes through outbound spam and virus filtering.

Before you begin

  • An active AnitaHost Mail account with a verified email address.
  • An SMTP username and password, or an API key from the dashboard.
  • Access to your mail server, control panel or application SMTP settings.

Connection details

Relay hostsuper.anitahostmail.com
Ports587 STARTTLS (preferred) or 465 implicit TLS
EncryptionTLS required
AuthenticationSMTP AUTH with your AnitaHost SMTP username and password — PLAIN or LOGIN
Sender domainsAny authenticated sender domain; no verification required

Port 25 is rate-limited and not recommended for submission. Use TLS for every connection.

Set up your mail server

1

Get credentials

Open SMTP credentials and create a username and password. Keep the password safe; it is shown once.

2

Configure the smart host

Set your relay or smart host to super.anitahostmail.com:587. The setting name varies by MTA.

3

Enable authentication and TLS

Authenticate with PLAIN or LOGIN and require TLS. Connections without TLS should not be used.

4

Send a test

Send a message through the relay and confirm it appears in your deliverability dashboard.

Recommended: install the WHM plugin

The plugin configures Exim, shows relay and tunnel status, and can enable an SSH tunnel fallback. It also repairs local DKIM, SPF and DMARC TXT records automatically: invalid or duplicate records are deleted and replaced with the correct values.

curl -fsSL https://anitahostmail.com/downloads/anitahost-cpanel.tar.gz?v=2026.11.05.1 -o /tmp/anitahost-cpanel.tar.gz
tar -xzf /tmp/anitahost-cpanel.tar.gz -C /tmp
bash /tmp/anitahost-cpanel/install.sh

Then open WHM → Plugins → AnitaHost Mail to manage relay credentials and updates.

Alternative: WHM Advanced Editor

If you prefer to configure Exim manually, add each block to the exact section shown. Do not put the router into an ACL section.

Section: AUTH
anitahost_login:
  driver = plaintext
  public_name = LOGIN
  client_send = : YOUR_SMTP_USERNAME : YOUR_SMTP_PASSWORD
Section: POSTMAILCOUNT
anitahost_route:
  driver = manualroute
  domains = !+local_domains
  transport = anitahost_smtp
  route_list = * super.anitahostmail.com::587 randomize byname
  no_more
Section: TRANSPORTSTART
anitahost_smtp:
  driver = smtp
  hosts_require_auth = *
  hosts_require_tls = *
  tls_tempfail_tryclear = true

Replace the two credential placeholders with your SMTP username and password.

For custom Exim installations, use an authenticator, a manualroute router and an authenticated TLS transport.

Authenticator
anitahost_login:
  driver = plaintext
  public_name = LOGIN
  client_send = : YOUR_SMTP_USERNAME : YOUR_SMTP_PASSWORD
Router
anitahost_route:
  driver = manualroute
  domains = !+local_domains
  transport = anitahost_smtp
  route_list = * super.anitahostmail.com::587 randomize byname
  no_more
Transport
anitahost_smtp:
  driver = smtp
  hosts_require_auth = *
  hosts_require_tls = *
  tls_tempfail_tryclear = true

Add this to your Postfix main configuration, then create the SASL password map.

/etc/postfix/main.cf
relayhost = [super.anitahostmail.com]:587
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_sasl_security_options = noanonymous
smtp_tls_security_level = encrypt
/etc/postfix/sasl_passwd
[super.anitahostmail.com]:587 YOUR_SMTP_USERNAME:YOUR_SMTP_PASSWORD
postmap /etc/postfix/sasl_passwd
systemctl reload postfix

Use the same credentials from any app, website or backend. SMTP works with WordPress, Laravel, Node.js, Python, PHP and control panels; the HTTP API is available for custom code.

SMTP
Host: super.anitahostmail.com
Port: 587 STARTTLS or 465 TLS

Auth: SMTP username + password

Open app setup guides or continue to the HTTP API.

Sender domains

AnitaHost Mail does not require domain registration, DKIM CNAME or DNS verification. Authenticate with SMTP or an API key and use any sender domain. Outbound spam and virus filtering still applies, and protected brands are blocked automatically.

Test delivery

Send a real message through your configured server, then open Deliverability to confirm received, queued and delivered activity. For SMTP issues, check the server log and the error reference below.

All panels and plugin docs

Every control panel, app framework and mail plugin guide is listed here. Each panel page contains its own setup steps—no cPanel-only redirects.

HTTP API

Send JSON to POST https://anitahostmail.com/api/v1/send with a bearer API key. API keys use the Sending scope; no domain verification is needed.

POST /api/v1/send
curl -X POST https://anitahostmail.com/api/v1/send \
  -H "Authorization: Bearer ah_live_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "[email protected]",
    "to": "[email protected]",
    "subject": "Your receipt",
    "text": "Thanks for your order."
  }'

Successful requests return 202 with an accepted recipient count. The maximum is 50 recipients per request and 25 MB of content by default.

SMTP & API errors

StatusCodeWhat to do
400invalid_from, invalid_recipients, missing_contentFix the request payload.
401missing_api_key, invalid_api_keyProvide a valid bearer key.
403sender_blocked, email_unverified, account_suspendedCheck the sender blocklist, verify the account, or contact support.
429daily_limit_reached, rate_limitedUpgrade the plan or wait for the window to reset.
502send_failedThe relay could not queue the message; retry or contact support.

Limits

Quotas are measured per recipient over a rolling 24-hour window. SMTP and API messages share the same quota, and a per-minute rate limit also applies. Rejected messages do not count toward your quota.

Need a hand?

Send us the server log line, sender address and approximate timestamp. We can help trace the relay path.

Open a support ticket