1SIVTEST(1)                        Cyrus IMAP                        SIVTEST(1)
2
3
4

NAME

6       sivtest - Cyrus IMAP documentation
7
8       Interactive MANAGESIEVE test program
9

SYNOPSIS

11       sivtest [ -t keyfile ] [ -p port ] [ -m mechanism ] [ -a userid ]
12           [ -u userid ] [ -k num ] [ -l num ] [ -r realm ] [ -f file ]
13           [ -n num ] [ -c ] [ -i ] [ -v ] [ -w passwd ] [ -o option=value ] hostname
14

DESCRIPTION

16       sivtest  is  a utility that allows you to authenticate to a MANAGESIEVE
17       server and interactively issue commands to it. Once  authenticated  you
18       may issue any MANAGESIEVE command by simply typing it in. It is capable
19       of multiple SASL authentication mechanisms and handles encryption  lay‐
20       ers transparently. This utility is often used for testing the operation
21       of a timsieved(8) server. Also  those  developing  MANAGESIEVE  clients
22       find it useful.
23

OPTIONS

25       -t keyfile
26              Enable  TLS.   keyfile contains the TLS public and private keys.
27              Specify "" to negotiate a TLS encryption layer but not  use  TLS
28              authentication.
29
30       -p port
31              Port  to  connect  to.  If  left  off  this defaults to sieve as
32              defined in /etc/services.
33
34       -m mechanism
35              Force sivtest to use mechanism for authentication. If not speci‐
36              fied,  the  strongest  authentication mechanism supported by the
37              server is chosen.   Specify  login  to  use  the  LOGIN  command
38              instead of AUTHENTICATE.
39
40       -a userid
41              Userid  to use for authentication; defaults to the current user.
42              This is the userid whose password or credentials  will  be  pre‐
43              sented to the server for verification.
44
45       -u userid
46              Userid  to  use for authorization; defaults to the current user.
47              This is the userid whose identity will be assumed after  authen‐
48              tication.
49
50              NOTE:
51                 This  is  only  used with SASL mechanisms that allow proxying
52                 (e.g. PLAIN, DIGEST-MD5).
53
54       -k num Minimum protection layer required.
55
56       -l num Maximum protection layer to use (0=none; 1=integrity; etc).  For
57              example  if  you are using the KERBEROS_V4 authentication mecha‐
58              nism specifying 0 will force imtest to not  use  any  layer  and
59              specifying  1  will  force  it  to  use the integrity layer.  By
60              default the maximum supported protection layer will be used.
61
62       -r realm
63              Specify the realm  to  use.  Certain  authentication  mechanisms
64              (e.g. DIGEST-MD5) may require one to specify the realm.
65
66       -f file
67              Pipe file into connection after authentication.
68
69       -n num Number of authentication attempts; default = 1.  The client will
70              attempt to do SSL/TLS session reuse  and/or  fast  reauth  (e.g.
71              DIGEST-MD5), if possible.
72
73       -c     Enable  challenge  prompt  callbacks.   This  will cause the OTP
74              mechanism to ask for the the one-time password  instead  of  the
75              secret pass-phrase (library generates the correct response).
76
77       -i     Don't  send an initial client response for SASL mechanisms, even
78              if the protocol supports it.
79
80       -v     Verbose. Print out more information than usual.
81
82       -w passwd
83              Password to use (if not supplied, we will prompt).
84
85       -o option=value
86              Set the SASL option to value.
87

EXAMPLES

SEE ALSO
90       timsieved(8)
91

AUTHOR
93       The Cyrus Team, Nic Bernstein (Onlight)
94

96       1993-2017, The Cyrus Team
97
98
99
100
1013.0.10                           May 27, 2019                       SIVTEST(1)



        

    


            
        

        

            Impressum