1SIVTEST(1) Cyrus IMAP SIVTEST(1)
2
3
4
6 sivtest - Cyrus IMAP documentation
7
8 Interactive MANAGESIEVE test program.
9
10 This is actually installed as a hard linked copy of imtest(1).
11
12 It allows you to authenticate and send MANAGESIEVE commands to the
13 server.
14
16 imtest [ -t keyfile ] [ -p port ] [ -m mechanism ]
17 [ -a userid ] [ -u userid ] [ -k num ] [ -l num ]
18 [ -r realm ] [ -f file ] [ -n num ] [ -s ] [ -q ]
19 [ -c ] [ -i ] [ -z ] [ -v ] [ -I file ] [ -x file ]
20 [ -X file ] [ -w passwd ] [ -o option=value ] hostname
21
23 imtest is a utility that allows you to authenticate to a IMAP or IMSP
24 server and interactively issue commands to it. Once authenticated you
25 may issue any IMAP or IMSP command by simply typing it in. It is capa‐
26 ble of multiple SASL authentication mechanisms and handles encryption
27 layers transparently. This utility is often used for testing the opera‐
28 tion of a imsp or imap server. Also those developing IMAP clients find
29 it useful.
30
32 -t keyfile
33 Enable TLS. keyfile contains the TLS public and private keys.
34 Specify "" to negotiate a TLS encryption layer but not use TLS
35 authentication.
36
37 -p port
38 Port to connect to. If left off this defaults to imap as defined
39 in /etc/services.
40
41 -m mechanism
42 Force imtest to use mechanism for authentication. If not speci‐
43 fied the strongest authentication mechanism supported by the
44 server is chosen. Specify login to use the LOGIN command in‐
45 stead of AUTHENTICATE.
46
47 -a userid
48 Userid to use for authentication; defaults to the current user.
49 This is the userid whose password or credentials will be pre‐
50 sented to the server for verification.
51
52 -u userid
53 Userid to use for authorization; defaults to the current user.
54 This is the userid whose identity will be assumed after authen‐
55 tication.
56
57 NOTE:
58 This is only used with SASL mechanisms that allow proxying
59 (e.g. PLAIN, DIGEST-MD5).
60
61 -k num Minimum protection layer required.
62
63 -l num Maximum protection layer to use (0=none; 1=integrity; etc). For
64 example if you are using the KERBEROS_V4 authentication mecha‐
65 nism specifying 0 will force imtest to not use any layer and
66 specifying 1 will force it to use the integrity layer. By de‐
67 fault the maximum supported protection layer will be used.
68
69 -r realm
70 Specify the realm to use. Certain authentication mechanisms
71 (e.g. DIGEST-MD5) may require one to specify the realm.
72
73 -f file
74 Pipe file into connection after authentication.
75
76 -n num Number of authentication attempts; default = 1. The client will
77 attempt to do SSL/TLS session reuse and/or fast reauth (e.g. DI‐
78 GEST-MD5), if possible.
79
80 -s Enable SSL over chosen protocol.
81
82 -q Enable IMAP COMPRESSion (after authentication).
83
84 -c Enable challenge prompt callbacks. This will cause the OTP
85 mechanism to ask for the the one-time password instead of the
86 secret pass-phrase (library generates the correct response).
87
88 -i Don't send an initial client response for SASL mechanisms, even
89 if the protocol supports it.
90
91 -I file
92 Echo the PID of the running process into file (This can be use‐
93 ful with -X).
94
95 -v Verbose. Print out more information than usual.
96
97 -z Timing test.
98
99 -x file
100 Open the named socket for the interactive portion.
101
102 -X file
103 Like -x, only close all file descriptors & daemonize the
104 process.
105
106 -w passwd
107 Password to use (if not supplied, we will prompt).
108
109 -o option=value
110 Set the SASL option to value.
111
114 imapd(8)
115
116 timsieved(8)
117
119 The Cyrus Team, Nic Bernstein (Onlight)
120
122 1993-2018, The Cyrus Team
123
124
125
126
1273.2.6 March 09, 2021 SIVTEST(1)