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

NAME

6       lmtptest - Cyrus IMAP documentation
7
8       Interactive LMTP test program
9

SYNOPSIS

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

DESCRIPTION

17       This is actually installed as a hard link to imtest(1).
18
19       lmtptest  is a utility that allows you to authenticate to a LMTP server
20       and interactively issue commands to  it.  Once  authenticated  you  may
21       issue  any LMTP command by simply typing it in. It is capable of multi‐
22       ple SASL authentication mechanisms and handles encryption layers trans‐
23       parently.  This  utility  is  often used for testing the operation of a
24       lmtp server. Also those developing LMTP clients find it useful.
25

OPTIONS

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

EXAMPLES

SEE ALSO

92       lmtpd(8)
93

AUTHOR

95       The Cyrus Team, Nic Bernstein (Onlight)
96

COPYRIGHT

98       1993-2017, The Cyrus Team
99
100
101
102
1033.0.13                         December 16, 2019                   LMTPTEST(1)