← Back to Complete Engineering Directory
RFC 8058 • Google & Yahoo 2026 Mandate

Free RFC 8058 One-Click List-Unsubscribe Header Generator & Bulk Sender Grader

By Fred Dawson • Updated for 2026 Google & Yahoo Bulk Sender Enforcement • 5 Min Tool

Generate the two headers Gmail and Yahoo require for bulk senders: List-Unsubscribe (https and mailto endpoints) and List-Unsubscribe-Post: One-Click. Copy the raw headers plus ready-made snippets for PowerMTA, KumoMTA and Postfix, and run the built-in 2026 bulk-sender checklist before your next campaign.

RFC 8058
Standard Specification
100% Native
Gmail & Yahoo Top Bar
< 48 Hours
Max Unsubscribe SLA
< 0.10%
Mandatory Spam Cap
RFC 8058 Wire Requirement:
The HTTPS endpoint must accept an HTTP POST with body List-Unsubscribe=One-Click and respond with HTTP 200 without requiring user login or confirmation.
PowerMTA Config (pmta.conf) 

        


        
        

          

            👁️ Gmail & Yahoo Native Inbox View Simulation
          

          

            

              
A

              

                
Acme Growth Team

                
<alex@outbound.acmecorp.com>

              

            

            

              Unsubscribe
              ✕
            

          

          

            ✓ Senders with valid RFC 8058 headers earn Gmail’s prominent top-bar unsubscribe button, reducing complaint spam button clicks by up to 74%.
          

        

      

    


    
    

      

        

          🛡️ 2026 Google & Yahoo Mandatory Bulk Sender Checklist
        

        
GRADE: A+ (100% COMPLIANT)

      

      

        

          
✅

          

            
RFC 8058 One-Click Header

            
List-Unsubscribe-Post: List-Unsubscribe=One-Click is injected on outbound mail streams.

          

        

        

          
✅

          

            
Dual-Method Fallback (HTTPS + Mailto)

            
Both RFC 2369 mailto: and HTTPS URLs are supplied in angle brackets.

          

        

        

          
✅

          

            
Zero-Friction POST Handler

            
Webhook accepts unauthenticated POST request and returns immediate HTTP 200 OK.

          

        

        

          
✅

          

            
DMARC Policy & Alignment

            
Domain has an active DMARC record (p=none, p=quarantine, or p=reject).

          

        

        

          
✅

          

            
Forward-Confirmed Reverse DNS (FCrDNS)

            
Sending IP PTR record matches the HELO/EHLO hostname with valid forward resolution.

          

        

        

          
✅

          

            
Spam Complaint Ratio Under 0.10%

            
Google Postmaster Tools spam rate stays strictly below 0.10% (never exceeding 0.30%).

          

        

      

    

  


  
  

    
1. What is RFC 8058 and Why Did Google & Yahoo Make It Mandatory?

    

      In February 2024, Google and Yahoo enacted strict bulk sender requirements for any organization sending more than 5,000 emails per day. In 2026, these rules apply universally across high-volume marketing broadcasts, product notifications, and scaled B2B cold outreach.
    

    

      Prior to RFC 8058, email clients relied solely on RFC 2369 mailto or web-link unsubscribe headers. Because many websites placed unsubscribes behind multi-step confirmation screens or password login walls, frustrated users routinely clicked the “Report Spam” button instead. Every spam report directly damages your sending IP and domain reputation in Google Postmaster Tools.
    

    

      RFC 8058 solves this by defining an automated, cryptographic, single-click unsubscribe standard. When Gmail or Yahoo detects valid headers, they render an unmistakable “Unsubscribe” action right beside the sender’s name at the very top of the inbox. When the recipient clicks it, the webmail client automatically executes an HTTP POST request behind the scenes, immediately removing the recipient without taking them away from their inbox.
    


    
2. RFC 8058 Wire Specification: The Two Mandatory Headers

    
To pass Google and Yahoo validation, your MTA or sending software must inject both of the following headers into the RFC 5322 message header stream:


    
List-Unsubscribe: <mailto:unsub@outbound.acmecorp.com?subject=unsubscribe>, <https://outbound.acmecorp.com/api/v1/unsub?id=recipient_token>
List-Unsubscribe-Post: List-Unsubscribe=One-Click


    
Header Rules & Formatting Requirements:

    
    
      
  • Enclosed in Angle Brackets: Both the mailto: and https:// URIs must be enclosed in < > brackets and separated by a comma.
    • 
      
  • Dual-Channel Redundancy: Supplying both mailto: and https:// guarantees backwards compatibility for legacy desktop email clients (like older Microsoft Outlook versions) while supporting modern webmail.
    • 
      
  • HTTPS Target POST Handling: The target server must respond to an HTTP POST request containing the body List-Unsubscribe=One-Click with an HTTP 200 OK status. It must NOT return an HTTP 302 redirect to a login screen or confirmation page.
    • 
    


    
