SENDXMPP(1p)

πŸ“¦
version 1.24 Β· 3 versions
, in debian trixie, ubuntu noble, ubuntu questing

πŸ‘‘ SENDXMPP(1p) β€” like, the perl user-contributed docs edition πŸ’…

okay bestie, gather round, because this is sendxmpp and she is iconic. This page lives in the User Contributed Perl Documentation section of your manual, and it's about yeeting XMPP (Jabber) messages straight from your terminal like the main character you are. πŸ¦‹


✨ NAME ✨

sendxmpp β€” send xmpp messages from the commandline.

🌸 SYNOPSIS 🌸

sendxmpp [options] <recipient1> [<recipient2> ...]

sendxmpp --raw [options]

πŸ’– DESCRIPTION πŸ’–

So, sendxmpp is a program that sends XMPP (Jabber) messages from the commandline, and honestly it's giving very much mail(1) energy. You can slide into individual people's DMs and you can drop messages into chatrooms. Both. She does both. πŸ’…

πŸŽ€ OPTIONS πŸŽ€

  • -f, --file file β€” use file as the config file instead of the usual ~/.sendxmpprc.
  • -u, --username user β€” use user instead of whatever username is sitting in the config file.
  • -p, --password password β€” use password instead of the one in the config file.
  • --sso β€” instead of typing out a username or password, try to use system level SSO (like kerberos) if it's supported. fancy. 🧚
  • -j, --jserver server β€” use this jabber server instead of the one in the config file.
  • -o, --component componentname β€” use componentname in the connect call. Seems to be needed for Google talk. πŸ‘€
  • -r, --resource res β€” use resource res for the sender [default: 'sendxmpp']; when you're sending to a chatroom, this is what decides your 'alias'.
  • -t, --tls β€” connect securely, using TLS. πŸ”’
  • -e, --ssl β€” connect securely, using SSL.
  • -n, --no-tls-verify β€” deactivate the verification of SSL certificates. > bestie, the better way is to use the parameter --tls-ca-path with the needed path to CA certificates. just saying. πŸ™ˆ
  • -a, --tls-ca-path β€” path to your custom CA certificates, so you can verificate SSL certificates during connecting.
  • -l, --headline β€” backward compatibility option. You should use --message-type=headline instead. Sends a headline type message (not stored in offline messages).
  • --messages-type β€” set the type of message. Supported types are: message chat headline. Default message type is message. Headline type message can be set also with the --headline option, see --headline.
  • -c, --chatroom β€” send the message to a chatroom.
  • -s, --subject subject β€” set the subject for the message to subject [default: '']; when sending to a chatroom, this sets the subject for the chatroom.
  • -m, --message message β€” read the message from message (a file) instead of stdin.
  • -i, --interactive β€” work in interactive mode, reading lines from stdin and sending them one-at-a-time.
  • -w, --raw β€” send raw XML message to the jabber server.
  • -v, --verbose β€” give verbose output about what is happening. she's chatty, we love her. πŸ’¬
  • -h, --help, --usage β€” show a 'Usage' message.
  • -d, --debug β€” show debugging info while running. > WARNING: This will include passwords etc. so be careful with the output! Specify multiple times to increase debug level. 😭 (fr fr, be careful)

πŸ¦‹ CONFIGURATION FILE πŸ¦‹

You may define a ~/.sendxmpprc file with all the necessary data for your xmpp-account. Since version 1.24 the following format is supported:

username: *your_username*
jserver: *jabber_server*
port: *jabber_port*
password: *your_jabber_password*
component: *optional_component_name*

Example for Google Talk servers:

username: *lubomir.host*
jserver: *talk.google.com*
password: *my-secure-password*
component: *gmail.com*

With version 1.23 and older, only the one-line format is supported:

user@server password componentname

e.g.:

# my account
alice@jabber.org  secret

('#' and newlines are allowed, like in shellscripts). You can add a host (or IP address) if it is different from the server part of your JID:

# account with specific connection host
alice@myjabberserver.com;foo.com secret

You can also add a port if it's not the standard XMPP port:

# account with weird port number
alice@myjabberserver.com:1234 secret

Of course, you may also mix the two:

# account with a specific host and port
alice@myjabberserver.com;foo.com:1234 secret
NOTE: for your security, sendxmpp demands that the configuration file is owned by you and readable only to you (permissions 600). no exceptions, she's protective like that. πŸ”

🌈 EXAMPLE 🌈

$ echo "hello bob!" | sendxmpp -s hello someone@jabber.org

or to send to a chatroom:

$ echo "Dinner Time" | sendxmpp -r TheCook --chatroom test2@conference.jabber.org

or to send your system logs somewhere, as new lines appear:

$ tail -f /var/log/syslog | sendxmpp -i sysadmin@myjabberserver.com
NOTE: be careful not the overload public jabber services πŸ™ (yes, we're keeping the original wording, and yes, we're all thinking about it)

⭐ SEE ALSO ⭐

πŸ’œ AUTHOR πŸ’œ

sendxmpp has been written by Dirk-Jan C. Binnema <djcb@djcbsoftware.nl>, and uses the Net::XMPP modules written by Ryan Eatmon. Current maintainer is Lubomir Host <lubomir.host@gmail.com>, <http://blog.hostname.sk>


and that's the whole page bestie, no notes. this one shipped with perl v5.36.0, dated 2023-08-19, and it's filed under SENDXMPP(1p). go send some messages, you absolute legend. 🫢✨

πŸ“¦ where this page comes from