The Deliverability Blog

Headers are the only place where the receiving server tells you the truth about your email: which hops it took, whether SPF and DKIM passed, what spam score it earned, and which…

Most "our email suddenly stopped working" incidents are a DNS record that was never right, only tolerated. Ten dig commands tell you whether your domain is actually configured to…

A domain registered last week is not penalised for being young; it is penalised for having no history. Understanding which signal is which decides whether you wait 30 days before…

If you send through a shared IP, every other sender on that IP is part of your sender reputation. That is fine when the pool is well policed and quietly catastrophic when it is…

Yahoo tells you more in its bounce messages than almost any other receiver — if you read the code. A 554 with a Spamhaus reference, a 421 rate limit and a 553 rejection need three…

Font choice does not trigger spam filters, but a broken font stack produces unreadable mail, unreadable mail gets deleted without engagement, and engagement is what reputation is…

Heatwave is a domain blocklist aimed specifically at manufactured sender reputation - networks of mailboxes generating fake opens, clicks and replies. It launched with more than a…

For years the Domain Reputation chart was the first thing a sender checked, and during a warm-up it was the only external proof the work was landing. Google retired it with v2.…

Validity Everest is a serious enterprise product: seed testing, Sender Score, trap monitoring, design preview, certification. It is also priced and shaped for a marketing team…

A "blacklist checker" that reports you on 3 of 60 lists tells you almost nothing, because most of those 60 lists are consulted by nobody. Knowing which four or five actually gate…

Most senders do delisting backwards: they submit the removal form first, get relisted within a week, and conclude the list is broken. The order matters. Find it, prove the cause,…

Being "on Spamhaus" is not one thing. An XBL listing means a machine on your network is compromised; a PBL listing means you are sending from the wrong kind of IP; a CSS listing…

UCEPROTECT Level 1 lists your IP. Level 2 lists your neighbourhood. Level 3 lists your provider\u2019s entire network. If you are on Level 2 or 3, you probably did nothing wrong…

SORBS was a significant DNSBL for two decades and has been switched off since June 2024. Guides telling you how to request SORBS delisting are describing a service that no longer…

Search for "blacklist removal tool" and you get monitoring products, lookup pages and a few paid express-delisting schemes. Only one category can actually delist you, and it is…

If Yahoo is deferring your mail, there is no form that fixes it. Yahoo scores your domain and IP internally, and the only lever you have is changed behaviour over days. The one…

Invaluement is a small paid blocklist with reach far beyond its size, and its URI list judges you by the links in your message body. Most senders listed on it never sent spam —…

There is no Gmail blacklist to be removed from. Gmail scores your domain and IP continuously and silently, and the only lever is sending behaviour. The error code tells you which…

A listing on a long-tail DNSBL will not change a single Gmail delivery. A Spamhaus SBL listing can take your mail off every corporate mail server in your pipeline the same hour.…

RATS-Dyna is not accusing you of spam. It is saying your IP looks like a home connection sending mail directly, usually because your PTR record still contains words like "dhcp",…

Most blacklist checkers answer a question you did not ask: they check the IP of your browser, against zones nobody queries, and report "not listed" for a domain problem. Checking…

A RATS-NoPtr listing means two things happened: your IP had no reverse DNS, and it did something that got it noticed. The missing PTR is why you landed in this zone rather than…

Truncate lists IPs that GBUdb sees sending essentially nothing but spam, malware or scams. It is automated end to end, which means the delisting process most guides describe does…

DroneBL is a security blocklist, not a spam-complaint list. A listing means something on your IP was seen behaving as a proxy, a bot or an exploited host. Delisting without…

An Abusix listing is useless information until you know which zone it came from. A policy-zone listing is a reverse DNS problem; an exploit-zone listing is a compromised host.…

Senders lose hours looking for a SpamCop removal button. There is not one worth finding. The SCBL expires on its own about a day after the last report, which means your only real…

Spamhaus states that space under the control of a legitimate network is never listed in DROP. So if your IP is in it, the useful question is not how to delist — it is why you are…

If a multi-list checker flags you on Woody's SMTP Blacklist, pause before you act. Public DNSBL trackers show no listings on its zones for years and failing test entries. The…

Hostkarma does not answer "listed" or "not listed" — it answers with a colour. A brown result and a black result have different causes and very different consequences, and the…

SURBL does not care which IP you send from. It reads the links in your message. That is why senders with spotless IP reputation get rejected, and why the fix starts with an…

A drop in replies is not evidence of a blacklist. Blocklist problems have a signature: hard rejections, quoted list names, and the same failure across every recipient at once.…

Suomispam is small, Finland-focused and slower than most lists: it states that review cycles typically run several months. That makes the usual "delist and move on" approach…

PSBL is simple: it lists the IP of anything that hits one of its spam traps, and it lets go on its own. The listing is cheap. The information is not — a trap hit means addresses…

Barracuda appliances guard a lot of corporate mail, which makes a BRBL listing one of the few that can quietly remove your entire B2B pipeline from reach while Gmail delivery…

An SPFBL listing is unusually specific about why. One code means complaints, another means nobody can reach your abuse contact, another means the address does not look like a mail…

Microsoft rejections name an internal block you cannot look up, and the delist portal only helps with some of them. The error code tells you which kind you have — and whether…

A Backscatterer listing is not about spam you sent. It is about bounces your server sent to people who never emailed you. The fix is in your MTA configuration, and the clock runs…

LashBack had the most interesting detection method in the business: probe addresses planted only in suppression files, so anyone mailing them had abused a do-not-contact list. Its…

A MultiRBL report full of red is alarming until you know what it is actually showing you: a tool that still queries dead and marginal zones alongside the handful that matter. Here…

If a bounce message or a vendor says "RBL," they almost never mean the original Real-Time Blackhole List — that service has not existed in its original form for years. Here is…

A URIBL listing almost never means your sending IP is suspect — it means a domain you linked to inside an email body shows up in spam. Here is how the Black, Grey and Red zones…

No single number tells you your IP reputation — it is reconstructed from blacklist checks, provider-specific tools, and your own sending metrics together. Here is the practical…

Older guides describe SORBS as seven or more separate blocklists, each with its own removal steps. All of them went dark with the service on 5 June 2024. Here is what each…

RATS-Spam is SpamRATS\u2019 list for IPs it has directly observed sending spam at volume — not a dynamic-IP or missing-PTR issue like its sibling lists. Here is the distinction…

Invaluement\u2019s ivmSIP and ivmSIP/24 are small, paid, high-precision blocklists with outsized reach in corporate spam filters. Unlike most DNSBLs, there is no free public zone…

SEM Fresh does not evaluate what you send — it lists a domain for the simple fact of being new, then stops automatically once enough time passes. There is nothing to request and…

A mail server never says "hard bounce". It sends a three-digit reply class and a free-text reason, and your tooling guesses the rest. This is the mapping from real provider…

That string comes from PHPMailer and friends, not from Gmail or Microsoft. Turn on SMTP debug, read the actual three-digit reply underneath, and the fix stops being guesswork.

This one is almost always misread as a recipient problem. It is not: your own Exim refused the message. The exim_mainlog line tells you which of five causes it was in about thirty…

Half of all 530 errors are not about credentials at all - they are about relaying, TLS ordering, or a tenant with SMTP AUTH switched off. The code is permanent; the cause is…

Every MTA that touches a message adds a Received header. When the count passes the hop limit, delivery stops permanently. The bounced message carries the whole evidence trail in…

If you are looking up 531 or 542, the first thing worth knowing is that no mainstream MTA sends them. This maps the folklore codes to the real replies senders actually get, so you…

Reply code tables are everywhere and most of them are wrong. This one is built around the only two decisions the codes exist to drive: retry or stop, and whose fault it is.

The 4.4.x family is network and routing, which means the fault usually sits between the two mail servers rather than in either one. Three commands will tell you which.

A 503 is the server telling your mail library it broke protocol. Nothing is wrong with the recipient, the content, or your reputation. Here is the command sequence the server…

Connection rate limiting and message rate limiting are different controls with different fixes. A 421 at the greeting is almost always the first one, and sending fewer messages…

The pairing itself is a clue: the RFC pairs 502 with 5.5.1 and 500 with 5.5.2. Seeing them crossed tells you which server you are talking to and narrows the cause immediately.

DMARC does not fail because SPF or DKIM failed. It fails because neither one passed *and aligned* with the From domain. That difference is the whole diagnosis, and it is why…

The receiving server is not rejecting your mail, it is rejecting your pace. Here is what 421 4.7.26 means, who it is aimed at, and the throttling and warm-up changes that make it…

The 5xx/4xx split in the SMTP reply code is the only distinction that matters here. Confusing the two is one of the fastest ways to tank a sending reputation — this is what each…

This one is almost never about you. 451 4.3.0 means the recipient server hit an internal fault — here is how to confirm that, what to do while it clears, and when to actually…

This is the catch-all permanent rejection: 554 5.0.0 with no further detail. Here is how to work out which of the handful of real causes you are looking at, and the order to check…

The recipient's inbox is full, not broken and not blocking you — 452 4.2.2 is purely a storage condition. Here is what happens next and when it actually becomes worth following up.

This is a protocol mismatch, not a rejection of your mail. 502 5.5.1 means the server flatly does not know the command it was just sent — here is how to find which one and fix the…

Mailchimp treats a hard bounce as final and will not send to that address again without manual intervention. Here is what actually causes hard bounces on Mailchimp campaigns and…

Different from "address does not exist": 550 5.2.1 says the mailbox is known but unavailable. Here is the distinction that matters and the correct response on both the sending and…

The receiver is giving you a retry window before it commits to rejecting on SPF grounds. Here is what causes 451 4.7.23 and the order to check SPF, forwarding, and alignment in.

This code is the receiver's automated abuse detection stepping in, not a permanent ban. Here is how to identify which behaviour tripped it and the sequence to fix it before it…

Content, not reputation: 554 5.6.0 means the server read the message and rejected what was in it. Here is what triggers content-based rejections and how to find the actual cause.

If a tool or log shows you 543, 546, or 547, that is not a code any compliant SMTP server sends. Here is what RFC 5321 actually defines, and the real codes behind routing…

This is a per-message cap, not a daily sending limit. 550 5.5.3 means one envelope had too many RCPT TO entries for the receiving server to accept — here is how providers set that…

Routing failures sit between you and the recipient, not at either end. Here is what 451 4.4.4 means, the difference between a sending-side and receiving-side cause, and how to…

Most bounce troubleshooting goes wrong at step one: not checking whether the failure was permanent or temporary. Here is the full breakdown of why emails bounce, organised by what…

This is one step past ordinary rate limiting: a temporary ban, not just a slowdown. Here is what triggers 421 4.7.30, how long these bans typically run, and how to make sure it…

454 on its own covers a family of temporary local problems, mostly auth and TLS. Here is how to tell which one you have from the free text, the real transcript, and the order to…

This one rejects who you claim to be, not what you sent. 553 5.7.1 fails at MAIL FROM, before any recipient or content is evaluated — here is what causes it and how it differs…

