Go to file
2021-07-02 10:47:12 +02:00
man Update documentation. 2021-06-26 10:05:47 +02:00
vendor Update vendored dependencies. 2021-07-02 10:47:12 +02:00
.gitignore Initial commit 2018-08-04 12:16:28 +02:00
connect.go Remove unnecessary else clause. 2021-03-04 20:00:42 +01:00
go-sendxmpp.go Add resource config option. 2021-06-26 09:59:08 +02:00
go.mod Update vendored dependencies. 2021-07-02 10:47:12 +02:00
go.sum Update vendored dependencies. 2021-07-02 10:47:12 +02:00
httpupload.go Update copyright year 2021-03-03 11:48:27 +01:00
jid.go Update copyright year 2021-03-03 11:48:27 +01:00
LICENSE Update copyright year 2021-03-03 11:48:27 +01:00
LICENSE-mellium Fix whitespaces in licenses. 2020-04-04 14:20:03 +02:00
README.md Update documentation. 2021-06-26 10:05:47 +02:00

go-sendxmpp

about

A little tool to send messages to an XMPP contact or MUC inspired by sendxmpp. You can find other sendxmpp alternatives in the XSF wiki.

support

You might join the chat if you have problems, want to contribute or just want to talk about the project. You might also talk about any of the other sendxmpp incarnations. :)

requirements

installation

If you have GOPATH set just run this commands:

$ go get salsa.debian.org/mdosch/go-sendxmpp
$ go install salsa.debian.org/mdosch/go-sendxmpp

You will find the binary in $GOPATH/bin or, if set, $GOBIN.

usage

You can either pipe a programs output to go-sendxmpp, write in your terminal (put ^D in a new line to finish) or send the input from a file (-m or --message).

The account data is expected at ~/.config/go-sendxmpp/sendxmpprc if no other configuration file location is specified with -f or --file. The configuration file is expected to be in the following format:

username: <your_jid>
password: <your_jabber_password>

If this is not sufficient to connect you might also specify jserver and port. It is also possible to use a password manager. In this case the password setting should be replaced by the eval_password setting:

eval_password: <command_to_unlock_your_password>

You can also configure the resource (and nickname for MUCs) via the resource setting:

resource: <my_resourceY>

If no configuration file is present or if the values should be overridden it is possible to define the account details via command line options:

 Usage: go-sendxmpp [-cdintx] [-f value] [--help] [--http-upload value] [-j value] [-m value] [-p value] [-r value] [-u value] [parameters ...]
 -c, --chatroom     Send message to a chatroom.
 -d, --debug        Show debugging info.
 -f, --file=value   Set configuration file. (Default: ~/.sendxmpprc)
     --help         Show help.
     --http-upload=value
                    Send a file via http-upload.
 -i, --interactive  Interactive mode (for use with e.g. 'tail -f').
 -j, --jserver=value
                    XMPP server address.
 -m, --message=value
                    Set file including the message.
 -n, --no-tls-verify
                    Skip verification of TLS certificates (not recommended).
 -p, --password=value
                    Password for XMPP account.
     --raw          Send raw XML
 -r, --resource=value
                    Set resource. When sending to a chatroom this is used as
                    'alias'. (Default: go-sendxmpp) [go-sendxmpp]
 -t, --tls          Use direct TLS.
 -u, --username=value
                    Username for XMPP account.
 -x, --start-tls    Use StartTLS. (DEPRECATED)

examples

Send a message to two recipients using a configuration file.

cat message.txt | ./go-sendxmpp -f ./sendxmpp recipient1@example.com recipient2@example.com

Send a message to two recipients directly defining account credentials.

cat message.txt | ./go-sendxmpp -u bob@example.com -j example.com -p swordfish recipient1@example.com recipient2@example.com

Send a message to two groupchats (-c) using a configuration file.

cat message.txt | ./go-sendxmpp -cf ./sendxmpp chat1@conference.example.com chat2@conference.example.com

Send file changes to two groupchats (-c) using a configuration file.

tail -f example.log | ./go-sendxmpp -cif ./sendxmpp chat1@conference.example.com chat2@conference.example.com