This manual page is for Mac OS X Server version 10.6.3

If you are running Mac OS X (client), this command is not available.

If you are running a different version of Mac OS X Server, view the documentation locally:

  • In Xcode

  • In Terminal, using the man(1) command

Reading manual pages

Manual pages are intended as a quick reference for people who already understand a technology.

  • For more information about the manual page format, see the manual page for manpages(5).

  • For more information about this technology, look for other documentation in the Apple Reference Library.

  • For general information about writing shell scripts, read Shell Scripting Primer.



SMTPTEST(1)                                                                                      SMTPTEST(1)



NAME
       smtptest - interactive SMTP test program

SYNOPSIS
       smtptest [ -t keyfile ] [ -p port ] [ -m mechanism ]
                [ -a userid ] [ -u userid ] [ -k num ] [ -l num ]
                [ -r realm ] [ -f file ] [ -n num ] [ -s ] [ -c ]
                [ -i ] [ -o option=value ] [ -v ] hostname

DESCRIPTION
       smtptest  is  a utility that allows you to authenticate to a SMTP server and interactively issue com-mands commands
       mands to it. Once authenticated you may issue any SMTP command by simply typing it in. It is  capable
       of  multiple SASL authentication mechanisms and handles encryption layers transparently. This utility
       is often used for testing the operation of a smtp server. Also those developing SMTP clients find  it
       useful.


OPTIONS
       -t keyfile
              Enable  TLS.  keyfile contains the TLS public and private keys.  Specify "" to negotiate a TLS
              encryption layer but not use TLS authentication.

       -p port
              Port to connect to. If left off this defaults to smtp as defined in /etc/services.

       -m mechanism
              Force smtptest to use mechanism for authentication. If not specified the strongest authentica-tion authentication
              tion mechanism supported by the server is chosen.

       -a userid
              Userid  to  use  for  authentication;  defaults to the current user.  This is the userid whose
              password or credentials will be presented to the server for verification.

       -u userid
              Userid to use for authorization; defaults to the current user.  This is the userid whose iden-tity identity
              tity  will be assumed after authentication.  NOTE: This is only used with SASL mechanisms that
              allow proxying (e.g. PLAIN, DIGEST-MD5).

       -k num Minimum protection layer required.

       -l num Maximum protection layer to use (0=none; 1=integrity; etc).  For example if you are using  the
              KERBEROS_V4 authentication mechanism specifying 0 will force smtptest to not use any layer and
              specifying 1 will force it to use the integrity layer.  By default the maximum supported  pro-tection protection
              tection layer will be used.

       -r realm
              Specify  the realm to use. Certain authentication mechanisms (e.g. DIGEST-MD5) may require one
              to specify the realm.

       -f file
              Pipe file into connection after authentication.

       -n num Number of authentication attempts; default = 1.  The client will attempt to do SSL/TLS session
              reuse and/or fast reauth (e.g. DIGEST-MD5), if possible.

       -s     Enable SMTP over SSL (smtps).

       -c     Enable  challenge prompt callbacks.  This will cause the OTP mechanism to ask for the the one-time onetime
              time password instead of the secret pass-phrase (library generates the correct response).

       -i     Don't send an initial client response for SASL mechanisms, even if the protocol supports it.

       -o option=value
              Set the SASL option to value.

       -v     Verbose. Print out more information than usual.

SEE ALSO
       sendmail(8)



CMU                                             Project Cyrus                                    SMTPTEST(1)

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors
Report errors in the content of this documentation with the feedback links below.
Bug reports
Report bugs in the functionality of the described tool or API through Bug Reporter.
Formatting problems
Report formatting mistakes in the online version of these pages with the feedback links below.

Did this document help you? Yes It's good, but... Not helpful...