Notix
Learn

Deliverability is a reputation, and you are the one earning it.

Whether a message reaches the inbox is decided by the receiving mailbox provider, using a history of your sending domain and IPs that nobody outside can read. A sending service can keep the parts it controls clean: authentication, bounces, complaints, the message itself. The rest, who you send to and how often, is yours. This page says which is which, and what the numbers are.

What mailbox providers actually score.

Gmail, Outlook, Yahoo and the rest each keep a private record of your mail. The inputs are broadly the same everywhere, and the useful question about each one is whether it belongs to you or to the service sending on your behalf.

SignalWhat it measuresWhose it is
Domain reputationThe history of mail from your domain: how much of it was wanted, complained about, or sent to addresses that do not exist.Entirely yours. It follows the domain wherever it sends from.
IP reputationThe same history for the IP addresses the mail left from.Shared with every other Notix sender on the same infrastructure, which is why Notix suppresses aggressively.
AuthenticationWhether SPF, DKIM and DMARC agree that the message really came from your domain.DKIM and SPF are set up when you verify the domain; DMARC is a record you publish.
Complaint rateThe share of delivered mail that recipients mark as spam.Yours. Notix stops sending to anyone who complains; it cannot stop them complaining.
Bounce rateThe share of mail sent to addresses that do not exist or will not accept it.Shared. Hard bounces are suppressed automatically; list hygiene before the first send is yours.
EngagementOpens, replies, moves out of spam, deletions without reading.Yours: who you send to, how often, and whether they asked for it.
ContentLinks, images, wording, structure, and whether the message resembles known spam.Yours, with a pre-send check that catches the avoidable part.

Two things follow. A new domain has no reputation, good or bad, so its first weeks are judged mostly on authentication and content, and on the shared IPs it borrows. And a reputation once damaged is repaired the same way it was built: by sending wanted mail to people who open it, for long enough that the history changes.

The complaint threshold that matters.

Only one major provider publishes a number. Google’s email sender guidelines (read on 13 September 2026) say to keep the spam rate reported in Postmaster Tools below 0.10%, and never to reach 0.30%. Below one complaint in a thousand you are fine. Between one and three in a thousand you are being watched. At three, Gmail starts filtering, and it takes weeks of clean sending to come back. Senders of more than 5,000 messages a day to Gmail must also authenticate with SPF and DKIM, publish a DMARC record (a policy of p=none is enough), and support one-click unsubscribe on marketing mail; the guidelines are worth reading in full once, because Yahoo’s match them closely.

A complaint is not an unsubscribe. An unsubscribe is a request you honour and nobody scores you for; a complaint is the recipient telling their provider your mail is unwanted, and it counts against the domain whether or not you would have removed them anyway. The practical conclusion is that the unsubscribe link must be easier to find than the spam button.

Warming a new domain on shared infrastructure.

Notix sends from shared IPs. There is no dedicated-IP option, and for most senders that is the better deal: the pool already has a history with every major provider, and the provider polices who sends from it, which is what the automatic suppression below is for. A dedicated IP starts with no reputation at all, has to be warmed by you over weeks, and loses ground every week you send too little from it. It earns its keep somewhere north of a hundred thousand steady messages a month.

What you still warm is the domain. In the first two weeks, send to the recipients most likely to open: recent sign-ups, active customers, anyone who asked for the mail this month. Keep the volume modest on day one and grow it steadily rather than moving an entire list across at once. Let transactional mail run throughout; receipts and codes are the most wanted mail you have and they build the domain’s record. Put marketing on its own subdomain so a bad campaign cannot drag password resets down with it; each subdomain you verify gets its own DKIM key. Watch bounces and complaints daily and slow down when either moves. Notix does not automate that ramp; the schedule is a decision only you can make.