This pairing looks contradictory on paper — 500 means syntax error, 5.7.1 means policy rejection — and that mismatch is itself the clue. Here is what is actually happening and how…

This 550 variant is a composite verdict, not one specific fault. Here is how to work through IP reputation, authentication, and content signals in the order that actually resolves…

535 always means authentication failed, but the enhanced code attached tells you which kind. 5.7.0 instead of the far more common 5.7.8 is worth noticing — here is what that…

This is stricter than 502: the server could not even parse what you sent, let alone decide whether it supports it. Here is how to isolate the malformed command and fix the client…

521 is a deliberate, permanent declaration from the server, not an outage code. RFC 7504 defines it precisely for this purpose — here is what it means and why retrying the same…

552 does double duty across providers: storage limits in one context, policy-based content rejection in this one. The 5.7.0 enhanced code is what tells you which you are looking…

The command itself was fine; its parameters were not. 555 5.5.2 is specific to malformed MAIL/RCPT parameters — here is how to find the exact malformed argument and fix the client…

This is the permanent sibling of 451 4.4.4 — same routing/DNS family, but the server has stopped retrying. Here is how to tell whose DNS is actually broken and fix it before the…

450 is the broad, catch-all temporary deferral for "this mailbox, right now, not right now" — here is the full set of real causes behind it and how to tell greylisting apart from…

This sits between a pure system fault and a mailbox-specific problem. Here is how 451 4.5.0 differs from the broader 451 4.3.0, and the checks worth running before you conclude it…

Same underlying condition as 550 5.5.3 — too many recipients in one transaction — but this version is explicitly temporary. The distinction changes whether you retry as-is or must…

If a verification tool or bounce dashboard shows you "error 510", that number never appeared on the wire. Here is what RFC 5321 actually defines, and the real 550 5.1.1 reply…

501 narrows the fault to the arguments, not the command. Here is how it differs from the broader 500 and the more address-specific 555, and the exact checks that find the…

Another set of numbers that never appeared on the wire. Here is what RFC 5321 actually defines for queued-mail and routing-timeout conditions, and the real codes behind the…

A 500 is the server saying 'I don't even know what that was.' It is a parser failure, not a policy decision, which means the fix lives in your client or your network path, not in…

Both 454 and 4.3.0 sound alarming, but together they mean the receiving server's own infrastructure hiccupped, not that you did anything wrong. Retry on a normal schedule and move…

A 454 4.7.0 looks like a login failure but behaves like a deferral: the credential was probably fine, the auth service was not available to check it. Wait, then retry the same…

The server understood 'authenticate', just not the method you proposed. Match the AUTH mechanism to what the server actually advertised in its EHLO response and the error…

"Email won't send" covers at least three unrelated failures with different causes. This walks through how to tell them apart in under five minutes using the actual error text, not…

This one is about you, not the recipient. A 550 5.1.0 means the receiving server looked at your own MAIL FROM address and decided it was not acceptable - usually a DNS problem on…

Three unrelated problems all show up as '534'. The fix depends entirely on which enhanced code and sentence follows it - treat the bare number as a hint, not a diagnosis.

This is the softer sibling of a permanent authentication rejection: Google is giving your message a second chance, not blocking it outright. Fix SPF/DKIM alignment before the…

The RFC meaning is routing. The real-world meaning, on Microsoft 365 specifically, is usually access policy. Knowing which system sent it tells you which explanation applies.

The server is enforcing the most basic rule in SMTP: say hello first. If you see this, a command was sent out of order, almost always by a hand-built or buggy client.

This is the most generic deferral there is: the server is saying 'something is wrong on my end' and hanging up, with no further detail. Retry later; there is nothing more specific…

The recipient exists and the address is correct - their mailbox is temporarily in a state where it cannot accept new mail. Retry later; there is nothing to fix on your end.

The server is not evaluating your message at all - it never let you in. Too many simultaneous connections from everyone, or from you specifically, hit its ceiling.

This is a size-limit rejection, not a quota rejection. The recipient's mailbox may have plenty of free space; the message was simply bigger than the system allows through at all.

There is no standard SMTP reply numbered 541. Before troubleshooting 'error 541', find the actual three-digit reply your server sent, because that is the code with a real,…

When a 502 arrives with no enhanced code at all, you are usually talking to an old or minimal mail system. Treat the bare number at face value: the command you sent is one it has…

This is not about whether the mailbox exists - it is about whether the recipient's domain can be found at all. A 553 5.1.2 means the receiving system itself could not be located.

This isn't a wrong password, it's the wrong kind of password. Once an account has two-step verification on, its everyday login password stops working for SMTP entirely, by design.

Microsoft folds several different authentication failures into one 535 5.7.3 string. The fix depends on whether SMTP AUTH is even enabled for this mailbox - checking that first…

Two codes, one message: the server said it supports something, then couldn't actually deliver on it when asked. That mismatch is almost always a middlebox - a firewall or security…

There is no standard reply numbered 512. What senders actually receive for this condition is 550 5.4.4: the recipient's system is known, but no route to it could be found.

Every 421 looks the same at first glance: a closed connection and a transient failure. The enhanced status code after it is the only thing that tells you which of five unrelated…

The mailbox is real and it is specifically turned off right now, not full and not nonexistent. Someone on the recipient's side needs to re-enable it before delivery can succeed.

The server told you it is shutting down right as you connected. There is nothing to diagnose on your end; the service will be back shortly and a retry will almost always succeed.

Your sending tool's status labels are translations, not facts. This maps the common dashboard words back to the real SMTP reply classes behind them, so you know what each label…

This is the retriable version of a sender-DNS problem: the receiving server could not find your sending domain right now, but is giving you another chance rather than refusing…

This looks identical to a sender-side rate limit but comes from the opposite direction: the recipient's own server is temporarily restricting delivery, usually tied to your IP's…

Three different codes share the 4.7.0 enhanced status with three different meanings depending on when in the session they appear. This one shows up after the envelope is underway,…

The verb is fine; the extra argument attached to it isn't. This is a narrower failure than 'command not implemented' - the server understood what you asked, just not one specific…

The server never got far enough to ask whether this sender is allowed to mail - it rejected the string itself as malformed before evaluating anything about it.

Your connection was accepted and the transaction was underway when the server's own state changed mid-stream. This is a timing-sensitive variant: a scheduled event caught your…

The mailbox did exist once. It has since moved somewhere the server can no longer forward to, and nothing you do on the sending side will reach it at this address again.

RFC 5321 defines code 555 specifically for this: a MAIL or RCPT parameter the server does not implement. The envelope syntax is correct; one add-on parameter attached to it is not…

This is the RCPT TO counterpart to a MAIL FROM syntax error: the recipient string itself is malformed, caught before the server ever asks whether that address actually exists.

421 4.7.28 means "try again later," not "you are blacklisted." Treating it like a permanent failure and panic-switching infrastructure usually makes the underlying reputation…

453 shows up in some deliverability tooling and blog posts, but it is not a code any RFC 5321-compliant server sends. Here is what is actually happening when you see it, and the…

A 421 4.4.2 reply almost always traces back to a network hiccup or an overloaded server dropping the connection mid-session, not anything in your message content or sender…

501 5.1.7 is rejected before the recipient is ever evaluated — the server is refusing the syntax of your own From address. This is a sender-side fix, usually in automated scripts…

452 4.3.1 is entirely a recipient-side resource problem — their mail server, not your sending setup. It resolves on its own once the receiving system frees up space; your job is…

554 5.1.1 means the mailbox genuinely does not exist. There is no retry, no delay, and no fix except removing the address — continuing to send to it damages your sender reputation…

A genuine mail server never issues a "442" reply. If your tooling reports it, what actually happened is the connection dropped before any SMTP code arrived, and your own MTA…

511 looks like a bad-address code, and it is often used that way informally, but no RFC-compliant mail server issues it. Here is the real code behind it and why the distinction…

421 4.4.1 is the SMTP equivalent of calling a number that rings with no answer. The recipient\u2019s mail server exists but didn\u2019t respond in time. Here is how to tell a…

553 covers a cluster of address-policy rejections, from malformed mailbox names to addresses the receiving server has specifically decided not to accept. Here is how to tell which…

A 5.7.2 rejection does not automatically mean SPF or DKIM is broken. Find the rejecting server, inspect the group’s posting rules, and retest with an authorized sender.

454 is one of the few non-obvious SMTP codes that is genuinely standard — defined by the STARTTLS extension. Paired with 4.7.5 it usually means a temporary credential or TLS…

554 4.4.7 is unusual: it is your own outbound mail server declaring defeat after repeated temporary failures, not a rejection the recipient actively issued. The real cause is…

471 shows up almost exclusively from legacy, self-hosted Windows SMTP relays rather than Gmail, Microsoft 365, or Yahoo \u2014 it is a vendor-specific IIS code, not an RFC-defined…

441 is used informally by some tools to mean "the recipient server never responded," but it is not something any mail server actually sends. Here is the real event behind the…

Most "mailbox full" bounces are a soft 4.2.2 deferral that retries automatically. 554 5.2.2 is the harder variant some servers use instead \u2014 a permanent refusal for this…

453 shows up mostly from older Sendmail-family servers and some shared-hosting MTAs under load. It is a deferral, not a bounce, and the fix is almost always on the receiving side,…

511 looks like a code but it is not one SMTP defines. Here is why it shows up anyway, and the two real codes it is usually standing in for.

471 is not in the RFC base table but it is genuinely emitted, mostly by Barracuda spam firewalls and legacy Exchange transport agents, when their own processing - not your content…

503 5.5.2 is a protocol-sequencing bug, not a content or reputation problem. If you see it, your sending code or script broke the SMTP state machine, and the fix is in your code,…

452 is a real transient resource failure, but 4.1.0 is the wrong enhanced code family for it. Here is what the base code tells you, why the subcode looks off, and what to do…

504 is "command parameter not implemented" - different from 500 (command not recognized) and 501 (syntax error in parameters). Here is the distinction and how to fix the actual…

431 and 432 do not exist as SMTP replies. Here is the real, standard code - 452 - that almost certainly generated whatever report you are looking at.

500 is the most basic SMTP rejection there is: the server literally does not know what command you just sent. Usually a malformed script, a stray character, or a command the…

555 is narrower than 500 or 501: it is specifically about MAIL FROM and RCPT TO parameters the server does not implement, defined explicitly in the SMTP extension mechanism.

450 4.1.2 looks alarming because "bad destination mailbox" sounds permanent, but the 450 base code means temporary. This is usually greylisting or a pending verification, not a…

451 4.3.5 is squarely a receiving-side configuration bug. It is a temporary failure, and no amount of changes on your side will fix it - only patience and, past a certain point,…

501 5.5.4 is a parsing failure in your own command or header syntax, not a judgement on the recipient or your reputation. Fixing it means fixing the exact malformed string, which…

4.0.0 is the catch-all enhanced status code. A 450 4.0.0 tells you almost nothing beyond "temporary failure, try later" - the real cause lives in the receiving server's own logs,…

4.2.1 specifically means the mailbox is known to exist but is in a state where it cannot receive right now - distinct from 4.1.2 (address status unconfirmed) and from a permanent…

Three numbers, none of them real. Here is the actual, standard code almost certainly behind whatever report cited 513, 515 or 517, and how to fix the real underlying address…

4.7.x enhanced codes mean policy, not resources or addressing. 450 4.7.0 is the receiving server saying "not now, because of something about how or how fast you are sending" - and…

5.7.1 is a policy enhanced code, and pairing it with 501 means the policy violation was caught at the command-parameter stage, not deeper in the transaction. Usually a relay or…

538 sits outside the core RFC 5321 code range, but do not mistake that for "fake" - it is a real, consistently implemented extension across every major provider for exactly one…

If your client shows "SMTP error 101," the server never said anything - your client never managed to connect. Here is what to check on the networking side, since there is no SMTP…

441 4.4.1 is your own system's way of recording "I tried to connect and nothing answered." The enhanced code 4.4.1 is real and standard; the base code 441 itself is a locally…

4.1.1 paired with a 450 is the holding pattern before a server commits to 550 5.1.1 ("no such user") or lets the message through. Treat it as pending, not as a verdict.

4.4.3 specifically means a routing failure: the server you connected to could not reach whatever internal or downstream host it needed to route your message onward. Different from…

420 sits outside the core RFC code set, similar to 538, but it is a real reply from identifiable infrastructure - mainly Yahoo - rather than a fabricated number. Here is what…

If a tool or legacy document cites 455, 458 or 459, treat them as historical curiosities, not something to expect from a current mail server - the real, current equivalent is…

551 is specifically about routing: "this is not the right server for this recipient." Usually caused by a stale MX record, an incomplete domain migration, or a relay being queried…

4.3.2 is the receiving system saying "I am intentionally not accepting mail right now" - different from being overloaded or broken; it is often a planned pause. Retry after a…

4.2.0 is the catch-all within the mailbox-status family: the receiving server knows the mailbox cannot accept mail right now but has not (or will not) tell you the specific reason…

354 is one of the few 3xx codes in everyday SMTP, and it means success-in-progress, not failure. If a report labels it an "error," the actual problem - if any - happened at a…

454 4.7.1 sits in the same family as 538 but with a temporary base code: the server is temporarily refusing your authentication attempt, usually because encryption needs to happen…

534 5.7.9 is one of the clearer authentication errors: your regular password will never work here. The account needs an app-specific password generated separately, because…

422 sits outside the core SMTP code range but is a documented, real Yahoo reply rather than an invented number - distinct from the fabricated codes elsewhere in this series.

553 5.3.0 sits a step beyond basic syntax errors: the mailbox name format itself is rejected outright by the server, often due to characters or structure the receiving domain…

smtp.gmail.com on port 587 with STARTTLS and an app password covers almost every case. The parts that break are app passwords without 2-step verification, From-address rewriting,…

Every authentication problem announces itself in one header line. Read it, match the verdict to the cause, apply the one DNS change that fixes it. No guessing, no republishing…

A DMARC record is one TXT record at _dmarc.yourdomain.com with about five tags that matter. The hard part is not the syntax, it is the order you tighten the policy in.

Microsoft 365 needs one MX record and one autodiscover CNAME. The records that actually get your mail rejected are the ones Microsoft does not host for you: the A record of your…

Brevo gives you a handful of DNS records and a green tick. The tick means Brevo can send; it does not mean your mail is DMARC-aligned. Here is the difference and how to verify it…

The include everyone pastes into their SPF record for Mailchimp is usually dead weight burning a DNS lookup. What actually makes Mailchimp mail pass DMARC is one CNAME.

spf=pass and dmarc=fail in the same header is not a contradiction. SPF authenticates the envelope; DMARC cares about the address your recipient sees. The gap between them is…

The most consequential AWeber setting is not a DNS record, it is the From address. Send from a gmail.com address and DMARC-enforcing receivers will reject you no matter how clean…

Most SMTP TLS is opportunistic, so a broken certificate usually means silent downgrade rather than failure — until a receiver enforces MTA-STS, and then the same certificate…

Publishing a DMARC record is five minutes of DNS. Reading the reports is the part that takes a tool, because they arrive daily as gzipped XML from every receiver that handled your…

Microsoft 365 signs your mail out of the box — with its own onmicrosoft.com domain, which does not align with your From address. Two CNAMEs and one toggle fix that.

Online checkers are convenient, but they cannot find your DKIM selector and they will not tell you which mechanism your DMARC pass depends on. Four dig commands and one message…

Mailgun asks you to add a sending domain, and the default it suggests is a subdomain. Take the subdomain. It gives transactional mail its own SPF budget and its own reputation,…

One hostname, used in four places: the EHLO banner, the forward A record, the PTR record and the TLS certificate. When they disagree, receivers treat you as a compromised host,…

Kit uses CNAME delegation rather than records you paste and maintain. That is a better design — it means Kit rotates keys and updates its own IP ranges without touching your DNS —…

Five record types carry every email system: MX for receiving, A for the hosts behind it, CNAME for delegation, TXT for authentication, PTR for reverse lookups. Knowing which one…

Campaign Monitor signs your campaigns, but the question that decides whether DMARC passes is which domain it signs with. One header line tells you, and it is not the one the…

Yahoo was the first large provider to publish p=reject on its own consumer domain, in 2014. That single change is still the reason platform mail from a yahoo.com address bounces,…

smtp.office365.com on port 587 with STARTTLS is the answer for Microsoft 365, and smtp-mail.outlook.com for personal accounts. The failures are never the ports — they are…

BIMI is the only email standard with a recurring certificate bill. It is worth it for brands that are impersonated, and a waste for most senders. Here is the real requirement list…

HubSpot will happily send from a domain you have not connected — and that mail fails DMARC on every enforcing receiver. Connecting the domain is the step that makes HubSpot mail…

Postmark will authenticate fine with DKIM alone. Adding the custom Return-Path CNAME is the step most people skip, and it is what turns a half-aligned setup into one that survives…

An SPF record is one line, and a generator writes that line for you. What a generator cannot do is count your DNS lookups, notice the include that resolves to nothing, or know…

Microsoft 365 passes SPF out of the box and signs with its own onmicrosoft.com domain unless you tell it otherwise. DMARC is what turns that into something aligned — and it only…

Forward DNS turns a name into an IP; a PTR record does the reverse. Receiving mail servers use it to confirm your sending IP actually belongs to the hostname it claims, and a…

SendGrid authenticates your sending domain with a set of CNAME records it generates for you, not a copy-paste DKIM key. Pair that with your own SPF include and a DMARC record and…

If Salesforce sends mail on your domain's behalf - from Marketing Cloud, Pardot, or standard Salesforce email - your SPF record needs to say so, and it needs to stay a single…

Constant Contact handles its side of SPF automatically once you add its include, generates a DKIM key you turn on from inside its UI, and leaves DMARC entirely up to you to…

Multiple SPF records is one of the most common self-inflicted authentication failures: every sender you add on its own gets a second TXT record, and DNS allows that even though…

Klaviyo's domain authentication panel gives you the exact DNS records to add; your job is publishing them correctly, verifying each one, and adding the DMARC record it doesn't…

"No DMARC record found" is not a bug in a checker tool - it means that lookup genuinely returned nothing. Here's how to confirm it, decide your starting policy, and publish a…

Amazon SES authenticates by default against its own amazonses.com subdomain, which passes SPF but doesn't align it to your domain for DMARC. A custom MAIL FROM domain fixes that -…

If you send from a domain hosted on Yahoo Small Business or Yahoo Business Mail, DKIM is enabled from inside that admin panel, not through a generic DNS template - here's what to…

A DKIM selector lets one domain run multiple DKIM keys at once - which is exactly why you can't guess it. Pull it from a real email's headers, then confirm it with a single dig…

Mailjet's domain authentication flow gives you an SPF snippet and a DKIM record tied to your account; getting both correctly published and verified is what actually lets DMARC…

SPF allows at most 10 DNS lookups during evaluation. Flattening collapses includes into raw IPs to dodge that ceiling, at the cost of having to manually re-flatten every time one…

Warming a mailbox builds sending history and engagement signal gradually - but if the IP it sends from has no PTR record, or one that doesn't match, every one of those warm-up…

If your domain sends mail through Yahoo Small Business or Yahoo Business Mail, SPF is a single TXT record you publish in your domain's DNS - here's the exact syntax, the…

Anyone can put your domain in a message's From: field - nothing about SMTP prevents it. DMARC is the layer that tells receiving mail servers to actually do something when a…

Once you've decided a record genuinely needs flattening, the mechanical part - resolving includes into IPs - can be done manually with dig or with a flattening tool. Here's the…

Publishing a key is only half the task. This guide covers the Google Workspace sequence, DNS pitfalls, and the header check that proves your domain is signing.

Microsoft consumer mail judges your sending IP harder than your domain, and there is no public list you can query to see whether you are blocked. The only real feedback channels…

Gmail gives senders one hard number to respect and a handful of requirements to meet. Everything else is engagement. This is the order to work through them, and the measurements…

Most Gmail placement numbers are wrong in a predictable direction: the Promotions tab carries the INBOX label, so API-based checks count it as a win. A correct test needs seed…

554 is the bluntest rejection in SMTP: the transaction failed and retrying unchanged will fail again. The text after the code is where the information lives, and it differs…

Microsoft publishes no blocklist you can query, so SNDS and JMRP are the whole of your Outlook-side visibility. Both are free, both need you to prove IP ownership, and both take…

Yahoo SMTP is smtp.mail.yahoo.com on port 465 with SSL, or 587 with STARTTLS — and your account password will not work. Yahoo requires an app password for third-party clients,…

A PTR record that does not resolve back to the same IP is a hard requirement failure at Gmail, not a nice-to-have. The check takes two commands, and the fix lives with whoever…

Gmail sorts messages into tabs after deciding they are not spam, using signals in the message itself: bulk structure, image-to-text ratio, link patterns and sender relationship.…

Acceptance, inbox placement and visible placement are decided by different inputs. Authentication and complaint rate decide the first, engagement history decides the second, and…

When Microsoft is unsure about a sender it slows the connection rather than refusing it. Queue delay is therefore a reputation reading, and the fixes are volume shape,…

Yahoo is often the provider senders ignore until bounces start. It shares its filtering with AOL, weights DKIM heavily, runs its own complaint feedback loop, and enforces the same…

Yahoo tells you when it is unhappy, in plain text, in the SMTP response. That makes warm-up progress measurable here in a way it is not on Gmail — if you know which codes mean…

Seed mailboxes are instruments, not treatments. Used properly they are the only way to see Gmail tab placement; used badly they produce a number that is confidently wrong in a…

Microsoft gives senders complaint rates and a colour grade, never placement. A seed set fills that gap — provided it covers both consumer Outlook and a Microsoft 365 tenant, which…

