2011 to 2017: sequencers turn follow-up into a system, Gmail starts grading the sender
Sequencers made follow-up a system from 2011 to 2017, and Gmail began grading senders by their history. Since then, a domain's past shapes where its mail lands.
Key takeaways
- Outreach (2014), Apollo (2015) and Woodpecker (2015) made the sequence standard: timed, templated follow-up steps that one rep could run for hundreds of people at once.
- In July 2015 Gmail added an artificial neural network to its spam filter, made filtering reflect each person's preferences, and launched Postmaster Tools to show senders their reputation.
- The current versions of the standards senders must publish today date from this era: DKIM (RFC 6376, 2011), SPF (RFC 7208, 2014), DMARC (RFC 7489, 2015) and one-click unsubscribe (RFC 8058, 2017).
- From here on, reputation belongs to the sending domain and follows it from campaign to campaign, so what the domain did last month shapes where today's email lands.
Between 2011 and 2017 sales engagement software turned follow-up into a system: write the steps once, enroll a list, and the software sends step two to everyone who did not answer step one. In the same years Gmail began grading senders by their history and by what each recipient did with their mail, so from this era on, what your domain did last month shapes where today's email lands. This part covers both halves, and why the current versions of the authentication standards you are now required to publish all date from this window.
What did a sequencer change about cold email?
Before sequencers, a follow-up was a rep remembering to write one. Outreach started in 2014, when a struggling Seattle recruiting startup turned the tool it had built for its own prospecting into a product. Apollo was founded in 2015 and went through Y Combinator the following winter. Woodpecker was created in 2015. Together with Reply, they sold versions of one idea: the sequence. A sequence is a set of timed steps, each one an email template with merge fields, sent until the person replies, opts out or reaches the end.
For a sales team the gain was real. Follow-up stopped depending on memory. A manager could see every step, test two versions of step one against each other, and hand a new rep a working sequence on day one. One rep could keep hundreds of people in motion at the same time.
For the inbox, the same feature looked different. Picture Dana Reyes, head of sales at Northwind, on a Tuesday morning in 2016. Four vendors' sequences reach step three that day. Each one is "bumping this to the top of your inbox." Each one was written once and sent to thousands of people. A message repeated at that scale is exactly what a learning filter is built to notice.
- Part 12001 to 2010Sending technologyCommercial email infrastructureSelf-serviceSend APIsBulk listsMailbox defenseRule-based spam filteringRulesBlocklistsContent scoring
- Part 22011 to 2017Sending technologySequencing turns follow-up into a systemSequencesSales engagementFollow-upMailbox defenseAdaptive filtering and sender reputationReputationEngagementAdaptive filters
- Part 32018 to 2021Sending technologyData connects to executionEnrichmentCRM syncSignalsMailbox defenseIdentity becomes a stronger signalDomain identityAlignmentFeedback
- Part 42021 to 2023Sending technologyMulti-mailbox scale meets generative draftingMailbox rotationWarmupAI draftingMailbox defensePattern recognition learns fasterBehaviorInfrastructureFeedback loops
- Part 5Feb 2024 to 2025Sending technologyMore throughput, more identity fragmentationOrchestrationAI researchMore capacityMailbox defense · formal enforcementAuthentication becomes a hard gateSPF · DKIM · DMARCOne-click opt-outSpam < 0.3%
- Part 62026 to 2027Sender capabilityResearch and drafting become nearly freeAgent researchDynamic variantsReply routingInbox prioritizationVisibility becomes the next gateRelationship contextMessage contextPriority visibility
How did Gmail start grading the sender?
In May 2013 Gmail introduced the tabbed inbox, which sorted mail into categories and put deals and offers in a tab of their own. A large provider was now deciding, on the reader's behalf, which commercial mail deserved the first screen.
In July 2015 Google described the next step, and it changed what a sender is up against.
For starters, the spam filter now uses an artificial neural network.
The same post said filtering would now reflect individual preferences: one person's welcome newsletter is another person's junk. Every click on "Report spam" or "Not spam" trains the filter for the future. And it launched Postmaster Tools, which gives high-volume senders data on delivery errors, spam reports and reputation. Google also put numbers on where it stood: less than 0.1% of the email in the average Gmail inbox was spam, and wanted mail landing in the spam folder was under 0.05%.
Read those three changes together. The filter learns from what each recipient does. Placement can differ from one reader to the next. And the provider now keeps a record on the sender and shows it to them. From 2015 the question was no longer only "is this message spam?" It was also "what has this sender done before?"
Were SPF, DKIM and DMARC around in this era?
Yes. The current versions of the standards that Gmail and Yahoo now require from bulk senders were all published in these years, and every one of them was optional at the time.
| Standard | Specification | What it proves |
|---|---|---|
| DKIM | RFC 6376, September 2011 | The message was signed by the sending domain and not altered on the way |
| SPF | RFC 7208, April 2014 | The server that sent the mail is authorized by the domain |
| DMARC | RFC 7489, March 2015 (replaced by RFC 9989 in May 2026) | The visible From: domain lines up with SPF or DKIM, and what a receiver should do when it does not |
| One-click unsubscribe | RFC 8058, January 2017 | The recipient can opt out with one click from the mail client |
A sequencer could send without any of it, and many senders skipped it. Nine years after DMARC was published, the same standards became the entry requirement for anyone sending at volume to Gmail and Yahoo users. Part 5 covers how that happened and what it means for a small team.
What era two means for a head of sales in 2026
- Reputation belongs to the domain, not the campaign. A sequence you switched off last quarter is still in the record the provider keeps. A new campaign inherits it.
- A follow-up is a new decision. Step three to someone who ignored steps one and two adds to the history the filter reads, and so does every spam report it earns. Send it because something changed, not because day nine arrived. Part 11 covers how to learn the follow-up rhythm per audience instead of copying a default.
- Placement is personal. Since 2015 the same email can land in Dana's inbox and her colleague's spam folder. An open rate is an average of many private decisions, which is one reason it is a weak measure.
- When replies drop, look at the sender first. The reputation layer sits underneath the message, so the diagnostic runbook in part 12 starts with sender and domain health before anyone rewrites copy.
A note on what anyone outside a mailbox provider can know. Google publishes which signals it measures and which dashboards senders can see. It does not publish how its models weigh them. Everything this series says about filters is built from what the providers have said in public, not from guesses about their internals.
Next in the series
Part 3 picks up in 2018, when enrichment and contact data plugged straight into the sequencer, and mailbox providers answered by leaning on identity: domain, IP, authentication and recipient feedback, read together. Part 1, on how sending at scale began, sets up the pattern. The series page lists every part in order.
Common questions
- What is sender reputation in email?
- Sender reputation is a mailbox provider's running assessment of a sending domain and its IP addresses, built from their history: authentication results, spam reports, delivery errors and how recipients treat the mail. Google's Postmaster Tools shows senders a domain reputation and an IP reputation rating among its dashboards. It follows the domain from campaign to campaign, which is why a domain that was burned last year still affects today's sends.
- Are email sequences bad for deliverability?
- Not by themselves. A sequence is a schedule. The damage comes from sending the same template at volume to people who ignore it, which adds spam reports and poor engagement to the domain's record. A follow-up that carries a new reason, sent to a list that fits, reads differently to both the filter and the person than step three of a template sent on day nine.
- When did SPF, DKIM and DMARC become standards?
- The versions in force today were published as DKIM in RFC 6376 (September 2011), SPF in RFC 7208 (April 2014) and DMARC in RFC 7489 (March 2015), which RFC 9989 replaced in May 2026. One-click unsubscribe followed in RFC 8058 (January 2017). All were optional until Gmail and Yahoo made them requirements for bulk senders in February 2024.
Sources
- Forbes, Inside Outreach: The Hard-Charging Cloud Startup Thriving In Salesforce's Shadow, February 20, 2020 (Outreach's 2014 start)
- Y Combinator, Apollo.io company page (founded 2015, Winter 2016 batch)
- Woodpecker, Woodpecker debuts on NewConnect (created in 2015)
- Gmail blog, the new tabbed inbox, May 29, 2013
- Gmail blog, The mail you want, not the spam you don't, July 9, 2015
- Google, Postmaster Tools dashboards
- IETF, RFC 6376: DomainKeys Identified Mail (DKIM) Signatures, September 2011
- IETF, RFC 7208: Sender Policy Framework (SPF), April 2014
- IETF, RFC 7489: DMARC, March 2015, replaced by RFC 9989 in May 2026
- IETF, RFC 8058: Signaling One-Click Functionality for List Email Headers, January 2017
Written by Jared Hawkins-Young from the system he builds and runs. Diagrams are drawn from the same specs as the software. Published October 8, 2026. Illustrative numbers are labelled as such; every other figure carries its source.