MJMAP(1)

πŸ“¦
version 1.1.1 Β· 2 versions
, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay so bestie, welcome to MJMAP(1) β€” the general commands manual for mjmap, a sendmail-compatible JMAP client. This is your group chat with Unix, and yes, it slays. πŸ’…


✨ SYNOPSIS ✨

mjmap [-h] [--version] [--mailbox <name>] [-c <file>] [-S] [-d] [-t] [-f <from>] [-i] [-X <file>] [<recipient...>]

πŸŽ€ POSITIONAL ARGUMENTS πŸŽ€

  • <recipient...> β€” email address of a recipient to send the message to. Can be specified multiple times. yes bestie, stack those recipients like your fave playlists πŸ’Œ

πŸ’… OPTIONS πŸ’…

  • -h, --help β€” show usage help and exit. your lil β€œwhat do I do again?” button 🫢
  • --version β€” print version information and exit. identity check, iconic behavior πŸ‘‘
  • -S, --server-info β€” print information about the JMAP server and exit. a little server vibe check πŸ”
  • --mailbox=<name> β€” additional mailbox to add the message to, in addition to Sent. Can be specified multiple times. yes, one message can live in multiple mailboxes β€” multitasking queen πŸ’…
  • -c, --config=<file> β€” use the specified configuration file. point it at ur chosen config, bestie πŸŽ€
  • -d, --debug β€” print lots of debugging information. lore dump mode 😭
  • -t, --read-recipients β€” read recipient addresses from the To, Cc, and Bcc headers of the mail in addition to the ones specified on the command line. the headers are speaking, and we’re listening πŸ‘€
  • -f, --from=<from> β€” set the envelope From address if it is missing from the email headers. gotta have a sender, no cap πŸ’Œ
  • -i, --ignore-dots β€” compatibility with sendmail(1), ignored option. it’s giving β€œI’m here for the compatibility” 🫠
  • -X, --logfile=<file> β€” compatibility with sendmail(1), ignored option. also just vibing in the options list ✨

🌸 CONFIGURATION 🌸

The -c, --config option specifies the configuration file. If the option is omitted, mjmap uses the path in MJMAP_CONFIG when set, then falls back to $XDG_CONFIG_HOME/mjmap/config.scfg. You will find a sample configuration file in /usr/share/mjmap/sample_config.scfg. cute, right? πŸ’–

The file format is SCFG: https://git.sr.ht/~emersion/scfg.

Minimal example, literally right here:

account "myaccount" {
session-url "https://api.fastmail.com/jmap/session"
token "my_token"
}

There must be a single account entry (the name does not matter and can even be omitted). Which supports the following configuration fields:

  • session-url "<url>" (mandatory) β€” the JMAP session endpoint. This is often in the form: "https://<hostname>/.well-known/jmap".
  • token β€” the secret token used for OAUTH bearer authentication. keep it secret, keep it safe 🫢
  • token-cmd β€” a command that will print the token value on its standard output to avoid storing it in plain text. The command is executed with sh -c. Example:
token-cmd "pass fastmail/api-token"
  • username β€” the username for basic authentication.
  • password β€” the password for basic authentication.
  • password-cmd β€” a command that will print the password value on its standard output to avoid storing it in plain text. The command is executed with sh -c. Example:
password-cmd "pass foobar/jmap-password"
bestie, if you’re putting secrets in plain text, maybe don’t? the *-cmd options are right there for a reason πŸ’€

πŸ¦‹ SEE ALSO πŸ¦‹


🌈 AUTHORS 🌈

Created by Tim Culverhouse who is assisted by other open source contributors. For more information about mjmap development, see https://git.sr.ht/~rockorager/mjmap. icons supporting icons, fr fr πŸ‘‘


xoxo bestie β€” this page is dated 1980-01-01 and signs off as MJMAP(1) πŸ«ΆπŸ’–

πŸ“¦ where this page comes from