Mail can inbox on outlook.com and be quarantined by a Microsoft 365 tenant on the same day. Tenant anti-spam policy, transport rules and quarantine are invisible to senders, which…

Senders were redirected to v2 from 30 September 2025 and v1 was gone by the end of 2025. The reputation grade that most deliverability advice still tells you to check no longer…

An open on Gmail may be a human reading your mail, a cache fetch, a prefetch, or a security scanner. Treating that number as an engagement metric leads to bad deliverability…

A rewritten link points at a domain whose reputation is scored separately from yours. Share a tracking domain with thousands of other senders and you inherit their behaviour on…

Yahoo tells you why it is slowing you down, in the SMTP response, with a bracketed code. That makes it the best provider for learning whether your sending path is the problem — if…

A Workspace mailbox inherits Google infrastructure, not Google reputation. Your domain, your SPF and DKIM setup, your volume shape and your list quality do all the work — and a…

Most people work this problem backwards, rewriting copy while a reputation signal burns. The order matters more than any individual fix, because the early steps are deterministic…

Compliance is binary and placement is not. Senders who read the requirements as a deliverability recipe pass every check, see no reputation grade to explain the gap, and conclude…

The published number is rarely the number that binds you. Rate per minute, recipients per message, per-tenant throttles and reputation-based deferrals all bite before the daily…

Connecting a Workspace mailbox is a two-minute OAuth flow with a few admin-side traps behind it. The work that matters happens before: DKIM generated, SPF scoped, DMARC published,…

Gmail SMTP is smtp.gmail.com on 465 with SSL or 587 with STARTTLS, and your account password will not work. App passwords require two-step verification, and OAuth is the better…

No tool can see your inbox placement end to end. Gmail shows you a spam rate, your ESP shows you acceptance, a seed test shows you folders, and none of them agree. Knowing which…

List cleaning is not a product category, it is a threshold problem. Every sending platform has a number at which your account gets reviewed or paused, and a suppression list that…

On a shared ESP pool the IP reputation is not yours to warm — but the domain reputation is, and that is increasingly what filters score. Here is what you can influence, in what…

The choice is not about price or features. It is about which path can carry replies, which one the receiving filter expects for that kind of message, and which one has a sending…

SES gives you excellent infrastructure and almost no guardrails. The sandbox, the 5% bounce threshold, the suppression list and the MAIL FROM subdomain are the four things that…

Most placement tests are run once, on a stripped-down test message, from the wrong sending path, and then quoted as a percentage for months. Four changes make the same test…

Most dedicated IP problems are not warm-up problems, they are volume-consistency problems. Before you ramp, work out whether you have enough daily mail to keep the IP warm at all…

HubSpot sends from shared IPs it manages, so almost every HubSpot deliverability problem is one of three things: an unconnected sending domain, a stale contact list, or a stream…

One agency mistake dominates the rest: letting two clients share a sending identity. Isolation per client is cheap to set up in DNS and on every major ESP, and it is the only…

Deliverability problems are rarely sudden; they are gradual and then visible. A short recurring review catches the slope. Here is the exact list, in order, with the numbers that…

The filters deciding your placement genuinely are machine-learning systems. Most sender-side "AI" is scheduling and anomaly detection with a new label. Both facts matter when you…

Mailchimp has two separate steps that sound the same: verifying a domain and authenticating it. Verification lets you send from the address. Authentication is what makes DKIM and…

Every sending platform now ships a warm-up toggle. What differs is who the recipients are, whether anyone reads the mail, and whether the tool can see which folder it landed in.…

Asking "how do I improve sender reputation" has no single answer, because there is no single reputation. Split it into four layers, find the one that is failing, and the fix…

SendGrid gives you more deliverability controls than most platforms and defaults almost none of them on. Domain authentication, IP pools, suppression hygiene and the event webhook…

Every email API will deliver your first thousand messages. The differences show up in stream separation, log retention, suppression control and what happens the week your bounce…

Most "Salesforce is not sending email" cases are one setting: the org-wide email deliverability access level, which sandboxes reset on every refresh. After that, the work is DKIM,…

Two ecommerce platforms with identical feature lists can produce very different inbox rates. The difference is almost always in how they authenticate your domain and how they…

Campaign dashboards tell you about mail you sent. Infrastructure monitoring tells you about the records and addresses that make sending work at all — and those fail quietly, which…

Verification is four DNS and SMTP checks plus a classification. Knowing the mechanics tells you why half a B2B list comes back "unknown" and why no verifier can detect a spam trap.

ActiveCampaign runs your mail on shared IP pools it manages, so the levers you hold are the sending domain, the audience and the sending pattern. In that order, that is where the…

Most Postmark deliverability questions have the same answer: use the right message stream and authenticate the domain rather than the address. The platform is opinionated on…

Brevo gates campaign sending on domain authentication for a reason — unauthenticated mail from a shared pool is what gets filtered. Once that is done, the remaining levers are the…

A 99% delivery rate in Mailchimp is an acceptance rate, not an inbox rate. Opens are inflated by image proxies. Here is which Mailchimp metric to trust for which decision, and…

SendX bundles sending infrastructure into its plans, which hides the authentication details you need to fix placement problems. This walks through the checks that actually move…

Free warm-up tools are not a lesser version of paid ones - they are a different product with different limits. This breaks down what each tier actually does, where free tools…

Most teams check deliverability by watching open rate drift and hoping. This walks through the metrics that actually indicate where mail lands, how a seed-inbox test works, and…

Moosend handles sending infrastructure for you, which means the authentication details that affect deliverability live in a settings screen most users never open. This covers what…

Drip is built for ecommerce lifecycle email, which creates deliverability risks that generic ESP advice misses: one-time buyers who never engage again, and automated flows that…

No single tool covers authentication setup, warm-up, placement testing, and list verification at once - treating them as one job is why outreach teams keep rediscovering…

Cold outreach lives or dies on sender reputation before the first real email goes out. This covers the ramp schedule that holds up, why running two warm-up tools at once…

Campaign Monitor handles infrastructure, which means the authentication and reputation details that drive deliverability are mostly invisible unless you go looking. This covers…

A gambling operator running several brands out of one email infrastructure risks one brand's bonus-blast reputation damage spreading to the others. This covers domain isolation,…

SendPulse bundles email, SMS, and chatbot sending into one account, which can obscure where an email-specific deliverability problem actually sits. This covers the checks worth…

GetResponse bundles marketing automation with email sending, which can bury the authentication settings that actually drive deliverability. This covers the checklist worth running…

HubSpot's marketing and sales email tools often share the same sending domain, so a bulk campaign's reputation hit can land on sales reps' one-to-one outreach. This covers domain…

Klaviyo's flow-based automation makes it easy to keep targeting contacts who stopped engaging months ago, which quietly damages domain reputation. This covers the…

Authentication is the first fix, not the only one. This covers what to check once SPF, DKIM, and DMARC are confirmed live and AWeber deliverability is still inconsistent.

Template checking and deliverability testing solve different problems, and conflating them is why some senders pass every template check and still land in spam. This covers what a…

Faster email generation does not mean faster-safe sending volume. This covers how AI-assisted outreach tools change the risk profile of cold email, and the deliverability…

Every cold-email sending platform now ships a built-in warm-up toggle. That does not make it a deliverability tool. Here is the line between the two and how to tell which side of…

A sandbox that catches your app's test emails before they reach a real inbox solves a development problem. It has nothing to say about whether your production mail is landing in…

Most email signatures are harmless. A few design choices inside them - embedded images with no alt text, a shortened link, a banner ad - can measurably affect spam filtering. Here…

Paste a test address, send one email, get a score out of ten. Single-send spam-score tools are fast and genuinely useful as a pre-send check - and they stop being useful the…

Creators moving from a free address to a custom sending domain on Kit are the group most likely to see a sudden deliverability drop - and it is almost never Kit's infrastructure…

Teams building a sending feature into their own product eventually hit the same question: build warm-up and placement testing in-house, or integrate it. Here is what each path…

Shopping for a warm-up tool alternative usually starts with a feature-list comparison. The features that actually determine whether your mail reaches the inbox rarely make the…

An Omnisend campaign that suddenly underperforms is rarely a platform issue. It is almost always authentication, list hygiene, or a frequency change that pushed engagement below…

Apollo finds the prospect, SendGrid sends the email, and a warm-up tool is supposed to keep the sending domain healthy. The stack works - but only if each tool's job stays in its…

MailerLite sends on solid shared infrastructure for most accounts. When deliverability drops, the cause is almost always something in your own setup - authentication, list…

Most email programs run on one ESP and assume it covers everything deliverability-related. It covers sending. Warm-up, verification, and placement testing are separate categories…

Three different interfaces now claim to give you access to deliverability data: a CLI, an API, and increasingly an MCP server for AI assistants. They are not interchangeable -…

SMTP and API sending both end up at the same inbox, but they are not identical paths. The differences show up in how fast you find out something went wrong, not in whether the…

Segmenting a list by engagement is usually pitched as a way to improve click-through rates. It is just as much a deliverability safeguard - mailing a stale segment is one of the…

Infrastructure vendors sell you domains, mailboxes and an IP. They do not sell you a reputation — that you earn. Here is the checklist that separates a provider worth moving to…

Most cold outreach fails on list quality and length, not on wording. This is the sequence that works, the short template it produces, and the legal and deliverability constraints…

Mailbox providers in this category differ mainly in whose IP you share and who administers the tenant. Those two facts predict most of your placement. Here is how to check them…

Most subject line tests measure noise: inflated opens from image pre-fetching, two variants sent from mailboxes with different reputations, and a placement problem underneath…

Unlimited mailboxes is not unlimited sending. The caps that bind you on Microsoft-based infrastructure are per-mailbox and per-tenant, and they are the first thing to ask an…

Some cold outreach folklore is merely wrong. The seven below are worse than wrong: acting on them raises your complaint rate, burns a domain, or makes you optimise a metric that…

Bundled domain-and-mailbox providers are convenient right up to the day you want to leave. Registrar ownership and DNS control are the two clauses that decide whether switching…

An agency can build a pipeline or it can burn your sending domain, and the contract rarely distinguishes. These are the questions that separate the two, and the answers that…

Resold Workspace mailboxes buy you Google-grade outbound infrastructure and a tenant you do not administer. That trade is fine as long as you know which half of it you are keeping…

Every template here is three to five sentences with one ask, one link and no image. That is not minimalism for its own sake: it is what survives filtering on a young outreach…

Separating outreach from your primary domain is sound. Registering thirty near-misses of your brand name with no website behind them is not. The difference is whether a recipient…

Gmail clips messages over roughly 102 KB, and what gets cut is the bottom of the email — including your unsubscribe link. Here are the sizes that matter and the ones that are…

Humour in a sign-off works when you already have a relationship and the message is low stakes. On a first cold email to a stranger it reads as a stranger being familiar. Here is…

