Allow use of XMPP StartTLS where XMPP server name is different from hostname

📑 I have found these related issues/pull requests I originally created and debugged this issue: Could be relevant for this issue: 🔖 Feature description A common XMPP server configuration is to use SRV records like this: This means that my xmpp server is at example.com, but to use port 5269 and to connect to the hostname xmpp.example.com (and to use StartTLS). For Uptime Kuma, I set up a monitor with the hostname xmpp.example.com and this works for direct TLS but not for StartTLS, as the hostname is passed in the StartTLS message [here]( and then the XMPP server responds with an error: To support my use-case, I just need a way to have Uptime Kuma pass in the proper name for the XMPP server there (example.com). ✔️ Solution I can see a couple ways to support this: 1. Explicitly support SRV records, so that the proper server name can be be passed in the StartTLS message. 2. When StartTLS is configured in the TCP Monitor, have a configuration option for the server name. 3. Have…