What changed
In a November 9, 2026 announcement, Mailgun said that from March 1, 2027 it will reject SMTP connections using TLS 1.0 or 1.1. Only SMTP senders negotiating TLS 1.2 or newer will continue to connect. HTTP API sending is unaffected. Mailgun says it monitors legacy TLS usage and will notify affected administrators by email and account dashboard banner.
Why it matters
Password resets, one-time login codes, receipts, order notices and alerts can silently fail at the sending boundary if an overlooked application, relay or plugin still negotiates obsolete TLS. A central Mailgun account may serve many independently configured systems; updating one application's library does not validate the others.
Scope and deadline
The March 1, 2027 cutoff concerns connections from senders to Mailgun's SMTP service. It is not a change to Mailgun's HTTP API or a claim that all email delivery to recipient domains requires TLS 1.2. The TLS version actually negotiated by each sending client matters.
Find every sender
Inventory production and staging applications, background jobs, CMS plugins, ecommerce integrations, scanners, CRMs, alerting systems and Postfix or other SMTP relays. Search for Mailgun SMTP credentials and smtp.mailgun.org configuration, including less frequently used disaster-recovery paths.
Test the negotiated protocol
Mailgun documents `openssl s_client -connect smtp.mailgun.org:587 -starttls smtp -tls1_2` as a direct TLS 1.2 handshake check. A successful probe shows the endpoint supports TLS 1.2; it does not alone prove an application's runtime uses that protocol. Test actual sends from each application's deployed environment and examine TLS negotiation and delivery logs.
Update old runtimes and libraries
Mailgun calls out older Windows Server, .NET Framework 4.5 and earlier, outdated OpenSSL and plugins that pin old protocol versions. Its guide gives minimum-version examples for Python smtplib, Nodemailer, .NET and Postfix. Apply settings appropriate to installed versions and retest both the SMTP handshake and message submission.
Limits of verification
The cutoff and migration instructions are documented by Mailgun itself. This dossier does not claim independent confirmation of live endpoint enforcement, which is scheduled for the future, nor quantify how many senders remain affected. A test from one workstation does not validate every relay or production client.