4 .TH MH-PROFILE %manext5% "%nmhdate%" MH.6.8 [%nmhversion%]
6 mh-profile \- user profile customization for mmh message handler
14 is expected to have a file named
16 in his or her home directory. This file contains
17 a set of user parameters used by some or all of the
19 family of programs. Each entry in the file is of the format
22 .IR Profile\-Component ": " value
25 If the text of profile entry is long, you may extend it across several
26 real lines by indenting the continuation lines with leading spaces or tabs.
28 .SS "Standard Profile Entries"
29 The possible profile components are exemplified below. The only mandatory
30 entry is `Path:'. The others are optional; some have default values if
31 they are not present. In the notation used below, (profile, default)
32 indicates whether the information is kept in the user's
36 context, and indicates what the default value is.
41 Sets the user's mail storage to \*(lqMail\*(rq. This is the
42 only mandatory profile entry. (profile, no default)
48 Declares the location of the
50 context file. This is overridden by the environment variable
55 (profile, default: $HOME/.mmh/context)
61 Keeps track of the current open folder.
62 (context, default: folder specified by \*(lqInbox\*(rq)
68 Defines the name of your default inbox.
69 (profile, default: inbox)
72 .BR Previous\-Sequence :
75 Names the sequence or sequences which should be defined as the `msgs' or
76 `msg' argument given to any
78 command. If not present or empty,
79 no such sequences are defined. Otherwise, for each name given, the
80 sequence is first zero'd and then each message is added to the sequence.
83 man page for the details about this sequence. (profile, no default)
86 .BR Sequence\-Negation :
89 Defines the string which, when prefixed to a sequence name, negates
90 that sequence. Hence, \*(lq!foo\*(rq means all those messages that
91 are not a member of the sequence \*(lqfoo\*(rq.
92 To deactivate this mechanism, define Sequence\-Negation to an empty value.
95 man page for the details. (profile, default: !)
98 .BR Unseen\-Sequence :
101 Names the sequence or sequences which shall contain any unread messages.
108 will add or remove messages from these
109 sequences when they are incorporated or read. If defined with an empty
110 value, no such sequences are defined. Otherwise, each message is
111 added to, or removed from, each sequence name given. Read the
113 man page for the details about this sequence.
114 (profile, default: u)
120 The name of the file in each folder which defines public sequences.
121 To disable the use of public sequences, leave the value portion of this
122 entry blank. (profile, default: \&.mh_sequences)
125 .BI atr\- seq \- folder :
128 Keeps track of the private sequence called \*(lqseq\*(rq in the specified
129 folder. Private sequences are generally used for read\-only folders.
132 man page for details about private sequences.
133 (context, no default)
139 Defines the editor to be used by the commands
145 (profile, default: vi)
156 (profile, default: %sendmailpath%)
162 The prefix that is prepended to the name of message files when they
163 are ``removed'' by rmm. This should typically be `,' or `#'.
164 (profile, default: `,')
170 Name of the link to the file to which you are replying or which you are
171 redistributing. See `$mhaltmsg' below.
172 (profile, default: `@')
175 .BR Attachment-Header :
178 The (pseudo) header in draft messages, that contains files to be attached
179 to the message on sending.
180 If you like to type a lot, name it `X-MH-Attachment'.
181 (profile, default: `Attach')
187 An octal number which defines the permission bits for new message files.
190 for an explanation of the octal number.
191 (profile, default: 0644)
194 .BR Folder\-Protect :
197 An octal number which defines the permission bits for new folder
200 for an explanation of the octal number.
201 (profile, default: 700)
207 Sets default switches to be used whenever the mmh program
209 is invoked. For example, one could override the \*(lqEditor:\*(rq profile
210 component when replying to messages by adding a component such as:
213 repl: \-editor /bin/ed
216 (profile, no defaults)
219 .IB lasteditor "-next:"
222 Names \*(lqnexteditor\*(rq to be the default editor after using
223 \*(lqlasteditor\*(rq. This takes effect at \*(lqWhat now?\*(rq prompt
231 the draft with \*(lqlasteditor\*(rq, the default editor is set to be
232 \*(lqnexteditor\*(rq. If the user types \*(lqedit\*(rq without any
233 arguments to \*(lqWhat now?\*(rq, then \*(lqnexteditor\*(rq is used.
234 (profile, no default)
240 The contents of the folder-stack for the
243 (context, no default)
252 auditfile in addition to its other tasks.
258 (profile, no default)
261 .BR Alternate\-Mailboxes :
262 mh@uci\-750a, bug-mh*
268 which addresses are really yours.
271 knows which addresses should be included in the
274 knows if the message really originated from you.
275 Addresses must be separated by a comma, and the hostnames listed should
276 be the \*(lqofficial\*(rq hostnames for the mailboxes you indicate, as
277 local nicknames for hosts are not replaced with their official site names.
278 For each address, if a host is not given, then that address on any host is
279 considered to be you. In addition, an asterisk (`*') may appear at either
280 or both ends of the mailbox and host to indicate wild-card matching.
281 (profile, default: your user-id)
288 Indicates aliases files for
292 This may be used instead of the
295 switch. (profile, no default)
301 Changes the default draft folder. Read the
303 man page for details. (profile, default: +drafts)
306 .BI digest\-issue\- list :
311 the last issue of the last volume sent for the digest
313 (context, no default)
316 .BI digest\-volume\- list :
321 the last volume sent for the digest
323 (context, no default)
331 your maildrop, if different from the default. This is
332 superseded by the environment variable
334 (profile, default: %mailspool%/$USER)
338 RAND MH System (agent: Marshall Rose)
342 your mail signature. This is superseded by the
347 is not set and this profile entry is not present, the \*(lqgcos\*(rq field of
348 the \fI/etc/passwd\fP file will be used; otherwise, on hosts where
350 was configured with the UCI option, the file
352 is consulted. Your signature will be added to the address
354 puts in the \*(lqFrom:\*(rq header; do not include an address in the
355 signature text. (profile, no default)
358 .SS "Process Profile Entries"
359 The following profile elements are used whenever an
361 program invokes some other program such as
363 The profile can be used to select alternate programs if the
364 user wishes. The default values are given in the examples.
370 This is the program used by
372 to process MIME composition files, created from drafts which require
379 This program is used to refile or link a message to another folder.
382 to file a copy of a message into a folder given
383 by a \*(lqFcc:\*(rq field. It is used by the draft folder facility in
390 message into another folder. It is used to refile a draft message in
393 directive at the \*(lqWhat now?\*(rq prompt.
401 to incorporate new mail when it
402 is invoked with no arguments.
408 This program is used to list the contents of a message in response
411 directive at the \*(lqWhat now?\*(rq prompt. It is
412 also used by the draft folder facility in
418 to display the draft message.
424 This is the program used to automatically mail various messages
425 and notifications. It is used by
429 option. It is used by
431 to post failure notices.
432 It is used to retrieve an external-body with access-type `mail-server'
433 (such as when storing the body with
440 This is the program used to filter messages in various ways. It
443 to filter and display the message headers
444 of MIME messages. When the
455 is used to filter the
456 message that you are forwarding, or to which you are replying.
467 to filter the copy of the message
468 that is sent to \*(lqBcc:\*(rq recipients.
474 This is the program used by
478 formatted message when displaying to a terminal. It is also the default
481 to display message bodies (or message parts) of type text/plain.
487 This is the program used by
496 post a message to the mail transport system.
502 This is the program used by
506 to delete a message from a folder.
512 This is the program to use by
514 to actually send the message
520 This is the program used by
522 to process and display non-text (MIME) messages.
528 This is the program used by
530 to filter and display text (non-MIME) messages.
536 This is the program invoked by
542 to query about the disposition of a composed draft message.
545 .SS "Environment Variables"
548 and its commands it also controlled by the
549 presence of certain environment variables.
551 Many of these environment variables are used internally by the
552 \*(lqWhat now?\*(rq interface. It's amazing all the information
553 that has to get passed via environment variables to make the
554 \*(lqWhat now?\*(rq interface look squeaky clean to the
556 user, isn't it? The reason for all this is that the
564 one of the standard shells. As a result, it's not possible to pass
565 information via an argument list. The convention is that environment
566 variables whose names are all upper-case are user-settable; those
567 whose names are lower-case only are used internally by mmh and should
568 not generally be set by the user.
572 option was set during
575 if this environment variable is set, then if the commands
580 are not given any `msgs'
581 arguments, then they will default to using the file indicated by
583 This is useful for getting the default behavior
584 supplied by the default
589 With this environment variable, you can specify an alternative
590 mmh directory. Personal mmh configuration files are located relative to
592 Non-absolute values are relative to the home directory.
593 This is one of the very few exceptions in
595 where non-absolute pathnames are not considered relative to the user's
601 With this environment variable, you can specify a profile
603 .I $HOME/.mmh/profile
607 that you invoke. If the value of
609 is not absolute, it will be presumed to start from the mmh directory.
614 With this environment variable, you can specify a
615 context other than the normal context file (as specified in
616 the profile). As always, unless the value of
618 is absolute, it will be presumed to start from your mmh directory.
623 With this environment variable, you can specify
624 the native character set you are using. You must be able to display
625 this character set on your terminal.
627 This variable is checked to see if a RFC-2047 header field should be
640 be called, since showmimeproc will be called if a text message uses
641 a character set that doesn't match
646 for matches against the charset parameter
647 of text contents to decide it the text content can be displayed
648 without modifications to your terminal. This variable is checked by
650 to decide what character set to specify in the charset
651 parameter of text contents containing 8\-bit characters.
653 When decoding text in such an alternate character set,
655 must be able to determine which characters are alphabetic, which
656 are control characters, etc. For many operating systems, this
657 will require enabling the support for locales (such as setting
658 the environment variable
667 the default maildrop. This supersedes the \*(lqMailDrop\*(rq profile entry.
676 your mail signature. This supersedes the \*(lqSignature\*(rq profile entry.
681 This variable tells all
683 programs your home directory
690 the default shell to run
699 The environment variable
701 is also consulted. In particular,
706 how to clear your terminal, and how
707 many columns wide your terminal is. They also tell
710 lines long your terminal screen is.
715 This is the alternate message.
721 during edit sessions so you can peruse the message being distributed or
722 replied to. The message is also available through a link called
723 \*(lq@\*(rq (if not changed by
725 in the current directory if your current working directory
726 and the message's folder are on the same UNIX filesystem.
731 This is the path to the working draft.
741 which file to ask \*(lqWhat now?\*(rq
764 about an alternate message associated with the
765 draft (the message being distributed or replied to).
775 that message re-distribution is occurring.
789 editor (unless overridden by
806 if annotations are to occur.
816 if annotations are to occur.
826 if annotations are to occur.
831 This is the folder containing the alternate message.
837 during edit sessions so you
838 can peruse other messages in the current folder besides the one being
839 distributed or replied to. The environment variable
853 .ta \w'%etcdir%/ExtraBigFileName 'u
854 ^$HOME/.mmh~^The user's mmh directory
855 ^or $MMH~^Rather than the standard mmh directory
856 ^$HOME/.mmh/profile~^The user's profile
857 ^or $MMHP~^Rather than the standard profile
858 ^$HOME/.mmh/context~^The user's context
859 ^or $MMHC~^Rather than the standard context
860 ^<folder>/.mh_sequences~^Public sequences for <folder>
864 nmh(1), environ(5), mh-sequence(7)
868 .I $HOME/.mmh/profile
869 contains only static information, which
873 update. Changes in context are made to the
874 .I $HOME/.mmh/context
876 This includes, but is not limited to: the \*(lqCurrent\-Folder\*(rq entry
877 and all private sequence information. Public sequence information is
878 kept in each folder in the file determined by the \*(lqMh\-Sequences\*(rq
879 profile entry (default is
880 .IR \&.mh_sequences ).
882 The profile may override the path of the
884 file, by specifying a \*(lqContext\*(rq entry.
885 As a result, you can actually have more than one set of
886 private sequences by using different context files.
889 The shell quoting conventions are not available in the profile.
890 Each token is separated by whitespace.
892 There is some question as to what kind of arguments should be placed
893 in the profile as options. In order to provide a clear answer, recall
894 command line semantics of all
896 programs: conflicting switches
901 may occur more than one time on the
902 command line, with the last switch taking effect. Other arguments, such
903 as message sequences, filenames and folders, are always remembered on
904 the invocation line and are not superseded by following arguments of
905 the same type. Hence, it is safe to place only switches (and their
906 arguments) in the profile.
910 program is being invoked again and again
911 with the same arguments, and those arguments aren't switches, then there
912 are a few possible solutions to this problem. The first is to create a
918 of your choice. By giving this link a different name, you can create
919 a new entry in your profile and use an alternate set of defaults for
922 command. Similarly, you could create a small shell script
925 program of your choice with an alternate set
926 of invocation line switches (using links and an alternate profile entry
927 is preferable to this solution).
931 user could create an alias for the command of the form:
934 alias cmd 'cmd arg1 arg2 ...'
937 In this way, the user can avoid lengthy type-in to the shell, and still
940 commands safely. (Recall that some
943 invoke others, and that in all cases, the profile is read, meaning that
944 aliases are disregarded beyond an initial command invocation)
projects / mmh / blob