Non-ASCII display names in mail headers are not MIME encoded
accepted as reported, fix in three separate locations (contained in Aug 10 2026 release).
Email validation incorrectly requires recipient domain to respond on port 80
confirmed, fix as reported (contained in Aug 10 2026 release).
function MbEncode() returns UTF-8 strings unencoded
Confirmed bug, but fix is at the correct architectural point rather than applying the supplied patch verbatim. The intended behavior should be: Plain ASCII subject → returned unchanged. UTF-8/non-ASCII subject → RFC 2047 encoded. MbEncode() returns only the encoded subject value, not Subject: .... Avoid encoding the same subject twice. Preserve proper CRLF folding. The existing call sites show that MbEncode() is used for both custom-header values and the Subject, so we should keep its contract as...
Missing .= in GetContentTypeBody()
not confirmed, not an issue.