Sender reputation is the history mailbox providers use to decide how much access your mail gets. Treat every campaign as a change to that history: authenticate the sender, control recipient quality and pace, then read the provider response before adding volume. Placement depends on authentication together with bounce rate, complaint rate, and sending behavior.1
What reputation changes
When delivery drops, use reputation to decide what to inspect. Providers assign sender reputation to a domain and IP using authentication, complaint rates, bounces, and recipient engagement.2 Mailbox providers assess sending practices with algorithms when they judge a sender.3 Their decision can put a message in the inbox, promotions, or spam, or cause throttling, a temporary failure, or a block.4
Map the sending surfaces
Before changing a campaign, identify the domain, subdomain, IP, and mailbox carrying the stream. This keeps a mailbox problem, a domain problem, and an IP problem from being treated as the same fault.
Providers evaluate reputation at the domain and subdomain levels.5 Mailbox reputation belongs to the specific sending account.6 Receiving servers use domain reputation together with the email server's IP to decide how to handle messages.7
Ask which domain, subdomain, IP, and mailbox carry this stream, and which other mail uses them. Record the answer before sending so you can trace a placement change to the right surface.
Prepare before sending
Check sender identity and recipient quality before judging campaign performance. Configure SPF, DKIM, and DMARC so mailbox providers can verify the sending domain and trust the mail.8 Authentication is a baseline requirement for high volume senders and plays an important role in inbox placement.9
Inspect the recipient pool next. Remove invalid, inactive, and unengaged contacts to maintain engagement signals and protect sender reputation.10 Invalid addresses cause hard bounces that directly damage sender reputation.11
Before proceeding, explain where each address came from and which contacts leave the sending pool when they become invalid or inactive. Move on when those answers are clear and the sending identity is configured.
Establish sending history
New sending infrastructure needs a history that providers can read, so make history building a separate gate before increasing campaign pace.
Providers pay attention when a domain with no sending history suddenly sends many emails.12 Warming mailboxes builds mailbox reputation, and warming mailboxes across a domain builds domain reputation too.13 Changing the mailbox leaves the need to warm the setup in place, because providers combine domain and IP reputation.14
Before the campaign reaches its normal pace, check whether reputation is being established at each surface you mapped. If one mailbox or subdomain behaves differently, investigate that surface before changing the whole sending setup.
Send and watch the response
Once mail is flowing, hold the sending pattern steady enough to read the response. Volume and frequency are reputation inputs, so read a delivery change alongside what changed in the send.
The volume sent from a domain or IP contributes to reputation.15 Sending frequency includes consistent traffic and large sends separated by long silent intervals.16 Providers also monitor opens, clicks, and spam complaints as engagement signals.17
Track engagement, hard and soft bounce rates, unsubscribes, and spam complaint rates by mailbox provider to find issues early.18 At each review, ask whether the change affected one provider, one domain, or every mailbox, and whether bounces or complaints moved with it. Keep the next change small enough to answer those questions.
When placement falls
Inspect sender history, recent behavior, and the affected surface, then choose one repair instead of changing several variables at once.
Make sender reputation checks part of the regular review.19 Run an extra check after a security incident or major email campaign, and immediately when messages start landing in spam.20
Compare the bounce, complaint, and engagement patterns with the domain, subdomain, IP, and mailbox that sent the affected mail. Decide whether the next fix belongs to authentication, recipient quality, or sending behavior. Recheck provider level outcomes before returning to the prior pace.
What not to do
Keep these failure modes visible while you run outbound. Each one can turn a local sending issue into a wider reputation problem.
- Do not send to spamtrap addresses. Recipient servers automatically identify senders that mail them as spammers.21
- Providers may discount future mail across every domain tied to the sender after a hard bounce, including domains other than the one with the failed address.22
- Avoid purchased contact lists, skipped routine list cleaning, and using a webmail address as the sending address, since these practices can damage reputation and inbox reach.23
- Sending cold email from the same domain as regular business mail without necessary precautions can quickly damage the domain's reputation. In extreme cases, messages to colleagues and existing customers may not be delivered.24