SENDXMPP(1p)
π 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,--filefile β use file as the config file instead of the usual~/.sendxmpprc.-u,--usernameuser β use user instead of whatever username is sitting in the config file.-p,--passwordpassword β 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,--jserverserver β use this jabber server instead of the one in the config file.-o,--componentcomponentname β use componentname in the connect call. Seems to be needed for Google talk. π-r,--resourceres β 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-pathwith 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=headlineinstead. Sends a headline type message (not stored in offline messages).--messages-typeβ set the type of message. Supported types are:messagechatheadline. Default message type ismessage. Headline type message can be set also with the--headlineoption, see--headline.-c,--chatroomβ send the message to a chatroom.-s,--subjectsubject β set the subject for the message to subject [default:'']; when sending to a chatroom, this sets the subject for the chatroom.-m,--messagemessage β 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,sendxmppdemands that the configuration file is owned by you and readable only to you (permissions600). 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 β
- Documentation for the
Net::XMPPmodule - The jabber homepage: <http://www.jabber.org/>
- The sendxmpp homepage: <http://sendxmpp.hostname.sk>
π 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
- debian trixie: sendxmpp 1.24-4 Β· GPL-2.0-only
- ubuntu noble: sendxmpp 1.24-4 Β· GPL-2.0-only
- ubuntu questing: sendxmpp 1.24-4
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms