Future-Proof Your Inbox: Advanced Authentication & 2027 Predictions

Apsis Deliverability Blog Series — Part 3 of 3

The Best Deliverability Work Is the Work You Never See

Whilst marketers craft campaigns and customers engage with content, someone is working behind the scenes—monitoring delivery reports at dawn, opening tickets with ISPs when patterns shift, negotiating with Microsoft when filtering logic changes unexpectedly. This invisible work is what keeps emails flowing.

Welcome to Part 3 of our deliverability series. We've covered modern challenges and regional compliance. Now we're diving into the technical infrastructure that makes it all possible: advanced authentication protocols, crisis management strategies, and what's coming next in the world of email deliverability. 

A Day in the Life: Behind the Scenes with a Deliverability Specialist

06:30 — Morning Monitoring

The day begins before most people start work. Overnight delivery reports need checking:

• Scan bounce rates across all major ISPs for unusual patterns
• Check Google Postmaster Tools for reputation warnings
• Review Microsoft SNDS data for any IP reputation changes
• Monitor blacklist status across dozens of reputation databases
• Look for bounce code patterns that might indicate emerging ISP filtering changes 

Most mornings, everything looks normal. But occasionally, something stands out.  

A recent example: a spike in bounces caused by a failed DNS lookup that had been quietly affecting sends since April 9th. After investigation, the issue was traced to a problem with one of four DNS providers—Cloudflare—which was removed, resolving the problem immediately. These aren't always high-profile incidents, but catching them quickly is exactly what daily monitoring is for. 

09:00 — ISP Communication

Ongoing dialogues with ISP support teams:

• Follow up on open tickets from previous issues
• Respond to ISP queries about sending patterns
• Maintain relationships with deliverability contacts at major providers
• Monitor industry forums and postmaster announcement channels

When the Microsoft filtering issue emerged in early 2026, this is where resolution happened—not through automated systems, but through persistent human communication. And it's worth noting: the Microsoft situation isn't the only example. Issues of one kind or another arise every week. The difference is having the monitoring in place to catch them early. 

11:00 — Customer Support

Investigating delivery anomalies and advising on specific sending situations—though most direct customer contact is handled by the support team:

• "My emails aren't reaching Outlook—what's wrong?"
• My bounce rate has suddenly increased—what's causing it?"
• "How do I warm up a new sending domain properly?"
• "My open rates dropped suddenly—is something broken?" 

14:00 — Infrastructure Management

Ongoing technical work:

• Monitor IP and domain reputation status across infrastructure
• Review authentication configurations for recent customer setups
• Investigate reported delivery anomalies
• Update internal documentation on ISP policy changes 

Later in the Day — Strategic Work

Looking ahead:

• Track emerging authentication protocols and implementation timelines
• Review industry research on deliverability trends
• Plan infrastructure upgrades and capacity improvements
• Document lessons learned from recent issues

Perspective: "People sometimes ask why we need dedicated deliverability specialists when so much is automated.The answer is simple: when an ISP changes filtering logic in a way that affects legitimate senders, no automation can fix it. You need someone who can explain the situation, provide evidence, and push for resolution. That's not something you can automate—and it happens more often than most people realise." 

Advanced Authentication: Beyond SPF, DKIM, and DMARC

Basic authentication — SPF, DKIM, and DMARC — is the non-negotiable foundation in 2026. If you don't have these correctly configured, everything else is secondary. But there are additional protocols worth understanding.

What it is: BIMI allows your brand logo to appear next to your emails in supporting inbox providers, similar to how verified accounts get badges on social media.

Requirements:

• Valid DMARC policy set to quarantine or reject
• Verified Mark Certificate (VMC) from an authorised certificate authority
• Properly formatted SVG logo meeting BIMI specifications
• BIMI DNS record published in your domain

Why it matters:

• Visual trust signal: Your logo in the inbox increases recognition and open rates
• Brand protection: Makes phishing attempts using your brand more obvious
• Deliverability signal: Demonstrates commitment to authentication best practices