Send plain text for cold outreach and multipart HTML for mail people asked for. The reason is not that filters hate HTML — it is that a designed template is a truthful signal that…

Security buyers are the most sceptical cold email audience there is, and they run the gateway that filters you. These four templates are built for that: no fear, no implied scan,…

A sequencer automates sending, which means it automates your mistakes too. The settings that matter are the boring ones, and the metric it cannot give you is the one that decides…

A sequence is not a pitch repeated. Each step should add one new thing and get shorter. Three messages is the right length, and the reason is complaint rate, not politeness.

Scaling outreach is an architecture problem, not a volume problem. The layout that survives is a small number of properly built domains with few mailboxes each, brought online in…

Divide the sends you need by a deliberately low per-mailbox daily figure, add spare capacity, and that is your answer. The common mistake is dividing by the provider ceiling…

The domain decides more about your placement than the copy does, because reputation attaches to it. Pick a secondary domain a recipient can verify, put a real page on it, and…

Before you rewrite anything, find out whether the mail is reaching an inbox. A campaign with no replies and no bounces is usually a campaign in spam, and your sequencer reports it…

AI-written cold email is not a high-risk AI system, and most of the Act does not reach it. The rules that do bind your outbound are still GDPR and the ePrivacy national laws. Here…

CTOR is clicks divided by opens, and opens stopped being trustworthy when mail clients began pre-fetching images. Here is what the metric can still tell you and what to use…

A signature is the part of your email you stopped looking at years ago, and it is often the heaviest, link-densest and most bulk-looking part of the message. Here is what to strip…

A cold email is read in under ten seconds, usually on a phone, often with images off. Every design decision you make for a cold send should be judged against that, not against…

Cold email means different things in different contexts, and some of those contexts carry real legal exposure. Before you build a sequence, work out which bucket you're in.

Every "top alternatives" post states competitor pricing and plans as fact, and those numbers are usually stale within months. Judge infrastructure providers on things you can…

A subject line can't get you into the inbox on its own, but specific patterns reliably make filters and recipients more suspicious. These are the ones worth actually removing from…

Any specific inbox-placement percentage you read somewhere was measured on a different list, a different industry, different mailbox providers, and a different point in those…

Trust in a cold email is decided before the recipient reaches your signature — by the from name, the reply-to address, and whether the sending domain matches what you claim to…

A startup's cold email problem isn't template quality — it's starting from zero reputation, zero recognition, and one person doing outreach alongside everything else. Plan around…

The choice between a batch campaign and a drip sequence isn't just a messaging decision — it changes the volume pattern your domain sends in, and mailbox providers watch volume…

A creative or marketing agency pitching new business by cold email is held to its own standard — the recipient is judging whether you can write a good email by reading the one you…

Teams know they need to "warm up" before cold sending, but most skip straight to volume ramp without confirming the parts a ramp schedule can't fix on its own. Check these first.

Five sentences, one ask, no filler — but which five sentences, and why those and not others. Here's the reasoning behind each part of a cold email that actually gets answered.

"Best time to send" advice is usually a borrowed average from someone else's audience. The timing decisions that are actually yours to control are spacing between touches and…

A voice note attached to a cold email might change reply rate through novelty, but it has no mechanism for changing inbox placement. Don't confuse an engagement tactic with a…

More sends does not reliably mean more leads if the extra volume is lower-quality, because the spam complaints it generates damage placement for every message after it, including…

The design question (clean vs. branded) is separate from the compliance question (what has to be there). Get the second one right regardless of which way you go on the first.

The second and third touches in a sequence don't behave the same way on Gmail as they do on Outlook, because the two platforms handle threading, quoted text, and header alignment…

The best social proof is specific, relevant, and easy to verify. This guide shows how to include it without turning a short prospecting email into a filtered marketing asset.

Unsubscribe links are not decorative compliance text. A clear one-click path gives people an alternative to marking mail as spam and gives your sender reputation less to recover…

Most "how to send cold email" guides start at the subject line. The subject line is step four. If your domain is not authenticated and your list has not been verified, no amount…

Clever subject lines age badly because spam filters learn the cleverness. The subject lines that still work are the boring ones: specific, short, and honest about what is inside.

Your IP can be poisoned by someone else: a compromised mailbox, an open relay, a subscription bomb, or a neighbour in a shared pool. Each leaves a different fingerprint in your…

Delivery rate and placement rate are not the same thing, and most "deliverability scores" are a blend of unrelated checks. A placement test needs seed mailboxes at each provider,…

A payments or lending domain gets scrutiny a SaaS domain does not: your brand is a phishing target, so providers treat lookalike patterns and sudden volume harshly. Enforce DMARC…

Reputation is not one number — it is several private ones, computed per provider and mostly from recipient behaviour. Here is what feeds it, which public signals still exist, and…

App passwords and basic auth are being closed off across providers, OAuth sees folder placement that SMTP cannot, and forwarded mail breaks SPF in ways SRS only partly fixes. Pick…

Two to six weeks per domain, but the variance is the whole problem: an inherited domain with a blocklist history takes longer than a fresh one. Audit before you quote, warm on…

If you cannot sustain steady daily volume, a dedicated IP will hurt you rather than help. If you can, warm it over four to six weeks, split by provider, and let deferrals set your…

Change your sending IP and a domain problem follows you. Change your domain and you throw away the history that makes you deliverable. A short diagnostic separates the two, and…

Most deliverability disasters were visible for two weeks before anyone noticed. A short daily check, a weekly review and a monthly audit catch almost all of them, and none of it…

If you send through Google Workspace, Microsoft 365 or a shared ESP pool, the IP is not yours to warm. What you warm is the domain and the mailbox. Here is how the two differ and…

Google Workspace caps a user at 2,000 messages a day. Microsoft 365 adds a per-minute rate limit. Amazon SES starts you in a sandbox at 200. Knowing which wall you hit changes the…

Half of new-domain warm-up failures are decided before the first message: a stale SPF include, no DMARC reporting address, mailboxes created in a batch. Work through this list in…

Warm-up builds a sending history. It cannot repair a bad list, a misaligned DKIM signature or a listed tracking domain. These are the five things to check when the ramp finished…

Every warm-up vendor sounds the same in a feature table. The question worth asking is what the product does on your behalf — send real mail and measure placement, or produce…

Delivery rate counts acceptances; a seed list tells you the folder. Here is how to assemble one that represents your actual recipients, how to send to it without distorting the…

If your seeds open and click your mail, your open rate goes up and your deliverability does not. Worse, Apple pre-fetches images and Gmail labels Promotions as INBOX, so the…

Dormant lists contain dead addresses, recycled spam traps and people who forgot you. Mailing all of them at once is how domains get listed. Ramp by recency, cap the segment, and…

Ask what the product sends on your behalf, whether it reads folder placement or infers it, which providers its network covers, and what it does after the ramp ends. Those four…

At 5,000 messages a day to consumer Gmail you are a bulk sender with published obligations. Plan capacity backwards from per-mailbox limits, ramp every mailbox separately, and…

Your open rate includes privacy pre-fetches and your click data includes link scanners. Filter the machines out first, then work on the three things that genuinely change clicks:…

iCloud is the provider most senders cannot see into. No postmaster tools, no complaint feed, terse rejections. Seed mailboxes and clean authentication are the whole toolkit, and…

Your recipients sit behind Proofpoint, Mimecast or Defender, and they report suspicious mail as a reflex. Publish strict DMARC early, avoid every phishing-adjacent pattern, and…

Filters treat gambling content as high-risk regardless of your reputation, and bonus-heavy copy makes it worse. The playbook: dedicated domains per stream and market, consent you…

On a shared pool you cannot fix the IP, so everything depends on domain authentication, list quality and stream separation. Here is the Mailjet-specific setup and the signals that…

Most reputation-repair advice reads as an unordered list. It isn't one. Fix the wrong thing first and you burn a week finding out the real problem was still there.

Passing a placement test and then watching a real campaign land in spam feels like the test lied. It didn't — it answered a narrower question than the one you were actually asking.

Under the marketing language, every warm-up tool does the same three things: connect to mailboxes, ramp volume, and simulate engagement. How it does each of those three is what…

Most warm-up tool comparisons are a list of checkmarks. Here is the shorter list of questions that actually predicts whether a tool will help or quietly hurt your domain.

Varying subject lines and body copy during warm-up isn't decoration. Sending the same template on a loop between a closed pool of mailboxes is a pattern filters can learn,…

Warm-up tools mostly look the same from the outside. These four signals separate the ones that build real reputation from the ones quietly building risk.

Not all engagement signals carry equal weight with mailbox providers. Knowing which one actually moves reputation changes how you read your own metrics and how you should think…

Manual domain reputation checks aren't wrong, they're incomplete. Here's exactly where the gaps are, and what a sensible hybrid routine looks like instead of an all-or-nothing…

A seed list and a placement test use the same underlying mailboxes but answer different questions — one is infrastructure, the other is a single measurement. Mixing them up is…

Filters already treat certain industries as higher risk before a single message is sent. That changes how much margin you have during warm-up, not what warm-up fundamentally is.

Manual warm-up isn't a worse version of automated warm-up — it's the right choice at a certain scale. Here is the actual decision point, not a blanket recommendation either way.

A seed list is only useful if someone actually looks at the results. Past a certain sending volume, a CSV nobody has time to open stops being a monitoring system and starts being…

A warm-up tool that reports its own click count is measuring the wrong thing. The number that matters is whether real per-provider placement actually changed as a result.

Warming up a Gmail or Outlook mailbox and warming up a custom SMTP domain look similar on paper and differ in one important way: you don't get the provider's own inbox-side…

Warm-up tools and cold outreach platforms get compared as competitors. They're not — they do different jobs, and most senders who rely on only one are missing the other.

Every warm-up timeline guide gives a number. The more useful question is which specific factors push that number up or down for your situation, because the honest answer is 'it…

Warm-up looks like a delay when you're staring at a launch date. In practice, skipping it rarely saves the time it appears to — it just moves the cost to later and adds a…

A domain's good reputation doesn't automatically transfer to every mailbox on it. A new address on an established domain starts ahead of a brand-new domain, but it still needs a…

Adding clicks to a warm-up pool isn't automatically better than open-only warm-up. It's a real lever with a real ceiling, and knowing where that ceiling is matters more than the…

There's no reputation API to query. Understanding reputation means knowing the specific, checkable inputs providers actually look at, because that's the closest thing to a…

A quick sign-up and a glance at the dashboard isn't a trial. Here's what to actually check, and for how long, before trusting a warm-up tool with a domain that matters.

Blacklisting feels like an emergency that needs an immediate fix. The honest answer is slower than that: most domains can recover, but recovery is measured in weeks, and sometimes…

Choosing between a dedicated and a shared sending IP changes what warm-up actually has to accomplish — one builds reputation from zero, the other borrows it from strangers.

Most cold outreach problems are visible in advance if you check for them. Here is the pre-launch checklist that catches the common causes before the campaign goes out, not after…

