Email timeout with Cloudflare SMTP.

### 👟 Reproduction steps # Sending a EMAIL through Cloudflare SMTP causes a timeout. ``` Failed sending to target admin@sitegardenr.com with error: SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/TroubleshootingSMTP server error: Called QUIT without being connected ``` A temporary fix as identified by Claude was the following but I don't have enough context about Appwrite's internals to understand why it's the way it is atm. https://chatgpt.com/c/6a9d383b-75f8-83ee-8abc-58b4b253e530 -- Copying from Claude -- ### Root cause --- confirmed by controlled experiment ----------------------------------------------- Appwrite's messaging worker sets its Swoole hook flags immediately before sending mail: ``` // src/Appwrite/Platform/Workers/Messaging.php:96 Runtime::setHookFlags(SWOOLE_HOOK_ALL ^ SWOOLE_HOOK_TCP); ``` They strip `HOOK_TCP` --- evidently they hit a related problem once --- but leave **`SWOOLE_HOOK_SSL`** enabled. On Swoole 5.1.7 + PHP 8.3.17 + OpenSSL 3.3.3, that hook breaks `ssl://` streams: the socket connects after a 30-second stall, then the first read returns EOF. PHPMailer reports that as `SMTP connect() failed`, and Appwrite records it as the message we've been staring at all day. I proved it by varying one flag at a time, in that exact container, against your real endpoint and credentials: | Hook flags | connect | Outcome | | --- | --- | --- | | `HOOK_ALL` | 30.03s | ❌ EHLO → EOF | | **`HOOK_ALL ^ HOOK_TCP`** ← what Appwrite does | 30.03s | ❌ EHLO → EOF | | `HOOK_ALL ^ HOOK_TLS` | 30.03s | ❌ EHLO → EOF | | `HOOK_ALL ^ HOOK_SSL` | **0.04s** | ✅ **AUTH true** | | `HOOK_TCP` only | 0.04s | ✅ AUTH true | | plain CLI (no coroutine) | 0.04s | ✅ AUTH true | That also explains every earlier dead end: it was never the network, DNS, IPv6, credentials, port, or encryption --- all of which we eliminated, correctly. Your `php -r` probe worked precisely *because* it ran outside Swoole. The fix --- one token, in two files -------------------------…