What Notix does for you.

  • Suppression on bounce and complaint. A hard bounce or a spam complaint puts the address on your team’s suppression list with the reason recorded (hard bounce, complaint, or manual when you add one), and a later send to it is refused rather than sent. One list covers transactional and marketing mail alike. How bounces are classified is on email bounce handling; what the list is for is on email suppression lists.
  • DKIM per domain. Verifying a domain generates its own signing key and the DNS record to publish under the notix selector, plus the SPF include. The three records and what each proves are on SPF, DKIM and DMARC.
  • One-click unsubscribe headers. Marketing and journey sends carry List-Unsubscribe and List-Unsubscribe-Post, the pair Gmail and Yahoo require, unless you set your own.
  • The pre-send check. Every campaign runs through the deliverability check before it goes and is refused on a blocking finding; you can call the same check on your transactional templates.

What stays yours.

  • DMARC. Notix suggests the record; you publish it, read the reports, and tighten the policy when they are clean. Examples for each policy are on DMARC record examples.
  • Content. The check catches raw-IP links, missing unsubscribe links and spam-filter symbols. It cannot make a dull or misleading message wanted.
  • List hygiene. Suppression stops the second send to a dead address. The first send, and the import that produced it, are yours to verify.
  • Cadence and consent. How often you send, to whom, and whether they asked. This is where complaint rates are made.

When it goes wrong.

Deliverability problems announce themselves in one of a few ways, and each points somewhere specific.

SymptomWhere to look
Everything lands in spam at one provider onlyReputation with that provider. Check Postmaster Tools for Gmail; look at the last month of sends to that domain for a stale list or a spike in volume.
Bounces jumped after an importThe list. Hard bounces are already suppressed; stop sending to the rest of the import until it has been verified.
Complaints rose after a campaignConsent and frequency. Who received it that did not expect it, and did the unsubscribe link work in one click.
Authentication failures in DMARC reportsA sender you forgot: a CRM, a form tool or a support desk sending as your domain without DKIM.
One template performs worse than the restContent. Run the pre-send check; a spam-filter symbol or a shortened link usually explains it.

The webhook events for delivered, bounced and complained mail are the raw material for all of this; the transactional email API emits them per message, and the dashboard shows the rates per domain.

FAQ

Questions, answered.

What is sender reputation?
A score each mailbox provider keeps, per sending domain and per sending IP, built from what happened to your previous mail: complaints, bounces, whether it was opened or deleted unread, whether it authenticated. Nobody outside the provider can read the score. Gmail exposes a coarse version of it in Postmaster Tools; the others show you nothing but the result.
What complaint rate is safe?
Google's sender guidelines say to keep the spam rate reported in Postmaster Tools below 0.10% and never to reach 0.30%. That is one complaint in a thousand delivered messages as the working ceiling, and three in a thousand as the point where Gmail starts filtering. Other providers do not publish a number; treat Google's as the bar for all of them.
Shared IP or dedicated IP for transactional email?
Shared, unless you send well over a hundred thousand messages a month on a steady schedule. A dedicated IP has no history, so you warm it yourself and every quiet week costs you reputation; a shared pool already has a track record and the provider polices who sends from it. Notix sends from shared infrastructure only and offers no dedicated IPs; if you need one with managed warm-up, that is a reason to pick a larger provider.
How do I warm up a new domain?
Start with your most engaged recipients, the ones who signed up recently and will open. Send a modest volume the first day and grow it steadily over two weeks rather than switching a full campaign over at once. Keep transactional mail flowing throughout; it is wanted mail and it builds the domain's history. Watch bounces and complaints daily, and slow down if either moves. Notix does not automate the ramp; the schedule is yours.
Does a new domain need to send from a subdomain?
It helps. Sending marketing from one subdomain and transactional from another keeps a bad campaign from dragging your password resets into spam, because reputation is tracked per domain. Verify each subdomain in Notix and each gets its own DKIM key.
What does Notix do about deliverability automatically?
Hard bounces and spam complaints put the address on your team's suppression list and later sends to it are refused; a DKIM key is generated per verified domain; marketing and journey sends carry the one-click List-Unsubscribe headers Gmail and Yahoo require; and every campaign runs through the pre-send deliverability check before it goes. DMARC, list hygiene, sending cadence and the content itself remain yours.

Verify a domain and see the records it needs.

DKIM key, SPF include and a suggested DMARC record, generated when you add the domain.