WHOM(1)                                                              [nmh-1.5]                                                             WHOM(1)

NAME

       whom - report to whom a message would go

SYNOPSIS

       whom [-alias aliasfile] [-check | -nocheck] [-draftfolder +folder] [-draftmessage msg] [-nodraftfolder] [-server servername] [-port port-
            name/number] [-sasl] [-saslmech mechanism] [-snoop] [-user username] [-tls] [-notls] [file] [-draft] [-version] [-help]

DESCRIPTION

       Whom is used to expand the headers of a message into a set of addresses and optionally verify that those addresses are deliverable at  that
       time (if -check is given).

       The -draftfolder +folder and -draftmessage msg switches invoke the nmh draft folder facility.  This is an advanced (and highly useful) fea-
       ture.  Consult the mh-draft(5) man page for more information.

       If nmh is using the SMTP MTA, the -server and the -port switches can  be  used  to  override  the  default  mail  server  (defined  by  the
       /etc/nmh/mts.conf  servers entry).  The -snoop switch can be used to view the SMTP transaction.  (Beware that the SMTP transaction may con-
       tain authentication information either in plaintext or easily decoded base64.)

       If nmh has been compiled with SASL support, the -sasl switch will enable the use of SASL authentication with the SMTP  MTA.   Depending  on
       the  SASL  mechanism  used,  this  may require an additional password prompt from the user (but the ".netrc" file can be used to store this
       password).  -saslmech switch can be used to select a particular SASL mechanism, and the the -user switch can be used to select a authoriza-
       tion userid to provide to SASL other than the default.

       If  SASL  authentication  is successful, nmh will attempt to negotiate a security layer for session encryption.  Encrypted data is labelled
       with `(encrypted)' and `(decrypted)' when viewing the SMTP transaction with the -snoop switch.  The  -saslmaxssf  switch  can  be  used  to
       select  the  maximum  value  of  the Security Strength Factor.  This is an integer value and the exact meaning of this value depends on the
       underlying SASL mechanism.  A value of 0 disables encryption.

       If nmh has been compiled with TLS support, the -tls and -notls switches will require and disable the negotiation of TLS support  when  con-
       necting to the SMTP MTA.  Encrypted data is labelled with `(tls-encrypted)' and `(tls-decrypted)' when viewing the SMTP transction with the
       -snoop switch.

       The files specified by the profile entry "Aliasfile:" and any additional alias files given by the -alias  aliasfile  switch  will  be  read
       (more than one file, each preceded by -alias, can be named). See mh-alias(5) for more information.

FILES

       $HOME/.mh_profile          The user profile

PROFILE COMPONENTS

       Path:                To determine the user's nmh directory
       Draft-Folder:        To find the default draft-folder
       Aliasfile:           For a default alias file
       postproc:            Program to post the message

SEE ALSO

       mh-alias(5), post(8)

DEFAULTS

       `file' defaults to <mh-dir>/draft
       `-nocheck'
       `-alias' defaults to  /etc/nmh/MailAliases

CONTEXT

       None

BUGS

       With  the  -check  option,  whom makes no guarantees that the addresses listed as being ok are really deliverable, rather, an address being
       listed as ok means that at the time that whom was run the address was thought to be  deliverable  by  the  transport  service.   For  local
       addresses,  this  is  absolute;  for network addresses, it means that the host is known; for uucp addresses, it (often) means that the UUCP
       network is available for use.

MH.6.8                                                             11 June 2012                                                            WHOM(1)