A footer is not decoration. It carries your identity, your postal address and the unsubscribe path that mailbox providers check for. Here is the minimum that keeps you legal, the…

Verification runs four checks, and only the first two are reliable. Here is what each layer proves, why Gmail and Microsoft 365 defeat the SMTP probe, how catch-all domains turn a…

The phrase is not rude or spammy — it is just empty. It asks for nothing, commits to nothing and gives the reader no next action. Here are replacements grouped by situation, and…

Your email client hands the message off and forgets about it. The MTA is what carries it, retries it, identifies itself to the receiving server, and decides how fast to push. Most…

Most phishing links give themselves away in the registrable domain, the redirect chain, or the mismatch between link text and href. The harder question is the one senders ignore:…

Deliverability problems have a fixed diagnostic order, and checking it out of order wastes days. Authentication first, because it is binary. Then blocklists. Then the list.…

Embedded video works in Apple Mail and essentially nowhere else. The reliable pattern is a static thumbnail with a play overlay linking to a hosted page — and the deliverability…

A form in an email body is stripped by Gmail and Outlook, and form markup itself raises filter suspicion. The pattern that works is a one-click link to a prefilled hosted page —…

Image buttons disappear when Outlook blocks images, which is by default. A bulletproof button is live text with a coloured background, and a clickable phone number is a tel: link…

GIFs are safe in email as long as frame one carries the message and the file stays small. Outlook on Windows shows only the first frame, there is no prefers-reduced-motion in…

Most deliverability checklists are unordered, so people start with subject lines and finish with SPF. Reverse it. Authentication is binary and takes an hour; list hygiene is where…

The expensive mistakes in an ecommerce email migration all happen in week one: one domain for every stream, an unfiltered list import, and a day-one blast to 80,000 addresses from…

The US has no opt-in requirement and the strictest provider enforcement. That combination means compliance is cheap and placement is hard. Here is what actually governs a US…

Ecommerce lists grow from checkouts, not from opt-ins, which is why ecommerce complaint rates are structurally higher than B2B. These are the ongoing practices that keep a growing…

When ecommerce email stops performing, the cause is usually one of four things: a shared pool you do not control, an app sending as your domain, addresses collected at checkout,…

DMARC became a standards-track specification, and the changes are real but small. The tree walk replaces the Public Suffix List, pct is gone, np and t are new. Most senders need a…

There is no standard email health score. Every tool invents its own composite from authentication, blocklist status, bounce and complaint rates, engagement and placement. Knowing…

Gambling email is filtered as a category, not as individual messages. Operators lose reputation faster than any other vertical, usually through affiliate-sourced lists and…

Any ESP can only control its own infrastructure. Your domain reputation, list quality and warm-up state are yours. Here is the split for Mailmodo, and the order to work through…

Most free options give you inbound mail, not outbound. That distinction decides whether your replies authenticate or land in spam. Here is what each free route actually provides…

B2B email changed in two ways that matter: open rates stopped being measurable, and mailbox providers started enforcing authentication. Most B2B best-practice lists have not…

Mailbox hosting and bulk sending are different products, and most comparison articles conflate them. Here are the criteria that decide whether a provider will serve you in two…

Attackers stopped sending malware attachments. They send a convincing invoice change, a consent prompt for an app, or a login page that relays your one-time code. Here are the…

A domain is the one asset your email reputation is attached to, and some domains arrive pre-damaged. Here is how to pick one, how to check its history, and what to publish before…

Sending to US recipients has its own rules and its own mailbox providers. Here is what to check before you scale a US list, and which metrics actually predict a problem.

Flash sales, abandoned-cart flows and checkout opt-ins create deliverability risk that most ecommerce teams only notice after a drop in open rate. Fix the infrastructure before…

Delivery rate and deliverability are not the same number. This guide covers what actually determines whether an ecommerce send reaches the inbox, and where to look when it fails.

Deliverability is not one setting - it is authentication, sending behavior, and list quality working together. Here is the short version of what actually keeps mail out of spam.

DMARCbis is not a new policy you need to adopt - it is the IETF formalizing DMARC as a real standard. A few mechanics changed underneath. Here is what matters for your existing…

A single "health score" number is a shortcut for several underlying signals. Knowing what feeds it is the fastest way to move it - and to know when it is hiding a real problem.

Casino and betting content trips spam filters that other verticals rarely hit. iGaming senders need tighter authentication, cleaner lists, and slower ramps than the average CRM…

An automated system that emails on its own schedule is still bound by SPF, DKIM, DMARC and sender reputation. Unmonitored automation is where deliverability problems go unnoticed…

By the time open rates visibly drop, a deliverability problem has usually been building for weeks. Here are the earlier signals worth checking on a regular basis.

A messy email list quietly caps deliverability no matter how good the campaigns are. These are the hygiene habits that keep an ecommerce list sending-safe.

High-converting B2B copy and high-deliverability copy are not the same skill, but they overlap more than most writers assume. Here is where the two pull in different directions.

Batch size is one of the more debated deliverability levers. It matters less for an established domain and much more for a new or recently-warmed one - here is why.

A free business email is possible, but "free" usually means either no custom domain or deliverability trade-offs. Here is what to check before choosing one.

Good B2B email marketing and good deliverability come from the same underlying discipline: a clean list, relevant content, and infrastructure that matches the volume you actually…

Most comparisons of business email providers focus on price and storage. Deliverability depends more on authentication support and how the provider handles sending reputation.

Email security for a SaaS sender is not just about blocking inbound phishing - it is about making sure your own outbound mail cannot be spoofed, and that a security incident does…

There is more than one way to get mail@yourcompany.com working. Here is what each route actually involves, side by side, and which DNS records you still have to set up yourself…

Open rate is the metric everyone watches and the one that explains the least about deliverability. Here is what belongs on a dashboard instead, and where each number comes from.

GDPR and email deliverability are usually covered separately, but the overlap is direct: nearly every GDPR requirement for email marketing also happens to be a deliverability best…

Five mailboxes means five warm-up curves, five sets of DNS records, and five reputations that can each fail independently. Here is how to manage that without losing visibility on…

Sender reputation does not reset overnight, in either direction. Here is what actually moves it, in the order that produces results fastest, and how long each step typically takes…

By the time Black Friday emails start landing in spam, the mistake that caused it usually happened two or three weeks earlier. Here is what to check before, not during, the sale.

Feeding email engagement data into ad retargeting is a reasonable growth tactic. Done carelessly, it also creates consent and list-quality problems that show up as deliverability…

Cold email works when the legal basis, the infrastructure, and the message are all handled correctly - and fails in a different way when any one of the three is skipped.

Getting listed on a blocklist is not the end of deliverability for a domain, but the fix depends on actually finding the cause before you request removal - a request without a fix…

Sending a test email to yourself and seeing it arrive is not a deliverability test. Here is what an actual test checks, and how to read the headers that tell you why a message…

Deliverability fixes compound in the wrong order if you tackle them randomly. Here is a phased roadmap - authentication, hygiene, warm-up, monitoring - that builds each phase on…

A founder does not need to read a DNS record to protect email deliverability - but does need to know which four questions to ask whoever sets up the sending infrastructure.

Sending volume at scale is limited by how many mailboxes you have, not just how big your list is. A mailbox calculator turns a target send volume into a required mailbox count,…

A startup sending its first cold outreach or its first product-update email starts with zero sending history - which is exactly the condition mailbox providers treat with the most…

Guessing at why a message landed in spam wastes time on the wrong fix. Here is the order to check things in, so you find the actual cause instead of the first plausible one.

A mailbox does not have one safe sending number - it has a curve that changes with warm-up stage, recent complaint rate, and domain reputation. Here is how to do that math without…

Most dashboards lead with open rate, which is the slowest metric to react when deliverability starts to slip. Here is the short list of metrics that move first, why they move…

Legitimate interest is the legal basis most B2B senders lean on under GDPR, but it comes with a balancing test, a mandatory opt-out, and record-keeping obligations that get…

Sender reputation isn't published by Gmail or Outlook as a single score you can check. It's inferred from signals you can partially observe - complaint rate, spam-folder rate,…

The sending volume spike around Black Friday and Cyber Monday exposes capacity problems that were invisible at normal send volume. Here's how to pressure-test your sending…

Email addresses collected through programmatic ad campaigns and lead-gen forms carry more risk than list addresses from almost any other source: incentivised sign-ups, bot…

A cold email template can use perfectly reasonable language and still get filtered because of structural choices: link density, image-to-text ratio, tracking redirects, and HTML…

Validity's Heatwave blocklist, launched 3 September 2026, is a domain-level list distinct from the older IP-based blocklists most senders are used to checking. Here's what it…

A seed-list inbox placement report shows exactly where one test send landed across a panel of mailboxes - inbox, Promotions, or spam, by provider. Here's how to read the result…

Running cold outreach or high-volume transactional sending from a single domain creates a single point of reputation failure. A multi-domain setup spreads that risk - but only…

If you run email marketing but don't have DNS access, deliverability can feel like a black box someone else owns. Here's the specific checklist to hand your IT or development…

A cold email list accumulated over months or imported from several sources carries risk that doesn't show up until you actually send to it. Here is the sequence to run before…

Proactive deliverability monitoring isn't about watching more dashboards - it's about setting specific, actionable thresholds on a small number of metrics so you're alerted…

Spam filtering today relies mostly on sender reputation and engagement history, not keyword matching - but subject-line and body language in certain categories still correlates…

A message in Gmail's Promotions tab is technically delivered to the inbox - it carries the INBOX label at the protocol level. But users check Promotions far less often and with…

Most email marketing platforms list the same feature categories - segmentation, automation, analytics. For a SaaS company specifically, the differences that actually affect…

Recruiting emails - candidate outreach, interview scheduling, offer communications - carry different deliverability risk than marketing campaigns, largely because of…

Agencies managing email for multiple clients face a deliverability risk marketing teams at a single company don't: one client's poor list hygiene or aggressive sending can affect…

UK email deliverability runs on the same core authentication standards as everywhere else, but two things differ meaningfully: a dual regulatory framework of UK GDPR and PECR that…

Cart abandonment emails often perform worse on deliverability than other ecommerce mail sent from the same domain, because of specific structural and behavioural patterns common…

SaaS onboarding drip sequences - welcome emails, setup nudges, feature announcements triggered by signup date - carry a specific deliverability risk tied to how they're sent:…

The CAN-SPAM Act sets the legal floor for commercial email sent to US recipients. Unlike GDPR, it doesn't require consent before a first message - but it has specific,…

A domain with flawless SPF, DKIM, and DMARC can still get blocked or filtered because of how it sends, not whether its headers authenticate correctly. Here are the behavioural…

The technical core of deliverability - authentication, list hygiene, warm-up - is the same everywhere. What changes region by region is the mix of dominant mailbox providers, the…

Microsoft's filtering for Exchange Online Protection (the system behind Microsoft 365 and Outlook.com) places significant weight on sending pattern and volume history, which means…

