Three guides for people who run outbound
How to read deliverability signals in the order they move, what each layer of a cold email setup does, and how sending.ac sets up Azure for cold email.
Three short guides
How to monitor cold email deliverability
Watch the signals in the order they move. Domain reputation slips first, inbox placement shifts next, and the reply rate drops last, often weeks later. Count only real replies, with warm-up and out-of-office kept apart.
- Check authentication and blocklists daily
- Measure placement from inside real inboxes
- Read the reply rate as the last signal
- ReputationSlips first, around week one, per domain and per sender
- PlacementShifts around week three, more mail landing in spam
- RepliesDrop around week five, the last signal to move
Cold email infrastructure in plain terms
Domains are the addresses you send from. DNS records prove each domain is yours. A tenant holds the IPs and the reputation. Mailboxes send. Warm-up builds a sending history. The sequencer writes and sends the campaign.
- sending.ac runs domains, DNS, tenants and mailboxes
- Not a sequencer and not a lead list
- Not a warm-up pool sold on its own
Is Azure safe for cold email?
On sending.ac each domain gets its own Azure tenant, with its own IPs, its own reputation and its own admin panel, never pooled with another customer. DNS is verified before the first send, with up to 75 mailboxes per domain.
- One tenant per domain
- SPF, DKIM and DMARC verified before sending
- Microsoft spam score and placement checked daily
Go through your setup with an advisor
A 15-minute call with a deliverability advisor, checking your domains against these three guides.