In the Termux app on Android I get a text file with all the SMSs like this: termux-sms-list >sms.txt And I need to send its content over xmpp automatically by script. The available command is xmppc, but it doesn't seem to support file uploads. I tried these ways and it didn't work: xmppc -j usersender@domain.tld -p "UserPassword" -m message chat userreceiver@domain.tld $(cat sms.txt) cat sms.txt | xmppc -j usersender@domain.tld -p "UserPassword" -m message chat userreceiver@domain.tld - Any idea?

I am trying to login with Dino XMPP client with user credentials at an XMPP domain which is hosted at conversations.im. Thus, there is no XMPP server at the domain. Instead, respective SRV records are pointing to xmpps-hosting or xmpp-hosting at conversations.im. Conversations XMPP client verifies the certificate for connection by PKIX over Secure HTTP (POSH), RFC 7711, which I configured, but Dino doesn't support it yet ([#451](https://github.com/dino/dino/issues/451)) . Thus, it fails connection at a self-signed certificate: > By default our server will create a self-signed certificate. On first connect you will be asked to verify the certificate manually. You can do this by comparing the certificate’s SHA-256 fingerprint that you are prompted with, with the fingerprint below. >

> 7e:9f:aa:ca:cb:2e:21:96:8d:85:8d:68:ef:04:ee:c6
> 0f:f7:78:44:12:ee:74:4b:a0:31:f8:10:96:03:72:b9
>

