Closed mxsasha closed 6 months ago
Hello! Thanks for the PR 😀. Before I look into it, do you know of an SMTP server on the Internet that I could connect to to try these changes ? You can email it to me if you have one. Thanks!
Not any that I'm aware of, though any SMTP server that accepted the old EHLO, which was not attached to the hostname, should accept a different one.
https://tcpbin.com/ has some support but would break the actual test, or https://github.com/rcx/tcpbin but the public instance of that has died.
Not sure why this one was closed? Is the feature or patch rejected?
Not sure either as I don't recall making the decision to close this without any comment or reply.
Maybe it was closed automatically because I deleted the target branch (as this PR didn't make the cut for the v6.0.0 release, which is what the branch was about)?
Some servers require that the SMTP EHLO hostname matches the reverse of the connecting client. This change allows Python clients to do that.
Did consider whether this was better placed in
ScanCommandsExtraArguments
, but I kept it simple and followed the flow ofxmpp_to
.Also all includes s small doc fix: tls_wrapped_protocol->tls_opportunistic_encryption.