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

NAME

6       mupdatetest - Cyrus IMAP documentation
7
8       Interactive MUPDATE test program
9

SYNOPSIS

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

DESCRIPTION

16       mupdatetest  is  a utility that allows you to authenticate to a MUPDATE
17       server and interactively issue commands to it. Once  authenticated  you
18       may issue any MUPDATE command by simply typing it in.  It is capable of
19       multiple SASL authentication mechanisms and handles  encryption  layers
20       transparently.  This utility is often used for testing the operation of
21       a mupdate server. Note that you must be an admin in order to  authenti‐
22       cate to an mupdate server.
23

OPTIONS

25       -p port
26              Port  to  connect  to.  If  left off this defaults to mupdate as
27              defined in /etc/services.
28
29       -m mechanism
30              Force mupdatetest to use mechanism for  authentication.  If  not
31              specified  the  strongest  authentication mechanism supported by
32              the server is chosen.  Specify login to use  the  LOGIN  command
33              instead of AUTHENTICATE.
34
35       -a userid
36              Userid  to use for authentication; defaults to the current user.
37              This is the userid whose password or credentials  will  be  pre‐
38              sented to the server for verification.
39
40       -u userid
41              Userid  to  use for authorization; defaults to the current user.
42              This is the userid whose identity will be assumed after  authen‐
43              tication.
44
45              NOTE:
46                 This  is  only  used with SASL mechanisms that allow proxying
47                 (e.g. PLAIN, DIGEST-MD5).
48
49       -k num Minimum protection layer required.
50
51       -l num Maximum protection layer to use (0=none; 1=integrity; etc).  For
52              example  if  you are using the KERBEROS_V4 authentication mecha‐
53              nism specifying 0 will force imtest to not  use  any  layer  and
54              specifying  1  will  force  it  to  use the integrity layer.  By
55              default the maximum supported protection layer will be used.
56
57       -r realm
58              Specify the realm  to  use.  Certain  authentication  mechanisms
59              (e.g. DIGEST-MD5) may require one to specify the realm.
60
61       -f file
62              Pipe file into connection after authentication.
63
64       -n num Number of authentication attempts; default = 1.  The client will
65              attempt to do SSL/TLS session reuse  and/or  fast  reauth  (e.g.
66              DIGEST-MD5), if possible.
67
68       -q     Enable MUPDATE COMPRESSion (after authentication).
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       -v     Verbose. Print out more information than usual.
78
79       -w passwd
80              Password to use (if not supplied, we will prompt).
81
82       -o option=value
83              Set the SASL option to value.
84

EXAMPLES

SEE ALSO
87       mupdate(8)
88

AUTHOR
90       The Cyrus Team, Nic Bernstein (Onlight)
91

93       1993-2017, The Cyrus Team
94
95
96
97
983.0.12                         November 15, 2019                MUPDATETEST(1)



        

    


            
        

        

            Impressum