1SIVTEST(1)                  General Commands Manual                 SIVTEST(1)
2
3
4
5 *
6

NAME

8       sivtest - interactive MANAGESIEVE test program
9

SYNOPSIS

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

DESCRIPTION

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

OPTIONS

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

SEE ALSO

83       timsieved(8)
84
85
86
87CMU                              Project Cyrus                      SIVTEST(1)