A honest view: BIMI is not a deliverability requirement, and the setup cost and ongoing certificate overhead is non-trivial. That said, many marketing teams find genuine value in the visual trust signal it provides. Whether it's right for your programme is a business decision more than a deliverability one. Current adoption: Gmail and Yahoo support BIMI. Outlook/Microsoft is evaluating.

A note on ARC: You may encounter references to ARC (Authenticated Received Chain) in deliverability literature. ARC operates on the receiving side and is not something senders need to configure or worry about. It's been removed from this guide to avoid confusion.

A note on MTA-STS and TLS-RPT: These protocols are similarly niche in practice and have been removed from this guide. They apply to specific infrastructure scenarios that are not relevant considerations for the vast majority of Apsis customers.

DMARC Monitoring — The Underrated Priority

If there's one thing that delivers more practical value than any advanced protocol, it's actively monitoring your DMARC reports. These reports show you exactly what's happening with your sending domain: whether authentication is passing, whether anyone is spoofing your domain, and where configuration issues are occurring. Setting up DMARC and never checking the reports is like installing a smoke detector and removing the battery. Make sure your policy is set to at minimum p=quarantine and that someone is regularly reviewing what comes in.

Infrastructure Optimisation: IP Warming and Reputation Management

Understanding IP Reputation

Every IP address used for sending email has a reputation score with each ISP, built on:

• Volume consistency: Sudden spikes trigger suspicion
• Bounce rates: High bounces indicate poor list quality
• Spam complaints: Even low rates (>0.1%) damage reputation
• Spam trap hits: Catastrophic for reputation
• Engagement patterns: How recipients interact with your emails
• Authentication compliance: Proper SPF/DKIM/DMARC setup

Apsis's IPs are already well-established. What matters most for your long-term deliverability is your sending domain's reputation—and this is what needs careful attention when starting fresh or returning after a long gap.

The principle is straightforward: start with your most engaged subscribers and increase volume incrementally, checking results at each step. If bounce rates or complaint rates rise, pause and investigate before continuing.

A practical approach: send to 1,000 recipients first. If results look healthy, try 10,000. Still good? Send to 100,000. Then scale to full volume. The right pace depends on your list and your domain's starting reputation—there's no one-size-fits-all schedule.

Advice: "The instinct to rush because of campaign deadlines is exactly what causes long-term damage. Patience in the first few weeks protects you for the following months and years." 

Domain Reputation vs. IP Reputation

Modern deliverability considers both:

1. Good IP + bad domain = deliverability problems
2. Bad IP + good domain = deliverability problems

Apsis manages IP reputation on your behalf. Your domain reputation is yours to maintain.

Domain reputation factors: historical sending behaviour, authentication consistency, website reputation, domain age, and brand trust signals. Protect it by using dedicated domains for transactional vs. marketing email, maintaining strict DMARC policies, and keeping sending practices consistent over time.

Crisis Management: When Deliverability Goes Wrong

Identifying Issues Quickly

Warning signs:

• Sudden bounce rate increases (5% warrants investigation; >10% is serious and may violate terms of service)
• Deferral spikes from specific ISPs
• Drop in delivered volume without sent volume changes
• Engagement metrics declining across the board
• Blacklist listings appearing
• Customer reports of non-delivery

Diagnostic Process

• Isolate the problem: Specific ISP? Certain domains? All traffic?
• Check authentication: Verify SPF/DKIM/DMARC still passing
• Review recent changes: New content? Different segments? Infrastructure updates?
• Check blacklists: Scan all major reputation databases
• Review ISP postmaster tools: Look for reputation warnings
• Analyse bounce codes: Specific error messages provide clues 

The Microsoft Crisis: A Template for Response

Phase 1 — Detection (Day 1–2): Noticed elevated bounce rates specifically to Microsoft domains. Confirmed pattern across multiple customers. Ruled out authentication or content issues. Identified as ISP-side filtering change.

Phase 2 — Communication (Day 2–5): Opened multiple support tickets. Provided detailed evidence of legitimate sending. Escalated through established contacts when initial responses were generic. Maintained pressure whilst remaining professional.

