GNU.WIKI: The GNU/Linux Knowledge Base

  [HOME] [PHP Manual] [HowTo] [ABS] [MAN1] [MAN2] [MAN3] [MAN4] [MAN5] [MAN6] [MAN7] [MAN8] [MAN9]

  [0-9] [Aa] [Bb] [Cc] [Dd] [Ee] [Ff] [Gg] [Hh] [Ii] [Jj] [Kk] [Ll] [Mm] [Nn] [Oo] [Pp] [Qq] [Rr] [Ss] [Tt] [Uu] [Vv] [Ww] [Xx] [Yy] [Zz]


NAME

       whom - report to whom a message would go

SYNOPSIS

       whom [-alias aliasfile] [-check | -nocheck] [-draftfolder +folder]
            [-draftmessage msg] [-nodraftfolder] [-mts smtp | sendmail/smtp |
            sendmail/pipe] [-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)
       feature.  Consult the mh-draft(5) man page for more information.

       The  mail transport system default is provided in /etc/nmh/mts.conf but
       can be overriiden here with the -mts switch.

       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
       contain  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,
       as  described in the mh-profile(5) man page).  The -saslmech switch can
       be used to select a particular SASL mechanism, and the -user switch can
       be  used to select a authorization userid to provide to SASL other than
       the default.  The credentials profile entry in  the  mh-profile(5)  man
       page describes the ways to supply a username and password.

       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 connecting
       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), mh-profile(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.



  All copyrights belong to their respective owners. Other content (c) 2014-2018, GNU.WIKI. Please report site errors to webmaster@gnu.wiki.
Page load time: 0.181 seconds. Last modified: November 04 2018 12:49:43.