2026 brought several concrete changes to email deliverability tooling and standards, not speculative trend predictions: an overhauled Google Postmaster Tools, DMARCbis formally…

An ESP (mailbox provider) block and a third-party blacklist listing produce a similar symptom - mail not arriving - but come from different systems, get detected differently, and…

The accuracy of any inbox placement test depends entirely on the quality of the seed list behind it - a panel of mailboxes spread across providers that the test sends to and…

SMTP is the original protocol for sending email, defined in the 1980s. ESMTP extended it to support the features modern sending - authentication, TLS, delivery status…

Most "email marketing tips" lists are written for ecommerce and retrofitted to SaaS. A SaaS product has a different problem: a small number of named accounts, a multi-year…

A "STARTTLS failed" message is a negotiation failure, not an encryption failure. The fastest diagnosis is to open the session by hand and read what the server advertises after…

The mechanism list a server advertises after EHLO looks like a menu of security levels. It is not. Two of them are equivalent, one is a historical curiosity, and one is the only…

Almost all mail between major providers is already encrypted in transit. The gap is that opportunistic TLS fails open — strip the STARTTLS advertisement and the message goes in…

Deferred mail is the receiver telling you to slow down or come back later. Treating those recipients as bounces deletes valid addresses; retrying them aggressively earns a longer…

Most SMTP authentication problems are three settings in the wrong combination. Get the port, the encryption mode and the credential type right together and the rest is one…

Receivers do not just count your messages, they look at the shape of the curve. A thousand messages at 09:00 from a thin-reputation sender is the pattern a compromised account…

Gmail, Outlook and most mailbox providers now accept mail over IPv6, but reputation tracking works differently on a /64 or /128 than it does on a single IPv4 address. This post…

Reverse DNS on IPv6 is a different delegation chain than IPv4, and the failure is silent until a mailbox provider starts rejecting your connections. This post is a working…

BIMI is an authentication-adjacent record, not a deliverability feature by itself - it requires DMARC enforcement first and a verified mark certificate at most receivers. This…

DNS propagation is not a fixed wait time - it is governed by TTL, resolver caching, and your registrar's own update speed. This post explains the mechanism and gives a sequence…

Sending from an alias instead of a dedicated mailbox changes how SPF, DKIM and reputation apply, and the gap is easy to miss until bounce or spam-folder rates climb. This post…

Sender reputation is not one score - it is the running total of small positive and negative feedback signals, most of which a sender never sees directly. This post breaks down…

TTL is the single setting that determines how long a DNS change takes to be consistent everywhere. This post is a practical sequence for lowering TTL ahead of an MX or SPF…

When an alias sends through infrastructure that was never added to the domain's SPF or DKIM configuration, every message from it fails authentication - quietly, until DMARC…

Formal FBL programmes exist at a subset of mailbox providers and give senders ARF-format complaint reports in near real time. This post covers the registration mechanics, what the…

Most deliverability questions can be answered from the raw message source if you know which three header blocks to read. This post walks through a real header set line by line and…

Authentication-Results is written by the receiving server at delivery time, which makes it the ground truth for how your mail actually authenticated at that specific provider.…

The From name and preheader are rendered by the recipient's mail client before the subject or body is read, and most senders either waste that space on boilerplate or let it…

Deliverability conversations use a specific, dense vocabulary that is easy to nod along to without actually knowing. This glossary defines each term the way it is used in a real…

Calling email an 'owned channel' usually glosses over the maintenance it requires to stay that way - a neglected domain's reputation can effectively revoke that ownership. This…

List hygiene is usually explained in terms of why it matters and skipped on how to actually run it. This post covers double opt-in implementation, bounce-based suppression rules,…

Every mailbox provider sees aggregate sending volume spike in the same narrow seasonal window, which tightens filtering sensitivity at exactly the moment most senders are pushing…

MIME errors usually show up as garbled attachments or raw headers printed in the inbox, not as a bounce. The fix is almost always in the Content-Type header or the multipart…

Every MTA holds messages in a queue between acceptance and final delivery. Understanding the difference between the active and deferred queues is the fastest way to diagnose why…

These codes aren't interchangeable - 220 opens the connection, 250 confirms a command succeeded, and 221 closes it. Seeing the wrong one at the wrong stage is the actual signal…

There's no universal certification for this role and no single tool that covers it. In practice it's a mix of DNS maintenance, log analysis, reputation monitoring, and translating…

Most audits fail by jumping straight to "check the blocklists" without first confirming authentication is even correctly configured. Do it in order: records, reputation, hygiene,…

A message in Promotions reached the inbox; a message in spam did not. Confusing the two when reading a deliverability test is one of the most common mistakes in reading Gmail…

The deliverability trade-off isn't about which is "better" in general - it's about who owns the IP reputation, who maintains the queue and feedback loops, and how much that…

The risk in switching warm-up providers isn't the new tool - it's the overlap window where both the old and new tool are sending from the same mailbox, plus whatever DNS records…

A spam filter doesn't have one "spam" category - it runs different detection logic for phishing (link and domain analysis), malware (attachment scanning), and bulk marketing…

Being compliant protects you legally; it doesn't move a single filtering signal. The gap between "legal" and "delivered" is exactly the engagement, reputation, and pattern data a…

Website backlink authority and email sender reputation are measured by different systems, evaluated by different teams even within the same company, and don't transfer between…

If email from your domain is landing in spam, restructuring your website's content or keyword targeting won't move that needle - the fix is in DNS records, sending reputation, and…

A list that was clean a year ago is not clean now. Addresses go dormant, domains get abandoned, and some of those abandoned addresses get reactivated as spam traps. Here is the…

A lead magnet's delivery email gets sent to everyone who filled out a form, immediately, often before anyone has confirmed the address is real or wanted to hear from you again.…

More leads in the pipeline is the goal, but the usual way teams try to get there - more email, to more people, faster - is also the fastest way to damage the sending reputation…

Picking a sending domain is usually treated as a branding decision, but a handful of structural choices - subdomain vs root, a clean history vs a reused one, avoiding look-alike…

Every list-building method trades speed for risk. The methods below are slower than buying a list, and that is the point - they produce addresses that belong to people who expect…

Address verification at signup is usually reduced to one step - a confirmation email - but that only proves consent. It doesn't catch a mistyped address, a disposable domain, or a…

A long B2B sales cycle means you don't need to email thousands of people a day to hit a pipeline target, and treating cold outreach like a volume game anyway is the most common…

The phrase send a video through email is misleading: no mainstream email client plays embedded video, so what you're really building is an email with an image that links to a…

The provider you send from matters less for deliverability than whether it's a consumer or business tier account, and whether that account has a sending history. Here is the…

If open rate is your main deliverability dashboard, you are looking at the metric most distorted by client-side privacy changes. Complaint rate, bounce rate, and direct placement…

Bad deliverability advice usually isn't malicious - it's outdated, oversimplified, or confuses a correlation for a cause. Here are seven claims worth retiring, and what to focus…

DANE (DNS-based Authentication of Named Entities) uses DNSSEC-signed TLSA records to let a receiving mail server verify the TLS certificate of the server it's connecting to,…

Modern spam filtering weighs how recipients have historically treated mail from you - opens, replies, deletions, spam reports - more heavily than any specific word or phrase in…

The best cold email CTA is the one most likely to get a genuine reply, and the structures that produce genuine replies - a single clear ask, low friction, plain language - also…

Comparing deliverability tools by feature checklist tends to miss the tradeoffs that actually matter - network size, provider coverage, how warm-up actually works, reporting…

Tracking pixels still work mechanically the way they always have, but what they measure has quietly become less trustworthy as mailbox clients changed how and when they load…

Exchange and Outlook.com wrap several different hard-bounce reasons in this one message. The fix depends entirely on the enhanced status code sitting inside it, not the wrapper…

Mail providers now require authenticated SMTP for outbound mail. If a client was configured years ago, or basic auth was switched off, you get a plain-text rejection telling you…

Gmail does not ask you to invent a special DMARC record - it enforces the same DMARC standard everyone else does, but it added a hard volume threshold and it suspends delivery,…

Mailbox providers do not have a secret bypass switch. They score authentication, sending infrastructure and recipient engagement, and mail that clears all three reaches the inbox.…

Volume alone doesn't trigger spam filtering - unverified recipients, missing authentication, and a sudden jump in sending volume do. This covers the mechanics that keep a bulk…

Sending marketing or cold outreach from a subdomain (mail.yourdomain.com) rather than your root domain keeps a reputation problem contained. Here is how to create that subdomain…

Most ESP comparisons start with templates and automation features. The decision that actually protects your inbox placement is whether the platform makes authentication, IP…

Technically, John.Smith@example.com and john.smith@example.com could be different mailboxes. In practice, the mailbox providers that matter treat them as identical - but a few…

AI-generated email content and AI-assisted personalization are now common in marketing tools, but none of it changes the fundamentals that decide inbox placement. Here is what AI…

A translated newsletter and a localized one perform differently, because translation changes the language and localization changes everything that language sits inside - layout…

Confusing ESP and ISP leads to troubleshooting the wrong system when mail doesn't arrive - one of them is your sending platform, the other is the recipient's mailbox provider, and…

Most spam-reduction advice is either outdated or ineffective. This covers the handful of habits - provider choice, filter training, address hygiene - that actually cut down what…

Every email you send travels over SMTP for at least part of its journey, but SMTP itself only handles the transfer between servers - retrieving mail into your inbox is a separate…

Subdomain stripping shows mail@yourdomain.com instead of mail@mail.yourdomain.com to the recipient, while the sending infrastructure still sits on the subdomain. It's a branding…

Google's own guidance treats a spam complaint rate above roughly 0.3% as a problem serious enough to affect inbox placement, and staying meaningfully under 0.1% is the safer…

Most 'why is my email in spam' advice predates 2024's bulk sender requirements. Here are the specific, named bars Google and Yahoo check, in the order they're worth fixing.

A lead generation program's real output isn't the lead count - it's how many of those contacts your domain can actually reach. Lead quality and sending reputation are the same…

Content and list practices are the half of spam-filter avoidance that doesn't involve DNS records - a reliable provider, a genuinely opted-in list, and testing before send catch…

IPv4 and IPv6 aren't just a bigger address space - for email specifically, the two have different reputation mechanics, different authentication expectations, and different…

Threading looks like a client-side display feature, but it's driven by specific headers set at send time. Getting those headers right (or wrong) determines whether a reply is…

A delayed send and a blocked send look similar from the outside, but throttling is a deliberate pacing decision, not a rejection - and whether it's your ESP or the recipient's…

Pseudo-leads waste sales time chasing contacts that were never going to convert, and when the underlying address is fake or mistyped, they also quietly damage sender reputation…

Most advice about generic and role-based addresses covers them as recipients to avoid on a list. This covers the less-discussed side: what happens to engagement and reputation…

A 99% delivery rate sounds like a deliverability win, but delivery rate only confirms a receiving server accepted the message - not where it landed once accepted. Here is the…

