SENDXMPP(1)

πŸ“¦
version 1.24 Β· 4 versions
, in opensuse-leap 16.0

Hey bestie πŸ’– welcome to the SENDXMPP(1) manual from the User Contributed Perl Documentation β€” this is the page for sendxmpp, the lil commandline bestie for sending XMPP (Jabber) messages. 🫢

πŸŽ€ NAME πŸŽ€

sendxmpp β€” send xmpp messages from the commandline. periodt. πŸ’…

🌸 SYNOPSIS 🌸

okay so the whole vibe is literally:

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

sendxmpp --raw [options]

πŸ¦‹ DESCRIPTION πŸ¦‹

sendxmpp is a program to send XMPP (Jabber) messages from the commandline, not unlike mail(1). Messages can be sent both to individual recipients and chatrooms. no cap, it's giving commandline mail energy but make it Jabber ✨

✨ OPTIONS ✨

every flag, no skips, periodt:

  • -f, --file file β€” Use file configuration file instead of ~/.sendxmpprc.
  • -u, --username user β€” Use user instead of the one in the configuration file.
  • -p, --password password β€” Use password instead of the one in the configuration file.
  • --sso β€” Instead of specifying username or password, attempt to use system level SSO (e.g. kerberos) if supported.
  • -j, --jserver server β€” Use jabber server instead of the one in the configuration file.
  • -o, --component componentname β€” Use componentname in connect call. Seems needed for Google talk.
  • -r, --resource res β€” Use resource res for the sender [default: 'sendxmpp']; when sending to a chatroom, this determines the 'alias'.
  • -t, --tls β€” Connect securely, using TLS.
  • -e, --ssl β€” Connect securely, using SSL.
  • -n, --no-tls-verify β€” Deactivate the verification of SSL certificates. Better way is to use parameter --tls-ca-path with the needed path to CA certificates.
  • -a, --tls-ca-path β€” Path to your custom CA certificates, so you can verify SSL certificates during connecting.
  • -l, --headline β€” Backward compatibility option. You should use --message-type=headline instead. Send a headline type message (not stored in offline messages).
  • --messages-type β€” Set type of message. Supported types are: message chat headline. Default message type is message. Headline type message can be set also with --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 will set 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 the one-at-time.
  • -w, --raw β€” Send raw XML message to jabber server.
  • -v, --verbose β€” Give verbose output about what is happening.
  • -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.

πŸ’– CONFIGURATION FILE πŸ’–

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

username: I<your_username>
jserver: I<jabber_server>
port: I<jabber_port>
password: I<your_jabber_password>
component: I<optional_component_name>

Example for Google Talk servers:

username: I<lubomir.host>
jserver: I<talk.google.com>
password: I<my-secure-password>
component: I<gmail.com>

With version 1.23 and older only 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 is 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). bestie, lock that file down fr fr πŸ”

πŸ”₯ EXAMPLE πŸ”₯

the examples are literally:

$ 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 to overload public jabber services, bestie πŸ™ˆ

🌈 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>. iconic credits, honestly 🌟


This page is from perl v5.42.0, dated 2022-10-16, and it's the SENDXMPP(1) manual β€” bye bestie πŸ’‹βœ¨

πŸ“¦ where this page comes from