1WHOM(1) General Commands Manual WHOM(1)
2
6 whom - show to whom an nmh message would be sent
7
9 whom [-help] [-version] [-alias aliasfile] [-check | -nocheck] [-draft‐
10 folder +folder] [-draftmessage msg] [-nodraftfolder] [-mts smtp |
11 sendmail/smtp | sendmail/pipe] [-server servername] [-port port-
12 name/number] [-sasl] [-saslmech mechanism] [-snoop] [-user user‐
13 name] [-tls] [-initialtls] [-notls] [file] [-draft]
14
16 whom is used to expand the headers of a message into a set of addresses
17 and optionally verify that those addresses are deliverable at that time
18 (if -check is given).
19 The -draftfolder +folder and -draftmessage msg switches invoke the nmh
21 draft folder facility. This is an advanced (and highly useful) fea‐
22 ture. Consult the mh-draft(5) man page for more information.
23 The mail transport system default is provided in /etc/nmh/mts.conf but
25 can be overridden here with the -mts switch.
26 If nmh is using the SMTP MTA, the -server and the -port switches can be
28 used to override the default mail server (defined by the
29 /etc/nmh/mts.conf servers entry). The -snoop switch can be used to
30 view the SMTP transaction. (Beware that the SMTP transaction may con‐
31 tain authentication information either in plaintext or easily decoded
32 base64.)
33 If nmh has been compiled with SASL support, the -sasl switch will
35 enable the use of SASL authentication with the SMTP MTA. Depending on
36 the SASL mechanism used, this may require an additional password prompt
37 from the user (but the netrc file can be used to store this password,
38 as described in the mh-profile(5) man page). The -saslmech switch can
39 be used to select a particular SASL mechanism, and the -user switch can
40 be used to select a authorization userid to provide to SASL other than
41 the default. The credentials profile entry in the mh-profile(5) man
42 page describes the ways to supply a username and password.
43 If SASL authentication is successful, nmh will attempt to negotiate a
45 security layer for session encryption. Encrypted data is labelled with
46 `(encrypted)' and `(decrypted)' when viewing the SMTP transaction with
47 the -snoop switch; see the post man page description of -snoop for its
48 other features.
49 If nmh has been compiled with TLS support, the -tls, -initialtls, and
51 -notls switches will require and disable the negotiation of TLS support
52 when connecting to the SMTP MTA. Encrypted data is labelled with
53 `(tls-encrypted)' and `(tls-decrypted)' when viewing the SMTP transac‐
54 tion with the -snoop switch; see the post man page description of
55 -snoop and the TLS flags for more details.
56 The files specified by the profile entry “Aliasfile:” and any addi‐
58 tional alias files given by the -alias aliasfile switch will be read
59 (more than one file, each preceded by -alias, can be named). See
60 mh-alias(5) for more information.
61
63 $HOME/.mh_profile The user profile
64
66 Path: To determine the user's nmh directory
67 Draft-Folder: To find the default draft-folder
68 Aliasfile: For a default alias file
69 postproc: Program to post the message
70
72 mh-alias(5), mh-profile(5), post(8)
73
75 `file' defaults to <mh-dir>/draft
76 `-nocheck'
77 `-alias' defaults to /etc/nmh/MailAliases
78
80 None
81
83 With the -check option, whom makes no guarantees that the addresses
84 listed as being ok are really deliverable, rather, an address being
85 listed as ok means that at the time that whom was run the address was
86 thought to be deliverable by the transport service. For local
87 addresses, this is absolute; for network addresses, it means that the
88 host is known; for uucp addresses, it (often) means that the UUCP net‐
89 work is available for use.
90nmh-1.7.1 2016-09-23 WHOM(1)