1 .TH MH-PROFILE %manext5% "December 21, 2014" "%nmhversion%"
6 mh-profile \- user profile customization for nmh message handler
10 is expected to have a file named
12 in his or her home directory. This file contains
13 a set of user parameters used by some or all of the
15 family of programs. Each entry in the file is of the format
18 .IR profile\-component ": " value
21 If the text of profile entry is long, you may extend it across several
22 real lines by indenting the continuation lines with leading spaces or tabs.
23 Comments may be introduced by a line starting with `#:':
30 Blank lines are not permitted in
32 The shell quoting conventions are not available in the
33 .IR \&.mh\(ruprofile ;
34 each token is separated by whitespace.
35 .SS "Standard Profile Entries"
36 The possible profile components are exemplified below. The only mandatory
37 entry is `Path:'. The others are optional; some have default values if
38 they are not present. In the notation used below, (profile, default)
39 indicates whether the information is kept in the user's
43 context, and indicates what the default value is. Note that a profile
44 component can only appear once. Multiple appearances with trigger a
45 warning that all appearances after the first are ignored.
47 Some MH programs, including
52 have specific profile components that are described in their respective
53 man pages. Each component name begins with the name of the program and
54 is followed by a dash.
61 transactions in directory \*(lqMail\*(rq. This is the
62 only mandatory profile entry. (profile, no default)
68 Declares the location of the
70 context file. This is overridden by the environment variable
75 (profile, default: <nmh\-dir>/context)
81 Keeps track of the current open folder.
82 (context, default: folder specified by \*(lqInbox\*(rq)
88 Defines the name of your default inbox.
89 (profile, default: inbox)
92 .BR Previous\-Sequence :
95 Names the sequence or sequences which should be defined as the `msgs' or
96 `msg' argument given to any
98 command. If not present or empty,
99 no such sequences are defined. Otherwise, for each name given, the
100 sequence is first zero'd and then each message is added to the sequence.
103 man page for the details about this sequence. (profile, no default)
106 .BR Sequence\-Negation :
109 Defines the string which, when prefixed to a sequence name, negates
110 that sequence. Hence, \*(lqnotseen\*(rq means all those messages that
111 are not a member of the sequence \*(lqseen\*(rq. Read the
113 man page for the details. (profile, no default)
116 .BR Unseen\-Sequence :
119 Names the sequence or sequences which should be defined as those
120 messages which are unread. The commands
126 will add or remove messages from these
127 sequences when they are incorporated or read. If not present or
128 empty, no such sequences are defined. Otherwise, each message is
129 added to, or removed from, each sequence name given. Read the
131 man page for the details about this sequence.
132 (profile, no default)
138 The name of the file in each folder which defines public sequences.
139 To disable the use of public sequences, leave the value portion of this
140 entry blank. (profile, default: \&.mh\(rusequences)
143 .BI atr\- seq \- folder :
146 Keeps track of the private sequence called \*(lqseq\*(rq in the specified
147 folder. Private sequences are generally used for read\-only folders.
150 man page for details about private sequences.
151 (context, no default)
157 Defines the editor to be used by the commands
163 If not set in profile the value will be taken from the VISUAL and
164 EDITOR environment variables.
165 (profile, default: vi)
171 An octal number which defines the permission bits for new message files.
174 for an explanation of the octal number. Note that some filesystems,
175 such as FAT32, do not support removal of read file permissions.
176 (profile, default: 0600)
179 .BR Folder\-Protect :
182 An octal number which defines the permission bits for new folder
185 for an explanation of the octal number.
186 (profile, default: 700)
192 The locking algorithm used to lock changes to any
194 data files, such as sequences or the context. The locking algorithm is
195 any one of the following entries:
203 Available locking algorithms can vary depending on what is supported by
204 the operating system. Note: currently transactional locking is only
205 supported on public sequences; see
207 for more information.
208 (profile, default: fcntl)
214 Sets default switches to be used whenever the mh program
216 is invoked. For example, one could override the \*(lqEditor:\*(rq profile
217 component when replying to messages by adding a component such as:
220 repl: \-editor /bin/ed
223 (profile, no defaults)
226 .IB lasteditor "-next:"
229 Names \*(lqnexteditor\*(rq to be the default editor after using
230 \*(lqlasteditor\*(rq. This takes effect at \*(lqWhat now?\*(rq prompt
238 the draft with \*(lqlasteditor\*(rq, the default editor is set to be
239 \*(lqnexteditor\*(rq. If the user types \*(lqedit\*(rq without any
240 arguments to \*(lqWhat now?\*(rq, then \*(lqnexteditor\*(rq is used.
241 (profile, no default)
247 The contents of the folder-stack for the
250 (context, no default)
254 Your Username <user@some.host>
256 Tells the various MH tools what your local mailbox is. If set, will be used
257 by the default component files by tools like
261 to construct your default \*(lqFrom\*(rq header. The text used here will
262 be copied exactly to your From: header, so it should already be RFC 822
263 compliant. If this is set, the
265 profile entry is NOT used, so it should include a signature as well. (profile,
266 default: userid@local.hostname)
269 .BR Alternate\-Mailboxes :
270 mh@uci\-750a, bug-mh*
276 which addresses are really yours.
279 knows which addresses should be included in the
282 knows if the message really originated from you.
283 Addresses must be separated by a comma, and the hostnames listed should
284 be the \*(lqofficial\*(rq hostnames for the mailboxes you indicate, as
285 local nicknames for hosts are not replaced with their official site names.
286 For each address, if a host is not given, then that address on any host is
287 considered to be you. In addition, an asterisk (`*') may appear at either
288 or both ends of the mailbox and host to indicate wild-card matching.
289 (profile, default: your user-id)
296 Indicates aliases files for
301 This may be used instead of the
304 switch. (profile, no default)
310 Indicates a default draft folder for
319 man page for details. (profile, no default)
322 .BI digest\-issue\- list :
327 the last issue of the last volume sent for the digest
329 (context, no default)
332 .BI digest\-volume\- list :
337 the last volume sent for the digest
339 (context, no default)
347 your maildrop, if different from the default. This is
348 superseded by the environment variable
350 (profile, default: %mailspool%/$USER)
354 RAND MH System (agent: Marshall Rose)
356 Tells front-end programs such as
361 your mail signature. This is superseded by the
366 is not set and this profile entry is not present, the \*(lqgcos\*(rq field of
367 the \fI/etc/passwd\fP file will be used.
368 Your signature will be added to the address
370 puts in the \*(lqFrom:\*(rq header; do not include an address in the
371 signature text. The \*(lqLocal\-Mailbox\*(rq profile component
372 supersedes all of this. (profile, no default)
378 Indicates how the username and password credentials will be retrieved
379 for access to external servers, such as those that provide SMTP or POP
380 service. The supported entry values are \*(lqlegacy\*(rq and
381 .RI \*(lqfile: netrc \*(rq.
382 With \*(lqlegacy\*(rq, or if there is no credentials entry, the
383 username is the first of:
397 2) the login name on the local machine
400 The password for SMTP services is the first of:
403 1) password value from matching entry in file named \*(lq.netrc\*(rq
404 in the user's home directory
406 2) password obtained by interactively prompting the user
409 The password for POP service when the
411 switch is used with one of these programs is the login name on the
415 .RI \*(lqfile: netrc \*(rq
417 entry, the username is the first of:
424 2) login name from matching entry in
428 3) value provided by user in response to interactive query
431 Similarly, the password is provided either in the
433 file or interactively.
435 can be any valid filename, either absolute or relative to Path or
438 file contains authentication information, for each server,
439 using a line of the following form. Replace the words
444 with your own account information:
457 file must be owned and readable only by you.
458 (profile, default: legacy)
460 .SS "Process Profile Entries"
461 The following profile elements are used whenever an
463 program invokes some other program such as
467 can be used to select alternate programs if the
468 user wishes. The default values are given in the examples.
470 If the profile element contains spaces, the element is split at spaces
471 into tokens and each token is given as a separate argument to the
473 system call. If the element contains shell metacharacters then the entire
474 element is executed using
481 This is the program used by
483 to process drafts which are MIME composition files.
489 This program is used to refile or link a message to another folder.
492 to file a copy of a message into a folder given
493 by a \*(lqFcc:\*(rq field. It is used by the draft folder facility in
500 message into another folder. It is used to refile a draft message in
503 directive at the \*(lqWhat now?\*(rq prompt.
510 to filter a component when it is tagged with the \*(lqformat\*(rq variable
511 in the mhl filter. See
513 for more information.
521 to incorporate new mail when it
522 is invoked with no arguments.
528 This program is used to list the contents of a message in response
531 directive at the \*(lqWhat now?\*(rq prompt. It is
532 also used by the draft folder facility in
538 to display the draft message.
541 supersedes the default built-in pager command.)
547 This is the program used to automatically mail various messages
548 and notifications. It is used by
550 to post failure notices.
551 It is used to retrieve an external-body with access-type `mail-server'
552 (such as when storing the body with
559 This is the program used to filter messages in various ways. It
562 to filter and display the message headers
563 of MIME messages. When the
574 is used to filter the
575 message that you are forwarding, or to which you are replying.
582 is used to filter the copy of the message
583 that is sent to \*(lqBcc:\*(rq recipients.
589 This is the program used by
593 formatted message when displaying to a terminal. It is also the default
596 to display message bodies (or message parts) of type text/plain.
599 supersedes the default built-in pager command.)
611 This is the program used by
620 post a message to the mail transport system. It is also called by
622 (called with the switches
626 to do address verification.
632 This is the program used by
637 to delete a message from a folder.
643 This is the program to use by
645 to actually send the message
651 This is the program used by
653 to process and display non-text (MIME) messages.
659 This is the program used by
661 to filter and display text (non-MIME) messages.
667 This is the program invoked by
673 to query about the disposition of a composed draft message.
679 This is the program used by
681 to determine to whom a message would be sent.
684 After consulting .mh_profile,
685 some programs read an optional profile specified by a
686 program-specific environment variable,
687 and then the system-wide profile %nmhetcdir%/mhn.defaults.
688 These programs are mhbuild, mhshow, mhstore, and mhn.
689 mhfixmsg is similar, but has no optional profile.
691 The first occurrence of a component is used,
692 e.g.\& .mh_profile's trumps $MHSHOW's.
693 A component with no value still stops further occurrences being used,
694 but is considered absent.
695 .SS "Environment Variables"
698 and its commands it also controlled by the
699 presence of certain environment variables.
701 Many of these environment variables are used internally by the
702 \*(lqWhat now?\*(rq interface. It's amazing all the information
703 that has to get passed via environment variables to make the
704 \*(lqWhat now?\*(rq interface look squeaky clean to the
706 user, isn't it? The reason for all this is that the
714 one of the standard shells. As a result, it's not possible to pass
715 information via an argument list. The convention is that environment
716 variables whose names are all upper-case are user-settable; those
717 whose names are lower-case only are used internally by nmh and should
718 not generally be set by the user.
722 With this environment variable, you can specify a profile
728 that you invoke. If the value of
730 is not absolute, (i.e., does
731 not begin with a \*(lq/\*(rq), it will be presumed to start from the current
732 working directory. This is one of the very few exceptions in
734 where non-absolute pathnames are not considered relative to the user's
741 With this environment variable, you can specify a
742 context other than the normal context file (as specified in
745 profile). As always, unless the value of
747 is absolute, it will be presumed to start from your
754 With this environment variable, you can specify an
755 additional user profile (file) to be read by
757 in addition to the mhn.defaults profile.
762 With this environment variable, you can specify an
763 additional user profile (file) to be read by
765 in addition to the mhn.defaults profile.
767 is deprecated, so support for this variable will
768 be removed from a future nmh release.
773 With this environment variable, you can specify an
774 additional user profile (file) to be read by
776 in addition to the mhn.defaults profile.
781 With this environment variable, you can specify an
782 additional user profile (file) to be read by
784 in addition to the mhn.defaults profile.
791 the default maildrop. This supersedes the \*(lqMailDrop\*(rq profile entry.
798 the POP host to query for mail to incorporate. See the
799 inc(1) man page for more information.
802 .B $USERNAME_EXTENSION
804 This variable is for use with username_extension masquerading. See the
805 mh-tailor(5) man page.
814 your mail signature. This supersedes the \*(lqSignature\*(rq profile entry,
815 and is not used when the \*(lqLocal\-Mailbox\*(rq profile component is set.
824 your default maildrop: see the \*(lqMailDrop\*(rq profile entry.
829 This variable tells all
831 programs your home directory
840 The environment variable
842 is also consulted. In particular,
847 how to clear your terminal, and how
848 many columns wide your terminal is. They also tell
851 lines long your terminal screen is.
856 If this variable is set to a non-null value, it specifies the
857 name of the mail transport configuration file to use by
860 and other programs that interact with the mail transport system,
861 instead of the default. See mh-tailor(5).
866 If this variable is set to a non-null value, it specifies the name of
867 a mail transport configuration file to be read in addition to the
868 default. See mh-tailor(5).
874 These variables are searched, in order, for the directory in which to
875 create some temporary files.
880 If this variable is set to a non-null value,
882 will emit debugging information.
887 If this variable is set to a non-null value,
889 will emit a representation of the search pattern.
891 is deprecated, so support for this variable will
892 be removed from a future nmh release. Instead,
901 If this variable is set to a non-null value,
903 commands that use the
904 .BR Alternate\-Mailboxes
905 profile entry will display debugging information
906 about the values in that entry.
911 If set to a non-null value, this supersedes the value of
912 the default built-in pager command.
917 This is the alternate message.
923 during edit sessions so you can
924 peruse the message being distributed or replied to. The message is also
928 through a link called \*(lq@\*(rq in the current directory if
929 your current working directory and the folder the message lives in are
930 on the same UNIX filesystem, and if your current working directory is
936 This is the path to the working draft.
946 which file to ask \*(lqWhat now?\*(rq
959 about an alternate message associated with the
960 draft (the message being distributed or replied to).
965 This is the folder containing the alternate message.
971 during edit sessions so you
972 can peruse other messages in the current folder besides the one being
973 distributed or replied to. The environment variable
991 that message re-distribution is occurring.
1004 the user's choice of
1005 editor (unless overridden by
1022 if annotations are to occur.
1032 if annotations are to occur.
1042 if annotations are to occur.
1047 .ta \w'%nmhetcdir%/ExtraBigFileName 'u
1048 ^$HOME/\&.mh\(ruprofile~^The user profile
1049 ^or $MH~^Rather than the standard profile
1050 ^<mh\-dir>/context~^The user context
1051 ^or $MHCONTEXT~^Rather than the standard context
1052 ^<folder>/\&.mh\(rusequences~^Public sequences for <folder>
1056 .IR mh-sequence (5),
1064 contains only static information, which
1068 update. Changes in context are made to the
1070 file kept in the users
1073 This includes, but is not limited to: the \*(lqCurrent\-Folder\*(rq entry
1074 and all private sequence information. Public sequence information is
1075 kept in each folder in the file determined by the \*(lqmh\-sequences\*(rq
1076 profile entry (default is
1077 .IR \&.mh\(rusequences ).
1081 may override the path of the
1083 file, by specifying a \*(lqcontext\*(rq entry (this must be in
1084 lower-case). If the entry is not absolute (does not start with a
1085 \*(lq/\*(rq), then it is interpreted relative to the user's
1087 directory. As a result, you can actually have more than one set of
1088 private sequences by using different context files.
1090 There is some question as to what kind of arguments should be placed
1091 in the profile as options. In order to provide a clear answer, recall
1092 command line semantics of all
1094 programs: conflicting switches
1099 may occur more than one time on the
1100 command line, with the last switch taking effect. Other arguments, such
1101 as message sequences, filenames and folders, are always remembered on
1102 the invocation line and are not superseded by following arguments of
1103 the same type. Hence, it is safe to place only switches (and their
1104 arguments) in the profile.
1106 If one finds that an
1108 program is being invoked again and again
1109 with the same arguments, and those arguments aren't switches, then there
1110 are a few possible solutions to this problem. The first is to create a
1116 of your choice. By giving this link a different name, you can create
1117 a new entry in your profile and use an alternate set of defaults for
1120 command. Similarly, you could create a small shell script
1123 program of your choice with an alternate set
1124 of invocation line switches (using links and an alternate profile entry
1125 is preferable to this solution).
1129 user could create an alias for the command of the form:
1132 alias cmd 'cmd arg1 arg2 ...'
1135 In this way, the user can avoid lengthy type-in to the shell, and still
1138 commands safely. (Recall that some
1141 invoke others, and that in all cases, the profile is read, meaning that
1142 aliases are disregarded beyond an initial command invocation)