The task is to make a mailing all@broadcast… with one button/script I installed python 3.11 and all dependencies for twisted + pyOpenSSL. I used examples Twisted Words: A Minimal Working Example (in Python) and https://docs.twisted.org/en/stable/_downloads/6906149497eea462ef7622c7a22b5c09/xmpp_client.py but nothing works. Launching in the terminal, as indicated in the instructions, just hangs without outputting information. In OpenFire - user sessions - there is no session of the user I entered. I am using Openfire 4.6.4. Can you provide a good example? I really want to understand this. Tell me what is needed to solve this problem?
This is probably more a question for the Twisted developers than it is a question for the Openfire community, but a couple of things that I noticed:
- You’re not providing much relevant information other that “it’s not working”. I don’t think that anyone will be able to help you with your problem if you’re not providing more details.
- Openfire 4.6.4 is very old. I strongly recommend that you try with a newer version.
I run this sample (2 links) in the console I enter test.py dewz@test.hol.main Aa1234 after I run it and that’s it, the line works and nothing happens. Sorry for not providing enough information, tell me what to provide I’ll try to find. I’m just not strong in python, but I really want to figure it out.
Let me present you an alternative, on your terminal install go-sendxmpp with : go install salsa.debian.org/mdosch/go-sendxmpp@latest then via terminal you send your messages like this: go-sendxmpp -u dewz@test.hol.main -p Aa1234 -m /path/to/file/containing/the/message targetuser@test.hol.main
You can also create a file containing your credentials and using : -f /path/to/credentials/file
This way you dont need -u and -p.
Thanks for the feedback, I’ll definitely try your example! I’ll write to you soon!
I just remembered that, if you install the go-sendxmpp with the command above, you will still cannot call it system wide, the binary will end up at the same dir you did call it on go/bin/go-sendxmpp.
To then call it you can just cd to this location and ./go-sendxmpp another way is to just copy this binary to /usr/sbin/ (this way you can call it system wide.
hello! I tried your example, but I get the error 2025-09-10 15:35:27 connect: failed to connect to server: no viable authentication method available: [PLAIN]. Have you ever had such a thing?
Does your server have the proper TLS certificates? if not does your server at least have self signed certs? what you can try out of the bat is to also use this flag also --no-tls-verify not sure it will work, but i think this might still require at least a encrypted connection(with self signed certs).
PLAIN is one of the authentication mechanisms that is commonly used. I think this error means that your test client has detected that your server does not support that mechanism.
You can enable and disable mechanism in Openfire’s admin console. Go to Server > Server Settings > Registration & Login and look at the bottom of the page.
1 Like
Your example did not give a result, the error was repeated. there was a mistake like this before:
Originally, publication date: 2025-09-10 16:23:28 Connection: Failed to connect to the server: starttls handshake: tls: failed to verify certificate: x509: Certificate signed by an unknown authority.
I found a good example of correcting this error https://www.youtube.com/watch?v=lz41cEi9fhI but it didn’t help either. What am I missing?
Yes, I went there too. First connection to the server: failed to connect to the server: no effective authentication method available:
with --no-tls-verify your error Connection: Failed to connect to the server: starttls handshake: tls: failed to verify certificate: x509: Certificate signed by an unknown authority. should not pop up. can you show me how you are running the command?
this error occurred before your example. I sent the link to the video above, and did everything as in the example. After that, an error appeared, which I sent to you.
OK, Next good thing is, check if you really have valid certificates, and maybe show us your client to server configs so we can know which mechanisms is your server using. And logs if you can(Openfire side and Go-sendxmpp side). to get more logs out of go-sendxmpp you can add also these 2 flags : -d -v right after ./go-sendxmpp. e.g: ./go-sendxmpp -d -v ...
main.txt (5,6 КБ) here’s what happened!
OK, so maybe you edited this to your privacy, but i tried to ping test.hol.main and there is no records for it. maybe you connect to it with your other clients via IP? without the records the client will not be able to find your server.
I managed to figure out the problem. Here is the solution :go-sendxmpp -u dewz@test.hol.main -p Aa1234 -m C:\dewz\desktop\mess.txt --no-tls-verify –alow-plain targetuser@test.hol.main the bypass has passed)
As long as your organization is doing this is a closed environment it will be OK. otherwise if you are doing this over the internet, that is as insecure as it can get.
1 Like
Thank you so much for your answers !!!
1 Like