Phase 3 — Mitigation (Day 3–7): Advised customers to temporarily reduce Microsoft-bound volume. Focused remaining sendings on most engaged segments. Monitored situation closely for changes.

Phase 4 — Resolution (Day 7–10): Microsoft acknowledged filtering logic issue. Adjustments made to reduce false positives. Volume gradually restored as deliverability recovered.

Phase 5 — Documentation (Day 10+): Incident timeline documented. Internal procedures updated. Monitoring continued for recurring issues.

Reflection: "The Microsoft situation is a useful example, but it's one of many. Similar issues come up regularly. What the incident illustrates is the value of daily monitoring, established relationships, and the persistence to push through until a problem is actually resolved—not just acknowledged."

Blacklist Remediation

The blacklists actively monitoreded daily include: spamhaus.org, spamcop.net, barracudacentral.org, surriel.com, spamrats.com, abuseat.org, dronebl.org, and surbl.org.

Remediation process:

• Identify the listing: Which blacklist? Which IP or domain?
• Understand the reason: Each listing includes explanation
• Fix the underlying issue: Don't just request removal—address the cause
• Request delisting: Follow each blacklist's specific process
• Monitor for relisting: If the problem wasn't truly fixed, you'll be relisted

Common blacklist causes:

• Spam trap hits (pristine or recycled)
• High complaint rates
• Account compromises (rare, but worth monitoring for unusual sending behaviour)
• Malware or phishing content
• Association with known spammers 

FREE DOWNLOAD
 

The 2026 Deliverability Audit Checklist
 

This checklist is focused on what genuinely moves the needle. Items handled automatically by Apsis One, or not relevant to sender-side decisions, have been removed. 

Authentication

• SPF record published and valid
• DKIM signing enabled (configured as part of Apsis One onboarding)
• DMARC policy published (minimum p=quarantine recommended)
• DMARC reports being monitored regularly
• BIMI implemented (if applicable and appropriate for your programme)
• Custom link tracking domain configured 

List Quality and Hygiene

• Email validation at signup to catch typos
•  Double opt-in implemented
• Hard bounces removed promptly (not necessarily on first occurrence—occasional hard bounces can happen for temporary reasons)
• Soft bounces monitored and managed
• Inactive subscribers (6+ months) addressed
• Spam trap indicators reviewed
• List growth sources documented and legitimate
• Engagement trends monitored regularly
• Re-engagement campaigns active
• Sunset policies for unengaged subscribers
• Email validation at point of signup
• Consistent sending cadence maintained (protects against recycled spam trap hits) 

Reputation Monitoring

• Google Postmaster Tools configured and checked weekly
• Microsoft SNDS monitored
• Blacklist status checked regularly (Apsis monitors IP blacklists; domain reputation monitoring requires your own postmaster tool access)
• Bounce rate trends tracked
• Spam complaint rate below 0.1%
• Engagement metrics trending positively
• Domain reputation monitored separately from IP reputation 

Content and Sending Practices

• Clear unsubscribe link in every email (handled automatically by Apsis One) 
• Honest, accurate subject lines
• Reasonable image-to-text ratio
• Links use clear, branded domains — no URL shorteners
• Sending volume consistent with no sudden spikes
• Personalisation implemented where appropriate

Compliance

• GDPR compliance verified for European recipients
• CASL compliance for Canadian recipients
• CAN-SPAM compliance for US recipients
• Consent documented and defensible
• Privacy policy published and accessible
• Unsubscribe requests honoured promptly

Advanced Optimisation

• Segmentation strategy active
• Preference centre available to subscribers
• Re-engagement campaigns running
• Testing programme in place (subject lines, content, timing)

FREE DOWNLOAD

Usage note: "Don't try to fix everything at once. Prioritise authentication first, then list hygiene, then reputation monitoring. And remember—if you're using Apsis One, much of the technical groundwork is already in place. Understanding these elements helps you make better strategic decisions, even when you're not configuring them yourself. 

