imtest is a utility that allows you to authenticate to a IMAP or IMSP server
and interactively issue commands to it. Once authenticated you may
issue any IMAP or IMSP command by simply typing it in. It is capable
of multiple SASL authentication mechanisms and handles encryption
layers transparently. This utility is often used for testing the
operation of a imsp or imap server. Also those developing IMAP clients
find it useful.
Enable TLS. keyfile contains the TLS public and private keys.
Specify "" to negotiate a TLS encryption layer but not use TLS
Port to connect to. If left off this defaults to imap as defined in
Force imtest to use mechanism for authentication. If not specified
the strongest authentication mechanism supported by the server is
chosen. Specify login to use the LOGIN command instead of AUTHENTICATE.
Userid to use for authentication; defaults to the current user.
This is the userid whose password or credentials will be presented to
the server for verification.
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, DIGEST-MD5).
Minimum protection layer required.
Maximum protection layer to use (0=none; 1=integrity;
etc). For example if you are using the KERBEROS_V4 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.
Specify the realm to use. Certain authentication mechanisms
(e.g. DIGEST-MD5) may require one to specify the realm.
Pipe file into connection after authentication.
Number of authentication attempts; default = 1. The client will
attempt to do SSL/TLS session reuse and/or fast reauth
(e.g. DIGEST-MD5), if possible.
Enable IMAP over SSL (imaps).
Enable challenge prompt callbacks. This will cause the OTP mechanism
to ask for the the one-time password instead of the secret pass-phrase
(library generates the correct response).
Dont send an initial client response for SASL mechanisms, even if the
protocol supports it.
Echo the PID of the running process into
file (This can be useful with -X).
Open the named socket for the interactive portion
Like -x, only close all file descriptors & daemonize the process.