Aliases solve real, narrow problems: a temporary address for a one-off signup, covering two roles from one inbox, an internal distribution point. Here is when each is the right…

Cold mailing isn't inherently spam, and it isn't a guaranteed-results channel either. Its real advantages and disadvantages depend almost entirely on execution - targeting,…

This is for SES senders already out of the sandbox who've hit a new spam problem - not initial setup. The usual causes are a quiet reputation decline, a feedback-loop gap, or a…

One account holding 300 mailboxes across eleven clients is not eleven accounts. The numbers blend, the wrong person pauses the wrong warmup, and nobody can answer "how is Acme…

Industry data shows that over 20% of legitimate cold emails never reach the primary inbox - they land in spam, promotions, or simply vanish. The causes are rarely obvious: a…

A new mailbox starts life with zero sending reputation - ISPs have no signal to trust it, so they default to skepticism. The classic mistake is ramping up volume too fast: jumping…

Email authentication is not optional for anyone sending at scale in 2025. Google and Yahoo's bulk sender requirements made that official, but the underlying logic is older: SPF…

Email warmup is standard advice for cold email senders - but does it actually move the needle on inbox placement? We analyzed 50,000 warmed accounts across Gmail, Outlook, and…

We tested Lemwarm, Warmy, Mailreach, Folderly, Mailivery, and Instantly's warmup features head-to-head across pool size, inbox placement accuracy, pricing, and ease of setup.…

The real warmup timeline depends on your domain age, sending history, and ESP - not the generic '30 days' advice you see everywhere. Here's what to expect at every stage of…

Most guides treat mailbox warmup and domain warmup as the same thing. They're not - and confusing them is one of the most common (and costly) mistakes cold email senders make.…

Gmail, Outlook, and Yahoo spam filters have evolved far beyond simple keyword matching. Modern inbox providers use machine learning reputation models, sender behavior graphs, and…

Setting up SPF for Google Workspace takes under 10 minutes if you know the exact DNS record to add. This guide covers the precise TXT record value, where to add it for every major…

If your domain is registered or hosted with Namecheap, here's the exact process to add or update your SPF record - with screenshots of every step, the precise field values to…

GoDaddy's DNS manager has a confusing interface for TXT records. Here's the step-by-step process to add your SPF record correctly - with the exact field values for Google…

Hostinger manages DNS through hPanel's DNS Zone Editor, which uses different labels than a typical cPanel setup. Here's the exact path to add or fix your SPF TXT record, with…

Zoho Mail is one of the most common ESPs for startups and small teams - and one of the easiest to break SPF for once you add a second sending tool. Here's the correct record,…

Cloudflare's proxy toggle is the single biggest source of confusion when setting up email authentication. Here's the exact SPF TXT record to add, plus the MX record gotcha that…

Bluehost runs DNS through cPanel's Zone Editor and often pre-populates a default SPF record that conflicts with Google Workspace or Microsoft 365. Here's how to replace it…

Google Postmaster Tools is the only free window into how Gmail sees your sending domain. Most senders set it up once and never look at it again. Here's how to read each metric,…

A damaged sender reputation means most of your emails land in spam before a human ever sees them. Here's the systematic, evidence-based process to diagnose your reputation score,…

The average cold email reply rate across B2B campaigns is 3-5%. The top decile achieves 15-25%. The gap between average and top performers is not mystery - it's five specific,…

Spamhaus, Barracuda, SURBL, URIBL - getting listed on any major blacklist can tank your deliverability overnight and persist for weeks if you don't know the right delisting…

New domain, zero sending reputation, emails going straight to spam - it happens to almost every cold email sender. Email warmup is the solution. Here is what it is, why it works,…

Everyone wants a free email warmup tool. The honest answer: truly free tools for production use don't exist - but some free trials are much better than others. Here's the complete…

Google and Yahoo changed bulk sender requirements in February 2024, making SPF, DKIM, DMARC, and spam rate compliance mandatory. Here is exactly what the requirements are, which…

The exact SPF TXT record for Microsoft 365, step-by-step setup instructions for every major registrar, the most common mistakes that break SPF for M365 users, and how to verify…

Spam traps are email addresses that flag you to ISPs and blacklist operators the moment you send to them - silently, with no bounce or notification. One hit can tank inbox…

LemWarm is the original email warmup tool. We tested it for 30 days across multiple mailboxes. Here is what inbox placement it actually delivered, what pricing looks like at…

Warmy.io markets itself on having the largest warmup network. We ran a 30-day test to see whether that network advantage translates to actual inbox placement results - and whether…

MailReach is a well-regarded warmup tool known for quality over quantity. We ran a 30-day test across 5 domains to measure inbox placement outcomes, compare pricing, and see how…

Folderly is the most expensive email deliverability platform on the market. We ran a 30-day test to measure whether the premium price translates to better inbox placement results…

Everything you need to know about email deliverability in 2025. Authentication setup, warmup, list hygiene, sending patterns, reputation monitoring, content rules, and how to…

SPF is the DNS record that tells email providers which servers are allowed to send mail for your domain. Here's how it works, what the policy qualifiers mean, the 10-lookup limit…

Google Workspace, Microsoft 365, Zoho, or custom SMTP? We compare the major email providers on deliverability, sending limits, cost per mailbox, and warmup compatibility - with a…

Image-only emails, heavy HTML templates, URL shorteners, and 5+ links - these common template patterns are actively flagged by Gmail's spam filters. Here's which choices tank…

We tracked 500+ accounts that stopped email warmup mid-program or cold-turkey after reaching inbox placement targets. Here is exactly what happens to sender reputation, inbox…

A damaged email domain reputation causes every send to land in spam. This guide covers the exact diagnostic process, the right order of fixes, and the realistic timeline to fully…

Email deliverability determines whether your emails reach the inbox or disappear into spam. This guide covers all five pillars - authentication, sender reputation, list hygiene,…

Your sign-off is the last thing a prospect reads before deciding to reply, ignore, or delete - which makes it disproportionately important in cold outreach. This guide covers the…

Most cold emails are lost in the last two sentences: the pitch is fine, and then the ending asks a stranger for a 30-minute demo. How you end a cold email decides whether they…

Copy-paste out-of-office templates for every scenario - vacation, fully offline, short absence, extended leave, and travel. Plus the part most guides skip: how OOO auto-replies…

You hit send, then instantly spotted the typo or the wrong attachment. Both Gmail and Outlook let you claw a message back - but only within a narrow window, and the two systems…

Most replies to cold outreach do not come from the first email - they come from the follow-ups. This guide covers the timing (a 3-4 touch cadence spaced across roughly two weeks),…

A great cold email template earns a reply and looks like a personal message, not a mass blast. Here are 9 templates you can adapt - each short, plain-text, and built around a…

When emails stop arriving, it is rarely one obvious cause - it is usually a small setting, a full mailbox, or a filter quietly doing its job. This guide walks through the 9 most…

Emails landing in spam is the most expensive problem in email - your message can be perfect and still go completely unseen. The causes fall into four buckets: authentication,…

When Gmail blocks your emails, you usually find out the hard way - a bounce message with a cryptic 550-5.7.1 error, or a silent drop where your mail simply never arrives. Gmail is…

Every Gmail account has a hard daily ceiling, and hitting it mid-campaign locks your sending. A free @gmail.com account can reach 500 recipients a day; a paid Google Workspace…

Finding a prospect's email rarely needs a paid database. These 11 free, legitimate methods - working out the company pattern, checking LinkedIn, free email finder tools, targeted…

"Did they even open it?" has a few real answers - read receipts, tracking pixels, and link tracking - but none is fully reliable. Gmail read receipts are Workspace-only and can be…

Serious cold-email teams almost never send from their primary domain - they use a dedicated sending subdomain so a bounced campaign or a spam complaint never poisons the domain…

A bounce with 550 in it is one of the most common and most misunderstood errors in email. A 550 is a permanent failure - the receiving server has decided your message will not be…

"Please send this by COB Friday" - what does COB actually mean, and by when do you need to reply? COB stands for close of business, the end of the working day (around 5 PM in the…

How to properly warm up a Google Workspace email account before cold outreach. Step-by-step warmup settings, timelines, and inbox placement tips specific to Gmail Business…

Warming up a Microsoft 365 email account requires different settings than Gmail. This guide covers the exact warmup steps, sending limits, and authentication setup for Outlook…

The exact daily sending schedule for email warmup - week by week for new domains, aged domains, and accounts with damaged reputation. Backed by data from 50,000 warmed mailboxes.

A free, proven email warmup schedule template you can copy directly. Includes daily send volumes, ramp-up timelines, and milestones for new domains, new mailboxes, and reputation…

Comparing the best email warmup tools available in India - pricing in INR, support quality, network size, and which tools work best for Indian cold email senders and agencies.

A high spam complaint rate tanks your sender reputation permanently. Here are 7 specific, actionable fixes to bring your cold email spam rate below the 0.1% Google threshold.

Email bounce rate above 2% damages your sender reputation with every send. Learn what hard bounces and soft bounces mean, what rates are acceptable, and 6 proven ways to bring…

B2B cold email lives and dies on deliverability. This playbook covers domain setup, warmup, authentication, sending limits, and list hygiene - everything you need to hit the…

A dirty email list kills inbox placement. Learn how to identify invalid addresses, remove spam traps, suppress unengaged contacts, and verify emails before sending - with a…

55 sourced statistics on email deliverability, inbox placement rates, spam thresholds, SPF/DKIM/DMARC requirements, cold email benchmarks, and ROI - pulled from Saleshandy,…

LemWarm requires a Lemlist subscription and lacks inbox placement monitoring. These are the best LemWarm alternatives in 2026 - compared on price, features, trial, and warmup…

How to warm up 5, 10, 25, or 100 email inboxes simultaneously without triggering spam filters. The complete agency warmup playbook - infrastructure, scheduling, monitoring, and…

Gmail's AI-powered inbox categorization and spam filtering changed significantly in 2025-2026. Here's exactly how it affects cold email deliverability and what your warmup…

Is email warmup GDPR compliant? What data does warmup software process, what consent is required, and which warmup tools meet EU/UK data protection standards. Everything…

Recruiting agencies send thousands of outreach emails per week. Here is how to warm up recruiting email accounts, set the right ramp-up schedule for high-volume outreach, and hit…

An honest, data-driven review of MailPilot's email warmup and deliverability platform. We tested inbox placement rates, warmup speed, DNS diagnostics, pricing, and support across…

Indian B2B startups and cold email agencies need email warmup designed for their sending patterns, budget in INR, and the Bangalore-to-global outreach workflow. Here is the…

Most guides tell you how to warm up an email domain. Almost none tell you what to do once warmup finishes. Here's the full post-warmup maintenance playbook: how many warmup emails…

Agencies and sales teams running 20 or more cold email inboxes at once face a unique warmup challenge. Too fast and you trigger spam filters across all accounts at once. Here is…

Looking for an email warmup tool with a free trial in India? This guide compares the top warmup tools available to Indian B2B senders, with INR pricing, free plan limits, and…