Looking Ahead: 2027 Predictions

AI-Powered Filtering Will Get More Prevalent

Current state: ISPs use machine learning to evaluate sender behaviour and content patterns. 2027 prediction: filtering AI becomes more widely deployed and more granular—real-time engagement prediction, natural language understanding detecting manipulation attempts, and collaborative filtering sharing signals within provider ecosystems. It may get worse before it gets better as adoption scales, but the direction of travel is clear.

What this means: Genuine engagement becomes even more critical. The gap between "technically correct" and "actually wanted" emails widens further.

Authentication Standards Will Continue Evolving

Likely developments: BIMI adoption expands. DMARC p=reject becomes the expected end-state rather than an advanced step. Post-quantum cryptography will eventually enter the authentication conversation as a long-term consideration.

Privacy Regulations Will Converge Globally

The fragmented regulatory landscape is slowly consolidating around GDPR-style principles. Organisations already following GDPR best practices will find global compliance increasingly straightforward. Those relying on lenient local regulations will face growing pressure to upgrade practices.

Engagement Quality Over Quantity Accelerates

List size becomes less relevant than engagement quality. Two-way communication — replies, not just clicks — will be weighted more heavily as a reputation signal. The era of spray-and-pray email marketing is genuinely ending.

Deliverability Expertise Becomes More Valuable

The paradox: as automation improves, human expertise becomes more critical, not less. Increased complexity requires deeper understanding. ISP relationships matter more as filtering sophistication grows. Crisis management can't be automated. Strategic decisions require human judgement.

A final thought: "The gap between organisations with proper deliverability support and those without it will become increasingly visible. The technical environment is too complex, and the consequences of getting it wrong too significant, to treat deliverability as a background concern."

The Bottom Line: Invisible Work, Visible Impact

We've covered a lot in this three-part series:

Part 1: Modern deliverability challenges, AI-powered filtering, the importance of expertise alongside technology

Part 2: Regional compliance, privacy regulations, list hygiene strategies

Part 3: Advanced authentication, infrastructure management, crisis response, future predictions

Throughout it all, one theme remains constant: the best deliverability work is the work you never see.

When Microsoft changed their filtering rules in early 2026, when a DNS misconfiguration quietly caused a spike in bounces, when a blacklist listing appeared overnight—most Apsis customers didn't notice any of it. Not because these problems aren't significant, but because someone was working behind the scenes to resolve them before they ever reached business operations.

That's what deliverability expertise looks like in 2026:

• Monitoring systems before most people start work
• Maintaining ISP relationships constantly, not just during crises
• Understanding not just what happened, but why it happened and how to fix it
• Possessing the persistence to push through ISP bureaucracy until problems are resolved
• Staying ahead of industry changes so customers don't face disruption

Email deliverability in 2026 requires both sophisticated technology and human expertise. Automation handles the routine; experts handle the exceptions. And in deliverability, exceptions happen regularly.

You're not just buying email marketing software—you're partnering with deliverability experts who ensure your emails reach their destination, every single day, often in ways you never see.

So here's my final shoutout to deliverability specialists everywhere, the people doing this work day in and day out: the early mornings checking overnight reports, the persistent ISP communication, the crisis management that prevents disruption before anyone else even notices there was a risk. Email marketing works because of that quiet effort in the background.

It's a strange kind of job satisfaction, knowing that success looks like nothing happening at all.

About Jesper Sörtoft

Jesper Sörtoft is Apsis's Deliverability Specialist, ensuring emails reach inboxes for customers across 40+ countries. When Microsoft unexpectedly changed filtering rules in early 2026, Jesper opened countless tickets, maintained constant dialogue with ISPs, and resolved the issue quietly—so Apsis customers never noticed the disruption. His dedication to maintaining ISP relationships, monitoring blacklists, and staying ahead of deliverability challenges keeps Apsis at the forefront of email marketing excellence.

END OF PART 3 — Apsis Deliverability Blog Series 2026

← Read from the start. Part 1