3. Server-Level Configuration Snippets

    
PowerMTA (`/etc/pmta/config`)

    
In Port25 PowerMTA, configure RFC 8058 headers globally or per virtual MTA pool:

    
# Inject RFC 8058 One-Click Headers in PowerMTA
add-header List-Unsubscribe <mailto:unsub@outbound.acmecorp.com?subject=unsubscribe>, <https://outbound.acmecorp.com/api/v1/unsub?id=%%recipient_id%%>
add-header List-Unsubscribe-Post List-Unsubscribe=One-Click


    
KumoMTA (`policy.lua`)

    
In KumoMTA, use the smtp_server_message_received or send_mail Lua hook to insert headers:

    
kumo.on(‘smtp_server_message_received’, function(msg)
  msg:add_header(‘List-Unsubscribe’, ‘<mailto:unsub@outbound.acmecorp.com?subject=unsubscribe>, <https://outbound.acmecorp.com/api/v1/unsub?id={{lead.id}}>’)
  msg:add_header(‘List-Unsubscribe-Post’, ‘List-Unsubscribe=One-Click’)
end)

  


  
  
  
  

    

    

      

        
🛡️ Deliverability Engineering Sequence

        
The Enterprise Outbound & Authentication Playbook

        
Follow this 7-step engineering roadmap to configure cryptographic sender authentication, comply with 2026 bulk sender mandates, and eliminate shared relay penalties.

      

      

        
          ⚡ All 48 Free Tools
          →
        
      

    


    
    

        
          

            ✓ COMPLETE
            DNS Auth
          

          
SPF Audit

          
Sender Policy Framework

        
        
          

            ✓ COMPLETE
            Cryptographic
          

          
DKIM Signing

          
2048-Bit RSA Keys

        
        
          

            ✓ COMPLETE
            Policy
          

          
DMARC Alignment

          
Enforcement & Reports

        
        
          

             CURRENT
            Mandate
          

          
RFC 8058 Unsub

          
1-Click Header Builder

        
        
          

            STEP 05
            Hygiene
          

          
HTML & Link Sanitize

          
Strip Pixels & Hops

        
        
          

            STEP 06
            Scale
          

          
Mailbox Fleet Sizer

          
4-Week Ramp Schedule

        
        
          

            ★ $97/mo FLAT
            Zero Seat Tax
          

          
Dedicated MTA Fleet

          
$97/mo Flat Rate

        
    


    
    

      

        
🧼

        

          RECOMMENDED NEXT STEP
          
Step 5: Sanitize Outbound HTML & Unmask Redirect Links

          
Spam filters scan outbound HTML for hidden 1×1 tracking pixels, high image-to-text ratios, and multiple tracking redirect hops. Clean RFC 2046 MIME and transparent links prevent silent spam folder routing.

        

      

      
        Proceed to Step 5: HTML Sanitizer
        →
      
    


    
    
  

  


  

    
Enterprise MTA Infrastructure

    
The AutoSMTP Turnkey Solution

    

      Configuring RFC 8058 headers, managing feedback loops, rotating clean dedicated IPs, and tuning DKIM/DMARC policies manually across multiple servers is time-consuming and error-prone. AutoSMTP delivers turnkey, fully managed PowerMTA and KumoMTA clusters engineered for uncompromising deliverability.
    


    

      

        
Turnkey Dedicated Bare-Metal Clusters

        
Provisions fully licensed PowerMTA and KumoMTA clusters on enterprise bare-metal with flat predictable pricing and zero per-seat markup.

      

      

        
Automated Gas-Pedal IP Warming

        
Monitors Google Postmaster spam ratios (<0.10%) and real-time deferrals across clean IPv4 subnets with automated volume pacing.

      

      

        
Native FBL & Socket Interceptors

        
RFC 5321 in-band 550 bounce suppression plus automated Yahoo and Outlook CFL complaint ingestion and suppression syncing.

      

      

        
Fully Managed DNS & RFC 8058 Auth

        
Pre-configured forward and reverse DNS (rDNS/PTR), SPF, 2048-bit DKIM, strict DMARC, BIMI integration, and native 1-click unsubscribe headers.

      

    

  


  
  

    
Deploy Your Dedicated Email Infrastructure Today

    

      Eliminate the seat tax of Google Workspace and Microsoft 365. Scale to millions of monthly emails on high-reputation, private bare-metal MTA infrastructure.
    

    
      Explore Dedicated MTA Clusters
      →
    
  


  
  

    
Related Deliverability & Infrastructure Tools

    

      ← Free Tools Directory
      SPF Record Checker
      DMARC Record Checker
      Mailbox Ramp Planner
      Outbound ROI Calculator
      Email Spam Trigger Checker
    

  









Key capabilities


    

  • RFC 8058 one-click compliant
    • 

  • https + mailto endpoints validated
    • 

  • MTA-specific snippets
    • 

  • Google/Yahoo requirements checklist.
    • 



Frequently asked questions



What is one-click unsubscribe?

RFC 8058 lets Gmail and Yahoo render an unsubscribe button that POSTs to your https endpoint — the subscriber never sees an email or landing page. Both headers are required.





Do these headers replace a footer link?

No — they complement it. The header powers the inbox-level button; your footer remains the fallback.







Related tools