What changed
Starting September 8, 2026, Gmail’s Verified Sender Program is available to eligible U.S. political committees. Candidate committees, parties, PACs and other qualifying 527 organizations registered with the FEC or a State, Local or Tribal Election Authority can enroll after verifying their sending domain through Campaign Verify and associating it with a verified Postmaster Tools account. Participating domains must comply with Gmail sender requirements, use SPF and DKIM, maintain a rolling 14-day user-reported spam rate below 0.3% and meet other program rules. Google says the program is intended to help verified, policy-compliant and non-abusive political mail reach personal Gmail accounts more reliably on an ongoing basis.
Why it matters
Large-volume email delivery depends on more than successful SMTP acceptance: mailbox providers apply reputation, authentication and user-engagement signals that can materially affect inbox placement. Gmail has now created a sender-class-specific program that ties identity verification, technical authentication and recipient-reported spam directly to continued participation. For email platforms and campaign operations teams, the important mechanics are reusable beyond politics: identity, domain reputation, SPF/DKIM, Postmaster telemetry, consistent sending history and user complaints all remain part of the delivery control plane. The program is narrow—U.S. political committees only—and should not be generalized into a new deliverability path for ordinary commercial senders.
Eligibility starts with verified political identity and domain ownership
The program is open to qualifying U.S. candidate committees, political parties, PACs and other political committees that are 527 tax-exempt organizations and registered with the FEC or an eligible State, Local or Tribal Election Authority. The committee must verify its sending domain through Campaign Verify, use a domain that hosts or redirects to a public committee website, and maintain a verified Postmaster Tools account.
A rolling 0.3% spam threshold becomes an explicit program gate
Google requires the average user-reported spam rate over the previous 14 days to remain below 0.3% for enrollment and continued participation. Pre-enrollment traffic counts in that rolling window. Spam reports from subdomains also roll up to the enrolled primary domain, making domain-wide list quality and segmentation part of the operational boundary.
Authentication and sender requirements still apply
Participating domains must configure SPF and DKIM and comply with Gmail’s normal sender requirements and anti-abuse policies. Google also recommends avoiding shared sending infrastructure because another sender on the same IP can create classification and delivery problems even though shared IP use does not automatically make a committee ineligible.
The program improves the delivery path; it does not override user choice
Google explicitly says Gmail users retain normal controls to mark mail as spam, block a sender and unsubscribe. Enrollment establishes sender authenticity and a specialized delivery program, but Google says deliverability still depends on ongoing policy compliance and positive recipient engagement.
Violations can return the sender to ordinary spam filtering
Program violations can trigger a seven-day suspension or permanent termination. A suspended or terminated domain can still send to Gmail recipients, but its messages return to Gmail’s standard filtering. Compliance and enrollment status are visible through Postmaster Tools, giving senders a concrete operational dashboard for the program.