PowerMTA Yahoo Delivery Configuration — Domain Blocks, FBL Enrollment, and Yahoo Postmaster

Yahoo and AOL (now both under Yahoo Inc. infrastructure) represent a significant portion of consumer email traffic, particularly in the United States. Yahoo's filtering system differs from Gmail and Microsoft — it uses different rate limits, different error codes, and a separate Postmaster portal. This guide covers the complete PowerMTA configuration for Yahoo/AOL delivery.

Yahoo Domain Block Configuration

# Yahoo/AOL domain block configuration

    virtual-mta-pool    yahoo-pool
    max-smtp-out tuning        8           # Yahoo tolerates higher concurrency than Microsoft
    max-conn-rate       1/s         # Standard connection rate
    max-msg-rate        500/h       # Per-IP per-hour limit
    retry-after         15m         # Standard retry interval
    mx-rollup           yahoo.com
    dkim-sign domain="yourdomain.com" key-file="/etc/pmta/dkim/yourdomain.private" selector="s1"


# Yahoo subsidiary domains — roll up to yahoo.com reputation
          { mx-rollup yahoo.com }
        { mx-rollup yahoo.com }
        { mx-rollup yahoo.com }
           { mx-rollup yahoo.com }
           { mx-rollup yahoo.com }

# AOL domains (now Yahoo infrastructure)

    virtual-mta-pool    yahoo-pool  # Same pool — Yahoo infrastructure
    mx-rollup           yahoo.com

            { mx-rollup yahoo.com }
        { mx-rollup yahoo.com }

Yahoo SMTP Error Codes and Responses

Yahoo Postmaster Tools and Sender Hub

# Yahoo Sender Hub (successor to Yahoo Postmaster)
# https://senders.yahooinc.com/

# Key features available:
# - IP reputation lookup
# - Block reason lookup
# - Block removal request form
# - Sender complaint feedback form

# Yahoo Postmaster key indicators:
# - Complaint rate: percentage of recipients marking as spam
# - Hard bounces: volume of invalid addresses
# - Email volume: messages per day reaching Yahoo servers

# IP Reputation Status Indicators:
# Sending traffic is being accepted normally
# Some traffic being deferred temporarily
# Traffic experiencing delivery issues
# Traffic being blocked

# To request IP block removal:
# https://senders.yahooinc.com/
# → Sender Inquiry → IP Block Removal
# Provide: IP address, description of sending practices, opt-in process

Yahoo FBL Enrollment and Complaint Processing

# Yahoo FBL (feedback loop configuration) Program
# Enrollment: https://postmaster.yahooinc.com/fbl/

# Yahoo FBL characteristics:
# - Provides per-message complaint reports (ARF format)
# - Recipient address is REDACTED (unlike Microsoft JMRP)
# - Reports delivered to registered complaint mailbox
# - Volume: 1 report per recipient complaint

# Processing Yahoo FBL:
# 1. FBL report arrives at fbl@yourdomain.com
# 2. Parse Original-Message-Id from ARF report
# 3. Look up message in PowerMTA accounting log format by Message-ID
# 4. Extract recipient from accounting log rcpt field
# 5. Add to suppression list

# Required PowerMTA accounting log retention: 30+ days
# (Yahoo FBL reports can arrive 24-48h after sending)

# Yahoo FBL report parsing (Python example)
import email, re

def parse_yahoo_fbl(raw_message):
    msg = email.message_from_bytes(raw_message)
    for part in msg.walk():
        if 'feedback-report' in part.get_content_type():
            content = part.get_payload(decode=True).decode()
            msg_id = re.search(r'Original-Message-Id:\s*(.+)', content)
            if msg_id:
                return msg_id.group(1).strip()
    return None

Frequently Asked Questions

Yahoo FBL and Postmaster Integration

Yahoo's Complaint Feedback Loop provides individual ARF reports for each Yahoo/AOL user who marks your message as spam. Enrollment at senders.yahooinc.com requires a verified sending domain. Process FBL reports in real time: each report contains Message-ID headers that allow recipient identification and immediate suppression. Yahoo's throttle codes (TSS04, TS03) in dsnDiag indicate temporary deferral — standard retry resolves these. More specific codes (CS04, BL23) indicate reputation issues requiring investigation before resuming normal sending volume.

Accounting Log Analysis for This Configuration

Monitor this configuration area through the PowerMTA accounting log's dsnDiag field. Filter accounting records for the specific ISP domains affected by this configuration and group dsnDiag responses by first 60 characters to identify the dominant error patterns. A deferral rate above 5% at any single ISP warrants investigation; above 15% requires immediate volume reduction and configuration review.

The dlvSourceIp field in the accounting log enables per-IP analysis within this configuration context. Comparing per-IP deferral rates identifies whether a configuration issue affects all IPs in a pool uniformly (configuration problem) or just specific IPs (reputation or IP-specific problem). This distinction determines the correct remediation path.

Calibrating to Your Current Environment

The parameter values documented in this reference are appropriate for established, warmed IPs with HIGH reputation at the target ISP. New or warming IPs, and IPs with MEDIUM or LOW reputation, require more conservative values. Move up incrementally as reputation signals confirm the infrastructure can sustain additional throughput. Review ISP-specific configuration monthly — Postmaster Tools reputation tier changes and SNDS status changes are the primary triggers.