Dino doesn't support manual verification of the certificate ([#57](https://github.com/dino/dino/issues/57) , [#452](https://github.com/dino/dino/issues/452)) . So, it cycles and then rejects connection when trying to add the account. It wouldn't be a problem if only I could get that certificate and then add it to the system trust store. However, I could not find a way to download the certificate. I tried an approach similar to [a Serverfault answer](https://serverfault.com/a/1074374/583863) , but couldn't get a certificate:

$ nslookup -type=SRV _xmpps-client._tcp.riabenko.com
Server:		127.0.0.53
Address:	127.0.0.53#53

Non-authoritative answer:
_xmpps-client._tcp.riabenko.com	service = 1 1 443 xmpps-hosting.conversations.im.

Authoritative answers can be found from:

$ openssl s_client -starttls xmpp -xmpphost riabenko.com -connect xmpps-hosting.conversations.im:443 -debug
CONNECTED(00000003)
write to 0x55db90fcebd0 [0x7fffa67799a0] (117 bytes => 117 (0x75))
0000 - 3c 73 74 72 65 61 6d 3a-73 74 72 65 61 6d 20 78   
read from 0x55db90fcebd0 [0x55db90f90020] (8192 bytes => 0)
read from 0x55db90fcebd0 [0x55db90f90020] (8192 bytes => 0)
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 117 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---
read from 0x55db90fcebd0 [0x55db90f8e010] (8192 bytes => 0)

How can I get the certificate from the server?

I'm using *pidgin* Jabber client ([pidgin-2.13.0-alt6](https://packages.altlinux.org/en/sisyphus/srpms/pidgin) on ALT Sisyphus), and I'd like [to set XMPP priority](https://superuser.com/a/1137749/65570) in pidgin. The reason: I'm also connecting to my Jabber account with another client from mobile smartphone (*aTalk*), and I'd like to set XMPP priority in pidgin, so that whenever I'm at my computer (where pidgin is running), it is [selected as the one which receives the messages](https://unix.stackexchange.com/q/163698/4319) people send to me, and whenever I'm away, the mobile client receives them (because there is more chance I'll see them on the mobile when I'm away). Where do I set XMPP priority in pidgin?

I use a jabberd2 MUC to monitor server status from Graylog and Nagios. The helpdesk guys would like to be able to join the MUC, however they are on Windows (I'm on Linux) and have a Cisco jabber client of some kind that doesn't appear to be configurable enough to point it at a second XMPP server. Is there any way to maybe "forward" messages from the Linux XMPP server to the Cisco XMPP server? **Update** (added SRV records): _jabber._tcp.jabber.my.lan.net. IN SRV 5 0 5269 jabber.my.lan.net. _xmpp-server._tcp.jabber.my.lan.net. IN SRV 5 0 5269 jabber.my.lan.net. _xmpp-client._tcp.jabber.my.lan.net. IN SRV 5 0 5222 jabber.my.lan.net. _jabber._tcp.conference.my.lan.net. IN SRV 5 0 5269 jabber.my.lan.net. _xmpp-server._tcp.conference.my.lan.net. IN SRV 5 0 5269 jabber.my.lan.net. _xmpp-client._tcp.conference.my.lan.net. IN SRV 5 0 5222 jabber.my.lan.net.

As seen in many tutorials and blogs, I've installed the EPEL (Extra Packages for Enterprise Linux). I checked whether EPEL was enabled in my CentOS 6. After I tried with the command sudo yum install ejabberd No Package ejabberd available Error: nothing to do. This is what happens every time I try to install it. I tried downloading the package directly by using a Lynx browser and tried to run using the command rpm -Uvh ejabberd-16.09-0.x86_64.rpm.gz It still says: It is not an rpm package I am using CentOS 6 from a VPS at GoDaddy.

I have a dedicated server (Inmotion) running a **Java XMPP server** through a screen session to keep it alive. Sometimes, after a long period, the execution of this Java XMPP server freeze and then when I connect to the SSH and reattach the screen session to see what is wrong, the execution defreeze itself and execute everything pending (send pending messages, queries to the DB, etc.) and it goes back to normal operation. Note that I do nothing, I just connect to the SSH and reattach the screen session to read the output. The period for this to happen is variable, sometimes hours, sometimes days later. **What can I do to avoid this behavior?**

I'm running an XMPP server on a raspberry pi on my home lan. I have a domain registered to point at my router's external ip and the ports are forwarded on my router. However, I can't use the external domain/ip when connected to my LAN, only when out and about. What's the easier way to configure my computers at home to recognize whether the server is local (and point to 192.168.x.x) or remote?

I've got a few friends to install XMPP clients on their cell phones. Some installed Xabber (which I basically chose for them to try). Another opted for Yaxim, a few days ago (for its "better appearance") after - for an unrelated problem - resetting his device totally and losing many things, including the installed programs, which included Xabber. But there seems to be too many limitations that I did not expect for these clients, compared with everything I do, using a computer, with anyone else in most XMPP clients. I can't send files to them while we're chatting, as I would do normally if they were using any XMPP client on a PC. And it seems that xabber does not have it all (and not much documentation either, so I could check); Yaxim neither. whatsapp is bad because it only works with a phone number - which I surely don't want or need to give for most people, but its popularity is unquestionable, so I'm barely alone with that idea within some groups of people. Is there a XMPP client that would support all things (or, at least, most) that people expect from a mobile client? Easily sending pictures or other "things" that mobiles usually have accessible within other programs, but without limiting it to a specific protocol. And all things that we can do with XMPP on a computer, like: sending/receiving files/pictures/whatever; personalized emoticons; sound messages; VOIP (although I never tried it with XMPP). I even imagine it using any open and free cloud file service to easily send a big file (like a video) to several users without waiting more than ~1 time for uploading or downloading this file (downloading to see and, resend to others after that). Yaxim seems freezed since 2013. That seems too long ago for anyone else?! Xabber seems better, but still limited. It is mentioned as "the best", in some software review sites I have read. Are there any better clients for XMPP? Which features does it have, and what is bad about it? Does anyone else miss this?

I installed openfire in CentOS 6.4 server (IP address: 192.168.1.118) and I was able to login into spark using the server as 192.168.1.118. We want to use spark from outside, so I did port forwarding in my dlink router with 192.168.1.118 and 9090 (default port of openfire). Even allowed it as public. We have a public static IP, for example xxx.x.xx.xx and if I give this public IP as server in Spark I am unable to login. But if type xxx.x.xx.xx:9090 in browser I can get the openfire admin page. Why am I unable to connect to Spark client even after port forwarding? It is not working in Windows even.

After validating of my public XMPP service on xmpp.net, I've got the error: Warning: Server offers no forward-secret ciphers. Grade capped to A-. Is there an easy way to enable these ciphers? As title states, I have Debian Stable and ejabberd installed from its repository. **ADDITION** I've checked all the servers listed in https://xmpp.net/directory.php which have ejabberd installed with its build date 2011/12/24. This is Debian Wheezy's ejabberd obviously. The top score of any of these servers is A-/A-, so I believe it is really difficult to enable PFS for this software.

I have jabber clients on my computer (pidgin) and on mobile phones (im+). For now each message is received by arbitrary one of them (or so it looks). For instance, if a person sends two messages one after another, one can get into one client, the second one into another. What makes a message being received by some particular client? Is there a way to make one particular client receive the messages? All the clients?