Python's email package, a Hebrew body: policy.SMTP writes short lines as raw 8-bit (Content-Transfer-Encoding: 8bit), and NFD Hebrew test text is the same string as NFC
Ray Postel · first seen 2026-10-13 on Python 3.14 from Homebrew (patch version not recorded), macOS on an Apple Silicon Mac; retested 2026-11-16 on Python 3.14.8 (Unicode 16.0.0) and on Apple's /usr/bin/python3 3.9.6 (Unicode 13.0.0), macOS 27.2, same results on both
The answer. With email.message.EmailMessage and policy.SMTP (and policy.default too), set_content() on Hebrew text whose lines all fit in 78 bytes picks Content-Transfer-Encoding: 8bit and writes the UTF-8 bytes raw. A long line makes it pick base64 instead, so a test with one long line passes for the wrong reason. policy.SMTP.clone(cte_type="7bit") made every body we tried come out as ASCII (base64). Separately: plain or pointed Hebrew is the same string in NFC and NFD, so a test "with NFD Hebrew" compares a string with itself. The limit: this is what set_content() chose for the bodies below on two Python versions; I haven't tried set_payload() or other charsets.
Python email: a display name given as an RFC 2047 encoded word containing "@" is written back decoded and unquoted, so the To header gains an address (gh-87720, fixed in 3.14.9)
Ray Postel · decoding seen 2026-11-15 on Python 3.14.8 (Homebrew), the lost quotes found on the retest; retested 2026-11-16 on Python 3.14.8 and Apple's /usr/bin/python3 3.9.6, macOS 27.2, same output on both; upstream fix read about, not run: CPython gh-87720, PR #134271, listed in the 3.14.9 changelog (released 2026-10-21)
The answer. On Python 3.14.8 and 3.9.6, a To value whose display name is an encoded word that decodes to an address, =?utf-8?q?boss=40good.example?= <[email protected]>, is serialized as To: [email protected] <[email protected]>. The encoding is gone and no quotes were added, so the name now reads as an address. Read back loosely, the header holds two recipients. This is CPython's gh-87720, "email: encoded headers lose their quoting when refolded", open since 2021 and closed on 2026-10-09 by PR #134271. The 3.14 changelog lists it under 3.14.9. The limit: I haven't run 3.14.9, and the fix's tests I could read use a comma, not an "@", so I haven't seen this exact case fixed.
Google Workspace "Activate Gmail" says MX "Incorrect" on GoDaddy DNS, though mail still arrives
Clio Follett · Google Workspace Admin setup page and GoDaddy's DNS editor, as seen on 2026-11-04 (versions not shown); DNS rechecked with dig on 2026-11-16
Answer. On 2026-11-04, Workspace marked a domain's MX records "Incorrect" and Activate Gmail asked for MX setup. The domain had Google's older set of four MX records (aspmx.l.google.com plus the alt hosts). They still delivered mail, but Workspace's check expected a single record, 1 smtp.google.com. We replaced the four with that one record and added Google's DKIM key as a TXT record at google._domainkey. Main limit: we saw the change take effect in DNS, but not the moment Workspace turned the mark green. The domain's owner pressed Activate on their side, and we didn't watch it.
email.utils.getaddresses(strict=False) vs strict=True on damaged To headers: in a seeded test, loose read a wrong well-formed address 7.7% of the time, a regex 6.1%, strict 0%
Ray Postel · first run 2026-11-15 on Python 3.14.8; rerun 2026-11-16 on Python 3.14.8 (Homebrew) and Apple's /usr/bin/python3 3.9.6, macOS 27.2, identical numbers on both; generated headers only, no real mail
The answer. On 1,850 generated To headers, each damaged once (a lost bracket, a stray parenthesis, a lost or doubled comma, a broken quote, junk at the end), email.utils.getaddresses([h], strict=False) returned a well-formed address the writer never meant in 7.7% of them, and a quick address regex in 6.1%. strict=True, the default on both Pythons we ran, did that 0% of the time. It refused 66% instead. The limit: the headers and their damage are mine, made by a script, so the rates describe that mix, not real mail. And the damage that caused nearly all the wrong reads, a ) inside an address, may be rare in real mail.