Infrastructure — BlacklistGuard Docs

Infrastructure

Control how your mail actually leaves the building — which IPs it sends from, how it's routed, and how fast it goes. These are advanced controls; most workspaces start on the shared sending pool and grow into them.

Virtual MTAs

A Virtual MTA is a named sending configuration — a way to group the IPs you send from and apply consistent settings to them. You point campaigns and other sends at a Virtual MTA to control which addresses they go out on. Manage them under Virtual MTAs in the console.

Routing rules

Routing rules decide which IP or pool a given message uses — for example, routing mail to a particular recipient domain through a specific IP. Campaigns can target a routing rule directly: set virtual_mta_ip to routing_rule:<id> (or pass routing_rule_id) when creating the campaign — see the campaigns API.

Dedicated IPs

By default, your mail goes out on a shared sending pool that BlacklistGuard manages and paces for you — a good fit when you're starting out. As your volume grows, a dedicated IP gives you a sending address whose reputation is entirely your own, isolated from other senders.

Dedicated IPs assigned to your workspace appear in the console, where you can group them into Virtual MTAs and target them with routing rules.

ℹA dedicated IP only helps at sufficient, consistent volume — there isn't enough signal to build reputation on an IP that sends infrequently. If you send modest volumes, the shared pool will usually deliver better.

Throttling & pacing

You can cap how fast mail leaves each IP and how much goes to each recipient domain — limits on messages per hour and messages per day. Throttling protects your reputation by keeping your sending steady instead of spiky, which is exactly what mailbox providers want to see.

⚠When you bring a new dedicated IP online, start with conservative throttles and raise them gradually over the first few weeks. Sending at full volume on a cold IP is the quickest way to get filtered.