MUPDATETEST(1)

✨ NAME ✨

okay so bestie, meet mupdatetest — it's Cyrus IMAP documentation, and it's an interactive MUPDATE test program 💅

Fun lil plot twist: this is actually installed as a hard linked copy of imtest(1) 🫶

What does it do? It lets you authenticate and send MUPDATE commands to the server. That's it, that's the whole vibe. 🌸

🦋 SYNOPSIS 🦋

imtest [ -t keyfile ] [ -p port ] [ -m mechanism ]
    [ -a userid ] [ -u userid ] [ -k num ] [ -l num ]
    [ -r realm ] [ -f file ] [ -n num ] [ -s ] [ -q ]
    [ -c ] [ -i ] [ -z ] [ -v ] [ -I file ] [ -x file ]
    [ -X file ] [ -w passwd ] [ -o option=value ]
    [ -H client-ip ] hostname

💖 DESCRIPTION 💖

so imtest is a utility that lets you authenticate to an IMAP server and then interactively issue commands to it, like you're texting the server directly 💬 Once you're authenticated, you can issue any IMAP command just by typing it in. no cap. It is capable of multiple SASL authentication mechanisms, and it handles encryption layers transparently — which is giving ✨effortless✨.

This utility is often used for testing the operation of an IMAP server, and also all the devs out there building IMAP clients find it useful 🧚 iykyk.

🎀 OPTIONS 🎀

• -t keyfile, --keyfile=keyfile — Enable TLS 🌈 keyfile contains the TLS public and private keys. Specify "" to negotiate a TLS encryption layer but not use TLS authentication.
• -p port, --port=port — Port to connect to. If you leave it off, this defaults to imap as defined in /etc/services.
• -m mechanism, --mechanism=mechanism — Force imtest to use mechanism for authentication. If you don't specify one, the strongest authentication mechanism supported by the server gets chosen 👑 Specify login to use the LOGIN command instead of AUTHENTICATE.
• -a userid, --authname=userid — Userid to use for authentication; defaults to the current user. This is the userid whose password or credentials get presented to the server for verification 🔐
• -u userid, --username=userid — Userid to use for authorization; defaults to the current user. This is the userid whose identity will be assumed after authentication. 🪄

NOTE: This is only used with SASL mechanisms that allow proxying (e.g. PLAIN).

• -k num, --minssf=num — Minimum protection layer required 🛡️
• -l num, --maxssf=num — Maximum protection layer to use (0=none; 1=integrity; etc). For example, if you are using the GSSAPI authentication mechanism, specifying 0 will force imtest to not use any layer, and specifying 1 will force it to use the integrity layer. By default the maximum supported protection layer will be used. 💫
• -r realm, --realm=realm — Specify the realm to use. Certain authentication mechanisms may require you to specify the realm.
• -f file, --input-filename=file — Pipe file into the connection after authentication 🍓
• -n num, --reauth-attempts=num — Number of authentication attempts; default = 1. The client will attempt to do SSL/TLS session reuse and/or fast reauth if possible. 🔁
• -s, --require-tls — Enable SSL over the chosen protocol.
• -q, --require-compression — Enable IMAP COMPRESSion (after authentication).
• -c, --do-challenge — Enable challenge prompt callbacks. This will cause the OTP mechanism to ask for the one-time password instead of the secret pass-phrase (the library generates the correct response). 🎲
• -i, --no-initial-response — Don't send an initial client response for SASL mechanisms, even if the protocol supports it. 🙈
• -I file, --pidfile=file — Echo the PID of the running process into file (this can be useful with -X).
• -v, --verbose — Verbose. Print out more information than usual. 👀
• -z, --run-stress-test — Timing test. ⏱️
• -x file, --output-socket=file — Open the named socket for the interactive portion.
• -X file — Like -x, only it closes all file descriptors & daemonizes the process. 😴
• -w password, --password=password — Password to use (if not supplied, we will prompt).
• -o option=value, --sasl-option=option=value — Set the SASL option to value.
• -H client-ip — Enable the HAProxy protocol and send the specified client IP address in a v1 header. If the address is "unknown", a v1 header with UNKNOWN protocol will be sent. If the address is "local", a v2 header with LOCAL command will be sent. 📬

🌈 EXAMPLES 🌈

(no examples here bestie — the original page is literally empty on this one, we're not making stuff up 💀)

💜 SEE ALSO 💜

• imapd(8)
• mupdate(8)

⭐ AUTHOR ⭐

The Cyrus Team, Nic Bernstein (Onlight) 🫶

👑 COPYRIGHT 👑

1993–2026, The Cyrus Team

---

and that's a wrap, bestie 🎀 this was MUPDATETEST(1) from the Cyrus IMAP crew, version 3.12.3, dated Jul 15, 2026 ✨ go forth and test your MUPDATE server, you absolute icon 💅 periodt.