-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Http Server - SWOOLE_HOOK_TCP - stream_socket_enable_crypto() #4909
Comments
I run into the same issue, also with SES. I was wandering if it's related to the Swoole and some hook. The only difference for me is using task for sending. But the smtp log looks exactly the same. |
SMTP uses the startSSL feature to dynamically enable encryption. There may be some problems with swoole hook support here. I am working to fix it |
Running into the same issue 👍🏻 |
Due to a bug in the Swoole TCP hook, the worker crashes when doing the TLS handshake. This PR disables the Swoole TCP hook just like we do in the mails worker. References: * #7914 * #6966 * swoole/swoole-src#4909
Looking forward to this feature |
@matyhtf Hey, do you think there's a chance to get this fixed? I'm asking because I suddenly got task to do where I will need to send e-mail from within api. Up until now I've manage to mitigate this by sending e-mail from different env. Now it won't be possible. So I'd love to be able to send this without have to find some quirk workaround. ;) |
Hi there, Love the project. Ran into a bit of an issue and I'm stumped.
Thanks!!
Server Info:
The text was updated successfully, but these errors were encountered: