1 .\"@ nail.1 - S-nail(1) reference manual.
3 .\" Copyright (c) 2000-2008 Gunnar Ritter, Freiburg i. Br., Germany.
4 .\" Copyright (c) 2012 - 2017 Steffen (Daode) Nurpmeso <steffen@sdaoden.eu>.
6 .\" Copyright (c) 1980, 1990, 1993
7 .\" The Regents of the University of California. All rights reserved.
9 .\" Redistribution and use in source and binary forms, with or without
10 .\" modification, are permitted provided that the following conditions
12 .\" 1. Redistributions of source code must retain the above copyright
13 .\" notice, this list of conditions and the following disclaimer.
14 .\" 2. Redistributions in binary form must reproduce the above copyright
15 .\" notice, this list of conditions and the following disclaimer in the
16 .\" documentation and/or other materials provided with the distribution.
17 .\" 3. Neither the name of the University nor the names of its contributors
18 .\" may be used to endorse or promote products derived from this software
19 .\" without specific prior written permission.
21 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
22 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
23 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
24 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
25 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
26 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
27 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
28 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
29 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
30 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
34 .\"@ S-nail(1): v14.9.0-rc1 / 2017-07-01
46 .\" If not ~/.mailrc, it breaks POSIX compatibility. And adjust main.c.
51 .ds OU [no v15-compat]
52 .ds ID [v15 behaviour may differ]
53 .ds NQ [Only new quoting rules]
64 .Nd send and receive Internet mail
70 .\" Keep in SYNC: ./nail.1:"SYNOPSIS, main()
79 .Op : Ns Fl a Ar attachment Ns \&:
80 .Op : Ns Fl b Ar bcc-addr Ns \&:
81 .Op : Ns Fl c Ar cc-addr Ns \&:
82 .Op Fl M Ar type | Fl m Ar file | Fl q Ar file | Fl t
85 .Fl S Ar var Ns Op Ns = Ns Ar value Ns
88 .Op : Ns Fl X Ar cmd Ns \&:
90 .Pf : Ar to-addr Ns \&:
91 .Op Fl Fl \~ Ns : Ns Ar mta-option Ns \&:
100 .Op Fl r Ar from-addr
102 .Fl S Ar var Ns Op Ns = Ns Ar value Ns
105 .Op : Ns Fl X Ar cmd Ns \&:
106 .Op Fl Fl \~ Ns : Ns Ar mta-option Ns \&:
115 .Op Fl r Ar from-addr
117 .Fl S Ar var Ns Op Ns = Ns Ar value Ns
119 .Op : Ns Fl X Ar cmd Ns \&:
121 .Op Fl Fl \~ Ns : Ns Ar mta-option Ns \&:
126 .Mx -toc -tree html pdf ps xhtml
129 .\" .Sh DESCRIPTION {{{
132 .Bd -filled -compact -offset indent
133 .Sy Compatibility note:
134 S-nail (\*(UA) will wrap up into \%S-mailx in v15.0 (circa 2018).
135 Backward incompatibility has to be expected \(en
138 .Sx "Shell-style argument quoting"
139 rules, for example, and shell metacharacters will become meaningful.
140 New and old behaviour is flagged \*(IN and \*(OU, and setting
143 .Sx "INTERNAL VARIABLES" ,
144 will choose new behaviour when applicable.
145 \*(OB flags what will vanish, and enabling
149 enables obsoletion warnings.
153 \*(UA provides a simple and friendly environment for sending and
155 It is intended to provide the functionality of the POSIX
157 command, but is MIME capable and optionally offers extensions for
158 line editing, S/MIME, SMTP and POP3, among others.
159 \*(UA divides incoming mail into its constituent messages and allows
160 the user to deal with them in any order.
164 .Sx "INTERNAL VARIABLES"
165 for manipulating messages and sending mail.
166 It provides the user simple editing capabilities to ease the composition
167 of outgoing messages, and increasingly powerful and reliable
168 non-interactive scripting capabilities.
170 .\" .Ss "Options" {{{
173 .Bl -tag -width ".It Fl BaNg"
176 Explicitly control which of the
178 shall be loaded: if the letter
180 is (case-insensitively) part of the
184 is loaded, likewise the letter
186 controls loading of the user's personal
188 file, whereas the letters
192 explicitly forbid loading of any resource files.
193 This option should be used by scripts: to avoid environmental noise they
196 from any configuration files and create a script-local environment,
197 explicitly setting any of the desired
198 .Sx "INTERNAL VARIABLES"
201 This option overrides
208 command for the given user email
210 after program startup is complete (all resource files are loaded, any
212 setting is being established; only
214 commands have not been evaluated yet).
215 Being a special incarnation of
217 macros for the purpose of bundling longer-lived
219 tings, activating such an email account also switches to the accounts
221 .Sx "primary system mailbox"
226 .It Fl a Ar file Ns Op Ar =input-charset Ns Op Ar #output-charset
229 to the message (for compose mode opportunities refer to
233 .Sx "Filename transformations"
236 will be performed, but shell word expansion is restricted to the tilde
240 not be accessible but contain a
242 character, then anything before the
244 will be used as the filename, anything thereafter as a character set
247 If an input character set is specified,
248 .Mx -ix "character set specification"
249 but no output character set, then the given input character set is fixed
250 as-is, and no conversion will be applied;
251 giving the empty string or the special string hyphen-minus
253 will be treated as if
255 has been specified (the default).
257 If an output character set has also been given then the conversion will
258 be performed exactly as specified and on-the-fly, not considering the
259 file's type and content.
260 As an exception, if the output character set is specified as the empty
261 string or hyphen-minus
263 then the default conversion algorithm (see
264 .Sx "Character sets" )
265 is applied (therefore no conversion is performed on-the-fly,
267 will be MIME-classified and its contents will be inspected first) \(em
268 without support for character set conversions
270 does not include the term
272 only this argument is supported.
275 (\*(OB: \*(UA will always use line-buffered output, to gain
276 line-buffered input even in batch mode enable batch mode via
281 Send a blind carbon copy to
288 .Sx "INTERNAL VARIABLES" ,
290 The option may be used multiple times.
292 .Sx "On sending mail, and non-interactive mode" .
296 Send carbon copies to the given receiver, if so allowed by
298 May be used multiple times.
303 the internal variable
305 which enables debug messages and disables message delivery,
306 among others; effectively turns almost any operation into a dry-run.
312 and thus discard messages with an empty message part body.
313 This command line option is \*(OB.
317 Just check if mail is present (in the system
319 or the one specified via
321 if yes, return an exit status of zero, a non-zero value otherwise.
322 To restrict the set of mails to consider in this evaluation a message
323 specification can be added with the option
328 Save the message to send in a file named after the local part of the
329 first recipient's address (instead of in
334 Read in the contents of the user's
336 .Sx "secondary mailbox"
338 (or the specified file) for processing;
339 when \*(UA is quit, it writes undeleted messages back to this file
345 argument will undergo some special
346 .Sx "Filename transformations"
351 is not a argument to the flag
353 but is instead taken from the command line after option processing has
357 that starts with a hyphen-minus, prefix with a relative path, as in
358 .Ql ./-hyphenbox.mbox .
364 and exit; a configurable summary view is available via the
370 Show a short usage summary.
376 to ignore tty interrupt signals.
382 of all messages that match the given
386 .Sx "Specifying messages"
391 option has been given in addition no header summary is produced,
392 but \*(UA will instead indicate via its exit status whether
398 note that any verbose output is suppressed in this mode and must instead
399 be enabled explicitly (e.g., by using the option
404 Special send mode that will flag standard input with the MIME
408 and use it as the main message body.
409 \*(ID Using this option will bypass processing of
410 .Va message-inject-head ,
413 .Va message-inject-tail .
419 Special send mode that will MIME classify the specified
421 and use it as the main message body.
422 \*(ID Using this option will bypass processing of
423 .Va message-inject-head ,
426 .Va message-inject-tail .
432 inhibit the initial display of message headers when reading mail or
437 for the internal variable
442 Standard flag that inhibits reading the system wide
447 allows more control over the startup sequence; also see
448 .Sx "Resource files" .
452 Special send mode that will initialize the message body with the
453 contents of the specified
455 which may be standard input
457 only in non-interactive context.
465 opened will be in read-only mode.
469 .It Fl r Ar from-addr
470 The source address that appears in the
473 header of a message (or in the
476 header if the former contains multiple addresses) is not used for
477 relaying and delegating a message over the wire via SMTP, but instead an
478 envelope will enwrap the message content and provide the necessary
479 information (i.e., the RFC 5321 reverse-path, also used to report, e.g.,
480 delivery errors) to transmit the message to its destination(s).
481 Whereas said headers and internal variables will be used by \*(UA to
482 create the envelope if the built-in SMTP
484 (Mail-Transfer-Agent) is used, a file-based MTA will instead use the
485 identity of the message-originating user.
487 This command line option can be used to specify the reverse-path, to be
488 passed to a file-based
490 when a message is sent, via
491 .Fl \&\&f Ar from-addr .
494 include a user name, then the address components will be separated and
495 the name part will be passed to a file-based
501 is also assigned to the internal variable
503 Many default installations and sites disallow explicit overriding of the
504 user identity which could be adjusted by this option, unless either
506 has been configured accordingly, or the user is member of a group with
507 special privileges, respectively.
509 If an empty string is passed as
511 then the content of the variable
513 (or, if that contains multiple addresses,
515 will be evaluated and used for this purpose whenever the file-based
518 Note that \*(UA by default, without
520 that is, neither passes
524 command line options to a file-based MTA by itself, unless this
525 automatic deduction is enforced by
527 ing the internal variable
528 .Va r-option-implicit .
532 .It Fl S Ar var Ns Op = Ns value
536 iable and, in case of a non-boolean variable which has a value, assign
540 .Sx "INTERNAL VARIABLES"
544 may be overwritten from within resource files,
545 the command line setting will be reestablished after all resource files
546 have been loaded in the order they have been given on the command line.
547 (\*(ID In the future such a setting may be in frozen state during startup.)
551 Specify the subject of the message to be sent.
552 Newline (NL) and carriage-return (CR) bytes are invalid and will be
553 normalized to space (SP) characters.
557 The message given (on standard input) is expected to contain, separated
558 from the message body by an empty line, a message header with
563 fields giving its recipients, which will be added to any recipients
564 specified on the command line.
565 If a message subject is specified via
567 then it will be used in favour of one given on the command line.
583 .Ql Mail-Followup-To: ,
584 by default created automatically dependent on message context, will
585 be used if specified (a special address massage will however still occur
587 Any other custom header field (also see
590 is passed through entirely
591 unchanged, and in conjunction with the option
593 it is possible to embed
594 .Sx "COMMAND ESCAPES" .
602 .Sx "primary system mailbox"
605 appropriate privileges presumed; effectively identical to
606 .Ql Fl \&\&f Ns \0%user .
615 will also show the list of
617 .Ql $ \*(uA -Xversion -Xx .
622 ting the internal variable
624 enables display of some informational context messages.
625 Using it twice increases the level of verbosity.
629 Add the given (or multiple for a multiline argument)
631 to the list of commands to be executed,
632 as a last step of program startup, before normal operation starts.
633 This is the only possibility to execute commands in non-interactive mode
634 when reading startup files is actively prohibited.
635 The commands will be evaluated as a unit, just as via
645 .Sx "COMMAND ESCAPES"
646 in compose mode even in non-interactive use cases.
647 This can be used to, e.g., automatically format the composed message
648 text before sending the message:
649 .Bd -literal -offset indent
650 $ ( echo 'line one. Word. Word2.';\e
651 echo '~| /usr/bin/fmt -tuw66' ) |\e
652 LC_ALL=C \*(uA -d~:/ -Sttycharset=utf-8 bob@exam.ple
657 Enables batch mode: standard input is made line buffered, the complete
658 set of (interactive) commands is available, processing of
659 .Sx "COMMAND ESCAPES"
660 is enabled in compose mode, and diverse
661 .Sx "INTERNAL VARIABLES"
662 are adjusted for batch necessities, exactly as if done via
678 The following prepares an email message in a batched dry run:
679 .Bd -literal -offset indent
680 $ LC_ALL=C printf 'm bob\en~s ubject\enText\en~.\enx\en' |\e
681 LC_ALL=C \*(uA -d#:/ -X'alias bob bob@exam.ple'
686 This flag forces termination of option processing in order to prevent
689 It also forcefully puts \*(UA into send mode, see
690 .Sx "On sending mail, and non-interactive mode" .
698 argument, as well as all receivers established by the command line options
702 are subject to checks established via
705 .Sx "INTERNAL VARIABLES" .
707 .Op Ar mta-option ...
709 arguments that are given at the end of the command line after a
711 separator will be passed through to a file-based
713 (Mail-Transfer-Agent) and persist for an entire (interactive) session
714 \(en if the setting of the internal variable
716 allows their recognition; no such constraints apply to the variable
720 .\" .Ss "A starter" {{{
723 \*(UA is a direct descendant of
725 Mail, a successor of the Research
728 .Dq was there from the start
731 It thus represents the user side of the
733 mail system, whereas the system side (Mail-Transfer-Agent, MTA) was
734 traditionally taken by
736 and most MTAs provide a binary of this name for compatibility purposes.
741 of \*(UA then the system side is not a mandatory precondition for mail
745 Because \*(UA strives for compliance with POSIX
747 it is likely that some configuration settings have to be adjusted before
748 using it is a smooth experience.
751 resource file bends those standard imposed settings of the
752 .Sx "INTERNAL VARIABLES"
753 a bit towards more user friendliness and safety, however, e.g., it
758 in order to suppress the automatic moving of messages to the
760 .Sx "secondary mailbox"
762 that would otherwise occur (see
763 .Sx "Message states" ) ,
766 to not remove empty system (MBOX) mailbox files in order not to mangle
767 file permissions when files eventually get recreated \(en
768 \*(UA will remove all empty (MBOX) mailbox files unless this variable is
771 mode has been enabled.
772 The file mode creation mask is explicitly managed via
774 symbolic links will not be followed when opening files for writing,
775 sufficient system support provided.
780 in order to synchronize \*(UA with the exit status report of the used
787 to enter interactive startup even if the initial mailbox is empty,
789 to allow editing of headers as well as
791 to not strip down addresses in compose mode, and
793 to include the message that is being responded to when
798 contains some more complete configuration examples.
801 .\" .Ss "On sending mail, and non-interactive mode" {{{
802 .Ss "On sending mail, and non-interactive mode"
804 To send a message to one or more people, using a local or a built-in
806 (Mail-Transfer-Agent) transport to actually deliver the generated mail
807 message, \*(UA can be invoked with arguments which are the names of
808 people to whom the mail will be sent, and the command line options
812 can be used to add (blind) carbon copy receivers:
814 .Bd -literal -offset indent
816 $ \*(uA -s ubject -a ttach.txt bill@exam.ple
818 # But... try it in an isolated dry-run mode (-d) first
819 $ LC_ALL=C \*(uA -d -:/ -Ssendwait -Sttycharset=utf8 \e
820 -b bcc@exam.ple -c cc@exam.ple \e
821 -. '(Lovely) Bob <bob@exam.ple>' eric@exam.ple
824 $ LC_ALL=C \*(uA -d -:/ -Sv15-compat -Ssendwait -Sttycharset=utf8 \e
825 -S mta=smtps://mylogin@exam.ple:465 -Ssmtp-auth=none \e
826 -S from=scriptreply@exam.ple \e
832 If standard input is a terminal rather than the message to be sent,
833 the user is expected to type in the message contents.
834 In this compose mode \*(UA treats lines beginning with the character
836 special \(en these are so-called
837 .Sx "COMMAND ESCAPES" ,
838 which can be used to read in files, process shell commands, add and edit
839 attachments and more; e.g., the command escape
841 will start the text editor to revise the message in its current state,
843 allows editing of the most important message headers, with
845 custom headers can be created (more specifically than with
848 gives an overview of most other available command escapes.
852 at the beginning of an empty line leaves compose mode and causes the
853 message to be sent, whereas typing
856 twice will abort the current letter (saving its contents in the file
867 .Sx "INTERNAL VARIABLES"
868 can be used to alter default behavior.
869 E.g., messages are sent asynchronously, without supervision, unless the
872 is set, therefore send errors will not be recognizable until then.
877 will automatically startup a text editor when compose mode is entered,
879 allows editing of headers additionally to plain body content, whereas
883 will cause the user to be prompted actively for (blind) carbon-copy
884 recipients, respectively, if the given list is empty.
887 Especially when using public mail provider accounts with the SMTP
889 it is often necessary to set
893 (even finer control via
894 .Va smtp-hostname ) ,
895 which (even if empty) also causes creation of
901 is set; saving a copy of sent messages in a
903 mailbox may be desirable \(en as for most mailbox
905 targets the value will undergo
906 .Sx "Filename transformations" .
909 for the purpose of arranging a complete environment of settings that can
910 be switched to with a single command or command line option may be
913 contains example configurations for sending messages via some of the
914 well-known public mail providers and also gives a compact overview on
915 how to setup a secure SSL/TLS environment).
920 sandbox dry-run tests first will prove correctness.
924 .Sx "On URL syntax and credential lookup"
925 will spread light on the different ways of how to specify user email
926 account credentials, the
928 variable chains, and accessing protocol-specific resources,
931 goes into the details of character encodings, and how to use them for
932 interpreting the input data given in
934 and representing messages and MIME part contents in
936 and reading the section
937 .Sx "The mime.types files"
938 should help to understand how the MIME-type of outgoing attachments are
939 classified, and what can be done for fine-tuning.
940 Over the wire an intermediate, configurable content-transfer-encoding
941 .Pf ( Va mime-encoding )
942 may be applied to the raw message part data.
945 Message recipients (as specified on the command line or defined in
950 may not only be email addressees but can also be names of mailboxes and
951 even complete shell command pipe specifications.
954 is not set then only network addresses (see
956 for a description of mail addresses) and plain user names (including MTA
957 aliases) may be used, other types will be filtered out, giving a warning
961 can be used to generate standard compliant network addresses.
963 .\" When changing any of the following adjust any RECIPIENTADDRSPEC;
964 .\" grep the latter for the complete picture
968 is set then extended recipient addresses will optionally be accepted:
969 Any name which starts with a vertical bar
971 character specifies a command pipe \(en the command string following the
973 is executed and the message is sent to its standard input;
974 Likewise, any name that starts with the character solidus
976 or the character sequence dot solidus
978 is treated as a file, regardless of the remaining content;
979 likewise a name that solely consists of a hyphen-minus
981 Any other name which contains a commercial at
983 character is treated as a network address;
984 Any other name which starts with a plus sign
986 character specifies a mailbox name;
987 Any other name which contains a solidus
989 character but no exclamation mark
993 character before also specifies a mailbox name;
994 What remains is treated as a network address.
996 .Bd -literal -offset indent
997 $ echo bla | \*(uA -Sexpandaddr -s test ./mbox.mbox
998 $ echo bla | \*(uA -Sexpandaddr -s test '|cat >> ./mbox.mbox'
999 $ echo safe | LC_ALL=C \e
1000 \*(uA -:/ -Sv15-compat -Ssendwait -Sttycharset=utf8 \e
1001 -Sexpandaddr=fail,-all,+addr,failinvaddr -s test \e
1006 It is possible to create personal distribution lists via the
1008 command, so that, for instance, the user can send mail to
1010 and have it go to a group of people.
1011 These aliases have nothing in common with the system wide aliases that
1012 may be used by the MTA, which are subject to the
1016 and are often tracked in a file
1022 Personal aliases will be expanded by \*(UA before the message is sent,
1023 and are thus a convenient alternative to specifying each addressee by
1024 itself; they correlate with the active set of
1031 .Dl alias cohorts bill jkf mark kridle@ucbcory ~/mail/cohorts.mbox
1034 .Va on-compose-enter , on-compose-leave
1036 .Va on-compose-cleanup
1037 hook variables may be set to
1039 d macros to automatically adjust some settings dependent
1040 on receiver, sender or subject contexts, and via the
1041 .Va on-compose-splice
1043 .Va on-compose-splice-shell
1044 variables, the former also to be set to a
1046 d macro, increasingly powerful mechanisms to perform automated message
1047 adjustments are available.
1048 (\*(ID These hooks work for commands which newly create messages, namely
1049 .Ic forward , mail , reply
1054 for now provide only the hooks
1057 .Va on-resend-cleanup . )
1060 To avoid environmental noise scripts should
1062 \*(UA from any configuration files and create a script-local
1063 environment, ideally with the command line options
1065 to disable any configuration file in conjunction with repetitions of
1067 to specify variables:
1069 .Bd -literal -offset indent
1070 $ env LC_ALL=C \*(uA -:/ \e
1071 -Sv15-compat -Ssendwait -Sttycharset=utf-8 \e
1072 -Sexpandaddr=fail,-all,failinvaddr \e
1073 -S mta=smtps://mylogin@exam.ple:465 -Ssmtp-auth=login \e
1074 -S from=scriptreply@exam.ple \e
1075 -s 'Subject to go' -a attachment_file \e
1076 -. 'Recipient 1 <rec1@exam.ple>' rec2@exam.ple \e
1081 As shown, scripts can
1083 a locale environment, the above specifies the all-compatible 7-bit clean
1086 but will nonetheless take and send UTF-8 in the message text by using
1088 In interactive mode, which is introduced in the next section, messages
1089 can be sent by calling the
1091 command with a list of recipient addresses:
1093 .Bd -literal -offset indent
1094 $ \*(uA -d -Squiet -Semptystart
1095 "/var/spool/mail/user": 0 messages
1096 ? mail "Recipient 1 <rec1@exam.ple>", rec2@exam.ple
1098 ? # Will do the right thing (tm)
1099 ? m rec1@exam.ple rec2@exam.ple
1103 .\" .Ss "On reading mail, and interactive mode" {{{
1104 .Ss "On reading mail, and interactive mode"
1106 When invoked without addressees \*(UA enters interactive mode in which
1108 When used like that the user's system
1112 for an in-depth description of the different mailbox types that exist)
1113 is read in and a one line header of each message therein is displayed.
1114 The visual style of this summary of
1116 can be adjusted through the variable
1118 and the possible sorting criterion via
1124 can be performed with the command
1126 If the initially opened mailbox is empty \*(UA will instead exit
1127 immediately (after displaying a message) unless the variable
1136 will give a listing of all available commands and
1138 will give a summary of some common ones.
1139 If the \*(OPal documentation strings are available one can type
1142 and see the actual expansion of
1144 and what its purpose is, i.e., commands can be abbreviated
1145 (note that POSIX defines some abbreviations, so that the alphabetical
1146 order of commands does not necessarily relate to the abbreviations; it is
1147 however possible to define overwrites with
1148 .Ic commandalias ) .
1149 These commands can also produce a more
1154 Messages are given numbers (starting at 1) which uniquely identify
1155 messages; the current message \(en the
1157 \(en will either be the first new message, or the first unread message,
1158 or the first message of the mailbox; the internal variable
1160 will instead cause usage of the last message for this purpose.
1165 ful of header summaries containing the
1169 will display only the summaries of the given messages, defaulting to the
1173 Message content can be displayed with the command
1180 controls whether and when \*(UA will use the configured
1182 for display instead of directly writing to the user terminal
1184 the sole difference to the command
1186 which will always use the
1190 will instead only show the first
1192 of a message (maybe even compressed if
1195 Message display experience may improve by setting and adjusting
1196 .Va mime-counter-evidence ,
1198 .Sx "HTML mail and MIME attachments" .
1201 By default the current message
1203 is displayed, but like with many other commands it is possible to give
1204 a fancy message specification (see
1205 .Sx "Specifying messages" ) ,
1208 will display all unread messages,
1213 will type the messages 1 and 5,
1215 will type the messages 1 through 5, and
1219 will display the last and the next message, respectively.
1222 (a more substantial alias for
1224 will display a header summary of the given message specification list
1225 instead of their content, e.g., the following will search for subjects:
1228 .Dl from "'@Some subject to search for'"
1231 In the default setup all header fields of a message will be
1233 d, but fields can be white- or blacklisted for a variety of
1234 applications by using the command
1236 e.g., to restrict display to a very restricted set:
1237 .Ql Ic \:headerpick Cd \:type retain Ar \:from to cc subject .
1238 In order to display all header fields of a message regardless of
1239 currently active ignore or retain lists, use the commands
1244 will show the raw message content.
1245 Note that historically the global
1247 not only adjusts the list of displayed headers, but also sets
1251 Dependent upon the configuration a line editor (see the section
1252 .Sx "On terminal control and line editor" )
1253 aims at making user experience with the many
1256 When reading the system
1262 specified a mailbox explicitly prefixed with the special
1264 modifier (propagating the mailbox to a
1266 .Sx "primary system mailbox" ) ,
1267 then messages which have been read will be moved to a
1269 .Sx "secondary mailbox" ,
1272 file, automatically when the mailbox is left, either by changing the
1273 active mailbox or by quitting \*(UA (also see
1274 .Sx "Message states" )
1275 \(en this automatic moving from a system or primary to the secondary
1276 mailbox is not performed when the variable
1279 Messages can also be explicitly
1281 d to other mailboxes, whereas
1283 keeps the original message.
1285 can be used to write out data content of specific parts of messages.
1288 After examining a message the user can
1290 to the sender and all recipients (which will also be placed in
1293 .Va recipients-in-cc
1296 exclusively to the sender(s).
1298 ing a message will allow editing the new message: the original message
1299 will be contained in the message body, adjusted according to
1301 When replying to or forwarding a message recipient addresses will be
1302 stripped from comments and names unless the internal variable
1309 messages: the former will add a series of
1311 headers, whereas the latter will not; different to newly created
1312 messages editing is not possible and no copy will be saved even with
1314 unless the additional variable
1317 Of course messages can also be
1319 but can spring into existence again via
1321 or when the \*(UA session is ended via the
1326 To end a mail processing session one may either issue
1328 to cause a full program exit, which possibly includes
1329 automatic moving of read messages to the
1331 .Sx "secondary mailbox"
1333 as well as updating the \*(OPal line editor
1337 instead in order to prevent any of these actions.
1340 .\" .Ss "HTML mail and MIME attachments" {{{
1341 .Ss "HTML mail and MIME attachments"
1343 Messages which are HTML-only become more and more common and of course
1344 many messages come bundled with a bouquet of MIME (Multipurpose Internet
1345 Mail Extensions) parts for, e.g., attachments.
1346 To get a notion of MIME types, \*(UA will first read
1347 .Sx "The mime.types files"
1348 (as configured and allowed by
1349 .Va mimetypes-load-control ) ,
1350 and then add onto that types registered directly with
1352 It (normally) has a default set of types built-in, too.
1353 To improve interaction with faulty MIME part declarations which are
1354 often seen in real-life messages, setting
1355 .Va mime-counter-evidence
1356 will allow \*(UA to verify the given assertion and possibly provide
1357 an alternative MIME type.
1360 Whereas \*(UA \*(OPally supports a simple HTML-to-text converter for
1361 HTML messages, it cannot handle MIME types other than plain text itself.
1362 Instead programs need to become registered to deal with specific MIME
1363 types or file extensions.
1364 These programs may either prepare plain text versions of their input in
1365 order to enable \*(UA to integrate their output neatlessly in its own
1366 message visualization (a mode which is called
1367 .Cd copiousoutput ) ,
1368 or display the content themselves, for example in an external graphical
1369 window: such handlers will only be considered by and for the command
1373 To install a handler program for a specific MIME type an according
1374 .Va pipe-TYPE/SUBTYPE
1375 variable needs to be set; to instead define a handler for a specific
1376 file extension the respective
1378 variable can be used \(en these handlers take precedence.
1379 \*(OPally \*(UA supports mail user agent configuration as defined in
1380 RFC 1524; this mechanism (see
1381 .Sx "The Mailcap files" )
1382 will be queried for display or quote handlers if none of the former two
1383 .\" TODO v15-compat "will be" -> "is"
1384 did; it will be the sole source for handlers of other purpose.
1385 A last source for handlers is the MIME type definition itself, when
1386 a (\*(UA specific) type-marker was registered with the command
1388 (which many built-in MIME types do).
1391 E.g., to display a HTML message inline (that is, converted to a more
1392 fancy plain text representation than the built-in converter is capable to
1393 produce) with either of the text-mode browsers
1397 teach \*(UA about MathML documents and make it display them as plain
1398 text, and to open PDF attachments in an external PDF viewer,
1399 asynchronously and with some other magic attached:
1401 .Bd -literal -offset indent
1402 if [ "$features" !@ +filter-html-tagsoup ]
1403 #set pipe-text/html='@* elinks -force-html -dump 1'
1404 set pipe-text/html='@* lynx -stdin -dump -force_html'
1405 # Display HTML as plain text instead
1406 #set pipe-text/html=@
1408 mimetype @ application/mathml+xml mathml
1409 wysh set pipe-application/pdf='@&=@ \e
1410 trap "rm -f \e"${MAILX_FILENAME_TEMPORARY}\e"" EXIT;\e
1411 trap "trap \e"\e" INT QUIT TERM; exit 1" INT QUIT TERM;\e
1412 mupdf "${MAILX_FILENAME_TEMPORARY}"'
1416 .\" .Ss "Mailing lists" {{{
1419 \*(UA offers some support to ease handling of mailing lists.
1422 promotes all given arguments to known mailing lists, and
1424 sets their subscription attribute, creating them first as necessary.
1429 automatically, but only resets the subscription attribute.)
1430 Using the commands without arguments will show (a subset of) all
1431 currently defined mailing lists.
1436 can be used to mark out messages with configured list addresses
1437 in the header display.
1440 \*(OPally mailing lists may also be specified as (extended) regular
1441 expressions, which allows matching of many addresses with a single
1443 However, all fully qualified list addresses are matched via a fast
1444 dictionary, whereas expressions are placed in (a) list(s) which is
1445 (are) matched sequentially.
1447 .Bd -literal -offset indent
1448 set followup-to followup-to-honour=ask-yes reply-to-honour=ask-yes
1449 wysh mlist a1@b1.c1 a2@b2.c2 '.*@lists\e.c3$'
1450 mlsubscribe a4@b4.c4 exact@lists.c3
1455 .Va followup-to-honour
1457 .Ql Mail-\:Followup-\:To:
1458 header is honoured when the message is being replied to (via
1464 controls whether this header is created when sending mails; it will be
1465 created automatically for a couple of reasons, too, like when the
1467 .Dq mailing list specific
1472 is used to respond to a message with its
1473 .Ql Mail-Followup-To:
1477 A difference in between the handling of known and subscribed lists is
1478 that the address of the sender is usually not part of a generated
1479 .Ql Mail-Followup-To:
1480 when addressing the latter, whereas it is for the former kind of lists.
1481 Usually because there are exceptions: say, if multiple lists are
1482 addressed and not all of them are subscribed lists.
1484 For convenience \*(UA will, temporarily, automatically add a list
1485 address that is presented in the
1487 header of a message that is being responded to to the list of known
1489 Shall that header have existed \*(UA will instead, dependent on the
1491 .Va reply-to-honour ,
1494 for this purpose in order to accept a list administrators' wish that
1495 is supposed to have been manifested like that (but only if it provides
1496 a single address which resides on the same domain as what is stated in
1500 .\" .Ss "Resource files" {{{
1501 .Ss "Resource files"
1503 Upon startup \*(UA reads in several resource files:
1505 .Bl -tag -width ".It Pa BaNg"
1508 System wide initialization file.
1509 Reading of this file can be suppressed, either by using the
1511 (and according argument) or
1513 command line options, or by setting the
1516 .Ev MAILX_NO_SYSTEM_RC .
1520 File giving initial commands.
1521 A different file can be chosen by setting the
1525 Reading of this file can be suppressed with the
1527 command line option.
1529 .It Va mailx-extra-rc
1530 Can be used to define an optional startup file to be read after all
1531 other resource files.
1532 It can be used to specify settings that are not understood by other
1534 implementations, for example.
1535 This variable is only honoured when defined in a resource file, e.g.,
1537 .Sx "INTERNAL VARIABLES" .
1541 The content of these files is interpreted as follows:
1544 .Bl -bullet -compact
1546 The whitespace characters space, tabulator and newline,
1547 as well as those defined by the variable
1549 are removed from the beginning and end of input lines.
1551 Empty lines are ignored.
1553 Any other line is interpreted as a command.
1554 It may be spread over multiple input lines if the newline character is
1556 by placing a reverse solidus character
1558 as the last character of the line; whereas any leading whitespace of
1559 follow lines is ignored, trailing whitespace before a escaped newline
1560 remains in the input.
1562 If the line (content) starts with the number sign
1564 then it is a comment-command \(en a real command! \(en and also ignored.
1565 This command is the only form of comment that is understood.
1569 Unless \*(UA is about to enter interactive mode syntax errors that occur
1570 while loading these files are treated as errors and cause program exit.
1571 More files with syntactically equal content can be
1573 The following, saved in a file, would be an examplary content:
1575 .Bd -literal -offset indent
1576 # This line is a comment command. And y\e
1577 es, it is really continued here.
1584 .\" .Ss "Character sets" {{{
1585 .Ss "Character sets"
1587 \*(OP \*(UA detects the character set of the terminal by using
1588 mechanisms that are controlled by the
1594 in that order; see there) environment variable, the internal variable
1596 will be set to the detected terminal character set accordingly,
1597 and will thus show up in the output of commands like, e.g.,
1603 However, the user may give a value for
1605 during startup, so that it is possible to send mail in a completely
1607 locale environment, an option which can be used to generate and send,
1608 e.g., 8-bit UTF-8 input data in a pure 7-bit US-ASCII
1610 environment (an example of this can be found in the section
1611 .Sx "On sending mail, and non-interactive mode" ) .
1612 Changing the value does not mean much beside that, because several
1613 aspects of the real character set are implied by the locale environment
1614 of the system, which stays unaffected by
1618 If the \*(OPal character set conversion capabilities are not available
1620 does not include the term
1624 will be the only supported character set,
1625 it is simply assumed that it can be used to exchange 8-bit messages
1626 (over the wire an intermediate configurable content-transfer-encoding,
1629 and the rest of this section does not apply;
1630 it may however still be necessary to explicitly set it if automatic
1631 detection fails, since in that case it defaults to
1632 .\" (Keep in SYNC: ./nail.1:"Character sets", ./config.h:CHARSET_*!)
1633 LATIN1 a.k.a. ISO-8859-1.
1636 \*(OP When reading messages, their text is converted into
1638 as necessary in order to display them on the users terminal.
1639 Unprintable characters and invalid byte sequences are detected
1640 and replaced by proper substitution characters.
1641 Character set mappings for source character sets can be established with
1644 which may be handy to work around faulty character set catalogues (e.g.,
1645 to add a missing LATIN1 to ISO-8859-1 mapping), or to enforce treatment
1646 of one character set as another one (e.g., to interpret LATIN1 as CP1252).
1648 .Va charset-unknown-8bit
1649 to deal with another hairy aspect of message interpretation.
1652 When sending messages all their parts and attachments are classified.
1653 Whereas no character set conversion is performed on those parts which
1654 appear to be binary data,
1655 the character set being used must be declared within the MIME header of
1656 an outgoing text part if it contains characters that do not conform to
1657 the set of characters that are allowed by the email standards.
1658 Permissible values for character sets used in outgoing messages can be
1663 which defines a catch-all last-resort fallback character set that is
1664 implicitly appended to the list of character sets in
1668 When replying to a message and the variable
1669 .Va reply-in-same-charset
1670 is set then the character set of the message being replied to is tried
1671 first (after mapping via
1672 .Ic charsetalias ) .
1673 And it is also possible to make \*(UA work even more closely related to
1674 the current locale setting automatically by using the variable
1675 .Va sendcharsets-else-ttycharset ,
1676 please see there for more information.
1679 All the specified character sets are tried in order unless the
1680 conversion of the part or attachment succeeds.
1681 If none of the tried (8-bit) character sets is capable to represent the
1682 content of the part or attachment,
1683 then the message will not be sent and its text will optionally be
1687 In general, if a message saying
1688 .Dq cannot convert from a to b
1689 appears, either some characters are not appropriate for the currently
1690 selected (terminal) character set,
1691 or the needed conversion is not supported by the system.
1692 In the first case, it is necessary to set an appropriate
1694 locale and/or the variable
1698 The best results are usually achieved when \*(UA is run in a UTF-8
1699 locale on an UTF-8 capable terminal, in which case the full Unicode
1700 spectrum of characters is available.
1701 In this setup characters from various countries can be displayed,
1702 while it is still possible to use more simple character sets for sending
1703 to retain maximum compatibility with older mail clients.
1706 On the other hand the POSIX standard defines a locale-independent 7-bit
1707 .Dq portable character set
1708 that should be used when overall portability is an issue, the even more
1709 restricted subset named
1710 .Dq portable filename character set
1711 consists of A-Z, a-z, 0-9, period
1719 .\" .Ss "Message states" {{{
1720 .Ss "Message states"
1722 \*(UA differentiates in between several different message states;
1723 the current state will be reflected in header summary displays if
1725 is configured to do so (via the internal variable
1727 and messages can also be selected and be acted upon depending on their
1729 .Sx "Specifying messages" ) .
1730 When operating on the system
1734 .Sx "primary system mailbox" ,
1735 special actions, like the automatic moving of messages to the
1737 .Sx "secondary mailbox"
1739 may be applied when the mailbox is left (also implicitly via
1740 a successful exit of \*(UA, but not if the special command
1742 is used) \(en however, because this may be irritating to users which
1745 mail-user-agents, the default global
1751 variables in order to suppress this behaviour.
1753 .Bl -hang -width ".It Ql new"
1755 Message has neither been viewed nor moved to any other state.
1756 Such messages are retained even in the
1758 .Sx "primary system mailbox" .
1761 Message has neither been viewed nor moved to any other state, but the
1762 message was present already when the mailbox has been opened last:
1763 Such messages are retained even in the
1765 .Sx "primary system mailbox" .
1768 The message has been processed by one of the following commands:
1787 will always try to automatically
1793 logical message, and may thus mark multiple messages as read, the
1795 command will do so if the internal variable
1800 command is used, messages that are in a
1802 .Sx "primary system mailbox"
1805 state when the mailbox is left will be saved in the
1807 .Sx "secondary mailbox"
1809 unless the internal variable
1814 The message has been processed by one of the following commands:
1820 can be used to access such messages.
1823 The message has been processed by a
1825 command and it will be retained in its current location.
1828 The message has been processed by one of the following commands:
1834 command is used, messages that are in a
1836 .Sx "primary system mailbox"
1839 state when the mailbox is left will be deleted; they will be saved in the
1841 .Sx "secondary mailbox"
1843 when the internal variable
1849 In addition to these message states, flags which otherwise have no
1850 technical meaning in the mail system except allowing special ways of
1851 addressing them when
1852 .Sx "Specifying messages"
1853 can be set on messages.
1854 These flags are saved with messages and are thus persistent, and are
1855 portable between a set of widely used MUAs.
1857 .Bl -hang -width ".It Ic answered"
1859 Mark messages as having been answered.
1861 Mark messages as being a draft.
1863 Mark messages which need special attention.
1867 .\" .Ss "Specifying messages" {{{
1868 .Ss "Specifying messages"
1875 can be given a list of message numbers as arguments to apply to a number
1876 of messages at once.
1879 deletes messages 1 and 2,
1882 will delete the messages 1 through 5.
1883 In sorted or threaded mode (see the
1887 will delete the messages that are located between (and including)
1888 messages 1 through 5 in the sorted/threaded order, as shown in the
1891 The following special message names exist:
1894 .Bl -tag -width ".It Ar BaNg"
1896 The current message, the so-called
1900 The message that was previously the current message.
1903 The parent message of the current message,
1904 that is the message with the Message-ID given in the
1906 field or the last entry of the
1908 field of the current message.
1911 The next previous undeleted message,
1912 or the next previous deleted message for the
1915 In sorted/threaded mode,
1916 the next previous such message in the sorted/threaded order.
1919 The next undeleted message,
1920 or the next deleted message for the
1923 In sorted/threaded mode,
1924 the next such message in the sorted/threaded order.
1927 The first undeleted message,
1928 or the first deleted message for the
1931 In sorted/threaded mode,
1932 the first such message in the sorted/threaded order.
1936 In sorted/threaded mode,
1937 the last message in the sorted/threaded order.
1941 selects the message addressed with
1945 is any other message specification,
1946 and all messages from the thread that begins at it.
1947 Otherwise it is identical to
1952 the thread beginning with the current message is selected.
1957 All messages that were included in the
1958 .Sx "Message list arguments"
1959 of the previous command.
1962 An inclusive range of message numbers.
1963 Selectors that may also be used as endpoints include any of
1968 .Dq any substring matches
1971 header, which will match addresses (too) even if
1973 is set (and POSIX says
1974 .Dq any address as shown in a header summary shall be matchable in this form ) ;
1977 variable is set, only the local part of the address is evaluated
1978 for the comparison, not ignoring case, and the setting of
1980 is completely ignored.
1981 For finer control and match boundaries use the
1985 .It Ar / Ns Ar string
1986 All messages that contain
1988 in the subject field (case ignored).
1995 the string from the previous specification of that type is used again.
1997 .It Xo Op Ar @ Ns Ar name-list Ns
2000 All messages that contain the given case-insensitive search
2002 ession; if the \*(OPal regular expression (see
2004 support is available
2006 will be interpreted as (an extended) one if any of the
2008 (extended) regular expression characters is seen: in this case this
2009 should match strings correctly which are in the locale
2013 .Ar @ Ns Ar name-list
2014 part is missing, the search is restricted to the subject field body,
2017 specifies a comma-separated list of header fields to search, as in
2019 .Dl '@to,from,cc@Someone i ought to know'
2021 In order to search for a string that includes a
2023 (commercial at) character the
2025 is effectively non-optional, but may be given as the empty string.
2026 Some special header fields may be abbreviated:
2040 respectively and case-insensitively.
2045 can be used to search in (all of) the header(s) of the message, and the
2054 can be used to perform full text searches \(en whereas the former
2055 searches only the body, the latter also searches the message header.
2057 This message specification performs full text comparison, but even with
2058 regular expression support it is almost impossible to write a search
2059 expression that savely matches only a specific address domain.
2060 To request that the content of the header is treated as a list of
2061 addresses, and to strip those down to the plain email address which the
2062 search expression is to be matched against, prefix the header name
2063 (abbreviation) with a tilde
2066 .Dl @~f@@a\e.safe\e.domain\e.match$
2069 All messages of state
2073 is one or multiple of the following colon modifiers:
2075 .Bl -tag -compact -width ".It Ar :M"
2080 Old messages (any not in state
2102 messages (cf. the variable
2103 .Va markanswered ) .
2108 \*(OP Messages classified as spam (see
2109 .Sx "Handling spam" . )
2111 \*(OP Messages with unsure spam classification.
2117 \*(OP IMAP-style SEARCH expressions may also be used.
2118 This addressing mode is available with all types of mailbox
2120 s; \*(UA will perform the search locally as necessary.
2121 Strings must be enclosed by double quotes
2123 in their entirety if they contain whitespace or parentheses;
2124 within the quotes, only reverse solidus
2126 is recognized as an escape character.
2127 All string searches are case-insensitive.
2128 When the description indicates that the
2130 representation of an address field is used,
2131 this means that the search string is checked against both a list
2134 .Bd -literal -offset indent
2135 (\*qname\*q \*qsource\*q \*qlocal-part\*q \*qdomain-part\*q)
2140 and the addresses without real names from the respective header field.
2141 These search expressions can be nested using parentheses, see below for
2145 .Bl -tag -compact -width ".It Ar _n_u"
2146 .It Ar ( criterion )
2147 All messages that satisfy the given
2149 .It Ar ( criterion1 criterion2 ... criterionN )
2150 All messages that satisfy all of the given criteria.
2152 .It Ar ( or criterion1 criterion2 )
2153 All messages that satisfy either
2158 To connect more than two criteria using
2160 specifications have to be nested using additional parentheses,
2162 .Ql (or a (or b c)) ,
2166 .Ql ((a or b) and c) .
2169 operation of independent criteria on the lowest nesting level,
2170 it is possible to achieve similar effects by using three separate
2174 .It Ar ( not criterion )
2175 All messages that do not satisfy
2177 .It Ar ( bcc \*q Ns Ar string Ns Ar \*q )
2178 All messages that contain
2180 in the envelope representation of the
2183 .It Ar ( cc \*q Ns Ar string Ns Ar \*q )
2184 All messages that contain
2186 in the envelope representation of the
2189 .It Ar ( from \*q Ns Ar string Ns Ar \*q )
2190 All messages that contain
2192 in the envelope representation of the
2195 .It Ar ( subject \*q Ns Ar string Ns Ar \*q )
2196 All messages that contain
2201 .It Ar ( to \*q Ns Ar string Ns Ar \*q )
2202 All messages that contain
2204 in the envelope representation of the
2207 .It Ar ( header name \*q Ns Ar string Ns Ar \*q )
2208 All messages that contain
2213 .It Ar ( body \*q Ns Ar string Ns Ar \*q )
2214 All messages that contain
2217 .It Ar ( text \*q Ns Ar string Ns Ar \*q )
2218 All messages that contain
2220 in their header or body.
2221 .It Ar ( larger size )
2222 All messages that are larger than
2225 .It Ar ( smaller size )
2226 All messages that are smaller than
2230 .It Ar ( before date )
2231 All messages that were received before
2233 which must be in the form
2237 denotes the day of the month as one or two digits,
2239 is the name of the month \(en one of
2240 .Ql Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec ,
2243 is the year as four digits, e.g.,
2247 All messages that were received on the specified date.
2248 .It Ar ( since date )
2249 All messages that were received since the specified date.
2250 .It Ar ( sentbefore date )
2251 All messages that were sent on the specified date.
2252 .It Ar ( senton date )
2253 All messages that were sent on the specified date.
2254 .It Ar ( sentsince date )
2255 All messages that were sent since the specified date.
2257 The same criterion as for the previous search.
2258 This specification cannot be used as part of another criterion.
2259 If the previous command line contained more than one independent
2260 criterion then the last of those criteria is used.
2264 .\" .Ss "On URL syntax and credential lookup" {{{
2265 .Ss "On URL syntax and credential lookup"
2267 \*(IN For accessing protocol-specific resources usage of Uniform
2268 Resource Locators (URL, RFC 1738) has become omnipresent.
2269 \*(UA expects and understands URLs in the following form;
2272 denote optional parts, optional either because there also exist other
2273 ways to define the information in question or because support of the
2274 part is protocol-specific (e.g.,
2276 is used by the local maildir and the IMAP protocol, but not by POP3);
2281 are specified they must be given in URL percent encoded form (RFC 3986;
2287 .Dl PROTOCOL://[USER[:PASSWORD]@]server[:port][/path]
2290 Note that these \*(UA URLs most often do not conform to any real
2291 standard, but instead represent a normalized variant of RFC 1738 \(en
2292 they are not used in data exchange but only meant as a compact,
2293 easy-to-use way of defining and representing information in
2294 a well-known notation.
2297 Many internal variables of \*(UA exist in multiple versions, called
2298 variable chains for the rest of this document: the plain
2303 .Ql variable-USER@HOST .
2310 had been specified in the respective URL, otherwise it refers to the plain
2316 that had been found when doing the user chain lookup as is described
2319 will never be in URL percent encoded form, whether it came from an URL
2320 or not; i.e., variable chain name extensions of
2321 .Sx "INTERNAL VARIABLES"
2322 must not be URL percent encoded.
2325 For example, whether an hypothetical URL
2326 .Ql smtp://hey%3Ayou@our.house
2327 had been given that includes a user, or whether the URL was
2328 .Ql smtp://our.house
2329 and the user had been found differently, to lookup the variable chain
2330 .Va smtp-use-starttls
2331 \*(UA first looks for whether
2332 .Ql smtp-\:use-\:starttls-\:hey:you@our.house
2333 is defined, then whether
2334 .Ql smtp-\:use-\:starttls-\:our.house
2335 exists before finally ending up looking at the plain variable itself.
2338 \*(UA obeys the following logic scheme when dealing with the
2339 necessary credential information of an account:
2345 has been given in the URL the variables
2349 are looked up; if no such variable(s) can be found then \*(UA will,
2350 when enforced by the \*(OPal variables
2351 .Va netrc-lookup-HOST
2358 specific entry which provides a
2360 name: this lookup will only succeed if unambiguous (one possible matching
2363 It is possible to load encrypted
2368 If there is still no
2370 then \*(UA will fall back to the user who is supposed to run \*(UA,
2371 the identity of which has been fixated during \*(UA startup and is
2372 known to be a valid user on the current host.
2375 Authentication: unless otherwise noted this will lookup the
2376 .Va PROTOCOL-auth-USER@HOST , PROTOCOL-auth-HOST , PROTOCOL-auth
2377 variable chain, falling back to a protocol-specific default should this
2383 has been given in the URL, then if the
2385 has been found through the \*(OPal
2387 that may have already provided the password, too.
2388 Otherwise the variable chain
2389 .Va password-USER@HOST , password-HOST , password
2390 is looked up and used if existent.
2392 Afterwards the complete \*(OPal variable chain
2393 .Va netrc-lookup-USER@HOST , netrc-lookup-HOST , netrc-lookup
2397 cache is searched for a password only (multiple user accounts for
2398 a single machine may exist as well as a fallback entry without user
2399 but with a password).
2401 If at that point there is still no password available, but the
2402 (protocols') chosen authentication type requires a password, then in
2403 interactive mode the user will be prompted on the terminal.
2408 S/MIME verification works relative to the values found in the
2412 header field(s), which means that the values of
2413 .Va smime-sign , smime-sign-cert , smime-sign-include-certs
2415 .Va smime-sign-message-digest
2416 will not be looked up using the
2420 chains from above but instead use the corresponding values from the
2421 message that is being worked on.
2422 In unusual cases multiple and different
2426 combinations may therefore be involved \(en on the other hand those
2427 unusual cases become possible.
2428 The usual case is as short as:
2431 .Dl set mta=smtp://USER:PASS@HOST smtp-use-starttls \e
2432 .Dl \ \ \ \ smime-sign smime-sign-cert=+smime.pair
2437 contains complete example configurations.
2440 .\" .Ss "On terminal control and line editor" {{{
2441 .Ss "On terminal control and line editor"
2443 \*(OP Terminal control will be realized through one of the standard
2445 libraries, either the
2447 or, alternatively, the
2449 both of which will be initialized to work with the environment variable
2451 Terminal control will enhance or enable interactive usage aspects, e.g.,
2452 .Sx "Coloured display" ,
2453 and extend behaviour of the Mailx-Line-Editor (MLE), which may learn the
2454 byte-sequences of keys like the cursor and function keys.
2455 The internal variable
2457 can be used to overwrite settings or to learn (correct(ed)) keycodes.
2458 \*(UA may also become a full-screen application by entering the
2459 so-called ca-mode and switching to an alternative \*(UA-exclusive screen
2460 shall the terminal support it and the internal variable
2462 has been set explicitly.
2463 Actual interaction with the chosen library can be disabled completely by
2464 setting the internal variable
2465 .Va termcap-disable ;
2467 will be queried regardless, even if the \*(OPal support for the
2468 libraries has not been enabled at configuration time.
2471 \*(OP The built-in \*(UA Mailx-Line-Editor (MLE) should work in all
2472 environments which comply to the ISO C standard
2474 and will support wide glyphs if possible (the necessary functionality
2475 had been removed from ISO C, but was included in
2477 Prevent usage of a line editor in interactive mode by setting the
2479 .Va line-editor-disable .
2480 Especially if the \*(OPal terminal control support is missing setting
2481 entries in the internal variable
2483 will help shall the MLE misbehave, see there for more.
2484 The MLE can support a little bit of
2490 feature is available then input from line editor prompts will be saved
2491 in a history list that can be searched in and be expanded from.
2492 Such saving can be prevented by prefixing input with any amount of
2494 Aspects of history, like allowed content and maximum size, as well as
2495 whether history shall be saved persistently, can be configured with the
2499 .Va history-gabby-persist
2504 The MLE supports a set of editing and control commands.
2505 By default (as) many (as possible) of these will be assigned to a set of
2506 single-letter control codes, which should work on any terminal (and can
2507 be generated by holding the
2509 key while pressing the key of desire, e.g.,
2513 command is available then the MLE commands can also be accessed freely
2514 by assigning the command name, which is shown in parenthesis in the list
2515 below, to any desired key-sequence, and the MLE will instead and also use
2517 to establish its built-in key bindings
2518 (more of them if the \*(OPal terminal control is available),
2519 an action which can then be suppressed completely by setting
2520 .Va line-editor-no-defaults .
2521 .Sx "Shell-style argument quoting"
2522 notation is used in the following;
2523 combinations not mentioned either cause job control signals or do not
2524 generate a (unique) keycode:
2528 .Bl -tag -compact -width ".It Ql Ba"
2530 Go to the start of the line
2532 .Pf ( Cd mle-go-home ) .
2535 Move the cursor backward one character
2537 .Pf ( Cd mle-go-bwd ) .
2540 Forward delete the character under the cursor;
2541 quits \*(UA if used on the empty line unless the internal variable
2545 .Pf ( Cd mle-del-fwd ) .
2548 Go to the end of the line
2550 .Pf ( Cd mle-go-end ) .
2553 Move the cursor forward one character
2555 .Pf ( Cd mle-go-fwd ) .
2558 Cancel current operation, full reset.
2559 If there is an active history search or tabulator expansion then this
2560 command will first reset that, reverting to the former line content;
2561 thus a second reset is needed for a full reset in this case
2563 .Pf ( Cd mle-reset ) .
2566 Backspace: backward delete one character
2568 .Pf ( Cd mle-del-bwd ) .
2572 Horizontal tabulator:
2573 try to expand the word before the cursor, supporting the usual
2574 .Sx "Filename transformations"
2576 .Pf ( Cd mle-complete ) .
2578 .Cd mle-quote-rndtrip .
2582 commit the current line
2584 .Pf ( Cd mle-commit ) .
2587 Cut all characters from the cursor to the end of the line
2589 .Pf ( Cd mle-snarf-end ) .
2594 .Pf ( Cd mle-repaint ) .
2597 \*(OP Go to the next history entry
2599 .Pf ( Cd mle-hist-fwd ) .
2602 (\*(OPally context-dependent) Invokes the command
2606 \*(OP Go to the previous history entry
2608 .Pf ( Cd mle-hist-bwd ) .
2611 Toggle roundtrip mode shell quotes, where produced,
2614 .Pf ( Cd mle-quote-rndtrip ) .
2615 This setting is temporary, and will be forgotten once the command line
2616 is committed; also see
2620 \*(OP Complete the current line from (the remaining) older history entries
2622 .Pf ( Cd mle-hist-srch-bwd ) .
2625 \*(OP Complete the current line from (the remaining) newer history entries
2627 .Pf ( Cd mle-hist-srch-fwd ) .
2630 Paste the snarf buffer
2632 .Pf ( Cd mle-paste ) .
2640 .Pf ( Cd mle-snarf-line ) .
2643 Prompts for a Unicode character (its hexadecimal number) to be inserted
2645 .Pf ( Cd mle-prompt-char ) .
2646 Note this command needs to be assigned to a single-letter control code
2647 in order to become recognized and executed during input of
2648 a key-sequence (only three single-letter control codes can be used for
2649 that shortcut purpose); this control code is special-treated and cannot
2650 be part of any other sequence, because any occurrence will perform the
2652 function immediately.
2655 Cut the characters from the one preceding the cursor to the preceding
2658 .Pf ( Cd mle-snarf-word-bwd ) .
2661 Move the cursor forward one word boundary
2663 .Pf ( Cd mle-go-word-fwd ) .
2666 Move the cursor backward one word boundary
2668 .Pf ( Cd mle-go-word-bwd ) .
2671 Escape: reset a possibly used multibyte character input state machine
2672 and \*(OPally a lingering, incomplete key binding
2674 .Pf ( Cd mle-cancel ) .
2675 This command needs to be assigned to a single-letter control code in
2676 order to become recognized and executed during input of a key-sequence
2677 (only three single-letter control codes can be used for that shortcut
2679 This control code may also be part of a multi-byte sequence, but if
2680 a sequence is active and the very control code is currently also an
2681 expected input, then it will first be consumed by the active sequence.
2684 (\*(OPally context-dependent) Invokes the command
2688 (\*(OPally context-dependent) Invokes the command
2692 (\*(OPally context-dependent) Invokes the command
2696 Cut the characters from the one after the cursor to the succeeding word
2699 .Pf ( Cd mle-snarf-word-fwd ) .
2710 this will immediately reset a possibly active search etc.
2715 ring the audible bell.
2719 .\" .Ss "Coloured display" {{{
2720 .Ss "Coloured display"
2722 \*(OP \*(UA can be configured to support a coloured display and font
2723 attributes by emitting ANSI / ISO 6429 SGR (select graphic rendition)
2725 Usage of colours and font attributes solely depends upon the
2726 capability of the detected terminal type that is defined by the
2727 environment variable
2729 and which can be fine-tuned by the user via the internal variable
2733 On top of what \*(UA knows about the terminal the boolean variable
2735 defines whether the actually applicable colour and font attribute
2736 sequences should also be generated when output is going to be paged
2737 through the external program defined by the environment variable
2742 This is not enabled by default because different pager programs need
2743 different command line switches or other configuration in order to
2744 support those sequences.
2745 \*(UA however knows about some widely used pagers and in a clean
2746 environment it is often enough to simply set
2748 please refer to that variable for more on this topic.
2753 is set then any active usage of colour and font attribute sequences
2754 is suppressed, but without affecting possibly established
2759 To define and control colours and font attributes a single multiplexer
2760 command family exists:
2762 shows or defines colour mappings for the given colour type (e.g.,
2765 can be used to remove mappings of a given colour type.
2766 Since colours are only available in interactive mode, it may make
2767 sense to conditionalize the colour setup by encapsulating it with
2770 .Bd -literal -offset indent
2771 if terminal && $features =@ +colour
2772 colour iso view-msginfo ft=bold,fg=green
2773 colour iso view-header ft=bold,fg=red "from,subject"
2774 colour iso view-header fg=red
2776 uncolour iso view-header from,subject
2777 colour iso view-header ft=bold,fg=magenta,bg=cyan
2778 colour 256 view-header ft=bold,fg=208,bg=230 subject,from
2779 colour mono view-header ft=bold
2780 colour mono view-header ft=bold,ft=reverse subject,from
2784 .\" }}} (DESCRIPTION)
2787 .\" .Sh COMMANDS {{{
2790 Each command is typed on a line by itself,
2791 and may take arguments following the command word.
2792 An unquoted reverse solidus
2794 at the end of a command line
2796 the newline character: it is discarded and the next line of input is
2797 used as a follow-up line, with all leading whitespace removed;
2798 once the entire command line is completed, the processing that is
2799 documented in the following, after removal of the whitespace characters
2800 .Cm space , tabulator , newline
2801 as well as those defined by the variable
2803 from the beginning and end of the line, begins.
2804 Placing any whitespace characters at the beginning of a line will
2805 prevent a possible addition of the command line to the \*(OPal history.
2808 Apart from this generic cleanup mechanism \*(UA uses command-specific
2809 syntax rules for command line arguments, documented in the following.
2810 This is a completely different approach to the
2812 ell, which implements a standardized (programming) language, and
2813 performs several successive transformation steps after decomposing the
2814 given command line into tokens following standardized syntax guidelines.
2815 E.g., in the following code snippets of otherwise identical meaning,
2816 a shell will see zero arguments, whereas \*(UA sees one, unless an
2817 additional expansion is explicitly used:
2819 .Bd -literal -offset indent
2820 $ cat > t.sh << '___'; cat > t.rc << '___'
2832 $ sh t.sh; \*(uA -X'source t.rc' -Xx
2839 Command names may be abbreviated, in which case the first command that
2840 matches the given prefix will be used.
2843 can be used to show the list of all commands, either alphabetically
2844 sorted or in prefix search order (these do not match, also because the
2845 POSIX standard prescribes a set of abbreviations).
2846 \*(OPally the command
2850 when given an argument, will show a documentation string for the
2851 command matching the expanded argument, as in
2853 which should be a shorthand of
2855 with these documentation strings both commands support a more
2857 listing mode which includes the argument type of the command and other
2858 information which applies; a handy suggestion might thus be:
2860 .Bd -literal -offset indent
2862 # Before v15: need to enable sh(1)ell-style on _entire_ line!
2863 localopts 1;wysh set verbose;ignerr eval "${@}";return ${?}
2865 ? commandalias xv '\ecall __xv'
2869 .\" .Ss "Command modifiers" {{{
2870 .Ss "Command modifiers"
2872 Commands may be prefixed by one or multiple command modifiers.
2876 The modifier reverse solidus
2879 to be placed first, prevents
2881 expansions on the remains of the line, e.g.,
2883 will always evaluate the command
2885 even if an (command)alias of the same name exists.
2887 content may itself contain further command modifiers, including
2888 an initial reverse solidus to prevent further expansions.
2894 indicates that any error generated by the following command should be
2895 ignored by the state machine and not cause a program exit with enabled
2897 or for the standardized exit cases in
2902 .Sx "INTERNAL VARIABLES" ,
2903 will be set to the real exit status of the command regardless.
2906 Some commands support the
2909 modifier: if used, they expect the name of a variable, which can itself
2910 be a variable, i.e., shell expansion is applied, as their first
2911 argument, and will place their computation result in it instead of the
2912 default location (it is usually written to standard output).
2914 The given name will be tested for being a valid
2916 variable name, and may therefore only consist of upper- and lowercase
2917 characters, digits, and the underscore; the hyphen-minus may be used as
2918 a non-portable extension; digits may not be used as first, hyphen-minus
2919 may not be used as last characters.
2920 In addition the name may either not be one of the known
2921 .Sx "INTERNAL VARIABLES" ,
2922 or must otherwise refer to a writable (non-boolean) value variable.
2923 The actual put operation may fail nonetheless, e.g., if the variable
2924 expects a number argument only a number will be accepted.
2925 Any error during these operations causes the command as such to fail,
2926 and the error number
2929 .Va ^ERR Ns -NOTSUP ,
2936 Last, but not least, the modifier
2939 can be used for some old and established commands to choose the new
2940 .Sx "Shell-style argument quoting"
2941 rules over the traditional
2942 .Sx "Old-style argument quoting" .
2946 .\" .Ss "Message list arguments" {{{
2947 .Ss "Message list arguments"
2949 Some commands expect arguments that represent messages (actually
2950 their symbolic message numbers), as has been documented above under
2951 .Sx "Specifying messages"
2953 If no explicit message list has been specified, the next message
2954 forward that satisfies the command's requirements will be used,
2955 and if there are no messages forward of the current message,
2956 the search proceeds backwards;
2957 if there are no good messages at all to be found, an error message is
2958 shown and the command is aborted.
2961 .\" .Ss "Old-style argument quoting" {{{
2962 .Ss "Old-style argument quoting"
2964 \*(ID This section documents the old, traditional style of quoting
2965 non-message-list arguments to commands which expect this type of
2966 arguments: whereas still used by the majority of such commands, the new
2967 .Sx "Shell-style argument quoting"
2968 may be available even for those via
2971 .Sx "Command modifiers" .
2972 Nonetheless care must be taken, because only new commands have been
2973 designed with all the capabilities of the new quoting rules in mind,
2974 which can, e.g., generate control characters.
2977 .Bl -bullet -offset indent
2979 An argument can be enclosed between paired double-quotes
2984 any whitespace, shell word expansion, or reverse solidus characters
2985 (except as described next) within the quotes are treated literally as
2986 part of the argument.
2987 A double-quote will be treated literally within single-quotes and vice
2989 Inside such a quoted string the actually used quote character can be
2990 used nonetheless by escaping it with a reverse solidus
2996 An argument that is not enclosed in quotes, as above, can usually still
2997 contain space characters if those spaces are reverse solidus escaped, as in
3001 A reverse solidus outside of the enclosing quotes is discarded
3002 and the following character is treated literally as part of the argument.
3006 .\" .Ss "Shell-style argument quoting" {{{
3007 .Ss "Shell-style argument quoting"
3009 Commands which don't expect message-list arguments use
3011 ell-style, and therefore POSIX standardized, argument parsing and
3013 \*(ID Most new commands only support these new rules and are flagged
3014 \*(NQ, some elder ones can use them with the command modifier
3016 in the future only this type of argument quoting will remain.
3019 A command line is parsed from left to right and an input token is
3020 completed whenever an unquoted, otherwise ignored, metacharacter is seen.
3021 Metacharacters are vertical bar
3027 as well as all characters from the variable
3030 .Cm space , tabulator , newline .
3031 The additional metacharacters left and right parenthesis
3033 and less-than and greater-than signs
3037 supports are not used, and are treated as ordinary characters: for one
3038 these characters are a vivid part of email addresses, and it seems
3039 highly unlikely that their function will become meaningful to \*(UA.
3041 .Bd -filled -offset indent
3042 .Sy Compatibility note:
3043 \*(ID Please note that even many new-style commands do not yet honour
3045 to parse their arguments: whereas the
3047 ell is a language with syntactic elements of clearly defined semantics,
3048 \*(UA parses entire input lines and decides on a per-command base what
3049 to do with the rest of the line.
3050 This also means that whenever an unknown command is seen all that \*(UA
3051 can do is cancellation of the processing of the remains of the line.
3053 It also often depends on an actual subcommand of a multiplexer command
3054 how the rest of the line should be treated, and until v15 we are not
3055 capable to perform this deep inspection of arguments.
3056 Nonetheless, at least the following commands which work with positional
3057 parameters fully support
3059 for an almost shell-compatible field splitting:
3060 .Ic call , call_if , read , vpospar , xcall .
3064 Any unquoted number sign
3066 at the beginning of a new token starts a comment that extends to the end
3067 of the line, and therefore ends argument processing.
3068 An unquoted dollar sign
3070 will cause variable expansion of the given name, which must be a valid
3072 ell-style variable name (see
3074 .Sx "INTERNAL VARIABLES"
3077 (shell) variables can be accessed through this mechanism, brace
3078 enclosing the name is supported (i.e., to subdivide a token).
3081 Whereas the metacharacters
3082 .Cm space , tabulator , newline
3083 only complete an input token, vertical bar
3089 also act as control operators and perform control functions.
3090 For now supported is semicolon
3092 which terminates a single command, therefore sequencing the command line
3093 and making the remainder of the line a subject to reevaluation.
3094 With sequencing, multiple command argument types and quoting rules may
3095 therefore apply to a single line, which can become problematic before
3096 v15: e.g., the first of the following will cause surprising results.
3099 .Dl ? echo one; set verbose; echo verbose=$verbose.
3100 .Dl ? echo one; wysh set verbose; echo verbose=$verbose.
3103 Quoting is a mechanism that will remove the special meaning of
3104 metacharacters and reserved words, and will prevent expansion.
3105 There are four quoting mechanisms: the escape character, single-quotes,
3106 double-quotes and dollar-single-quotes:
3109 .Bl -bullet -offset indent
3111 The literal value of any character can be preserved by preceding it
3112 with the escape character reverse solidus
3116 Arguments which are enclosed in
3117 .Ql 'single-\:quotes'
3118 retain their literal value.
3119 A single-quote cannot occur within single-quotes.
3122 The literal value of all characters enclosed in
3123 .Ql \(dqdouble-\:quotes\(dq
3124 is retained, with the exception of dollar sign
3126 which will cause variable expansion, as above, backquote (grave accent)
3128 (which not yet means anything special), reverse solidus
3130 which will escape any of the characters dollar sign
3132 (to prevent variable expansion), backquote (grave accent)
3136 (to prevent ending the quote) and reverse solidus
3138 (to prevent escaping, i.e., to embed a reverse solidus character as-is),
3139 but has no special meaning otherwise.
3142 Arguments enclosed in
3143 .Ql $'dollar-\:single-\:quotes'
3144 extend normal single quotes in that reverse solidus escape sequences are
3145 expanded as follows:
3147 .Bl -tag -compact -width "Ql \eNNN"
3149 bell control character (ASCII and ISO-10646 BEL).
3151 backspace control characer (ASCII and ISO-10646 BS).
3153 escape control character (ASCII and ISO-10646 ESC).
3155 escape control character.
3157 form feed control character (ASCII and ISO-10646 FF).
3159 line feed control character (ASCII and ISO-10646 LF).
3161 carriage return control character (ASCII and ISO-10646 CR).
3163 horizontal tabulator control character (ASCII and ISO-10646 HT).
3165 vertical tabulator control character (ASCII and ISO-10646 VT).
3167 emits a reverse solidus character.
3171 double quote (escaping is optional).
3173 eight-bit byte with the octal value
3175 (one to three octal digits), optionally prefixed by an additional
3177 A 0 byte will suppress further output for the quoted argument.
3179 eight-bit byte with the hexadecimal value
3181 (one or two hexadecimal characters).
3182 A 0 byte will suppress further output for the quoted argument.
3184 the Unicode / ISO-10646 character with the hexadecimal codepoint value
3186 (one to eight hexadecimal digits) \(em note that Unicode defines the
3187 maximum codepoint ever to be supported as
3192 This escape is only supported in locales that support Unicode (see
3193 .Sx "Character sets" ) ,
3194 in other cases the sequence will remain unexpanded unless the given code
3195 point is ASCII compatible or can be represented in the current locale.
3196 The character NUL will suppress further output for the quoted argument.
3200 except it takes only one to four hexadecimal digits.
3202 Emits the non-printable (ASCII and compatible) C0 control codes
3203 0 (NUL) to 31 (US), and 127 (DEL).
3204 Printable representations of ASCII control codes can be created by
3205 mapping them to a different part of the ASCII character set, which is
3206 possible by adding the number 64 for the codes 0 to 31, e.g., 7 (BEL) is
3207 .Ql 7 + 64 = 71 = G .
3208 The real operation is a bitwise logical XOR with 64 (bit 7 set, see
3210 thus also covering code 127 (DEL), which is mapped to 63 (question mark):
3211 .Ql ? vexpr ^ 127 64 .
3213 Whereas historically circumflex notation has often been used for
3214 visualization purposes of control codes, e.g.,
3216 the reverse solidus notation has been standardized:
3218 Some control codes also have standardized (ISO-10646, ISO C) aliases,
3219 as shown above (e.g.,
3223 whenever such an alias exists it will be used for display purposes.
3224 The control code NUL
3226 a non-standard extension) will suppress further output for the remains
3227 of the token (which may extend beyond the current quote), or, depending
3228 on the context, the remains of all arguments for the current command.
3230 Non-standard extension: expand the given variable name, as above.
3231 Brace enclosing the name is supported.
3233 Not yet supported, just to raise awareness: Non-standard extension.
3240 .Bd -literal -offset indent
3241 echo 'Quotes '${HOME}' and 'tokens" differ!"# no comment
3242 echo Quotes ${HOME} and tokens differ! # comment
3243 echo Don"'"t you worry$'\ex21' The sun shines on us. $'\eu263A'
3247 .\" .Ss "Raw data arguments for codec commands" {{{
3248 .Ss "Raw data arguments for codec commands"
3250 A special set of commands, which all have the string
3252 in their name, e.g.,
3256 take raw string data as input, which means that the content of the
3257 command input line is passed completely unexpanded and otherwise
3258 unchanged: like this the effect of the actual codec is visible without
3259 any noise of possible shell quoting rules etc., i.e., the user can input
3260 one-to-one the desired or questionable data.
3261 To gain a level of expansion, the entire command line can be
3265 .Bd -literal -offset indent
3266 ? vput shcodec res encode /usr/Sch\[:o]nes Wetter/heute.txt
3268 $'/usr/Sch\eu00F6nes Wetter/heute.txt'
3270 $'/usr/Sch\eu00F6nes Wetter/heute.txt'
3271 ? eval shcodec d $res
3272 /usr/Sch\[:o]nes Wetter/heute.txt
3276 .\" .Ss "Filename transformations" {{{
3277 .Ss "Filename transformations"
3279 Filenames, where expected, and unless documented otherwise, are
3280 subsequently subject to the following filename transformations, in
3283 .Bl -bullet -offset indent
3285 If the given name is a registered
3287 it will be replaced with the expanded shortcut.
3290 The filename is matched against the following patterns or strings:
3292 .Bl -hang -compact -width ".Ar %user"
3294 (Number sign) is expanded to the previous file.
3296 (Percent sign) is replaced by the invoking
3297 .Mx -ix "primary system mailbox"
3298 user's primary system mailbox, which either is the (itself expandable)
3300 if that is set, the standardized absolute pathname indicated by
3302 if that is set, or a built-in compile-time default otherwise.
3304 Expands to the primary system mailbox of
3306 (and never the value of
3308 regardless of its actual setting).
3310 (Ampersand) is replaced with the invoking users
3311 .Mx -ix "secondary mailbox"
3312 secondary mailbox, the
3319 directory (if that variable is set).
3321 Expands to the same value as
3323 but has special meaning when used with, e.g., the command
3325 the file will be treated as a primary system mailbox by, e.g., the
3329 commands, meaning that messages that have been read in the current
3330 session will be moved to the
3332 mailbox instead of simply being flagged as read.
3336 Meta expansions are applied to the resulting filename, as applicable to
3337 the resulting file access protocol (also see
3338 .Sx "On URL syntax and credential lookup" ) .
3339 If the fully expanded filename results in multiple pathnames and the
3340 command is expecting only one file, an error results.
3342 For the file-protocol, a leading tilde
3344 character will be replaced by the expansion of
3346 except when followed by a valid user name, in which case the home
3347 directory of the given user is used instead.
3349 In addition a shell expansion as if specified in double-quotes (see
3350 .Sx "Shell-style argument quoting" )
3351 is applied, so that any occurrence of
3355 will be replaced by the expansion of the variable, if possible;
3356 .Sx "INTERNAL VARIABLES"
3359 (shell) variables can be accessed through this mechanism.
3361 In interactive context, in order to allow simple value acceptance (via
3363 arguments will usually be displayed in a properly quoted form, e.g., a file
3364 .Ql diet\e is \ecurd.txt
3366 .Ql 'diet\e is \ecurd.txt' .
3370 .\" .Ss "Commands" {{{
3373 The following commands are available:
3375 .Bl -tag -width ".It Ic BaNg"
3382 command which follows, replacing unescaped exclamation marks with the
3383 previously executed command if the internal variable
3386 This command supports
3389 .Sx "Command modifiers" ,
3390 and manages the error number
3392 A 0 or positive exit status
3394 reflects the exit status of the command, negative ones that
3395 an error happened before the command was executed, or that the program
3396 did not exit cleanly, but, e.g., due to a signal: the error number is
3397 .Va ^ERR Ns -CHILD ,
3401 In conjunction with the
3403 modifier the following special cases exist:
3404 a negative exit status occurs if the collected data could not be stored
3405 in the given variable, which is a
3407 error that should otherwise not occur.
3408 .Va ^ERR Ns -CANCELED
3409 indicates that no temporary file could be created to collect the command
3410 output at first glance.
3411 In case of catchable out-of-memory situations
3413 will occur and \*(UA will try to store the empty string, just like with
3414 all other detected error conditions.
3419 The comment-command causes the entire line to be ignored.
3421 this really is a normal command which' purpose is to discard its
3424 indicating special character, which means that, e.g., trailing comments
3425 on a line are not possible.
3429 Goes to the next message in sequence and types it
3435 Display the preceding message, or the n'th previous message if given
3436 a numeric argument n.
3440 Show the current message number (the
3445 Show a brief summary of commands.
3446 \*(OP Given an argument a synopsis for the command in question is
3447 shown instead; commands can be abbreviated in general and this command
3448 can be used to see the full expansion of an abbreviation including the
3449 synopsis, try, e.g.,
3454 and see how the output changes.
3455 This mode also supports a more
3457 output, which will provide the informations documented for
3468 .It Ic account , unaccount
3469 (ac, una) Creates, selects or lists (an) account(s).
3470 Accounts are special incarnations of
3472 macros and group commands and variable settings which together usually
3473 arrange the environment for the purpose of creating an email account.
3474 Different to normal macros settings which are covered by
3476 \(en here by default enabled! \(en will not be reverted before the
3481 (case-insensitive) always exists, and all but it can be deleted by the
3482 latter command, and in one operation with the special name
3485 Without arguments a listing of all defined accounts is shown.
3486 With one argument the given account is activated: the system
3488 of that account will be activated (as via
3490 a possibly installed
3492 will be run, and the internal variable
3495 The two argument form is identical to defining a macro as via
3497 .Bd -literal -offset indent
3499 set folder=~/mail inbox=+syste.mbox record=+sent.mbox
3500 set from='(My Name) myname@myisp.example'
3501 set mta=smtp://mylogin@smtp.myisp.example
3508 Perform email address codec transformations on raw-data argument, rather
3509 according to email standards (RFC 5322; \*(ID will furtherly improve).
3513 .Sx "Command modifiers" ) ,
3514 and manages the error number
3516 The first argument must be either
3517 .Ar [+[+[+]]]e[ncode] ,
3521 and specifies the operation to perform on the rest of the line.
3524 Decoding will show how a standard-compliant MUA will display the given
3525 argument, which should be an email address.
3526 Please be aware that most MUAs have difficulties with the address
3527 standards, and vary wildly when (comments) in parenthesis,
3529 strings, or quoted-pairs, as below, become involved.
3530 \*(ID \*(UA currently does not perform decoding when displaying addresses.
3533 Skinning is identical to decoding but only outputs the plain address,
3534 without any string, comment etc. components.
3535 Another difference is that it may fail with the error number
3539 if decoding fails to find a(n) (valid) email address, in which case the
3540 unmodified input will be output again.
3543 Encoding supports four different modes, lesser automated versions can be
3544 chosen by prefixing one, two or three plus signs: the standard imposes
3545 a special meaning on some characters, which thus have to be transformed
3546 to so-called quoted-pairs by pairing them with a reverse solidus
3548 in order to remove the special meaning; this might change interpretation
3549 of the entire argument from what has been desired, however!
3550 Specify one plus sign to remark that parenthesis shall be left alone,
3551 two for not turning double quotation marks into quoted-pairs, and three
3552 for also leaving any user-specified reverse solidus alone.
3553 The result will always be valid, if a successful exit status is reported.
3554 \*(ID Addresses need to be specified in between angle brackets
3557 if the construct becomes more difficult, otherwise the current parser
3558 will fail; it is not smart enough to guess right.
3560 .Bd -literal -offset indent
3561 ? addrc enc "Hey, you",<diet@exam.ple>\e out\e there
3562 "\e"Hey, you\e", \e\e out\e\e there" <diet@exam.ple>
3563 ? addrc d "\e"Hey, you\e", \e\e out\e\e there" <diet@exam.ple>
3564 "Hey, you", \e out\e there <diet@exam.ple>
3565 ? addrc s "\e"Hey, you\e", \e\e out\e\e there" <diet@exam.ple>
3572 .It Ic alias , unalias
3573 (a, una) Aliases are a method of creating personal distribution lists
3574 that map a single alias name to none to multiple real receivers;
3575 these aliases become expanded after message composing is completed.
3576 The latter command removes the given list of aliases, the special name
3578 will discard all existing aliases.
3579 The former command shows all currently defined aliases when used without
3580 arguments, and with one argument the expansion of the given alias.
3581 With more than one argument, creates or appends to the alias name given
3582 as the first argument the remaining arguments.
3583 Alias names are restricted to alphabetic characters, digits, the
3584 underscore, hyphen-minus, the number sign, colon, commercial at and
3585 period, the last character can also be the dollar sign:
3586 .Ql [[:alnum:]_#:@.-]+$? .
3589 .It Ic alternates , unalternates
3590 \*(NQ(alt) Manage a list of alternate addresses or names of the active user,
3591 members of which will be removed from recipient lists.
3592 The latter command removes the given list of alternates, the special name
3594 will discard all existing aliases.
3595 The former command manages the error number
3597 and shows the current set of alternates when used without arguments; in
3598 this mode it supports
3601 .Sx "Command modifiers" ) .
3602 Otherwise the given arguments (after being checked for validity) are
3603 appended to the list of alternate names; in
3605 mode they replace that list instead.
3606 There is a set of implicit alternates which is formed of the values of
3615 .It Ic answered , unanswered
3616 Take a message lists and mark each message as having been answered,
3617 having not been answered, respectively.
3618 Messages will be marked answered when being
3620 to automatically if the
3624 .Sx "Message states" .
3629 .It Ic bind , unbind
3630 \*(OP\*(NQ The bind command extends the MLE (see
3631 .Sx "On terminal control and line editor" )
3632 with freely configurable key bindings.
3633 The latter command removes from the given context the given key binding,
3634 both of which may be specified as a wildcard
3638 will remove all bindings of all contexts.
3639 Due to initialization order unbinding will not work for built-in key
3640 bindings upon program startup, however: please use
3641 .Va line-editor-no-defaults
3642 for this purpose instead.
3645 With one argument the former command shows all key bindings for the
3646 given context, specifying an asterisk
3648 will show the bindings of all contexts; a more verbose listing will be
3649 produced if either of
3654 With two or more arguments a binding is (re)established:
3655 the first argument is the context to which the binding shall apply,
3656 the second argument is a comma-separated list of the
3658 which form the binding, and any remaining arguments form the expansion.
3659 To indicate that a binding shall not be auto-committed, but that the
3660 expansion shall instead be furtherly editable by the user, a commercial at
3662 (that will be removed) can be placed last in the expansion, from which
3663 leading and trailing whitespace will finally be removed.
3664 Reverse solidus cannot be used as the last character of expansion.
3667 Contexts define when a binding applies, i.e., a binding will not be seen
3668 unless the context for which it is defined for is currently active.
3669 This is not true for the shared binding
3671 which is the foundation for all other bindings and as such always
3672 applies, its bindings, however, only apply secondarily.
3673 The available contexts are the shared
3677 context which is used in all not otherwise documented situations, and
3679 which applies to compose mode only.
3683 which form the binding are specified as a comma-separated list of
3684 byte-sequences, where each list entry corresponds to one key(press).
3685 \*(OPally a list entry may, indicated by a leading colon character
3687 also refer to the name of a terminal capability;
3688 several dozen names will be compiled into \*(UA and may be specified
3691 or, if existing, by their
3693 name, regardless of the actually used terminal control library.
3694 It is however possible to use any capability, as long as the name is
3695 resolvable by the control library or defined in the internal variable
3697 Input sequences are not case-normalized, so that an exact match is
3698 required to update or remove a binding.
3701 .Bd -literal -offset indent
3702 bind base $'\eE',d mle-snarf-word-fwd # Esc(ape)
3703 bind base $'\eE',$'\ec?' mle-snarf-word-bwd # Esc, Delete
3704 bind default $'\ecA',:khome,w 'echo An editable binding@'
3705 bind default a,b,c rm -rf / @ # Another editable binding
3706 bind default :kf1 File %
3707 bind compose :kf1 ~e
3711 Note that the entire comma-separated list is first parsed (over) as a
3712 shell-token with whitespace as the field separator, before being parsed
3713 and expanded for real with comma as the field separator, therefore
3714 whitespace needs to be properly quoted, see
3715 .Sx "Shell-style argument quoting" .
3716 Using Unicode reverse solidus escape sequences renders a binding
3717 defunctional if the locale does not support Unicode (see
3718 .Sx "Character sets" ) ,
3719 and using terminal capabilities does so if no terminal control support
3720 is (currently) available.
3723 The following terminal capability names are built-in and can be used in
3725 or (if available) the two-letter
3727 notation regardless of the actually used library.
3728 See the respective manual for a list of capabilities.
3731 can be used to show all the capabilities of
3733 or the given terminal type;
3736 flag will also show supported (non-standard) extensions.
3739 .Bl -tag -compact -width kcuuf_or_kcuuf
3740 .It Cd kbs Ns \0or Cd kb
3742 .It Cd kdch1 Ns \0or Cd kD
3744 .It Cd kDC Ns \0or Cd *4
3745 \(em shifted variant.
3746 .It Cd kel Ns \0or Cd kE
3747 Clear to end of line.
3748 .It Cd kext Ns \0or Cd @9
3750 .It Cd kich1 Ns \0or Cd kI
3752 .It Cd kIC Ns \0or Cd #3
3753 \(em shifted variant.
3754 .It Cd khome Ns \0or Cd kh
3756 .It Cd kHOM Ns \0or Cd #2
3757 \(em shifted variant.
3758 .It Cd kend Ns \0or Cd @7
3760 .It Cd knp Ns \0or Cd kN
3762 .It Cd kpp Ns \0or Cd kP
3764 .It Cd kcub1 Ns \0or Cd kl
3765 Left cursor (with more modifiers: see below).
3766 .It Cd kLFT Ns \0or Cd #4
3767 \(em shifted variant.
3768 .It Cd kcuf1 Ns \0or Cd kr
3769 Right cursor (ditto).
3770 .It Cd kRIT Ns \0or Cd %i
3771 \(em shifted variant.
3772 .It Cd kcud1 Ns \0or Cd kd
3773 Down cursor (ditto).
3775 \(em shifted variant (only terminfo).
3776 .It Cd kcuu1 Ns \0or Cd ku
3779 \(em shifted variant (only terminfo).
3780 .It Cd kf0 Ns \0or Cd k0
3782 Add one for each function key up to
3787 .It Cd kf10 Ns \0or Cd k;
3789 .It Cd kf11 Ns \0or Cd F1
3791 Add one for each function key up to
3799 Some terminals support key-modifier combination extensions, e.g.,
3801 For example, the delete key,
3803 in its shifted variant, the name is mutated to
3805 then a number is appended for the states
3817 .Ql Shift+Alt+Control
3819 The same for the left cursor key,
3821 .Cd KLFT , KLFT3 , KLFT4 , KLFT5 , KLFT6 , KLFT7 , KLFT8 .
3824 It is advisable to use an initial escape or other control character (e.g.,
3826 for bindings which describe user key combinations (as opposed to purely
3827 terminal capability based ones), in order to avoid ambiguities whether
3828 input belongs to key sequences or not; it also reduces search time.
3831 may help shall keys and sequences be falsely recognized.
3836 \*(NQ Calls the given macro, which must have been created via
3841 Parameters given to macros are implicitly local to the macro's scope, and
3842 may be accessed via special (positional) parameters, e.g.,
3847 The positional parameters may be removed by
3849 ing them off the stack (exceeding the supported number of arguments
3851 .Va ^ERR Ns -OVERFLOW ) ,
3852 and are otherwise controllable via
3854 Macro execution can be terminated at any time by calling
3857 Calling macros recursively will at some time excess the stack size
3858 limit, causing a hard program abortion; if recursively calling a macro
3859 is the last command of the current macro, consider to use the command
3861 which will first release all resources of the current macro before
3862 replacing the current macro with the called one.
3863 Numeric and string operations can be performed via
3867 may be helpful to recreate argument lists.
3868 .Bd -literal -offset indent
3870 echo Parameter 1 of ${#} is ${1}, all: ${*} / ${@}
3873 call exmac Hello macro exmac!
3880 if the given macro has been created via
3882 but doesn't fail nor warn if the macro doesn't exist.
3886 (ch) Change the working directory to
3888 or the given argument.
3894 \*(OP Only applicable to S/MIME signed messages.
3895 Takes a message list and a filename and saves the certificates
3896 contained within the message signatures to the named file in both
3897 human-readable and PEM format.
3898 The certificates can later be used to send encrypted messages to the
3899 respective message senders by setting
3900 .Va smime-encrypt-USER@HOST
3905 .It Ic charsetalias , uncharsetalias
3906 \*(NQ Manage (character set conversion) character set alias mappings,
3907 as documented in the section
3908 .Sx "Character sets" .
3909 Character set aliases are expanded recursively, but no expansion is
3910 performed on values of the user-settable variables, e.g.,
3912 These are effectively no-operations if character set conversion
3913 is not available (i.e., no
3917 Without arguments the list of all currently defined aliases is shown,
3918 with one argument the expansion of the given alias.
3919 Otherwise all given arguments are treated as pairs of character sets and
3920 their desired target alias name, creating new or changing already
3921 existing aliases, as necessary.
3923 The latter deletes all aliases given as arguments, the special argument
3925 will remove all aliases.
3929 (ch) Change the working directory to
3931 or the given argument.
3937 .It Ic collapse , uncollapse
3938 Only applicable to threaded mode.
3939 Takes a message list and makes all replies to these messages invisible
3940 in header summaries, except for
3944 Also when a message with collapsed replies is displayed,
3945 all of these are automatically uncollapsed.
3946 The latter command undoes collapsing.
3951 .It Ic colour , uncolour
3952 \*(OP\*(NQ Manage colour mappings of and for a
3953 .Sx "Coloured display" .
3954 The type of colour is given as the (case-insensitive) first argument,
3955 which must be one of
3957 for 256-colour terminals,
3962 for the standard 8-colour ANSI / ISO 6429 color palette and
3966 for monochrome terminals.
3967 Monochrome terminals cannot deal with colours, but only (some) font
3971 Without further arguments the list of all currently defined mappings
3972 for the given colour type is shown (as a special case giving
3976 will show the mappings of all types).
3977 Otherwise the second argument defines the mappable slot, and the third
3978 argument a (comma-separated list of) colour and font attribute
3979 specification(s), and the optional fourth argument can be used to
3980 specify a precondition: if conditioned mappings exist they are tested in
3981 (creation) order unless a (case-insensitive) match has been found, and
3982 the default mapping (if any has been established) will only be chosen as
3984 The types of precondition available depend on the mappable slot (see
3985 .Sx "Coloured display"
3986 for some examples), the following of which exist:
3989 Mappings prefixed with
3991 are used for the \*(OPal built-in Mailx-Line-Editor (MLE, see
3992 .Sx "On terminal control and line editor" )
3993 and do not support preconditions.
3995 .Bl -tag -compact -width view-partinfo
3997 This mapping is used for the position indicator that is visible when
3998 a line cannot be fully displayed on the screen.
4005 Mappings prefixed with
4007 are used in header summaries, and they all understand the preconditions
4009 (the current message) and
4011 for elder messages (only honoured in conjunction with
4012 .Va datefield-markout-older ) .
4014 .Bl -tag -compact -width view-partinfo
4016 This mapping is used for the
4018 that can be created with the
4022 formats of the variable
4025 For the complete header summary line except the
4027 and the thread structure.
4029 For the thread structure which can be created with the
4031 format of the variable
4036 Mappings prefixed with
4038 are used when displaying messages.
4040 .Bl -tag -compact -width view-partinfo
4042 This mapping is used for so-called
4044 lines, which are MBOX file format specific header lines.
4047 A comma-separated list of headers to which the mapping applies may be
4048 given as a precondition; if the \*(OPal regular expression support is
4049 available then if any of the
4051 (extended) regular expression characters is seen the precondition will
4052 be evaluated as (an extended) one.
4054 For the introductional message info line.
4055 .It Ar view-partinfo
4056 For MIME part info lines.
4060 The following (case-insensitive) colour definitions and font attributes
4061 are understood, multiple of which can be specified in a comma-separated
4071 It is possible (and often applicable) to specify multiple font
4072 attributes for a single mapping.
4075 foreground colour attribute:
4085 To specify a 256-color mode a decimal number colour specification in
4086 the range 0 to 255, inclusive, is supported, and interpreted as follows:
4088 .Bl -tag -compact -width "999 - 999"
4090 the standard ISO 6429 colors, as above.
4092 high intensity variants of the standard colors.
4094 216 colors in tuples of 6.
4096 grayscale from black to white in 24 steps.
4098 .Bd -literal -offset indent
4100 fg() { printf "\e033[38;5;${1}m($1)"; }
4101 bg() { printf "\e033[48;5;${1}m($1)"; }
4103 while [ $i -lt 256 ]; do fg $i; i=$(($i + 1)); done
4104 printf "\e033[0m\en"
4106 while [ $i -lt 256 ]; do bg $i; i=$(($i + 1)); done
4107 printf "\e033[0m\en"
4111 background colour attribute (see
4113 for possible values).
4119 will remove for the given colour type (the special type
4121 selects all) the given mapping; if the optional precondition argument is
4122 given only the exact tuple of mapping and precondition is removed.
4125 will remove all mappings (no precondition allowed), thus
4127 will remove all established mappings.
4132 .It Ic commandalias , uncommandalias
4133 \*(NQ Define or list, and remove, respectively, command aliases.
4134 An (command)alias can be used everywhere a normal command can be used,
4135 but always takes precedence: any arguments that are given to the command
4136 alias are joined onto the alias expansion, and the resulting string
4137 forms the command line that is, in effect, executed.
4138 The latter command removes all given aliases, the special name
4140 will remove all existing aliases.
4141 When used without arguments the former shows a list of all currently
4142 known aliases, with one argument only the expansion of the given one.
4144 With two or more arguments a command alias is defined or updated: the
4145 first argument is the name under which the remaining command line should
4146 be accessible, the content of which can be just about anything.
4147 An alias may itself expand to another alias, but to avoid expansion loops
4148 further expansion will be prevented if an alias refers to itself or if
4149 an expansion depth limit is reached.
4150 Explicit expansion prevention via reverse solidus
4153 .Sx "Command modifiers" .
4154 .Bd -literal -offset indent
4156 \*(uA: `commandalias': no such alias: xx
4157 ? commandalias xx echo hello,
4159 commandalias xx 'echo hello,'
4168 (C) Copy messages to files whose names are derived from the author of
4169 the respective message and do not mark them as being saved;
4170 otherwise identical to
4175 (c) Copy messages to the named file and do not mark them as being saved;
4176 otherwise identical to
4181 Show the name of the current working directory, as reported by
4186 .Sx "Command modifiers" ) .
4187 The return status is tracked via
4192 \*(OP For unencrypted messages this command is identical to
4194 Encrypted messages are first decrypted, if possible, and then copied.
4198 \*(OP For unencrypted messages this command is identical to
4200 Encrypted messages are first decrypted, if possible, and then copied.
4204 .It Ic define , undefine
4205 Without arguments the current list of macros, including their content,
4206 is shown, otherwise a macro is defined, replacing an existing macro of
4208 A macro definition is a sequence of commands in the following form:
4209 .Bd -literal -offset indent
4218 A defined macro can be invoked explicitly by using the
4222 commands, or implicitly if a macro hook is triggered, e.g., a
4224 It is possible to localize adjustments, like creation, deletion and
4226 .Sx "INTERNAL VARIABLES" ,
4229 command; the scope which is localized depends on how (i.e.,
4231 normal macro, folder hook, hook,
4233 switch) the macro is invoked.
4234 Execution of a macro body can be stopped from within by calling
4238 ed macro, given positional parameters can be
4242 The latter command deletes the given macro, the special name
4244 will discard all existing macros.
4245 Creation and deletion of (a) macro(s) can be performed from within
4250 .It Ic delete , undelete
4251 (d, u) Marks the given message list as being or not being
4253 respectively; if no argument has been specified then the usual search
4254 for a visible message is performed, as documented for
4255 .Sx "Message list arguments" ,
4256 showing only the next input prompt if the search fails.
4257 Deleted messages will neither be saved in the
4259 .Sx "secondary mailbox"
4261 nor will they be available for most other commands.
4264 variable is set, the new
4266 or the last message restored, respectively, is automatically
4276 Superseded by the multiplexer
4282 Delete the given messages and automatically
4286 if one exists, regardless of the setting of
4293 up or down by one message when given
4297 argument, respectively.
4301 .It Ic draft , undraft
4302 Take message lists and mark each given message as being draft, or not
4303 being draft, respectively, as documented in the section
4304 .Sx "Message states" .
4308 \*(NQ (ec) Echoes arguments to standard output and writes a trailing
4309 newline, whereas the otherwise identical
4312 .Sx "Shell-style argument quoting"
4314 .Sx "Filename transformations"
4315 are applied to the expanded arguments.
4321 except that is echoes to standard error.
4324 In interactive sessions the \*(OPal message ring queue for
4326 will be used instead, if available.
4332 but does not write a trailing newline.
4338 but does not write a trailing newline.
4342 (e) Point the text editor (as defined in
4344 at each message from the given list in turn.
4345 Modified contents are discarded unless the
4347 variable is set, and are not used unless the mailbox can be written to
4348 and the editor returns a successful exit status.
4353 .Ic if Ns \0/\: Ic elif Ns \0/\: Ic else Ns \0/\: Ic endif
4354 conditional \(em if the condition of a preceding
4356 was false, check the following condition and execute the following block
4357 if it evaluates true.
4362 .Ic if Ns \0/\: Ic elif Ns \0/\: Ic else Ns \0/\: Ic endif
4363 conditional \(em if none of the conditions of the preceding
4367 commands was true, the
4373 (en) Marks the end of an
4374 .Ic if Ns \0/\: Ic elif Ns \0/\: Ic else Ns \0/\: Ic endif
4375 conditional execution block.
4380 \*(NQ \*(UA has a strict notion about which variables are
4381 .Sx "INTERNAL VARIABLES"
4382 and which are managed in the program
4384 Since some of the latter are a vivid part of \*(UAs functioning,
4385 however, they are transparently integrated into the normal handling of
4386 internal variables via
4390 To integrate other environment variables of choice into this
4391 transparent handling, and also to export internal variables into the
4392 process environment where they normally are not, a
4394 needs to become established with this command, as in, e.g.,
4397 .Dl environ link PERL5LIB from TZ
4400 Afterwards changing such variables with
4402 will cause automatic updates of the program environment, and therefore
4403 be inherited by newly created child processes.
4404 Sufficient system support provided (it was in BSD as early as 1987, and
4405 is standardized since Y2K) removing such variables with
4407 will remove them also from the program environment, but in any way
4408 the knowledge they ever have been
4411 Note this implies that
4413 may cause loss of links.
4418 will remove an existing link, but leaves the variables as such intact.
4419 Additionally the subcommands
4423 are provided, which work exactly the same as the documented commands
4427 but (additionally) link the variable(s) with the program environment and
4428 thus immediately export them to, or remove them from (if possible),
4429 respectively, the program environment.
4434 \*(OP Since \*(UA uses the console as a user interface it can happen
4435 that messages scroll by too fast to become recognized.
4436 An error message ring queue is available which stores duplicates of any
4437 error message and notifies the user in interactive sessions whenever
4438 a new error has occurred.
4439 The queue is finite: if its maximum size is reached any new message
4440 replaces the eldest.
4443 can be used to manage this message queue: if given
4445 or no argument the queue will be displayed and cleared,
4447 will only clear all messages from the queue.
4451 \*(NQ Construct a command by concatenating the arguments, separated with
4452 a single space character, and then evaluate the result.
4453 This command passes through the exit status
4457 of the evaluated command; also see
4459 .Bd -literal -offset indent
4470 call yyy '\ecall xxx' "b\e$'\et'u ' "
4478 (ex or x) Exit from \*(UA without changing the active mailbox and skip
4479 any saving of messages in the
4481 .Sx "secondary mailbox"
4483 as well as a possibly tracked line editor history file.
4484 The optional status number argument will be passed through to
4486 \*(ID For now it can happen that the given status will be overwritten,
4487 later this will only occur if a later error needs to be reported onto an
4488 otherwise success indicating status.
4494 but open the mailbox read-only.
4499 (fi) The file command switches to a new mailbox.
4500 Without arguments it shows status information of the current mailbox.
4501 If an argument is given, it will write out changes (such as deletions)
4502 the user has made, open a new mailbox, update the internal variables
4503 .Va mailbox-resolved
4505 .Va mailbox-display ,
4506 and optionally display a summary of
4513 .Sx "Filename transformations"
4514 will be applied to the
4518 prefixes are understood, e.g.,
4519 .Ql maildir:///tmp/mdirbox :
4520 if a protocol prefix is used the mailbox type is fixated and neither
4521 the auto-detection (read on) nor the
4524 \*(OPally URLs can also be used to access network resources, see
4525 .Sx "On URL syntax and credential lookup" :
4528 .Dl \*(IN protocol://[user[:password]@]host[:port][/path]
4529 .Dl \*(OU protocol://[user@]host[:port][/path]
4532 \*(OPally supported network protocols are
4536 (POP3 with SSL/TLS encrypted transport),
4538 part is valid only for IMAP; there it defaults to
4540 Network URLs require a special encoding as documented in the said section.
4541 It is possible to proxy all network traffic over a SOCKS5 server given via
4545 If the resulting file protocol (MBOX database)
4547 is located on a local filesystem then the list of all registered
4549 s is traversed in order to see whether a transparent intermediate
4550 conversion step is necessary to handle the given mailbox, in which case
4551 \*(UA will use the found hook to load and save data into and from
4552 a temporary file, respectively.
4553 Changing hooks will not affect already opened mailboxes.
4554 For example, the following creates hooks for the
4556 compression tool and a combined compressed and encrypted format:
4558 .Bd -literal -offset indent
4560 gzip 'gzip -dc' 'gzip -c' \e
4561 zst.pgp 'gpg -d | zstd -dc' 'zstd -19 -zc | gpg -e'
4565 MBOX database files are generally locked during file operations in order
4566 to avoid inconsistencies due to concurrent modifications.
4567 \*(OPal Mailbox files which \*(UA treats as the system
4572 .Sx "primary system mailbox" Ns
4573 es in general will also be protected by so-called dotlock files, the
4574 traditional way of mail spool file locking: for any file
4578 will be created for the duration of the synchronization \(em
4579 as necessary a privilege-separated dotlock child process will be used
4580 to accommodate for necessary privilege adjustments in order to create
4581 the dotlock file in the same directory
4582 and with the same user and group identities as the file of interest.
4585 \*(UA by default uses tolerant POSIX rules when reading MBOX database
4586 files, but it will detect invalid message boundaries in this mode and
4587 complain (even more with
4589 if any is seen: in this case
4591 can be used to create a valid MBOX database from the invalid input.
4594 If no protocol has been fixated, and
4596 refers to a directory with the subdirectories
4601 then it is treated as a folder in
4604 \*(ID Also, if no protocol has been fixated and no existing file has
4605 been found, the variable
4607 controls the format of mailboxes yet to be created.
4612 .It Ic filetype , unfiletype
4613 \*(NQ Define or list, and remove, respectively, file handler hooks,
4614 which provide (shell) commands that enable \*(UA to load and save MBOX
4615 files from and to files with the registered file extensions;
4616 it will use an intermediate temporary file to store the plain data.
4617 The latter command removes the hooks for all given extensions,
4619 will remove all existing handlers.
4621 When used without arguments the former shows a list of all currently
4622 defined file hooks, with one argument the expansion of the given alias.
4623 Otherwise three arguments are expected, the first specifying the file
4624 extension for which the hook is meant, and the second and third defining
4625 the load- and save commands, respectively, to deal with the file type,
4626 both of which must read from standard input and write to standard
4628 Changing hooks will not affect already opened mailboxes (\*(ID except below).
4629 \*(ID For now too much work is done, and files are oftened read in twice
4630 where once would be sufficient: this can cause problems if a filetype is
4631 changed while such a file is opened; this was already so with the
4632 built-in support of .gz etc. in Heirloom, and will vanish in v15.
4633 \*(ID For now all handler strings are passed to the
4634 .Ev SHELL for evaluation purposes; in the future a
4636 prefix to load and save commands may mean to bypass this shell instance:
4637 placing a leading space will avoid any possible misinterpretations.
4638 .Bd -literal -offset indent
4639 filetype bz2 'bzip2 -dc' 'bzip2 -zc' \e
4640 gz 'gzip -dc' 'gzip -c' xz 'xz -dc' 'xz -zc' \e
4641 zst 'zstd -dc' 'zstd -19 -zc' \e
4642 zst.pgp 'gpg -d | zstd -dc' 'zstd -19 -zc | gpg -e'
4643 set record=+sent.zst.pgp
4648 .It Ic flag , unflag
4649 Take message lists and mark the messages as being flagged, or not being
4650 flagged, respectively, for urgent/special attention.
4652 .Sx "Message states" .
4661 With no arguments, list the names of the folders in the folder directory.
4662 With an existing folder as an argument,
4663 lists the names of folders below the named folder.
4669 but saves the message in a file named after the local part of the first
4670 recipient's address (instead of in
4677 but saves the message in a file named after the local part of the first
4678 recipient's address (instead of in
4685 but responds to all recipients regardless of the
4690 .It Ic followupsender
4693 but responds to the sender only regardless of the
4701 but saves the message in a file named after the local part of the
4702 recipient's address (instead of in
4707 Takes a message and the address of a recipient
4708 and forwards the message to him.
4709 The text of the original message is included in the new one,
4710 with the value of the
4711 .Va forward-header-inject
4712 variable preceding it.
4713 To filter the included header fields to the desired subset use the
4715 slot of the white- and blacklisting command
4717 Only the first part of a multipart message is included unless
4718 .Va forward-as-attachment ,
4719 and recipient addresses will be stripped from comments, names etc.
4720 unless the internal variable
4726 (f) Takes a list of message specifications and displays a summary of
4727 their message headers, exactly as via
4729 An alias of this command is
4732 .Sx "Specifying messages" .
4743 \*(OB Superseded by the multiplexer
4747 \*(OB Superseded by the multiplexer
4750 .It Ic ghost , unghost
4753 .Ic uncommandalias .
4757 .It Ic headerpick , unheaderpick
4758 \*(NQ Multiplexer command to manage white- and blacklisting
4759 selections of header fields for a variety of applications.
4760 Without arguments the set of contexts that have settings is displayed.
4761 When given arguments, the first argument is the context to which the
4762 command applies, one of (case-insensitively)
4764 for display purposes (via, e.g.,
4767 for selecting which headers shall be stored persistently when
4773 ing messages (note that MIME related etc. header fields should not be
4774 ignored in order to not destroy usability of the message in this case),
4776 for stripping down messages when
4778 ing message (has no effect if
4779 .Va forward-as-attachment
4782 for defining user-defined set of fields for the command
4786 The current settings of the given context are displayed if only the
4787 first argument is given.
4788 A second argument denotes the type of restriction that is to be chosen,
4789 it may be (a case-insensitive prefix of)
4793 for white- and blacklisting purposes, respectively.
4794 Establishing a whitelist suppresses inspection of the corresponding
4796 If no further argument is given the current settings of the given type
4797 will be displayed, otherwise the remaining arguments specify header
4798 fields, which \*(OPally may be given as regular expressions, to be be
4799 added to the given type.
4800 The special wildcard field (asterisk,
4802 will establish a (fast) shorthand setting which covers all fields.
4804 The latter command always takes three or more arguments and can be used
4805 to remove fields from the given type of list of the given context, the
4808 will remove all fields.
4813 (h) Show the current group of headers, the size of which depends on
4816 and the style of which can be adjusted with the variable
4818 If a message-specification is given the group of headers containing the
4819 first message therein is shown and the message at the top of the screen
4832 (this mode also supports a more
4836 the list of history entries;
4839 argument selects and evaluates the respective history entry,
4840 which will become the new history top; a negative number is used as an
4841 offset to the current command, e.g.,
4843 will select the last command, the history top.
4844 The default mode if no arguments are given is
4851 Takes a message list and marks each message therein to be saved in the
4856 .Sx "secondary mailbox"
4858 Does not override the
4861 \*(UA deviates from the POSIX standard with this command, because a
4863 command issued after
4865 will display the following message, not the current one.
4870 (i) Part of the nestable
4871 .Ic if Ns \0/\: Ic elif Ns \0/\: Ic else Ns \0/\: Ic endif
4872 conditional execution construct \(em if the given condition is true then
4873 the encapsulated block is executed.
4874 The POSIX standards supports the (case-insensitive) conditions
4879 end, all remaining conditions are non-portable extensions.
4880 (Be aware that a faulty condition skips all following branches until
4882 \*(ID These commands do not yet use
4883 .Sx "Shell-style argument quoting"
4884 and therefore do not know about input tokens, so that syntax
4885 elements have to be surrounded by whitespace; in v15 \*(UA will inspect
4886 all conditions bracket group wise and consider the tokens, representing
4887 values and operators, therein, which also means that variables will
4888 already have been expanded at that time (just like in the shell).
4890 .Bd -literal -offset indent
4899 The (case-insensitive) condition
4901 erminal will evaluate to true if the standard input is a terminal, i.e.,
4902 in interactive sessions.
4903 Another condition can be any boolean value (see the section
4904 .Sx "INTERNAL VARIABLES"
4905 for textual boolean representations) to mark an enwrapped block as
4908 .Dq always execute .
4912 .Sx "Shell-style argument quoting"
4913 will be used, and this command will simply interpret expanded tokens.)
4914 It is possible to check
4915 .Sx "INTERNAL VARIABLES"
4918 variables for existence or compare their expansion against a user given
4919 value or another variable by using the
4921 .Pf ( Dq variable next )
4922 conditional trigger character;
4923 a variable on the right hand side may be signalled using the same
4925 Variable names may be enclosed in a pair of matching braces.
4926 When this mode has been triggered, several operators are available:
4929 Integer operators treat the arguments on the left and right hand side of
4930 the operator as integral numbers and compare them arithmetically.
4931 It is an error if any of the operands is not a valid integer, an empty
4932 argument (which implies it had been quoted) is treated as if it were 0.
4933 Available operators are
4937 (less than or equal to),
4943 (greater than or equal to), and
4948 String data operators compare the left and right hand side according to
4949 their textual content.
4950 Unset variables are treated as the empty string.
4951 The behaviour of string operators can be adjusted by prefixing the
4952 operator with the modifier trigger commercial at
4954 followed by none to multiple modifiers: for now supported is
4956 which turns the comparison into a case-insensitive one: this is
4957 implied if no modifier follows the trigger.
4960 Available string operators are
4964 (less than or equal to),
4970 (greater than or equal to),
4974 (is substring of) and
4976 (is not substring of).
4977 By default these operators work on bytes and (therefore) do not take
4978 into account character set specifics.
4979 If the case-insensitivity modifier has been used, case is ignored
4980 according to the rules of the US-ASCII encoding, i.e., bytes are
4984 When the \*(OPal regular expression support is available, the additional
4990 They treat the right hand side as an extended regular expression that is
4991 matched according to the active locale (see
4992 .Sx "Character sets" ) ,
4993 i.e., character sets should be honoured correctly.
4996 Conditions can be joined via AND-OR lists (where the AND operator is
4998 and the OR operator is
5000 which have equal precedence and will be evaluated with left
5001 associativity, thus using the same syntax that is known for the
5003 It is also possible to form groups of conditions and lists by enclosing
5004 them in pairs of brackets
5005 .Ql [\ \&.\&.\&.\ ] ,
5006 which may be interlocked within each other, and also be joined via
5010 The results of individual conditions and entire groups may be modified
5011 via unary operators: the unary operator
5013 will reverse the result.
5015 .Bd -literal -offset indent
5019 if [ "$ttycharset" == UTF-8 ] || [ "$ttycharset" @i== UTF8 ]
5020 echo *ttycharset* is UTF-8, the former case-sensitive!
5023 if [ "${t1}" == "${t2}" ]
5024 echo These two variables are equal
5026 # This is a string test, -ge has been added for v14.9.0
5027 if [ "$features" =% +regex ] && [ "$TERM" @i=~ "^xterm\&.*" ]
5028 echo ..in an X terminal
5030 if [ [ true ] && [ [ "${debug}" != '' ] || \e
5031 [ "$verbose" != '' ] ] ]
5034 if true && [ "$debug" != '' ] || [ "${verbose}" != '' ]
5035 echo Left associativity, as is known from the shell
5037 if ! ! true && ! [ ! "$debug" && ! "$verbose" ]
5038 echo Unary operator support
5047 Superseded by the multiplexer
5052 Shows the names of all available commands, alphabetically sorted.
5053 If given any non-whitespace argument the list will be shown in the order
5054 in which command prefixes are searched.
5055 \*(OP In conjunction with a set variable
5057 additional information will be provided for each command: the argument
5058 type will be indicated, the documentation string will be shown,
5059 and the set of command flags will show up:
5061 .Bl -tag -compact -width ".It Ql BaNg"
5062 .It Ql "vput modifier"
5063 command supports the command modifier
5065 .It Ql "errno in *!*"
5066 the error number is tracked in
5069 commands needs an active mailbox, a
5071 .It Ql "ok: batch or interactive"
5072 command may only be used in interactive or
5075 .It Ql "ok: send mode"
5076 command can be used in send mode.
5077 .It Ql "not ok: compose mode"
5078 command is not available when in compose mode.
5079 .It Ql "not ok: during startup"
5080 command cannot be used during program startup, e.g., while loading
5081 .Sx "Resource files" .
5082 .It Ql "ok: in subprocess"
5083 command is allowed to be used when running in a subprocess instance,
5084 e.g., from within a macro that is called via
5085 .Va on-compose-splice .
5090 This command can be used to localize changes to variables, meaning that
5091 their state will be reverted to the former one once the covered scope
5093 It can only be used inside of macro definition blocks introduced by
5097 and is interpreted as a boolean (string, see
5098 .Sx "INTERNAL VARIABLES" ) ;
5101 of an account is left once it is switched off again.
5102 .Bd -literal -offset indent
5103 define temporary_settings {
5104 set possibly_global_option1
5109 set possibly_global_option2
5118 enables change localization and calls
5120 which explicitly resets localization, then any value changes within
5122 will still be reverted by
5124 \*(ID Once the outermost level, the one which enabled localization
5125 first, is left, but no earlier, all adjustments will be unrolled.
5126 \*(ID Likewise worth knowing, if in this example
5128 changes to a different
5130 which sets some variables that are yet covered by localizations, their
5131 scope will be extended, and in fact leaving the
5133 will (thus) restore settings in (likely) global scope which actually
5134 were defined in a local, private context.
5138 Reply to messages that come in via known
5141 .Pf ( Ic mlsubscribe )
5142 mailing lists, or pretend to do so (see
5143 .Sx "Mailing lists" ) :
5146 functionality this will actively resort and even remove message
5147 recipients in order to generate a message that is supposed to be sent to
5149 For example it will also implicitly generate a
5150 .Ql Mail-Followup-To:
5151 header if that seems useful, regardless of the setting of the variable
5153 For more documentation please refer to
5154 .Sx "On sending mail, and non-interactive mode" .
5160 but saves the message in a file named after the local part of the first
5161 recipient's address (instead of in
5166 (m) Takes a (list of) recipient address(es) as (an) argument(s),
5167 or asks on standard input if none were given;
5168 then collects the remaining mail content and sends it out.
5169 For more documentation please refer to
5170 .Sx "On sending mail, and non-interactive mode" .
5174 (mb) The given message list is to be sent to the
5176 .Sx "secondary mailbox"
5178 when \*(UA is quit; this is the default action unless the variable
5181 \*(ID This command can only be used in a
5183 .Sx "primary system mailbox" .
5187 .It Ic mimetype , unmimetype
5188 Without arguments the content of the MIME type cache will displayed;
5189 a more verbose listing will be produced if either of
5194 When given arguments they will be joined, interpreted as shown in
5195 .Sx "The mime.types files"
5197 .Sx "HTML mail and MIME attachments" ) ,
5198 and the resulting entry will be added (prepended) to the cache.
5199 In any event MIME type sources are loaded first as necessary \(en
5200 .Va mimetypes-load-control
5201 can be used to fine-tune which sources are actually loaded.
5203 The latter command deletes all specifications of the given MIME type, thus
5204 .Ql ? unmimetype text/plain
5205 will remove all registered specifications for the MIME type
5209 will discard all existing MIME types, just as will
5211 but which also reenables cache initialization via
5212 .Va mimetypes-load-control .
5216 .It Ic mlist , unmlist
5217 The latter command removes all given mailing-lists, the special name
5219 can be used to remove all registered lists.
5220 The former will list all currently defined mailing lists (and their
5221 attributes, if any) when used without arguments; a more verbose listing
5222 will be produced if either of
5227 Otherwise all given arguments will be added and henceforth be recognized
5229 If the \*(OPal regular expression support is available then mailing
5230 lists may also be specified as (extended) regular expressions (see
5236 \*(ID Only available in interactive mode, this command allows to display
5237 MIME parts which require external MIME handler programs to run which do
5238 not integrate in \*(UAs normal
5241 .Sx "HTML mail and MIME attachments" ) .
5242 (\*(ID No syntax to directly address parts, this restriction may vanish.)
5243 The user will be asked for each non-text part of the given message in
5244 turn whether the registered handler shall be used to display the part.
5248 .It Ic mlsubscribe , unmlsubscribe
5249 The latter command removes the subscription attribute from all given
5250 mailing-lists, the special name
5252 can be used to do so for any registered list.
5253 The former will list all currently defined mailing lists which have
5254 a subscription attribute when used without arguments; a more verbose
5255 listing will be produced if either of
5260 Otherwise this attribute will be set for all given mailing lists,
5261 newly creating them as necessary (as via
5270 but moves the messages to a file named after the local part of the
5271 sender address of the first message (instead of in
5278 but marks the messages for deletion if they were transferred
5285 but also displays header fields which would not pass the
5287 selection, and all MIME parts.
5295 on the given messages, even in non-interactive mode and as long as the
5296 standard output is a terminal.
5302 \*(OP When used without arguments or if
5304 has been given the content of the
5306 cache is shown, loading it first as necessary.
5309 then the cache will only be initialized and
5311 will remove its contents.
5312 Note that \*(UA will try to load the file only once, use
5313 .Ql Ic \&\&netrc Ns \:\0\:clear
5314 to unlock further attempts.
5319 .Sx "On URL syntax and credential lookup" ;
5321 .Sx "The .netrc file"
5322 documents the file format in detail.
5326 Checks for new mail in the current folder without committing any changes
5328 If new mail is present, a message is shown.
5332 the headers of each new message are also shown.
5333 This command is not available for all mailbox types.
5341 Goes to the next message in sequence and types it.
5342 With an argument list, types the next matching message.
5356 If the current folder is accessed via a network connection, a
5358 command is sent, otherwise no operation is performed.
5364 but also displays header fields which would not pass the
5366 selection, and all MIME parts.
5374 on the given messages, even in non-interactive mode and as long as the
5375 standard output is a terminal.
5383 but also pipes header fields which would not pass the
5385 selection, and all parts of MIME
5386 .Ql multipart/alternative
5391 (pi) Takes a message list and a shell command
5392 and pipes the messages through the command.
5393 Without an argument the current message is piped through the command
5400 every message is followed by a formfeed character.
5421 (q) Terminates the session, saving all undeleted, unsaved messages in
5424 .Sx "secondary mailbox"
5426 preserving all messages marked with
5430 or never referenced in the system
5432 and removing all other messages from the
5434 .Sx "primary system mailbox" .
5435 If new mail has arrived during the session,
5437 .Dq You have new mail
5439 If given while editing a mailbox file with the command line option
5441 then the edit file is rewritten.
5442 A return to the shell is effected,
5443 unless the rewrite of edit file fails,
5444 in which case the user can escape with the exit command.
5445 The optional status number argument will be passed through to
5447 \*(ID For now it can happen that the given status will be overwritten,
5448 later this will only occur if a later error needs to be reported onto an
5449 otherwise success indicating status.
5453 \*(NQ Read a line from standard input, or the channel set active via
5455 and assign the data, which will be splitted as indicated by
5457 to the given variables.
5458 The variable names are checked by the same rules as documented for
5460 and the same error codes will be seen in
5464 indicates the number of bytes read, it will be
5466 with the error number
5470 in case of I/O errors, or
5473 If there are more fields than variables, assigns successive fields to the
5474 last given variable.
5475 If there are less fields than variables, assigns the empty string to the
5477 .Bd -literal -offset indent
5480 ? echo "<$a> <$b> <$c>"
5482 ? wysh set ifs=:; read a b c;unset ifs
5483 hey2.0,:"'you ",:world!:mars.:
5484 ? echo $?/$^ERRNAME / <$a><$b><$c>
5485 0/NONE / <hey2.0,><"'you ",><world!:mars.:><><>
5490 \*(NQ Manages input channels for
5492 to be used to avoid complicated or impracticable code, like calling
5494 from within a macro in non-interactive mode.
5495 Without arguments, or when the first argument is
5497 a listing of all known channels is printed.
5498 Channels can otherwise be
5500 d, and existing channels can be
5504 d by giving the string used for creation.
5506 The channel name is expected to be a file descriptor number, or,
5507 if parsing the numeric fails, an input file name that undergoes
5508 .Sx "Filename transformations" .
5509 E.g. (this example requires a modern shell):
5510 .Bd -literal -offset indent
5511 $ LC_ALL=C printf 'echon "hey, "\enread a\enyou\enecho $a' |\e
5514 $ LC_ALL=C printf 'echon "hey, "\enread a\enecho $a' |\e
5515 LC_ALL=C 6<<< 'you' \*(uA -R#X'readctl create 6'
5529 Removes the named files or directories.
5530 If a name refer to a mailbox, e.g., a Maildir mailbox, then a mailbox
5531 type specific removal will be performed, deleting the complete mailbox.
5532 The user is asked for confirmation in interactive mode.
5536 Takes the name of an existing folder
5537 and the name for the new folder
5538 and renames the first to the second one.
5539 Both folders must be of the same type.
5543 (R) Replies to only the sender of each message of the given message
5544 list, by using the first message as the template to quote, for the
5548 will exchange this command with
5550 Unless the internal variable
5552 is set the recipient address will be stripped from comments, names etc.
5556 (r) Take a message and group-responds to it by addressing the sender
5557 and all recipients, subject to
5561 .Va followup-to-honour ,
5564 .Va recipients-in-cc
5565 influence response behaviour.
5566 Unless the internal variable
5568 is set recipient addresses will be stripped from comments, names etc.
5578 offers special support for replying to mailing lists.
5579 For more documentation please refer to
5580 .Sx "On sending mail, and non-interactive mode" .
5586 but initiates a group-reply regardless of the value of
5593 but responds to the sender only regardless of the value of
5600 but does not add any header lines.
5601 This is not a way to hide the sender's identity,
5602 but useful for sending a message again to the same recipients.
5606 Takes a list of messages and a user name
5607 and sends each message to the named user.
5609 and related header fields are prepended to the new copy of the message.
5612 is only performed if
5632 .It Ic respondsender
5638 (ret) Superseded by the multiplexer
5643 Only available inside the scope of a
5647 this will stop evaluation of any further macro content, and return
5648 execution control to the caller.
5649 The two optional parameters must be specified as positive decimal
5650 numbers and default to the value 0:
5651 the first argument specifies the signed 32-bit return value (stored in
5653 and later extended to signed 64-bit),
5654 the second the signed 32-bit error number (stored in
5658 a non-0 exit status may cause the program to exit.
5664 but saves the messages in a file named after the local part of the
5665 sender of the first message instead of (in
5667 and) taking a filename argument; the variable
5669 is inspected to decide on the actual storage location.
5673 (s) Takes a message list and a filename and appends each message in turn
5674 to the end of the file.
5675 If no filename is given, the
5677 .Sx "secondary mailbox"
5680 The filename in quotes, followed by the generated character count
5681 is echoed on the user's terminal.
5684 .Sx "primary system mailbox"
5685 the messages are marked for deletion.
5686 .Sx "Filename transformations"
5690 \*(OB Superseded by the multiplexer
5694 \*(OB Superseded by the multiplexer
5698 \*(OB Superseded by the multiplexer
5703 Takes a message specification (list) and displays a header summary of
5704 all matching messages, as via
5706 This command is an alias of
5709 .Sx "Specifying messages" .
5713 Takes a message list and marks all messages as having been read.
5719 (se, \*(NQ uns) The latter command will delete all given variables,
5720 the former, when used without arguments, will show all variables which
5721 are currently known to \*(UA; this will not automatically link-in
5723 variables which are known to \*(UA even if they exist in the program
5724 environment: only explicit addressing of variables, e.g., via
5726 using a variable in a
5728 condition or a string passed to
5730 or via program-internal use cases will perform this task.
5731 A more verbose listing will be produced if
5739 Otherwise the given variables (and arguments) are set or adjusted.
5740 Arguments are of the form
5742 (no space before or after
5746 if there is no value, i.e., a boolean variable.
5747 \*(ID In conjunction with the
5750 .Sx "Shell-style argument quoting"
5751 can be used to quote arguments as necessary.
5752 \*(ID Otherwise quotation marks may be placed around any part of the
5753 assignment statement to quote blanks or tabs.
5756 .Dl wysh set indentprefix=' -> '
5759 If an argument begins with
5763 the effect is the same as invoking the
5765 command with the remaining part of the variable
5766 .Pf ( Ql unset save ) .
5771 that is known to map to an environment variable will automatically cause
5772 updates in the program environment (unsetting a variable in the
5773 environment requires corresponding system support) \(em use the command
5775 for further environmental control.
5780 .Sx "INTERNAL VARIABLES"
5787 Apply shell quoting rules to the given raw-data arguments.
5791 .Sx "Command modifiers" ) ,
5792 The first argument specifies the operation:
5796 cause shell quoting to be applied to the remains of the line, and
5797 expanded away thereof, respectively.
5798 If the former is prefixed with a plus-sign, the quoted result will not
5799 be roundtrip enabled, and thus can be decoded only in the very same
5800 environment that was used to perform the encode; also see
5801 .Cd mle-quote-rndtrip .
5802 If the coding operation fails the error number
5805 .Va ^ERR Ns -CANCELED ,
5806 and the unmodified input is used as the result; the error number may
5807 change again due to output or result storage errors.
5811 (sh) Invokes an interactive version of the shell,
5812 and returns its exit status.
5816 .It Ic shortcut , unshortcut
5817 Without arguments the list of all currently defined shortcuts is
5818 shown, with one argument the expansion of the given shortcut.
5819 Otherwise all given arguments are treated as pairs of shortcuts and
5820 their expansions, creating new or changing already existing shortcuts,
5822 The latter command will remove all given shortcuts, the special name
5824 will remove all registered shortcuts.
5828 Shift the positional parameter stack (starting at
5830 by the given number (which must be an unsigned, positive, decimal),
5831 or 1 if no argument has been given.
5832 It is an error if the value exceeds the number of positional parameters.
5833 If the given number is 0, no action is performed, successfully.
5834 The stack as such can be managed via
5836 Note this command will fail in
5838 and hook macros unless the positional parameter stack has been
5839 explicitly created in the current context via
5846 but performs neither MIME decoding nor decryption, so that the raw
5847 message text is shown.
5851 (si) Shows the size in characters of each message of the given
5856 \*(NQ Sleep for the specified number of seconds (and optionally
5857 milliseconds), by default interruptably.
5858 If a third argument is given the sleep will be uninterruptible,
5859 otherwise the error number
5863 if the sleep has been interrupted.
5864 The command will fail and the error number will be
5865 .Va ^ERR Ns -OVERFLOW
5866 if the given duration(s) overflow the time datatype, and
5868 if the given durations are no valid integers.
5873 .It Ic sort , unsort
5874 The latter command disables sorted or threaded mode, returns to normal
5875 message order and, if the
5878 displays a header summary.
5879 The former command shows the current sorting criterion when used without
5880 an argument, but creates a sorted representation of the current folder
5881 otherwise, and changes the
5883 command and the addressing modes such that they refer to messages in
5885 Message numbers are the same as in regular mode.
5889 a header summary in the new order is also displayed.
5890 Automatic folder sorting can be enabled by setting the
5892 variable, as in, e.g.,
5893 .Ql set autosort=thread .
5894 Possible sorting criterions are:
5897 .Bl -tag -compact -width "subject"
5899 Sort the messages by their
5901 field, that is by the time they were sent.
5903 Sort messages by the value of their
5905 field, that is by the address of the sender.
5908 variable is set, the sender's real name (if any) is used.
5910 Sort the messages by their size.
5912 \*(OP Sort the message by their spam score, as has been classified by
5915 Sort the messages by their message status.
5917 Sort the messages by their subject.
5919 Create a threaded display.
5921 Sort messages by the value of their
5923 field, that is by the address of the recipient.
5926 variable is set, the recipient's real name (if any) is used.
5932 \*(NQ (so) The source command reads commands from the given file.
5933 .Sx "Filename transformations"
5935 If the given expanded argument ends with a vertical bar
5937 then the argument will instead be interpreted as a shell command and
5938 \*(UA will read the output generated by it.
5939 Interpretation of commands read is stopped when an error is encountered.
5942 cannot be used from within macros that execute as
5943 .Va folder-hook Ns s
5946 i.e., it can only be called from macros that were
5951 \*(NQ The difference to
5953 (beside not supporting pipe syntax aka shell command input) is that
5954 this command will not generate an error nor warn if the given file
5955 argument cannot be opened successfully.
5959 \*(OP Takes a list of messages and clears their
5965 \*(OP Takes a list of messages and causes the
5967 to forget it has ever used them to train its Bayesian filter.
5968 Unless otherwise noted the
5970 flag of the message is inspected to chose whether a message shall be
5978 \*(OP Takes a list of messages and informs the Bayesian filter of the
5982 This also clears the
5984 flag of the messages in question.
5988 \*(OP Takes a list of messages and rates them using the configured
5989 .Va spam-interface ,
5990 without modifying the messages, but setting their
5992 flag as appropriate; because the spam rating headers are lost the rate
5993 will be forgotten once the mailbox is left.
5994 Refer to the manual section
5996 for the complete picture of spam handling in \*(UA.
6000 \*(OP Takes a list of messages and sets their
6006 \*(OP Takes a list of messages and informs the Bayesian filter of the
6012 flag of the messages in question.
6028 slot for white- and blacklisting header fields.
6032 (to) Takes a message list and types out the first
6034 lines of each message on the users' terminal.
6035 Unless a special selection has been established for the
6039 command, the only header fields that are displayed are
6050 It is possible to apply compression to what is displayed by setting
6052 Messages are decrypted and converted to the terminal character set
6057 (tou) Takes a message list and marks the messages for saving in the
6059 .Sx "secondary mailbox"
6061 \*(UA deviates from the POSIX standard with this command,
6064 command will display the following message instead of the current one.
6070 but also displays header fields which would not pass the
6072 selection, and all visualizable parts of MIME
6073 .Ql multipart/alternative
6078 (t) Takes a message list and types out each message on the users terminal.
6079 The display of message headers is selectable via
6081 For MIME multipart messages, all parts with a content type of
6083 all parts which have a registered MIME type handler (see
6084 .Sx "HTML mail and MIME attachments" )
6085 which produces plain text output, and all
6087 parts are shown, others are hidden except for their headers.
6088 Messages are decrypted and converted to the terminal character set
6092 can be used to display parts which are not displayable as plain text.
6135 \*(OB Superseded by the multiplexer
6139 \*(OB Superseded by the multiplexer
6144 Superseded by the multiplexer
6155 .It Ic unmlsubscribe
6166 Takes a message list and marks each message as not having been read.
6170 Superseded by the multiplexer
6174 \*(OB Superseded by the multiplexer
6178 \*(OB Superseded by the multiplexer
6200 Perform URL percent codec operations on the raw-data argument, rather
6201 according to RFC 3986.
6205 .Sx "Command modifiers" ) ,
6206 and manages the error number
6208 This is a character set agnostic and thus locale dependent operation,
6209 and it may decode bytes which are invalid in the current
6211 \*(ID This command does not about URLs beside that.
6213 The first argument specifies the operation:
6217 perform plain URL percent en- and decoding, respectively.
6221 perform a slightly modified operation which should be better for
6222 pathnames: it does not allow a tilde
6224 and will neither accept hyphen-minus
6228 as an initial character.
6229 The remains of the line form the URL data which is to be converted.
6230 If the coding operation fails the error number
6233 .Va ^ERR Ns -CANCELED ,
6234 and the unmodified input is used as the result; the error number may
6235 change again due to output or result storage errors.
6239 \*(NQ Edit the values of or create the given variable(s) in the
6241 Boolean variables cannot be edited, and variables can also not be
6247 \*(NQ This command produces the same output as the listing mode of
6251 ity adjustments, but only for the given variables.
6255 \*(OP Takes a message list and verifies each message.
6256 If a message is not a S/MIME signed message,
6257 verification will fail for it.
6258 The verification process checks if the message was signed using a valid
6260 if the message sender's email address matches one of those contained
6261 within the certificate,
6262 and if the message content has been altered.
6275 \*(NQ Evaluate arguments according to a given operator.
6276 This is a multiplexer command which can be used to perform signed 64-bit
6277 numeric calculations as well as byte string and string operations.
6278 It uses polish notation, i.e., the operator is the first argument and
6279 defines the number and type, and the meaning of the remaining arguments.
6280 An empty argument is replaced with a 0 if a number is expected.
6284 .Sx "Command modifiers" ) .
6287 The result that is shown in case of errors is always
6289 for usage errors and numeric operations, and the empty string for byte
6290 string and string operations;
6291 if the latter two fail to provide result data for
6293 errors, e.g., when a search operation failed, they also set the
6296 .Va ^ERR Ns -NODATA .
6297 Except when otherwise noted numeric arguments are parsed as signed 64-bit
6298 numbers, and errors will be reported in the error number
6300 as the numeric error
6301 .Va ^ERR Ns -RANGE .
6304 Numeric operations work on one or two signed 64-bit integers.
6305 One integer is expected by assignment (equals sign
6307 which does nothing but parsing the argument, thus detecting validity and
6308 possible overflow conditions, and unary not (tilde
6310 which creates the bitwise complement.
6311 Two integers are used by addition (plus sign
6313 subtraction (hyphen-minus
6315 multiplication (asterisk
6319 and modulo (percent sign
6321 as well as for the bitwise operators logical or (vertical bar
6324 bitwise and (ampersand
6327 bitwise xor (circumflex
6329 the bitwise signed left- and right shifts
6332 as well as for the unsigned right shift
6336 All numeric operators can be suffixed with a commercial at
6340 this will turn the operation into a saturated one, which means that
6341 overflow errors and division and modulo by zero are no longer reported
6342 via the exit status, but the result will linger at the minimum or
6343 maximum possible value, instead of overflowing (or trapping).
6344 This is true also for the argument parse step.
6345 For the bitwise shifts, the saturated maximum is 63.
6346 Any catched overflow will be reported via the error number
6349 .Va ^ERR Ns -OVERFLOW .
6352 Character set agnostic string functions have no notion of locale
6353 settings and character sets.
6356 which performs the usual
6357 .Sx "Filename transformations"
6358 on its argument, and
6360 which generates a random string of the given length, or of
6362 bytes (a constant from
6364 if the value 0 is given; the random string will be base64url encoded
6365 according to RFC 4648, and thus be usable as a (portable) filename.
6368 Byte string operations work on 8-bit bytes and have no notion of locale
6369 settings and character sets, effectively assuming ASCII data.
6370 Operations that take one argument are
6372 which queries the length of the given argument, and
6374 which calculates the Chris Torek hash of the given argument.
6377 Byte string operations with two or more arguments are
6379 which byte-searches in the first for the second argument, and shows the
6380 resulting 0-based offset shall it have been found,
6382 which is identical to
6384 but works case-insensitively according to the rules of the ASCII
6387 will show a substring of its first argument:
6388 the second argument is the 0-based starting offset, the optional third
6389 argument can be used to specify the length of the desired substring,
6390 by default the entire string is used;
6391 this operation tries to work around faulty arguments (set
6393 for error logs), but reports them via the error number
6396 .Va ^ERR Ns -OVERFLOW .
6399 String operations work, sufficient support provided, according to the
6400 active user's locale encoding and character set (see
6401 .Sx "Character sets" ) .
6402 There is the one argument operation
6404 which (one-way) converts the argument to something safely printable on
6410 is a string operation that will try to match the first argument with the
6411 regular expression given as the second argument, as does
6413 but which is case-insensitive.
6414 If the optional third argument has been given then instead of showing
6415 the match offset a replacement operation is performed:
6416 the third argument is treated as if specified via dollar-single-quote
6418 .Sx "Shell-style argument quoting" ) ,
6419 and any occurrence of a positional parameter, e.g.,
6421 is replaced by the corresponding match group of the regular expression.
6423 .Bd -literal -offset indent
6424 ? vexpr -@ +1 -9223372036854775808
6425 ? vput vexpr res ir bananarama (.*)NanA(.*) '\e${1}au\e$2'
6432 \*(NQ Manage the positional parameter stack (see
6436 If the first argument is
6438 then the positional parameter stack of the current context, or the
6439 global one, if there is none, is cleared.
6442 then the remaining arguments will be used to (re)create the stack,
6443 if the parameter stack size limit is excessed an
6444 .Va ^ERR Ns -OVERFLOW
6448 If the first argument is
6450 a round-trip capable representation of the stack contents is created,
6451 with each quoted parameter separated from each other with the first
6454 and followed by the first character of
6456 if that is not empty and not identical to the first.
6457 If that results in no separation at all a
6463 .Sx "Command modifiers" ) .
6464 I.e., the subcommands
6468 can be used (in conjunction with
6470 to (re)create an argument stack from and to a single variable losslessly.
6472 .Bd -literal -offset indent
6473 ? vpospar set hey, "'you ", world!
6474 ? echo $#: <${1}><${2}><${3}>
6475 ? vput vpospar x quote
6477 ? echo $#: <${1}><${2}><${3}>
6478 ? eval vpospar set ${x}
6479 ? echo $#: <${1}><${2}><${3}>
6485 (v) Takes a message list and invokes the display editor on each message.
6486 Modified contents are discarded unless the
6488 variable is set, and are not used unless the mailbox can be written to
6489 and the editor returns a successful exit status.
6493 (w) For conventional messages the body without all headers is written.
6494 The original message is never marked for deletion in the originating
6496 The output is decrypted and converted to its native format as necessary.
6497 If the output file exists, the text is appended.
6498 If a message is in MIME multipart format its first part is written to
6499 the specified file as for conventional messages, handling of the remains
6500 depends on the execution mode.
6501 No special handling of compressed files is performed.
6503 In interactive mode the user is consecutively asked for the filenames of
6504 the processed parts.
6505 For convience saving of each part may be skipped by giving an empty
6506 value, the same result as writing it to
6508 Shell piping the part content by specifying a leading vertical bar
6510 character for the filename is supported.
6511 Other user input undergoes the usual
6512 .Sx "Filename transformations" ,
6513 and contents of the destination file are overwritten if the file
6516 \*(ID In non-interactive mode any part which does not specify a filename
6517 is ignored, and suspicious parts of filenames of the remaining parts are
6518 URL percent encoded (as via
6520 to prevent injection of malicious character sequences, resulting in
6521 a filename that will be written into the current directory.
6522 Existing files will not be overwritten, instead the part number or
6523 a dot are appended after a number sign
6525 to the name until file creation succeeds (or fails due to other
6530 \*(NQ The sole difference to
6532 is that the new macro is executed in place of the current one, which
6533 will not regain control; all resources of the current macro will be
6534 released before control is given to the replacer.
6535 Note this implies that
6537 may become cleaned up if the teared down macro context is the outermost
6538 level of the cleanup stack.
6539 If this command is not used from within a
6541 ed macro it will silently be (a more expensive variant of)
6551 \*(NQ \*(UA presents message headers in
6553 fuls as described under the
6556 Without arguments this command scrolls to the next window of messages,
6557 likewise if the argument is
6561 scrolls to the last,
6563 scrolls to the first, and
6568 A number argument prefixed by
6572 indicates that the window is calculated in relation to the current
6573 position, and a number without a prefix specifies an absolute position.
6579 but scrolls to the next or previous window that contains at least one
6589 .\" .Sh COMMAND ESCAPES {{{
6590 .Sh "COMMAND ESCAPES"
6592 Here is a summary of the command escapes available in compose mode,
6593 which are used to perform special functions when composing messages.
6594 Command escapes are only recognized at the beginning of lines, and
6595 consist of a trigger (escape) and a command character.
6596 The actual escape character can be set via the internal variable
6598 it defaults to the tilde
6600 Otherwise ignored whitespace characters following the escape character
6601 will prevent a possible addition of the command line to the \*(OPal
6605 Unless otherwise noted all compose mode commands ensure proper updates
6606 of the variables which represent the error number
6612 is set they will, unless stated otherwise, error out message compose
6613 mode if an operation fails.
6614 It is however possible to place the character hyphen-minus
6616 after (possible whitespace following) the escape character, which has an
6617 effect equivalent to the command modifier
6621 .Bl -tag -width ".It Ic BaNg"
6624 Insert the string of text in the message prefaced by a single
6626 (If the escape character has been changed,
6627 that character must be doubled instead.)
6630 .It Ic ~! Ar command
6631 Execute the indicated shell
6633 which follows, replacing unescaped exclamation marks with the previously
6634 executed command if the internal variable
6636 is set, then return to the message.
6640 Same effect as typing the end-of-file character.
6643 .It Ic ~: Ar \*(UA-command Ns \0or Ic ~_ Ar \*(UA-command
6644 Execute the given \*(UA command.
6645 Not all commands, however, are allowed.
6649 Write a summary of command escapes.
6652 .It Ic ~< Ar filename
6657 .It Ic ~<! Ar command
6659 is executed using the shell.
6660 Its standard output is inserted into the message.
6663 .It Ic ~@ Op Ar filename...
6664 Append or edit the list of attachments.
6665 Does not manage the error number
6671 instead if this is a concern).
6674 arguments is expected as shell tokens (see
6675 .Sx "Shell-style argument quoting" ;
6676 any token-separating commas are ignored), to be
6677 interpreted as documented for the command line option
6679 with the message number exception as below.
6682 arguments the attachment list is edited, entry by entry;
6683 if a filename is left empty, that attachment is deleted from the list;
6684 once the end of the list is reached either new attachments may be
6685 entered or the session can be quit by committing an empty
6688 For each mode, if a given filename solely consists of the number sign
6690 followed by a valid message number of the currently active mailbox, then
6691 the given message is attached as a MIME
6693 part (the number sign is the shell comment character and must be quoted).
6697 Inserts the string contained in the
6700 .Ql Ic ~i Ns \0Sign ) .
6701 \*(OB The escape sequences tabulator
6705 are understood (use the
6709 ting the variable(s) instead).
6713 Inserts the string contained in the
6716 .Ql Ic ~i Ns \0sign ) .
6717 \*(OB The escape sequences tabulator
6721 are understood (use the
6725 ting the variable(s) instead).
6728 .It Ic ~b Ar name ...
6729 Add the given names to the list of blind carbon copy recipients.
6732 .It Ic ~c Ar name ...
6733 Add the given names to the list of carbon copy recipients.
6737 Read the file specified by the
6739 variable into the message.
6743 Invoke the text editor on the message collected so far.
6744 After the editing session is finished,
6745 the user may continue appending text to the message.
6748 .It Ic ~F Ar messages
6749 Read the named messages into the message being sent, including all
6750 message headers and MIME parts.
6751 If no messages are specified, read in the current message.
6754 .It Ic ~f Ar messages
6755 Read the named messages into the message being sent.
6756 If no messages are specified, read in the current message.
6757 Strips down the list of header fields according to the
6759 white- and blacklist selection of
6761 For MIME multipart messages,
6762 only the first displayable part is included.
6766 Edit the message header fields
6771 by typing each one in turn and allowing the user to edit the field.
6772 The default values for these fields originate from the
6780 Edit the message header fields
6786 by typing each one in turn and allowing the user to edit the field.
6789 .It Ic ~i Ar variable
6790 Insert the value of the specified variable into the message,
6791 adding a newline character at the end.
6792 The message remains unaltered if the variable is unset or empty.
6793 \*(OB The escape sequences tabulator
6797 are understood (use the
6801 ting the variable(s) instead).
6804 .It Ic ~M Ar messages
6805 Read the named messages into the message being sent,
6808 If no messages are specified, read the current message, the
6812 .It Ic ~m Ar messages
6813 Read the named messages into the message being sent,
6816 If no messages are specified, read the current message.
6817 Strips down the list of header fields according to the
6819 white- and blacklist selection of
6821 For MIME multipart messages,
6822 only the first displayable part is included.
6826 Display the message collected so far,
6827 prefaced by the message header fields
6828 and followed by the attachment list, if any.
6832 Abort the message being sent,
6833 copying it to the file specified by the
6840 .It Ic ~R Ar filename
6843 but indent each line that has been read by
6847 .It Ic ~r Ar filename Op Ar HERE-delimiter
6848 Read the named file, object to the usual
6849 .Sx "Filename transformations" ,
6850 into the message; if (the expanded)
6854 then standard input is used, e.g., for pasting purposes.
6855 Only in this latter mode
6857 may be given: if it is data will be read in until the given
6859 is seen on a line by itself, and encountering EOF is an error; the
6861 is a required argument in non-interactive mode; if it is single-quote
6862 quoted then the pasted content will not be expanded, \*(ID otherwise
6863 a future version of \*(UA may perform shell-style expansion on the content.
6867 Cause the named string to become the current subject field.
6868 Newline (NL) and carriage-return (CR) bytes are invalid and will be
6869 normalized to space (SP) characters.
6872 .It Ic ~t Ar name ...
6873 Add the given name(s) to the direct recipient list.
6876 .It Ic ~U Ar messages
6877 Read in the given / current message(s) excluding all headers, indented by
6881 .It Ic ~u Ar messages
6882 Read in the given / current message(s), excluding all headers.
6886 Invoke an alternate editor (defined by the
6888 environment variable) on the message collected so far.
6889 Usually, the alternate editor will be a screen editor.
6890 After the editor is quit,
6891 the user may resume appending text to the end of the message.
6894 .It Ic ~w Ar filename
6895 Write the message onto the named file, which is object to the usual
6896 .Sx "Filename transformations" .
6898 the message is appended to it.
6904 except that the message is not saved at all.
6907 .It Ic ~| Ar command
6908 Pipe the message through the specified filter command.
6909 If the command gives no output or terminates abnormally,
6910 retain the original text of the message.
6913 is often used as a rejustifying filter.
6917 .It Ic ~^ Ar cmd Op Ar subcmd Op Ar arg3 Op Ar arg4
6918 Low-level command meant for scripted message access, i.e., for
6919 .Va on-compose-splice-shell
6921 .Va on-compose-splice .
6922 The used protocol is likely subject to changes, and therefore the
6923 mentioned hooks receive the used protocol version as an initial line.
6924 In general the first field of a response line represents a status code
6925 which specifies whether a command was successful or not, whether result
6926 data is to be expected, and if, the format of the result data.
6927 Does not manage the error number
6931 because errors are reported via the protocol
6932 (hard errors like I/O failures cannot be handled).
6933 This command has read-only access to several virtual pseudo headers in
6934 the \*(UA private namespace, which may not exist (except for the first):
6938 .Bl -tag -compact -width ".It Va BaNg"
6939 .It Ql Mailx-Command:
6940 The name of the command that generates the message, one of
6946 .It Ql Mailx-Raw-To:
6947 .It Ql Mailx-Raw-Cc:
6948 .It Ql Mailx-Raw-Bcc:
6949 Represent the frozen initial state of these headers before any
6950 transformation (e.g.,
6953 .Va recipients-in-cc
6956 .It Ql Mailx-Orig-From:
6957 .It Ql Mailx-Orig-To:
6958 .It Ql Mailx-Orig-Cc:
6959 .It Ql Mailx-Orig-Bcc:
6960 The values of said headers of the original message which has been
6962 .Ic reply , forward , resend .
6966 The status codes are:
6970 .Bl -tag -compact -width ".It Ql _210_"
6972 Status ok; the remains of the line are the result.
6975 Status ok; the rest of the line is optionally used for more status.
6976 What follows are lines of result addresses, terminated by an empty line.
6977 The address lines consist of two fields, the first of which is the
6978 plain address, e.g.,
6980 separated by a single ASCII SP space from the second which contains the
6981 unstripped address, even if that is identical to the first field, e.g.,
6982 .Ql (Lovely) Bob <bob@exam.ple> .
6983 (All the input, including the empty line, must be consumed before
6984 further commands can be issued.)
6987 Status ok; the rest of the line is optionally used for more status.
6988 What follows are lines of furtherly unspecified string content,
6989 terminated by an empty line.
6991 including the empty line, must be consumed before further commands can
6995 Syntax error; invalid command.
6998 Syntax error in parameters or arguments.
7001 Error: an argument fails verification.
7002 For example an invalid address has been specified, or an attempt was
7003 made to modify anything in \*(UAs own namespace.
7006 Error: an otherwise valid argument is rendered invalid due to context.
7007 For example, a second address is added to a header which may consist of
7008 a single address only.
7013 If a command indicates failure then the message will have remained
7015 Most commands can fail with
7017 if required arguments are missing (false command usage).
7018 The following (case-insensitive) commands are supported:
7021 .Bl -hang -width ".It Cm header"
7023 This command allows listing, inspection, and editing of message headers.
7024 Header name case is not normalized, and case-insensitive comparison
7025 should be used when matching names.
7026 The second argument specifies the subcommand to apply, one of:
7028 .Bl -hang -width ".It Cm remove"
7030 Without a third argument a list of all yet existing headers is given via
7032 this command is the default command of
7034 if no second argument has been given.
7035 A third argument restricts output to the given header only, which may
7038 if no such field is defined.
7041 Shows the content of the header given as the third argument.
7042 Dependent on the header type this may respond with
7046 any failure results in
7050 This will remove all instances of the header given as the third
7055 if no such header can be found, and
7057 on \*(UA namespace violations.
7060 This will remove from the header given as the third argument the
7061 instance at the list position (counting from one!) given with the fourth
7066 if the list position argument is not a number or on \*(UA namespace
7069 if no such header instance exists.
7072 Create a new or an additional instance of the header given in the third
7073 argument, with the header body content as given in the fourth argument
7074 (the remains of the line).
7077 if the third argument specifies a free-form header field name that is
7078 invalid, or if body content extraction fails to succeed,
7080 if any extracted address does not pass syntax and/or security checks or
7081 on \*(UA namespace violations, and
7083 to indicate prevention of excessing a single-instance header \(em note that
7085 can be appended to (a space separator will be added automatically first).
7088 is returned upon success, followed by the name of the header and the list
7089 position of the newly inserted instance.
7090 The list position is always 1 for single-instance header fields.
7091 All free-form header fields are managed in a single list.
7096 This command allows listing, removal and addition of message attachments.
7097 The second argument specifies the subcommand to apply, one of:
7099 .Bl -hang -width ".It Cm remove"
7101 List all attachments via
7105 if no attachments exist.
7106 This command is the default command of
7108 if no second argument has been given.
7111 This will remove the attachment given as the third argument, and report
7115 if no such attachment can be found.
7116 If there exists any path component in the given argument, then an exact
7117 match of the path which has been used to create the attachment is used
7118 directly, but if only the basename of that path matches then all
7119 attachments are traversed to find an exact match first, and the removal
7120 occurs afterwards; if multiple basenames match, a
7123 Message attachments are treated as absolute pathnames.
7125 If no path component exists in the given argument, then all attachments
7126 will be searched for
7128 parameter matches as well as for matches of the basename of the path
7129 which has been used when the attachment has been created; multiple
7134 This will interpret the third argument as a number and remove the
7135 attachment at that list position (counting from one!), reporting
7139 if the argument is not a number or
7141 if no such attachment exists.
7144 Adds the attachment given as the third argument, specified exactly as
7145 documented for the command line option
7147 and supporting the message number extension as documented for
7151 upon success, with the index of the new attachment following,
7153 if the given file cannot be opened,
7155 if an on-the-fly performed character set conversion fails, otherwise
7157 is reported; this is also reported if character set conversion is
7158 requested but not available.
7161 This uses the same search mechanism as described for
7163 and prints any known attributes of the first found attachment via
7167 if no such attachment can be found.
7168 The attributes are written as lines of keyword and value tuples, the
7169 keyword being separated from the rest of the line with an ASCII SP space
7173 This uses the same search mechanism as described for
7175 and is otherwise identical to
7178 .It Cm attribute-set
7179 This uses the same search mechanism as described for
7181 and will assign the attribute given as the fourth argument, which is
7182 expected to be a value tuple of keyword and other data, separated by
7183 a ASCII SP space or TAB tabulator character.
7184 If the value part is empty, then the given attribute is removed, or
7185 reset to a default value if existence of the attribute is crucial.
7189 upon success, with the index of the found attachment following,
7191 for message attachments or if the given keyword is invalid, and
7193 if no such attachment can be found.
7194 The following keywords may be used (case-insensitively):
7196 .Bl -hang -compact -width ".It Ql filename"
7198 Sets the filename of the MIME part, i.e., the name that is used for
7199 display and when (suggesting a name for) saving (purposes).
7200 .It Ql content-description
7201 Associate some descriptive information to the attachment's content, used
7202 in favour of the plain filename by some MUAs.
7204 May be used for uniquely identifying MIME entities in several contexts;
7205 this expects a special reference address format as defined in RFC 2045
7208 upon address content verification failure.
7210 Defines the media type/subtype of the part, which is managed
7211 automatically, but can be overwritten.
7212 .It Ql content-disposition
7213 Automatically set to the string
7217 .It Cm attribute-set-at
7218 This uses the same search mechanism as described for
7220 and is otherwise identical to
7230 .\" .Sh INTERNAL VARIABLES {{{
7231 .Sh "INTERNAL VARIABLES"
7233 Internal \*(UA variables are controlled via the
7237 commands; prefixing a variable name with the string
7241 has the same effect as using
7247 Creation or editing of variables can be performed in the
7252 will give more insight on the given variable(s), and
7254 when called without arguments, will show a listing of all variables.
7255 Both commands support a more
7258 Some well-known variables will also become inherited from the
7261 implicitly, others can be explicitly imported with the command
7263 and henceforth share said properties.
7266 Two different kind of internal variables exist.
7267 There are boolean variables, which can only be in one of the two states
7271 and value variables with a(n optional) string value.
7272 For the latter proper quoting is necessary upon assignment time, the
7273 introduction of the section
7275 documents the supported quoting rules.
7277 .Bd -literal -offset indent
7278 wysh set one=val\e 1 two="val 2" \e
7279 three='val "3"' four=$'val \e'4\e''; \e
7280 varshow one two three four; \e
7281 unset one two three four
7285 Dependent upon the actual option the string values will be interpreted
7286 as numbers, colour names, normal text etc., but there also exists
7287 a special kind of string value, the
7288 .Dq boolean string ,
7289 which must either be a decimal integer (in which case
7293 and any other value is true) or any of the (case-insensitive) strings
7299 for a false boolean and
7305 for a true boolean; a special kind of boolean string is the
7307 which is a boolean string that can optionally be prefixed with the
7308 (case-insensitive) term
7312 which causes prompting of the user in interactive mode, with the given
7313 boolean as the default value.
7315 .\" .Ss "Initial settings" {{{
7316 .\" (Keep in SYNC: ./nail.h:okeys, ./nail.rc, ./nail.1:"Initial settings")
7317 .Ss "Initial settings"
7319 The standard POSIX 2008/Cor 2-2016 mandates the following initial
7325 .Pf no Va autoprint ,
7339 .Pf no Va ignoreeof ,
7341 .Pf no Va keepsave ,
7343 .Pf no Va outfolder ,
7351 .Pf no Va sendwait ,
7360 Notes: \*(UA does not support the
7362 variable \(en use command line options or
7364 to pass options through to a
7366 And the default global
7368 file, which is loaded unless the
7370 (with according argument) or
7372 command line options have been used, or the
7373 .Ev MAILX_NO_SYSTEM_RC
7374 environment variable is set (see
7375 .Sx "Resource files" )
7376 bends those initial settings a bit, e.g., it sets the variables
7381 to name a few, establishes a default
7383 selection etc., and should thus be taken into account.
7386 .\" .Ss "Variables" {{{
7389 .Bl -tag -width ".It Va BaNg"
7393 \*(RO The exit status of the last command, or the
7398 This status has a meaning in the state machine: in conjunction with
7400 any non-0 exit status will cause a program exit, and in
7402 mode any error while loading (any of the) resource files will have the
7406 .Sx "Command modifiers" ,
7407 can be used to instruct the state machine to ignore errors.
7411 \*(RO The current error number
7412 .Pf ( Xr errno 3 ) ,
7413 which is set after an error occurred; it is also available via
7415 and the error name and documentation string can be queried via
7419 \*(ID This machinery is new and the error number is only really usable
7420 if a command explicitly states that it manages the variable
7422 for others errno will be used in case of errors, or
7424 if that is 0: it thus may or may not reflect the real error.
7425 The error number may be set with the command
7431 \*(RO This is a multiplexer variable which performs dynamic expansion of
7432 the requested state or condition, of which there are:
7435 .Bl -tag -compact -width ".It Va BaNg"
7439 .It Va ^ERR , ^ERRDOC , ^ERRNAME
7440 The number, documentation, and name of the current
7442 respectively, which is usually set after an error occurred.
7443 \*(ID This machinery is new and is usually reliable only if a command
7444 explicitly states that it manages the variable
7446 which is effectively identical to
7448 Each of those variables can be suffixed with a hyphen minus followed by
7449 a name or number, in which case the expansion refers to the given error.
7450 Note this is a direct mapping of (a subset of) the system error values:
7451 .Bd -literal -offset indent
7453 eval echo \e$1: \e$^ERR-$1: \e$^ERRNAME-$1: \e$^ERRDOC-$1
7454 vput vexpr i + "$1" 1
7466 \*(RO Expands all positional parameters (see
7468 separated by a space character.
7469 \*(ID The special semantics of the equally named special parameter of the
7471 are not yet supported.
7475 \*(RO Expands all positional parameters (see
7477 separated by a space character.
7478 If placed in double quotation marks, each positional parameter is
7479 properly quoted to expand to a single parameter again.
7483 \*(RO Expands to the number of positional parameters in decimal.
7487 \*(RO Inside the scope of a
7491 ed macro this expands to the name of the calling macro, or to the empty
7492 string if the macro is running from top-level.
7493 For the \*(OPal regular expression search and replace operator of
7495 this expands to the entire matching expression.
7496 It represents the program name in global context.
7500 \*(RO Access of the positional parameter stack.
7501 All further parameters can be accessed with this syntax, too, e.g.,
7504 etc.; positional parameters can be shifted off the stack by calling
7506 The parameter stack contains, e.g., the arguments of a
7510 d macro, the matching groups of the \*(OPal regular expression search
7511 and replace expression of
7513 and can be explicitly created or overwritten with the command
7518 \*(RO Is set to the active
7522 .It Va add-file-recipients
7523 \*(BO When file or pipe recipients have been specified,
7524 mention them in the corresponding address fields of the message instead
7525 of silently stripping them from their recipient list.
7526 By default such addressees are not mentioned.
7530 \*(BO Causes only the local part to be evaluated
7531 when comparing addresses.
7535 \*(BO Causes messages saved in the
7537 .Sx "secondary mailbox"
7539 to be appended to the end rather than prepended.
7540 This should always be set.
7544 \*(BO Causes \*(UA to prompt for the subject of each message sent.
7545 If the user responds with simply a newline,
7546 no subject field will be sent.
7550 \*(BO Causes the prompts for
7554 lists to appear after the message has been edited.
7558 \*(BO If set, \*(UA asks for files to attach at the end of each message,
7559 shall the list be found empty at that time.
7560 An empty line finalizes the list.
7564 \*(BO Causes the user to be prompted for carbon copy recipients
7565 (at the end of each message if
7569 are set) shall the list be found empty (at that time).
7570 An empty line finalizes the list.
7574 \*(BO Causes the user to be prompted for blind carbon copy
7575 recipients (at the end of each message if
7579 are set) shall the list be found empty (at that time).
7580 An empty line finalizes the list.
7584 \*(BO\*(OP Causes the user to be prompted if the message is to be
7585 signed at the end of each message.
7588 variable is ignored when this variable is set.
7592 \*(BO Alternative name for
7597 A sequence of characters to display in the
7601 as shown in the display of
7603 each for one type of messages (see
7604 .Sx "Message states" ) ,
7605 with the default being
7608 .Ql NU\ \ *HMFAT+\-$~
7611 variable is set, in the following order:
7613 .Bl -tag -compact -width ".It Ql _"
7635 start of a collapsed thread.
7637 an uncollapsed thread (TODO ignored for now).
7641 classified as possible spam.
7647 Specifies a list of recipients to which a blind carbon copy of each
7648 outgoing message will be sent automatically.
7652 Specifies a list of recipients to which a carbon copy of each outgoing
7653 message will be sent automatically.
7657 \*(BO Causes threads to be collapsed automatically when threaded mode
7664 \*(BO Enable automatic
7666 ing of a(n existing)
7672 commands, e.g., the message that becomes the new
7674 is shown automatically, as via
7680 \*(BO\*(OB Causes threaded mode (see the
7682 command) to be entered automatically when a folder is opened.
7684 .Ql autosort=thread .
7688 Causes sorted mode (see the
7690 command) to be entered automatically with the value of this variable as
7691 sorting method when a folder is opened, e.g.,
7692 .Ql set autosort=thread .
7696 \*(BO Enables the substitution of all not (reverse-solidus) escaped
7699 characters by the contents of the last executed command for the
7701 shell escape command and
7703 one of the compose mode
7704 .Sx "COMMAND ESCAPES" .
7705 If this variable is not set no reverse solidus stripping is performed.
7707 .It Va batch-exit-on-error
7708 \*(OB\*(BO Predecessor of
7713 \*(OP Terminals generate multi-byte sequences for certain forms of
7714 input, for example for function and other special keys.
7715 Some terminals however do not write these multi-byte sequences as
7716 a whole, but byte-by-byte, and the latter is what \*(UA actually reads.
7717 This variable specifies the timeout in milliseconds that the MLE (see
7718 .Sx "On terminal control and line editor" )
7719 waits for more bytes to arrive unless it considers a sequence
7725 \*(BO Sets some cosmetical features to traditional BSD style;
7726 has the same affect as setting
7728 and all other variables prefixed with
7730 it also changes the behaviour of
7732 (which does not exist in BSD).
7736 \*(BO Changes the letters shown in the first column of a header
7737 summary to traditional BSD style.
7741 \*(BO Changes the display of columns in a header summary to traditional
7746 \*(BO Changes some informational messages to traditional BSD style.
7752 field to appear immediately after the
7754 field in message headers and with the
7756 .Sx "COMMAND ESCAPES" .
7760 .It Va build-os , build-osenv
7761 \*(RO The operating system \*(UA has been build for, usually taken from
7767 respectively, the former being lowercased.
7771 The value that should appear in the
7775 MIME header fields when no character set conversion of the message data
7777 This defaults to US-ASCII, and the chosen character set should be
7778 US-ASCII compatible.
7782 \*(OP The default 8-bit character set that is used as an implicit last
7783 member of the variable
7785 This defaults to UTF-8 if character set conversion capabilities are
7786 available, and to ISO-8859-1 otherwise, in which case the only supported
7789 and this variable is effectively ignored.
7790 Refer to the section
7791 .Sx "Character sets"
7792 for the complete picture of character set conversion in \*(UA.
7795 .It Va charset-unknown-8bit
7796 \*(OP RFC 1428 specifies conditions when internet mail gateways shall
7798 the content of a mail message by using a character set with the name
7800 Because of the unclassified nature of this character set \*(UA will not
7801 be capable to convert this character set to any other character set.
7802 If this variable is set any message part which uses the character set
7804 is assumed to really be in the character set given in the value,
7805 otherwise the (final) value of
7807 is used for this purpose.
7809 This variable will also be taken into account if a MIME type (see
7810 .Sx "The mime.types files" )
7811 of a MIME message part that uses the
7813 character set is forcefully treated as text.
7817 The default value for the
7822 .It Va colour-disable
7823 \*(BO\*(OP Forcefully disable usage of colours.
7824 Also see the section
7825 .Sx "Coloured display" .
7829 \*(BO\*(OP Whether colour shall be used for output that is paged through
7831 Note that pagers may need special command line options, e.g.,
7839 in order to support colours.
7840 Often doing manual adjustments is unnecessary since \*(UA may perform
7841 adjustments dependent on the value of the environment variable
7843 (see there for more).
7847 .It Va contact-mail , contact-web
7848 \*(RO Addresses for contact per email and web, respectively, e.g., for
7849 bug reports, suggestions, or help regarding \*(UA.
7850 The former can be used directly:
7851 .Ql ? eval mail $contact-mail .
7855 In a(n interactive) terminal session, then if this valued variable is
7856 set it will be used as a threshold to determine how many lines the given
7857 output has to span before it will be displayed via the configured
7861 can be forced by setting this to the value
7863 setting it without a value will deduce the current height of the
7864 terminal screen to compute the treshold (see
7869 \*(ID At the moment this uses the count of lines of the message in wire
7870 format, which, dependent on the
7872 of the message, is unrelated to the number of display lines.
7873 (The software is old and historically the relation was a given thing.)
7877 Define a set of custom headers to be injected into newly composed or
7878 forwarded messages; it is also possible to create custom headers in
7881 which can be automated by setting one of the hooks
7882 .Va on-compose-splice
7884 .Va on-compose-splice-shell .
7885 The value is interpreted as a comma-separated list of custom headers to
7886 be injected, to include commas in the header bodies escape them with
7888 \*(ID Overwriting of automatically managed headers is neither supported
7891 .Dl set customhdr='Hdr1: Body1-1\e, Body1-2, Hdr2: Body2'
7895 Controls the appearance of the
7897 date and time format specification of the
7899 variable, that is used, for example, when viewing the summary of
7901 If unset, then the local receiving date is used and displayed
7902 unformatted, otherwise the message sending
7904 It is possible to assign a
7906 format string and control formatting, but embedding newlines via the
7908 format is not supported, and will result in display errors.
7910 .Ql %Y-%m-%d %H:%M ,
7912 .Va datefield-markout-older .
7915 .It Va datefield-markout-older
7916 Only used in conjunction with
7918 Can be used to create a visible distinction of messages dated more than
7919 a day in the future, or older than six months, a concept comparable to the
7921 option of the POSIX utility
7923 If set to the empty string, then the plain month, day and year of the
7925 will be displayed, but a
7927 format string to control formatting can be assigned.
7933 \*(BO Enables debug messages and obsoletion warnings, disables the
7934 actual delivery of messages and also implies
7940 .It Va disposition-notification-send
7942 .Ql Disposition-Notification-To:
7943 header (RFC 3798) with the message.
7947 .\" TODO .It Va disposition-notification-send-HOST
7949 .\".Va disposition-notification-send
7950 .\" for SMTP accounts on a specific host.
7951 .\" TODO .It Va disposition-notification-send-USER@HOST
7953 .\".Va disposition-notification-send
7954 .\"for a specific account.
7958 \*(BO When dot is set, a period
7960 on a line by itself during message input in (interactive or batch
7962 compose mode will be treated as end-of-message (in addition to the
7963 normal end-of-file condition).
7964 This behaviour is implied in
7970 .It Va dotlock-ignore-error
7971 \*(BO\*(OP Synchronization of mailboxes which \*(UA treats as
7973 .Sx "primary system mailbox" Ns
7974 es (see, e.g., the notes on
7975 .Sx "Filename transformations" ,
7976 as well as the documentation of
7978 will be protected with so-called dotlock files\(emthe traditional mail
7979 spool file locking method\(emin addition to system file locking.
7980 Because \*(UA ships with a privilege-separated dotlock creation program
7981 that should always be able to create such a dotlock file there is no
7982 good reason to ignore dotlock file creation errors, and thus these are
7983 fatal unless this variable is set.
7987 \*(BO If this variable is set then the editor is started automatically
7988 when a message is composed in interactive mode, as if the
7990 .Sx "COMMAND ESCAPES"
7994 variable is implied for this automatically spawned editor session.
7998 \*(BO When a message is edited while being composed,
7999 its header is included in the editable text.
8009 fields are accepted within the header, other fields are ignored.
8013 \*(BO When entering interactive mode \*(UA normally writes
8014 .Dq \&No mail for user
8015 and exits immediately if a mailbox is empty or does not exist.
8016 If this variable is set \*(UA starts even with an empty or non-existent
8017 mailbox (the latter behaviour furtherly depends upon
8023 \*(BO Let each command with a non-0 exit status, including every
8027 s a non-0 status, cause a program exit unless prefixed by
8030 .Sx "Command modifiers" ) ;
8031 please refer to the variable
8033 for more on this topic.
8037 The first character of this value defines the escape character for
8038 .Sx "COMMAND ESCAPES"
8040 The default value is the character tilde
8042 If set to the empty string, command escapes are disabled.
8046 If not set then file and command pipeline targets are not allowed,
8047 and any such address will be filtered out, giving a warning message.
8048 If set without a value then all possible recipient address
8049 specifications will be accepted \(en see the section
8050 .Sx "On sending mail, and non-interactive mode"
8052 To accept them, but only in interactive mode, or when tilde commands
8053 were enabled explicitly by using one of the command line options
8057 set this to the (case-insensitive) value
8059 (it actually acts like
8060 .Ql restrict,-all,+name,+addr ,
8061 so that care for ordering issues must be taken) .
8063 In fact the value is interpreted as a comma-separated list of values.
8066 then the existence of disallowed specifications is treated as a hard
8067 send error instead of only filtering them out.
8068 The remaining values specify whether a specific type of recipient
8069 address specification is allowed (optionally indicated by a plus sign
8071 prefix) or disallowed (prefixed with a hyphen-minus
8075 addresses all possible address specifications,
8079 command pipeline targets,
8081 plain user names and (MTA) aliases (\*(OB
8083 may be used as an alternative syntax to
8088 These kind of values are interpreted in the given order, so that
8089 .Ql restrict,\:fail,\:+file,\:-all,\:+addr
8090 will cause hard errors for any non-network address recipient address
8091 unless \*(UA is in interactive mode or has been started with the
8095 command line option; in the latter case(s) any address may be used, then.
8097 Historically invalid network addressees are silently stripped off.
8098 To change this and ensure that any encountered invalid email address
8099 instead causes a hard error, ensure the string
8101 is an entry in the above list.
8102 Setting this automatically enables network addressees
8103 (it actually acts like
8104 .Ql failinvaddr,+addr ,
8105 so that care for ordering issues must be taken) .
8109 Unless this variable is set additional
8111 (Mail-Transfer-Agent)
8112 arguments from the command line, as can be given after a
8114 separator, are ignored due to safety reasons.
8115 However, if set to the special (case-insensitive) value
8117 then the presence of additional MTA arguments is treated as a hard
8118 error that causes \*(UA to exit with failure status.
8119 A lesser strict variant is the otherwise identical
8121 which does accept such arguments in interactive mode, or if tilde
8122 commands were enabled explicitly by using one of the command line options
8129 \*(RO String giving a list of features \*(UA, preceded with a plus sign
8131 if the feature is available, and a hyphen-minus
8134 The output of the command
8136 will include this information.
8140 \*(BO This setting reverses the meanings of a set of reply commands,
8141 turning the lowercase variants, which by default address all recipients
8142 included in the header of a message
8143 .Pf ( Ic reply , respond , followup )
8144 into the uppercase variants, which by default address the sender only
8145 .Pf ( Ic Reply , Respond , Followup )
8148 .Ic replysender , respondsender , followupsender
8150 .Ic replyall , respondall , followupall
8151 are not affected by the current setting of
8156 The default path under which mailboxes are to be saved:
8157 filenames that begin with the plus sign
8159 will have the plus sign replaced with the value of this variable if set,
8160 otherwise the plus sign will remain unchanged when doing
8161 .Sx "Filename transformations" ;
8164 for more on this topic.
8165 The value supports a subset of transformations itself, and if the
8166 non-empty value does not start with a solidus
8170 will be prefixed automatically.
8171 Once the actual value is evaluated first, the internal variable
8173 will be updated for caching purposes.
8177 This variable can be set to the name of a
8179 macro which will be called whenever a
8182 The macro will also be invoked when new mail arrives,
8183 but message lists for commands executed from the macro
8184 only include newly arrived messages then.
8186 are activated by default in a folder hook, causing the covered settings
8187 to be reverted once the folder is left again.
8190 Macro behaviour, including option localization, will change in v15.
8191 One should be aware of that and possibly embed version checks in the
8192 used resource file(s).
8195 .It Va folder-hook-FOLDER
8200 Unlike other folder specifications, the fully expanded name of a folder,
8201 without metacharacters, is used to avoid ambiguities.
8202 However, if the mailbox resides under
8206 specification is tried in addition, e.g., if
8210 (and thus relative to the user's home directory) then
8211 .Pa /home/usr1/mail/sent
8213 .Ql folder-hook-/home/usr1/mail/sent
8214 first, but then followed by
8215 .Ql folder-hook-+sent .
8218 .It Va folder-resolved
8219 \*(RO Set to the fully resolved path of
8221 once that evaluation has occurred; rather internal.
8225 \*(BO Controls whether a
8226 .Ql Mail-Followup-To:
8227 header is generated when sending messages to known mailing lists.
8229 .Va followup-to-honour
8231 .Ic mlist , mlsubscribe , reply
8236 .It Va followup-to-honour
8238 .Ql Mail-Followup-To:
8239 header is honoured when group-replying to a message via
8243 This is a quadoption; if set without a value it defaults to
8253 .It Va forward-as-attachment
8254 \*(BO Original messages are normally sent as inline text with the
8257 and only the first part of a multipart message is included.
8258 With this setting enabled messages are sent as unmodified MIME
8260 attachments with all of their parts included.
8263 .It Va forward-inject-head
8264 The string to put before the text of a message with the
8266 command instead of the default
8267 .Dq -------- Original Message -------- .
8268 No heading is put if it is set to the empty string.
8269 This variable is ignored if the
8270 .Va forward-as-attachment
8275 The address (or a list of addresses) to put into the
8277 field of the message header, quoting RFC 5322:
8278 the author(s) of the message, that is, the mailbox(es) of the person(s)
8279 or system(s) responsible for the writing of the message.
8282 ing to messages these addresses are handled as if they were in the
8286 If the machine's hostname is not valid at the Internet (for example at
8287 a dialup machine) then either this variable or
8289 (\*(IN and with a defined SMTP protocol in
8292 adds even more fine-tuning capabilities),
8296 contains more than one address,
8299 variable is required (according to the standard RFC 5322).
8301 If a file-based MTA is used, then
8303 (or, if that contains multiple addresses,
8305 can nonetheless be enforced to appear as the envelope sender address at
8306 the MTA protocol level (the RFC 5321 reverse-path), either by using the
8308 command line option (with an empty argument; see there for the complete
8309 picture on this topic), or by setting the internal variable
8310 .Va r-option-implicit .
8314 \*(BO When replying to or forwarding a message \*(UA normally removes
8315 the comment and name parts of email addresses.
8316 If this variable is set such stripping is not performed,
8317 and comments, names etc. are retained.
8320 \*(OB Predecessor of
8321 .Va forward-inject-head .
8325 \*(BO Causes the header summary to be written at startup and after
8326 commands that affect the number of messages or the order of messages in
8331 mode a header summary will also be displayed on folder changes.
8332 The command line option
8340 A format string to use for the summary of
8342 similar to the ones used for
8345 Format specifiers in the given string start with a percent sign
8347 and may be followed by an optional decimal number indicating the field
8348 width \(em if that is negative, the field is to be left-aligned.
8349 Valid format specifiers are:
8352 .Bl -tag -compact -width ".It Ql _%%_"
8354 A plain percent sign.
8357 a space character but for the current message
8359 for which it expands to
8363 a space character but for the current message
8365 for which it expands to
8368 \*(OP The spam score of the message, as has been classified via the
8371 Shows only a replacement character if there is no spam support.
8373 Message attribute character (status flag); the actual content can be
8377 The date found in the
8379 header of the message when
8381 is set (the default), otherwise the date when the message was received.
8382 Formatting can be controlled by assigning a
8387 The indenting level in threaded mode.
8389 The address of the message sender.
8391 The message thread tree structure.
8392 (Note that this format does not support a field width.)
8394 The number of lines of the message, if available.
8398 The number of octets (bytes) in the message, if available.
8400 Message subject (if any).
8402 Message subject (if any) in double quotes.
8404 Message recipient flags: is the addressee of the message a known or
8405 subscribed mailing list \(en see
8410 The position in threaded/sorted order.
8414 .Ql %>\&%a\&%m\ %-18f\ %16d\ %4l/%\-5o\ %i%-s ,
8416 .Ql %>\&%a\&%m\ %20-f\ \ %16d\ %3l/%\-5o\ %i%-S
8427 .It Va headline-bidi
8428 Bidirectional text requires special treatment when displaying headers,
8429 because numbers (in dates or for file sizes etc.) will not affect the
8430 current text direction, in effect resulting in ugly line layouts when
8431 arabic or other right-to-left text is to be displayed.
8432 On the other hand only a minority of terminals is capable to correctly
8433 handle direction changes, so that user interaction is necessary for
8435 Note that extended host system support is required nonetheless, e.g.,
8436 detection of the terminal character set is one precondition;
8437 and this feature only works in an Unicode (i.e., UTF-8) locale.
8439 In general setting this variable will cause \*(UA to encapsulate text
8440 fields that may occur when displaying
8442 (and some other fields, like dynamic expansions in
8444 with special Unicode control sequences;
8445 it is possible to fine-tune the terminal support level by assigning
8447 no value (or any value other than
8452 will make \*(UA assume that the terminal is capable to properly deal
8453 with Unicode version 6.3, in which case text is embedded in a pair of
8454 U+2068 (FIRST STRONG ISOLATE) and U+2069 (POP DIRECTIONAL ISOLATE)
8456 In addition no space on the line is reserved for these characters.
8458 Weaker support is chosen by using the value
8460 (Unicode 6.3, but reserve the room of two spaces for writing the control
8461 sequences onto the line).
8466 select Unicode 1.1 support (U+200E, LEFT-TO-RIGHT MARK); the latter
8467 again reserves room for two spaces in addition.
8471 \*(OP If a line editor is available then this can be set to
8472 name the (expandable) path of the location of a permanent history file.
8477 .It Va history-gabby
8478 \*(BO\*(OP Add more entries to the history as is normally done.
8481 .It Va history-gabby-persist
8482 \*(BO\*(OP \*(UA's own MLE will not save the additional
8484 entries in persistent storage unless this variable is set.
8485 On the other hand it will not loose the knowledge of whether
8486 a persistent entry was gabby or not.
8492 \*(OP Setting this variable imposes a limit on the number of concurrent
8494 If set to the value 0 then no further history entries will be added, and
8495 loading and incorporation of the
8497 upon program startup can also be suppressed by doing this.
8498 Runtime changes will not be reflected, but will affect the number of
8499 entries saved to permanent storage.
8503 \*(BO This setting controls whether messages are held in the system
8505 and it is set by default.
8509 Use this string as hostname when expanding local addresses instead of
8510 the value obtained from
8514 It is used, e.g., in
8518 fields, as well as when generating
8520 MIME part related unique ID fields.
8521 Setting it to the empty string will cause the normal hostname to be
8522 used, but nonetheless enables creation of said ID fields.
8523 \*(IN in conjunction with the built-in SMTP
8526 also influences the results:
8527 one should produce some test messages with the desired combination of
8536 \*(BO\*(OP Can be used to turn off the automatic conversion of domain
8537 names according to the rules of IDNA (internationalized domain names
8539 Since the IDNA code assumes that domain names are specified with the
8541 character set, an UTF-8 locale charset is required to represent all
8542 possible international domain names (before conversion, that is).
8546 The input field separator that is used (\*(ID by some functions) to
8547 determine where to split input data.
8549 .Bl -tag -compact -width ".It MMM"
8551 Unsetting is treated as assigning the default value,
8554 If set to the empty value, no field splitting will be performed.
8556 If set to a non-empty value, all whitespace characters are extracted
8557 and assigned to the variable
8561 .Bl -tag -compact -width ".It MMM"
8564 will be ignored at the beginning and end of input.
8565 Diverging from POSIX shells default whitespace is removed in addition,
8566 which is owed to the entirely different line content extraction rules.
8568 Each occurrence of a character of
8570 will cause field-splitting, any adjacent
8572 characters will be skipped.
8577 \*(RO Automatically deduced from the whitespace characters in
8582 \*(BO Ignore interrupt signals from the terminal while entering
8583 messages; instead echo them as
8585 characters and discard the current line.
8589 \*(BO Ignore end-of-file conditions
8590 .Pf ( Ql control-D )
8591 in compose mode on message input and in interactive command input.
8592 If set an interactive command input session can only be left by
8593 explicitly using one of the commands
8597 and message input in compose mode can only be terminated by entering
8600 on a line by itself or by using the
8602 .Sx "COMMAND ESCAPES" ;
8603 Setting this implies the behaviour that
8611 If this is set to a non-empty string it will specify the users
8613 .Sx "primary system mailbox" ,
8616 and the system-dependent default, and (thus) be used to replace
8619 .Sx "Filename transformations" ;
8622 for more on this topic.
8623 The value supports a subset of transformations itself.
8631 .Sx "COMMAND ESCAPES"
8634 option for indenting messages,
8635 in place of the normal tabulator character
8637 which is the default.
8638 Be sure to quote the value if it contains spaces or tabs.
8642 \*(BO If set, an empty
8644 .Sx "primary system mailbox"
8645 file is not removed.
8646 Note that, in conjunction with
8648 any empty file will be removed unless this variable is set.
8649 This may improve the interoperability with other mail user agents
8650 when using a common folder directory, and prevents malicious users
8651 from creating fake mailboxes in a world-writable spool directory.
8652 \*(ID Only local regular (MBOX) files are covered, Maildir or other
8653 mailbox types will never be removed, even if empty.
8656 .It Va keep-content-length
8657 \*(BO When (editing messages and) writing MBOX mailbox files \*(UA can
8662 header fields that some MUAs generate by setting this variable.
8663 Since \*(UA does neither use nor update these non-standardized header
8664 fields (which in itself shows one of their conceptual problems),
8665 stripping them should increase interoperability in between MUAs that
8666 work with with same mailbox files.
8667 Note that, if this is not set but
8668 .Va writebackedited ,
8669 as below, is, a possibly performed automatic stripping of these header
8670 fields already marks the message as being modified.
8671 \*(ID At some future time \*(UA will be capable to rewrite and apply an
8673 to modified messages, and then those fields will be stripped silently.
8677 \*(BO When a message is saved it is usually discarded from the
8678 originating folder when \*(UA is quit.
8679 This setting causes all saved message to be retained.
8682 .It Va line-editor-disable
8683 \*(BO Turn off any enhanced line editing capabilities (see
8684 .Sx "On terminal control and line editor"
8688 .It Va line-editor-no-defaults
8689 \*(BO\*(OP Do not establish any default key binding.
8693 Error log message prefix string
8694 .Pf ( Ql "\*(uA: " ) .
8697 .It Va mailbox-display
8698 \*(RO The name of the current mailbox
8700 possibly abbreviated for display purposes.
8703 .It Va mailbox-resolved
8704 \*(RO The fully resolved path of the current mailbox.
8707 .It Va mailx-extra-rc
8708 An additional startup file that is loaded as the last of the
8709 .Sx "Resource files" .
8710 Use this file for commands that are not understood by other POSIX
8712 implementations, i.e., mostly anything which is not covered by
8713 .Sx "Initial settings" .
8717 \*(BO When a message is replied to and this variable is set,
8718 it is marked as having been
8721 .Sx "Message states" .
8725 \*(BO When opening MBOX mailbox databases \*(UA by default uses tolerant
8726 POSIX rules for detecting message boundaries (so-called
8728 lines) due to compatibility reasons, instead of the stricter rules that
8729 have been standardized in RFC 4155.
8730 This behaviour can be switched to the stricter RFC 4155 rules by
8731 setting this variable.
8732 (This is never necessary for any message newly generated by \*(UA,
8733 it only applies to messages generated by buggy or malicious MUAs, or may
8734 occur in old MBOX databases: \*(UA itself will choose a proper
8736 to avoid false interpretation of
8738 content lines in the MBOX database.)
8740 This may temporarily be handy when \*(UA complains about invalid
8742 lines when opening a MBOX: in this case setting this variable and
8743 re-opening the mailbox in question may correct the result.
8744 If so, copying the entire mailbox to some other file, as in
8745 .Ql copy * SOME-FILE ,
8746 will perform proper, all-compatible
8748 quoting for all detected messages, resulting in a valid MBOX mailbox.
8749 Finally the variable can be unset again:
8750 .Bd -literal -offset indent
8752 localopts yes; wysh set mbox-rfc4155;\e
8753 wysh File "${1}"; eval copy * "${2}"
8755 call mboxfix /tmp/bad.mbox /tmp/good.mbox
8760 \*(BO Internal development variable.
8763 .It Va message-id-disable
8764 \*(BO By setting this variable the generation of
8766 can be completely suppressed, effectively leaving this task up to the
8768 (Mail-Transfer-Agent) or the SMTP server.
8769 (According to RFC 5321 a SMTP server is not required to add this
8770 field by itself, so it should be ensured that it accepts messages without
8772 This variable also affects automatic generation of
8777 .It Va message-inject-head
8778 A string to put at the beginning of each new message.
8779 The escape sequences tabulator
8786 .It Va message-inject-tail
8787 A string to put at the end of each new message.
8788 The escape sequences tabulator
8796 \*(BO Usually, when an
8798 expansion contains the sender, the sender is removed from the expansion.
8799 Setting this option suppresses these removals.
8804 option to be passed through to the
8806 (Mail-Transfer-Agent); though most of the modern MTAs no longer document
8807 this flag, no MTA is known which does not support it (for historical
8811 .It Va mime-allow-text-controls
8812 \*(BO When sending messages, each part of the message is MIME-inspected
8813 in order to classify the
8816 .Ql Content-Transfer-Encoding:
8819 that is required to send this part over mail transport, i.e.,
8820 a computation rather similar to what the
8822 command produces when used with the
8826 This classification however treats text files which are encoded in
8827 UTF-16 (seen for HTML files) and similar character sets as binary
8828 octet-streams, forcefully changing any
8833 .Ql application/octet-stream :
8834 If that actually happens a yet unset charset MIME parameter is set to
8836 effectively making it impossible for the receiving MUA to automatically
8837 interpret the contents of the part.
8839 If this variable is set, and the data was unambiguously identified as
8840 text data at first glance (by a
8844 file extension), then the original
8846 will not be overwritten.
8849 .It Va mime-alternative-favour-rich
8850 \*(BO If this variable is set then rich MIME alternative parts (e.g.,
8851 HTML) will be preferred in favour of included plain text versions when
8852 displaying messages, provided that a handler exists which produces
8853 output that can be (re)integrated into \*(UA's normal visual display.
8854 (E.g., at the time of this writing some newsletters ship their full
8855 content only in the rich HTML part, whereas the plain text part only
8856 contains topic subjects.)
8859 .It Va mime-counter-evidence
8862 field is used to decide how to handle MIME parts.
8863 Some MUAs, however, do not use
8864 .Sx "The mime.types files"
8866 .Sx "HTML mail and MIME attachments" )
8867 or a similar mechanism to correctly classify content, but specify an
8868 unspecific MIME type
8869 .Pf ( Ql application/octet-stream )
8870 even for plain text attachments.
8871 If this variable is set then \*(UA will try to re-classify such MIME
8872 message parts, if possible, for example via a possibly existing
8873 attachment filename.
8874 A non-empty value may also be given, in which case a number is expected,
8875 actually a carrier of bits.
8876 Creating the bit-carrying number is a simple addition:
8877 .Bd -literal -offset indent
8878 ? !echo Value should be set to $((2 + 4 + 8))
8879 Value should be set to 14
8882 .Bl -bullet -compact
8884 If bit two is set (2) then the detected
8886 will be carried along with the message and be used for deciding which
8887 MIME handler is to be used, for example;
8888 when displaying such a MIME part the part-info will indicate the
8889 overridden content-type by showing a plus sign
8892 If bit three is set (4) then the counter-evidence is always produced
8893 and a positive result will be used as the MIME type, even forcefully
8894 overriding the parts given MIME type.
8896 If bit four is set (8) then as a last resort the actual content of
8897 .Ql application/octet-stream
8898 parts will be inspected, so that data which looks like plain text can be
8903 .It Va mime-encoding
8905 .Ql Content-Transfer-Encoding
8906 to use in outgoing text messages and message parts, where applicable.
8907 (7-bit clean text messages are sent as-is, without a transfer encoding.)
8910 .Bl -tag -compact -width ".It Ql _%%_"
8913 8-bit transport effectively causes the raw data be passed through
8914 unchanged, but may cause problems when transferring mail messages over
8915 channels that are not ESMTP (RFC 1869) compliant.
8916 Also, several input data constructs are not allowed by the
8917 specifications and may cause a different transfer-encoding to be used.
8918 .It Ql quoted-printable
8920 Quoted-printable encoding is 7-bit clean and has the property that ASCII
8921 characters are passed through unchanged, so that an english message can
8922 be read as-is; it is also acceptible for other single-byte locales that
8923 share many characters with ASCII, like, e.g., ISO-8859-1.
8924 The encoding will cause a large overhead for messages in other character
8925 sets: e.g., it will require up to twelve (12) bytes to encode a single
8926 UTF-8 character of four (4) bytes.
8928 .Pf (Or\0 Ql b64 . )
8929 The default encoding, it is 7-bit clean and will always be used for
8931 This encoding has a constant input:output ratio of 3:4, regardless of
8932 the character set of the input data it will encode three bytes of input
8933 to four bytes of output.
8934 This transfer-encoding is not human readable without performing
8939 .It Va mimetypes-load-control
8940 Can be used to control which of
8941 .Sx "The mime.types files"
8942 are loaded: if the letter
8944 is part of the option value, then the user's personal
8946 file will be loaded (if it exists); likewise the letter
8948 controls loading of the system wide
8949 .Pa /etc/mime.types ;
8950 directives found in the user file take precedence, letter matching is
8952 If this variable is not set \*(UA will try to load both files.
8953 Incorporation of the \*(UA-built-in MIME types cannot be suppressed,
8954 but they will be matched last (the order can be listed via
8957 More sources can be specified by using a different syntax: if the
8958 value string contains an equals sign
8960 then it is instead parsed as a comma-separated list of the described
8963 pairs; the given filenames will be expanded and loaded, and their
8964 content may use the extended syntax that is described in the section
8965 .Sx "The mime.types files" .
8966 Directives found in such files always take precedence (are prepended to
8967 the MIME type cache).
8972 To choose an alternate Mail-Transfer-Agent, set this option to either
8973 the full pathname of an executable (optionally prefixed with a
8975 protocol indicator), or \*(OPally a SMTP protocol URL, e.g., \*(IN
8977 .Dl smtps?://[user[:password]@]server[:port]
8980 .Ql [smtp://]server[:port] . )
8981 The default has been chosen at compie time.
8982 All supported data transfers are executed in child processes, which
8983 run asynchronously, and without supervision, unless either the
8988 If such a child receives a TERM signal, it will abort and
8995 For a file-based MTA it may be necessary to set
8997 in in order to choose the right target of a modern
9000 It will be passed command line arguments from several possible sources:
9003 if set, from the command line if given and the variable
9006 Argument processing of the MTA will be terminated with a
9011 The otherwise occurring implicit usage of the following MTA command
9012 line arguments can be disabled by setting the boolean variable
9013 .Va mta-no-default-arguments
9014 (which will also disable passing
9018 (for not treating a line with only a dot
9020 character as the end of input),
9028 variable is set); in conjunction with the
9030 command line option \*(UA will also (not) pass
9036 \*(OP \*(UA can send mail over SMTP network connections to a single
9037 defined SMTP smarthost, the access URL of which has to be assigned to
9039 To use this mode it is helpful to read
9040 .Sx "On URL syntax and credential lookup" .
9041 It may be necessary to set the
9043 variable in order to use a specific combination of
9048 with some mail providers.
9049 All network traffic can be forwarded over a specified
9053 .Bl -bullet -compact
9055 The plain SMTP protocol (RFC 5321) that normally lives on the
9056 server port 25 and requires setting the
9057 .Va smtp-use-starttls
9058 variable to enter a SSL/TLS encrypted session state.
9059 Assign a value like \*(IN
9060 .Ql smtp://[user[:password]@]server[:port]
9062 .Ql smtp://server[:port] )
9063 to choose this protocol.
9065 The so-called SMTPS which is supposed to live on server port 465
9066 and is automatically SSL/TLS secured.
9067 Unfortunately it never became a standardized protocol and may thus not
9068 be supported by your hosts network service database
9069 \(en in fact the port number has already been reassigned to other
9072 SMTPS is nonetheless a commonly offered protocol and thus can be
9073 chosen by assigning a value like \*(IN
9074 .Ql smtps://[user[:password]@]server[:port]
9076 .Ql smtps://server[:port] ) ;
9077 due to the mentioned problems it is usually necessary to explicitly
9082 Finally there is the SUBMISSION protocol (RFC 6409), which usually
9083 lives on server port 587 and is practically identically to the SMTP
9084 protocol from \*(UA's point of view beside that; it requires setting the
9085 .Va smtp-use-starttls
9086 variable to enter a SSL/TLS secured session state.
9087 Assign a value like \*(IN
9088 .Ql submission://[user[:password]@]server[:port]
9090 .Ql submission://server[:port] ) .
9095 .It Va mta-arguments
9096 Arguments to pass through to a file-based
9098 can be given via this variable, which is parsed according to
9099 .Sx "Shell-style argument quoting"
9100 into an array of arguments, and which will be joined onto MTA options
9101 from other sources, and then passed individually to the MTA:
9103 .Dl wysh set mta-arguments='-t -X \&"/tmp/my log\&"'
9106 .It Va mta-no-default-arguments
9107 \*(BO Unless this variable is set \*(UA will pass some well known
9108 standard command line options to a file-based
9110 (Mail-Transfer-Agent), see there for more.
9114 Many systems use a so-called
9116 environment to ensure compatibility with
9118 This works by inspecting the name that was used to invoke the mail
9120 If this variable is set then the mailwrapper (the program that is
9121 actually executed when calling the file-based
9123 will treat its contents as that name.
9128 .It Va netrc-lookup-USER@HOST , netrc-lookup-HOST , netrc-lookup
9129 \*(BO\*(IN\*(OP Used to control usage of the users
9131 file for lookup of account credentials, as documented in the section
9132 .Sx "On URL syntax and credential lookup"
9136 .Sx "The .netrc file"
9137 documents the file format.
9149 then \*(UA will read the output of a shell pipe instead of the users
9151 file if this variable is set (to the desired shell command).
9152 This can be used to, e.g., store
9156 .Dl set netrc-pipe='gpg -qd ~/.netrc.pgp'
9160 If this variable has the value
9162 newly created local folders will be in Maildir instead of MBOX format.
9166 Checks for new mail in the current folder each time the prompt is shown.
9167 A Maildir folder must be re-scanned to determine if new mail has arrived.
9168 If this variable is set to the special value
9170 then a Maildir folder will not be rescanned completely, but only
9171 timestamp changes are detected.
9175 \*(BO Causes the filename given in the
9178 and the sender-based filenames for the
9182 commands to be interpreted relative to the directory given in the
9184 variable rather than to the current directory,
9185 unless it is set to an absolute pathname.
9188 .It Va on-compose-cleanup
9189 Macro hook which will be called after the message has been sent (or not,
9190 in case of failures), as the very last step before unrolling compose mode
9192 This hook is run even in case of fatal errors, and it is advisable to
9193 perform only absolutely necessary actions, like cleaning up
9196 For compose mode hooks that may affect the message content please see
9197 .Va on-compose-enter , on-compose-leave , on-compose-splice .
9198 \*(ID This hook exists only because
9199 .Ic alias , alternates , commandalias , shortcut ,
9200 to name a few, are currently not covered by
9202 or a similar mechanism: any changes applied in compose mode will
9203 continue to be in effect thereafter.
9207 .It Va on-compose-enter , on-compose-leave
9208 Macro hooks which will be called before compose mode is entered,
9209 and after composing has been finished (but before the
9211 is injected, etc.), respectively.
9213 are enabled for these hooks, causing any setting to be forgotten after
9214 the message has been sent;
9215 .Va on-compose-cleanup
9216 can be used to perform any other necessary cleanup.
9217 The following (read-only) variables will be set temporarily during
9218 execution of the macros to represent the according message headers, or
9219 the empty string for non-existent; they correspond to accoding virtual
9220 temporary message headers that can be accessed via
9223 .Sx "COMMAND ESCAPES" :
9225 .Bl -tag -compact -width ".It Va mailx_subject"
9226 .It Va mailx-command
9227 The command that generates the message.
9228 .It Va mailx-subject
9234 .It Va mailx-to , mailx-cc , mailx-bcc
9235 The list of receiver addresses as a space-separated list.
9236 .It Va mailx-raw-to , mailx-raw-cc , mailx-raw-bcc
9237 The list of receiver addresses before any mangling (due to, e.g.,
9240 .Va recipients-in-cc )
9241 as a space-separated list.
9242 .It Va mailx-orig-from
9243 When replying, forwarding or resending, this will be set to the
9245 of the given message.
9246 .It Va mailx-orig-to , mailx-orig-cc , mailx-orig-bcc
9247 When replying, forwarding or resending, this will be set to the
9248 receivers of the given message.
9254 .It Va on-compose-splice , on-compose-splice-shell
9255 These hooks run once the normal compose mode is finished, but before the
9256 .Va on-compose-leave
9257 macro hook is called, the
9260 Both hooks will be executed in a subprocess, with their input and output
9261 connected to \*(UA such that they can act as if they would be an
9263 The difference in between them is that the latter is a
9265 command, whereas the former is a normal \*(UA macro, but which is
9266 restricted to a small set of commands (the
9270 will indicate said capability).
9272 are enabled for these hooks (in the parent process), causing any setting
9273 to be forgotten after the message has been sent;
9274 .Va on-compose-cleanup
9275 can be used to perform other cleanup as necessary.
9278 During execution of these hooks \*(UA will temporarily forget whether it
9279 has been started in interactive mode, (a restricted set of)
9280 .Sx "COMMAND ESCAPES"
9281 will always be available, and for guaranteed reproducibilities sake
9285 will be set to their defaults.
9286 The compose mode command
9288 has been especially designed for scriptability (via these hooks).
9289 The first line the hook will read on its standard input is the protocol
9290 version of said command escape, currently
9292 backward incompatible protocol changes have to be expected.
9295 Care must be taken to avoid deadlocks and other false control flow:
9296 if both involved processes wait for more input to happen at the
9297 same time, or one doesn't expect more input but the other is stuck
9298 waiting for consumption of its output, etc.
9299 There is no automatic synchronization of the hook: it will not be
9300 stopped automatically just because it, e.g., emits
9302 The hooks will however receive a termination signal if the parent enters
9304 \*(ID Protection against and interaction with signals is not yet given;
9305 it is likely that in the future these scripts will be placed in an
9306 isolated session, which is signalled in its entirety as necessary.
9308 .Bd -literal -offset indent
9309 wysh set on-compose-splice-shell=$'\e
9311 printf "hello $version! Headers: ";\e
9312 echo \e'~^header list\e';\e
9313 read status result;\e
9314 echo "status=$status result=$result";\e
9317 set on-compose-splice=ocsm
9320 echo Splice protocol version is $ver
9321 echo '~^h l'; read hl; vput vexpr es substring "${hl}" 0 1
9323 echoerr 'Cannot read header list'; echo '~x'; xit
9325 if [ "$hl" @i!@ ' cc' ]
9326 echo '~^h i cc Diet is your <mirr.or>'; read es;\e
9327 vput vexpr es substring "${es}" 0 1
9329 echoerr 'Cannot insert Cc: header'; echo '~x'
9337 .It Va on-resend-cleanup
9339 .Va on-compose-cleanup ,
9340 but is only triggered by
9344 .It Va on-resend-enter
9346 .Va on-compose-enter ,
9347 but is only triggered by
9352 \*(BO If set, each message feed through the command given for
9354 is followed by a formfeed character
9358 .It Va password-USER@HOST , password-HOST , password
9359 \*(IN Variable chain that sets a password, which is used in case none has
9360 been given in the protocol and account-specific URL;
9361 as a last resort \*(UA will ask for a password on the user's terminal if
9362 the authentication method requires a password.
9363 Specifying passwords in a startup file is generally a security risk;
9364 the file should be readable by the invoking user only.
9366 .It Va password-USER@HOST
9367 \*(OU (see the chain above for \*(IN)
9368 Set the password for
9372 If no such variable is defined for a host,
9373 the user will be asked for a password on standard input.
9374 Specifying passwords in a startup file is generally a security risk;
9375 the file should be readable by the invoking user only.
9379 \*(BO Send messages to the
9381 command without performing MIME and character set conversions.
9385 .It Va pipe-TYPE/SUBTYPE
9386 When a MIME message part of type
9388 (case-insensitive) is displayed or quoted,
9389 its text is filtered through the value of this variable interpreted as
9391 Note that only parts which can be displayed inline as plain text (see
9393 are displayed unless otherwise noted, other MIME parts will only be
9394 considered by and for the command
9396 The special value commercial at
9398 forces interpretation of the message part as plain text, e.g.,
9399 .Ql set pipe-application/xml=@
9400 will henceforth display XML
9402 (The same could also be achieved by adding a MIME type marker with the
9405 And \*(OPally MIME type handlers may be defined via
9406 .Sx "The Mailcap files"
9407 \(em these directives,
9409 has already been used, should be referred to for further documentation.
9414 can in fact be used as a trigger character to adjust usage and behaviour
9415 of a following shell command specification more thoroughly by appending
9416 more special characters which refer to further mailcap directives, e.g.,
9417 the following hypothetical command specification could be used:
9419 .Bd -literal -offset indent
9420 set pipe-X/Y='@!++=@vim ${MAILX_FILENAME_TEMPORARY}'
9424 .Bl -tag -compact -width ".It Ql __"
9426 The command produces plain text to be integrated in \*(UAs output:
9430 If set the handler will not be invoked when a message is to be quoted,
9431 but only when it will be displayed:
9432 .Cd x-mailx-noquote .
9435 Run the command asynchronously, i.e., without blocking \*(UA:
9439 The command must be run on an interactive terminal, \*(UA will
9440 temporarily release the terminal to it:
9444 Request creation of a zero-sized temporary file, the absolute pathname
9445 of which will be made accessible via the environment variable
9446 .Ev MAILX_FILENAME_TEMPORARY :
9447 .Cd x-mailx-tmpfile .
9448 If given twice then the file will be unlinked automatically by \*(UA
9449 when the command loop is entered again at latest:
9450 .Cd x-mailx-tmpfile-unlink .
9453 Normally the MIME part content is passed to the handler via standard
9454 input; if this flag is set then the data will instead be written into
9455 .Ev MAILX_FILENAME_TEMPORARY
9456 .Pf ( Cd x-mailx-tmpfile-fill ) ,
9457 the creation of which is implied; note however that in order to cause
9458 deletion of the temporary file you still have to use two plus signs
9463 To avoid ambiguities with normal shell command content you can use
9464 another commercial at to forcefully terminate interpretation of
9465 remaining characters.
9466 (Any character not in this list will have the same effect.)
9470 Some information about the MIME part to be displayed is embedded into
9471 the environment of the shell command:
9474 .Bl -tag -compact -width ".It Ev _AIL__ILENAME__ENERATED"
9476 .It Ev MAILX_CONTENT
9477 The MIME content-type of the part, if known, the empty string otherwise.
9480 .It Ev MAILX_CONTENT_EVIDENCE
9482 .Va mime-counter-evidence
9483 includes the carry-around-bit (2), then this will be set to the detected
9484 MIME content-type; not only then identical to
9485 .Ev \&\&MAILX_CONTENT
9489 .It Ev MAILX_FILENAME
9490 The filename, if any is set, the empty string otherwise.
9493 .It Ev MAILX_FILENAME_GENERATED
9497 .It Ev MAILX_FILENAME_TEMPORARY
9498 If temporary file creation has been requested through the command prefix
9499 this variable will be set and contain the absolute pathname of the
9505 .It Va pipe-EXTENSION
9506 This is identical to
9507 .Va pipe-TYPE/SUBTYPE
9510 (normalized to lowercase using character mappings of the ASCII charset)
9511 names a file extension, e.g.,
9513 Handlers registered using this method take precedence.
9516 .It Va pop3-auth-USER@HOST , pop3-auth-HOST , pop3-auth
9517 \*(OP\*(IN Variable chain that sets the POP3 authentication method.
9518 The only possible value as of now is
9520 which is thus the default.
9523 .Mx Va pop3-bulk-load
9524 .It Va pop3-bulk-load-USER@HOST , pop3-bulk-load-HOST , pop3-bulk-load
9525 \*(BO\*(OP When accessing a POP3 server \*(UA loads the headers of
9526 the messages, and only requests the message bodies on user request.
9527 For the POP3 protocol this means that the message headers will be
9529 If this variable is set then \*(UA will download only complete messages
9530 from the given POP3 server(s) instead.
9532 .Mx Va pop3-keepalive
9533 .It Va pop3-keepalive-USER@HOST , pop3-keepalive-HOST , pop3-keepalive
9534 \*(OP POP3 servers close the connection after a period of inactivity;
9535 the standard requires this to be at least 10 minutes,
9536 but practical experience may vary.
9537 Setting this variable to a numeric value greater than
9541 command to be sent each value seconds if no other operation is performed.
9544 .It Va pop3-no-apop-USER@HOST , pop3-no-apop-HOST , pop3-no-apop
9545 \*(BO\*(OP Unless this variable is set the
9547 authentication method will be used when connecting to a POP3 server that
9551 is that the password is not sent in clear text over the wire and that
9552 only a single packet is sent for the user/password tuple.
9554 .Va pop3-no-apop-HOST
9557 .Mx Va pop3-use-starttls
9558 .It Va pop3-use-starttls-USER@HOST , pop3-use-starttls-HOST , pop3-use-starttls
9559 \*(BO\*(OP Causes \*(UA to issue a
9561 command to make an unencrypted POP3 session SSL/TLS encrypted.
9562 This functionality is not supported by all servers,
9563 and is not used if the session is already encrypted by the POP3S method.
9565 .Va pop3-use-starttls-HOST
9571 \*(BO This flag enables POSIX mode, which changes behaviour of \*(UA
9572 where that deviates from standardized behaviour.
9573 It will be set implicitly before the
9574 .Sx "Resource files"
9575 are loaded if the environment variable
9577 is set, and adjusting any of those two will be reflected by the other
9579 The following behaviour is covered and enforced by this mechanism:
9582 .Bl -bullet -compact
9584 In non-interactive mode, any error encountered while loading resource
9585 files during program startup will cause a program exit, whereas in
9586 interactive mode such errors will stop loading of the currently loaded
9587 (stack of) file(s, i.e., recursively).
9588 These exits can be circumvented on a per-command base by using
9591 .Sx "Command modifiers" ,
9592 for each command which shall be allowed to fail.
9596 will replace the list of alternate addresses instead of appending to it.
9599 Upon changing the active
9603 will be displayed even if
9610 implies the behaviour described by
9616 is extended to cover any empty mailbox, not only empty
9618 .Sx "primary system mailbox" Ns
9619 es: they will be removed when they are left in empty state otherwise.
9624 .It Va print-alternatives
9625 \*(BO When a MIME message part of type
9626 .Ql multipart/alternative
9627 is displayed and it contains a subpart of type
9629 other parts are normally discarded.
9630 Setting this variable causes all subparts to be displayed,
9631 just as if the surrounding part was of type
9632 .Ql multipart/mixed .
9636 The string used as a prompt in interactive mode.
9637 Whenever the variable is evaluated the value is expanded as via
9638 dollar-single-quote expansion (see
9639 .Sx "Shell-style argument quoting" ) .
9640 This (post-assignment, i.e., second) expansion can be used to embed
9641 status information, for example
9646 .Va mailbox-display .
9648 In order to embed characters which should not be counted when
9649 calculating the visual width of the resulting string, enclose the
9650 characters of interest in a pair of reverse solidus escaped brackets:
9652 a slot for coloured prompts is also available with the \*(OPal command
9654 Prompting may be prevented by setting this to the null string
9656 .Ql set noprompt ) .
9660 This string is used for secondary prompts, but is otherwise identical to
9667 \*(BO Suppresses the printing of the version when first invoked.
9671 If set, \*(UA starts a replying message with the original message
9672 prefixed by the value of the variable
9674 Normally, a heading consisting of
9675 .Dq Fromheaderfield wrote:
9676 is put before the quotation.
9681 variable, this heading is omitted.
9684 is assigned, only the headers selected by the
9687 selection are put above the message body,
9690 acts like an automatic
9692 .Sx "COMMAND ESCAPES"
9696 is assigned, all headers are put above the message body and all MIME
9697 parts are included, making
9699 act like an automatic
9702 .Va quote-as-attachment .
9705 .It Va quote-as-attachment
9706 \*(BO Add the original message in its entirety as a
9708 MIME attachment when replying to a message.
9709 Note this works regardless of the setting of
9714 \*(OP Can be set in addition to
9716 Setting this turns on a more fancy quotation algorithm in that leading
9717 quotation characters are compressed and overlong lines are folded.
9719 can be set to either one or two (space separated) numeric values,
9720 which are interpreted as the maximum (goal) and the minimum line length,
9721 respectively, in a spirit rather equal to the
9723 program, but line-, not paragraph-based.
9724 If not set explicitly the minimum will reflect the goal algorithmically.
9725 The goal cannot be smaller than the length of
9727 plus some additional pad.
9728 Necessary adjustments take place silently.
9731 .It Va r-option-implicit
9732 \*(BO Setting this option evaluates the contents of
9734 (or, if that contains multiple addresses,
9736 and passes the results onto the used (file-based) MTA as described for the
9738 option (empty argument case).
9741 .It Va recipients-in-cc
9748 are by default merged into the new
9750 If this variable is set, only the original
9754 the rest is merged into
9759 Unless this variable is defined, no copies of outgoing mail will be saved.
9760 If defined it gives the pathname, subject to the usual
9761 .Sx "Filename transformations" ,
9762 of a folder where all new, replied-to or forwarded messages are saved:
9763 when saving to this folder fails the message is not sent, but instead
9767 The standard defines that relative (fully expanded) paths are to be
9768 interpreted relative to the current directory
9770 to force interpretation relative to
9773 needs to be set in addition.
9777 \*(BO If this variable is set the meaning of
9779 will be extended to cover messages which target only file and pipe
9782 These address types will not appear in recipient lists unless
9783 .Va add-file-recipients
9787 .It Va record-resent
9788 \*(BO If this variable is set the meaning of
9790 will be extended to also cover the
9797 .It Va reply-in-same-charset
9798 \*(BO If this variable is set \*(UA first tries to use the same
9799 character set of the original message for replies.
9800 If this fails, the mechanism described in
9801 .Sx "Character sets"
9802 is evaluated as usual.
9805 .It Va reply-strings
9806 Can be set to a comma-separated list of (case-insensitive according to
9807 ASCII rules) strings which shall be recognized in addition to the
9810 reply message indicators \(en built-in are
9812 which is mandated by RFC 5322, as well as the german
9817 which often has been seen in the wild;
9818 I.e., the separating colon has to be specified explicitly.
9822 A list of addresses to put into the
9824 field of the message header.
9825 Members of this list are handled as if they were in the
9830 .It Va reply-to-honour
9833 header is honoured when replying to a message via
9837 This is a quadoption; if set without a value it defaults to
9841 .It Va rfc822-body-from_
9842 \*(BO This variable can be used to force displaying a so-called
9844 line for messages that are embedded into an envelope mail via the
9846 MIME mechanism, for more visual convenience.
9850 \*(BO Enable saving of (partial) messages in
9852 upon interrupt or delivery error.
9856 The number of lines that represents a
9865 line display and scrolling via
9867 If this variable is not set \*(UA falls back to a calculation based upon
9868 the detected terminal window size and the baud rate: the faster the
9869 terminal, the more will be shown.
9870 Overall screen dimensions and pager usage is influenced by the
9871 environment variables
9879 .It Va searchheaders
9880 \*(BO Expand message-list specifiers in the form
9882 to all messages containing the substring
9886 The string search is case insensitive.
9890 \*(OP A comma-separated list of character set names that can be used in
9891 outgoing internet mail.
9892 The value of the variable
9894 is automatically appended to this list of character sets.
9895 If no character set conversion capabilities are compiled into \*(UA then
9896 the only supported charset is
9899 .Va sendcharsets-else-ttycharset
9900 and refer to the section
9901 .Sx "Character sets"
9902 for the complete picture of character set conversion in \*(UA.
9905 .It Va sendcharsets-else-ttycharset
9906 \*(BO\*(OP If this variable is set, but
9908 is not, then \*(UA acts as if
9910 had been set to the value of the variable
9912 In effect this combination passes through the message data in the
9913 character set of the current locale encoding:
9914 therefore mail message text will be (assumed to be) in ISO-8859-1
9915 encoding when send from within a ISO-8859-1 locale, and in UTF-8
9916 encoding when send from within an UTF-8 locale.
9920 never comes into play as
9922 is implicitly assumed to be 8-bit and capable to represent all files the
9923 user may specify (as is the case when no character set conversion
9924 support is available in \*(UA and the only supported character set is
9926 .Sx "Character sets" ) .
9927 This might be a problem for scripts which use the suggested
9929 setting, since in this case the character set is US-ASCII by definition,
9930 so that it is better to also override
9936 An address that is put into the
9938 field of outgoing messages, quoting RFC 5322: the mailbox of the agent
9939 responsible for the actual transmission of the message.
9940 This field should normally not be used unless the
9942 field contains more than one address, on which case it is required.
9945 address is handled as if it were in the
9949 .Va r-option-implicit .
9952 \*(OB Predecessor of
9955 .It Va sendmail-arguments
9956 \*(OB Predecessor of
9959 .It Va sendmail-no-default-arguments
9960 \*(OB\*(BO Predecessor of
9961 .Va mta-no-default-arguments .
9963 .It Va sendmail-progname
9964 \*(OB Predecessor of
9969 \*(BO When sending a message wait until the
9971 (including the built-in SMTP one) exits before accepting further commands.
9973 with this variable set errors reported by the MTA will be recognizable!
9974 If the MTA returns a non-zero exit status,
9975 the exit status of \*(UA will also be non-zero.
9979 \*(BO This setting causes \*(UA to start at the last message
9980 instead of the first one when opening a mail folder.
9984 \*(BO Causes \*(UA to use the sender's real name instead of the plain
9985 address in the header field summary and in message specifications.
9989 \*(BO Causes the recipient of the message to be shown in the header
9990 summary if the message was sent by the user.
9994 The string to expand
9997 .Sx "COMMAND ESCAPES" ) .
10001 The string to expand
10004 .Sx "COMMAND ESCAPES" ) .
10008 Must correspond to the name of a readable file if set.
10009 The file's content is then appended to each singlepart message
10010 and to the first part of each multipart message.
10011 Be warned that there is no possibility to edit the signature for an
10012 individual message.
10015 .It Va skipemptybody
10016 \*(BO If an outgoing message does not contain any text in its first or
10017 only message part, do not send it but discard it silently (see also the
10018 command line option
10023 .It Va smime-ca-dir , smime-ca-file
10024 \*(OP Specify the location of trusted CA certificates in PEM (Privacy
10025 Enhanced Mail) format as a directory and a file, respectively, for the
10026 purpose of verification of S/MIME signed messages.
10027 It is possible to set both, the file will be loaded immediately, the
10028 directory will be searched whenever no match has yet been found.
10029 The set of CA certificates which are built into the SSL/TLS library can
10030 be explicitly turned off by setting
10031 .Va smime-ca-no-defaults ,
10032 and further fine-tuning is possible via
10033 .Va smime-ca-flags .
10036 .It Va smime-ca-flags
10037 \*(OP Can be used to fine-tune behaviour of the X509 CA certificate
10038 storage, and the certificate verification that is used.
10039 The actual values and their meanings are documented for
10043 .It Va smime-ca-no-defaults
10044 \*(BO\*(OP Do not load the default CA locations that are built into the
10045 used to SSL/TLS library to verify S/MIME signed messages.
10047 .Mx Va smime-cipher
10048 .It Va smime-cipher-USER@HOST , smime-cipher
10049 \*(OP Specifies the cipher to use when generating S/MIME encrypted
10050 messages (for the specified account).
10051 RFC 5751 mandates a default of
10054 Possible values are (case-insensitive and) in decreasing cipher strength:
10062 (DES EDE3 CBC, 168 bits; default if
10064 is not available) and
10066 (DES CBC, 56 bits).
10068 The actually available cipher algorithms depend on the cryptographic
10069 library that \*(UA uses.
10070 \*(OP Support for more cipher algorithms may be available through
10071 dynamic loading via, e.g.,
10072 .Xr EVP_get_cipherbyname 3
10073 (OpenSSL) if \*(UA has been compiled to support this.
10076 .It Va smime-crl-dir
10077 \*(OP Specifies a directory that contains files with CRLs in PEM format
10078 to use when verifying S/MIME messages.
10081 .It Va smime-crl-file
10082 \*(OP Specifies a file that contains a CRL in PEM format to use when
10083 verifying S/MIME messages.
10086 .It Va smime-encrypt-USER@HOST
10087 \*(OP If this variable is set, messages send to the given receiver are
10088 encrypted before sending.
10089 The value of the variable must be set to the name of a file that
10090 contains a certificate in PEM format.
10092 If a message is sent to multiple recipients,
10093 each of them for whom a corresponding variable is set will receive an
10094 individually encrypted message;
10095 other recipients will continue to receive the message in plain text
10097 .Va smime-force-encryption
10099 It is recommended to sign encrypted messages, i.e., to also set the
10104 .It Va smime-force-encryption
10105 \*(BO\*(OP Causes \*(UA to refuse sending unencrypted messages.
10109 \*(BO\*(OP S/MIME sign outgoing messages with the user's private key
10110 and include the user's certificate as a MIME attachment.
10111 Signing a message enables a recipient to verify that the sender used
10112 a valid certificate,
10113 that the email addresses in the certificate match those in the message
10114 header and that the message content has not been altered.
10115 It does not change the message text,
10116 and people will be able to read the message as usual.
10118 .Va smime-sign-cert , smime-sign-include-certs
10120 .Va smime-sign-message-digest .
10122 .Mx Va smime-sign-cert
10123 .It Va smime-sign-cert-USER@HOST , smime-sign-cert
10124 \*(OP Points to a file in PEM format.
10125 For the purpose of signing and decryption this file needs to contain the
10126 user's private key, followed by his certificate.
10128 For message signing
10130 is always derived from the value of
10132 (or, if that contains multiple addresses,
10134 For the purpose of encryption the recipient's public encryption key
10135 (certificate) is expected; the command
10137 can be used to save certificates of signed messages (the section
10138 .Sx "Signed and encrypted messages with S/MIME"
10139 gives some details).
10140 This mode of operation is usually driven by the specialized form.
10142 When decrypting messages the account is derived from the recipient
10147 of the message, which are searched for addresses for which such
10149 \*(UA always uses the first address that matches,
10150 so if the same message is sent to more than one of the user's addresses
10151 using different encryption keys, decryption might fail.
10153 For signing and decryption purposes it is possible to use encrypted
10154 keys, and the pseudo-host(s)
10155 .Ql USER@HOST.smime-cert-key
10156 for the private key
10158 .Ql USER@HOST.smime-cert-cert
10159 for the certificate stored in the same file)
10160 will be used for performing any necessary password lookup,
10161 therefore the lookup can be automatized via the mechanisms described in
10162 .Sx "On URL syntax and credential lookup" .
10163 For example, the hypothetical address
10165 could be driven with a private key / certificate pair path defined in
10166 .Va \&\&smime-sign-cert-bob@exam.ple ,
10167 and needed passwords would then be looked up via the pseudo hosts
10168 .Ql bob@exam.ple.smime-cert-key
10170 .Ql bob@exam.ple.smime-cert-cert ) .
10171 To include intermediate certificates, use
10172 .Va smime-sign-include-certs .
10174 .Mx Va smime-sign-include-certs
10175 .It Va smime-sign-include-certs-USER@HOST , smime-sign-include-certs
10176 \*(OP If used, this is supposed to a consist of a comma-separated list
10177 of files, each of which containing a single certificate in PEM format to
10178 be included in the S/MIME message in addition to the
10179 .Va smime-sign-cert
10181 This can be used to include intermediate certificates of the certificate
10182 authority, in order to allow the receiver's S/MIME implementation to
10183 perform a verification of the entire certificate chain, starting from
10184 a local root certificate, over the intermediate certificates, down to the
10185 .Va smime-sign-cert .
10186 Even though top level certificates may also be included in the chain,
10187 they won't be used for the verification on the receiver's side.
10189 For the purpose of the mechanisms involved here,
10191 refers to the content of the internal variable
10193 (or, if that contains multiple addresses,
10196 .Ql USER@HOST.smime-include-certs
10197 will be used for performing password lookups for these certificates,
10198 shall they have been given one, therefore the lookup can be automatized
10199 via the mechanisms described in
10200 .Sx "On URL syntax and credential lookup" .
10202 .Mx Va smime-sign-message-digest
10203 .It Va smime-sign-message-digest-USER@HOST , smime-sign-message-digest
10204 \*(OP Specifies the message digest to use when signing S/MIME messages.
10205 RFC 5751 mandates a default of
10207 Possible values are (case-insensitive and) in decreasing cipher strength:
10215 The actually available message digest algorithms depend on the
10216 cryptographic library that \*(UA uses.
10217 \*(OP Support for more message digest algorithms may be available
10218 through dynamic loading via, e.g.,
10219 .Xr EVP_get_digestbyname 3
10220 (OpenSSL) if \*(UA has been compiled to support this.
10221 Remember that for this
10223 refers to the variable
10225 (or, if that contains multiple addresses,
10229 \*(OB\*(OP To use the built-in SMTP transport, specify a SMTP URL in
10231 \*(ID For compatibility reasons a set
10233 is used in preference of
10237 .It Va smtp-auth-USER@HOST , smtp-auth-HOST , smtp-auth
10238 \*(OP Variable chain that controls the SMTP
10240 authentication method, possible values are
10246 as well as the \*(OPal methods
10252 method does not need any user credentials,
10254 requires a user name and all other methods require a user name and
10262 .Va smtp-auth-password
10264 .Va smtp-auth-user ) .
10269 .Va smtp-auth-USER@HOST :
10270 may override dependent on sender address in the variable
10273 .It Va smtp-auth-password
10274 \*(OP\*(OU Sets the global fallback password for SMTP authentication.
10275 If the authentication method requires a password, but neither
10276 .Va smtp-auth-password
10278 .Va smtp-auth-password-USER@HOST
10280 \*(UA will ask for a password on the user's terminal.
10282 .It Va smtp-auth-password-USER@HOST
10284 .Va smtp-auth-password
10285 for specific values of sender addresses, dependent upon the variable
10288 .It Va smtp-auth-user
10289 \*(OP\*(OU Sets the global fallback user name for SMTP authentication.
10290 If the authentication method requires a user name, but neither
10293 .Va smtp-auth-user-USER@HOST
10295 \*(UA will ask for a user name on the user's terminal.
10297 .It Va smtp-auth-user-USER@HOST
10300 for specific values of sender addresses, dependent upon the variable
10304 .It Va smtp-hostname
10305 \*(OP\*(IN Normally \*(UA uses the variable
10307 to derive the necessary
10309 information in order to issue a
10316 can be used to use the
10318 from the SMTP account
10325 from the content of this variable (or, if that is the empty string,
10327 or the local hostname as a last resort).
10328 This often allows using an address that is itself valid but hosted by
10329 a provider other than which (in
10331 is about to send the message.
10332 Setting this variable also influences generated
10338 .Mx Va smtp-use-starttls
10339 .It Va smtp-use-starttls-USER@HOST , smtp-use-starttls-HOST , smtp-use-starttls
10340 \*(BO\*(OP Causes \*(UA to issue a
10342 command to make an SMTP
10344 session SSL/TLS encrypted, i.e., to enable transport layer security.
10347 .It Va socks-proxy-USER@HOST , socks-proxy-HOST , socks-proxy
10348 \*(OP If this is set to the hostname (SOCKS URL) of a SOCKS5 server then
10349 \*(UA will proxy all of its network activities through it.
10350 This can be used to proxy SMTP, POP3 etc. network traffic through the
10351 Tor anonymizer, for example.
10352 The following would create a local SOCKS proxy on port 10000 that
10353 forwards to the machine
10355 and from which the network traffic is actually instantiated:
10356 .Bd -literal -offset indent
10357 # Create local proxy server in terminal 1 forwarding to HOST
10358 $ ssh -D 10000 USER@HOST
10359 # Then, start a client that uses it in terminal 2
10360 $ \*(uA -Ssocks-proxy-USER@HOST=localhost:10000
10364 .It Va spam-interface
10365 \*(OP In order to use any of the spam-related commands (like, e.g.,
10367 the desired spam interface must be defined by setting this variable.
10368 Please refer to the manual section
10369 .Sx "Handling spam"
10370 for the complete picture of spam handling in \*(UA.
10371 All or none of the following interfaces may be available:
10373 .Bl -tag -width ".It Ql _ilte_"
10379 .Pf ( Lk http://spamassassin.apache.org SpamAssassin )
10381 Different to the generic filter interface \*(UA will automatically add
10382 the correct arguments for a given command and has the necessary
10383 knowledge to parse the program's output.
10384 A default value for
10386 will have been compiled into the \*(UA binary if
10390 during compilation.
10391 Shall it be necessary to define a specific connection type (rather than
10392 using a configuration file for that), the variable
10393 .Va spamc-arguments
10394 can be used as in, e.g.,
10395 .Ql -d server.example.com -p 783 .
10396 It is also possible to specify a per-user configuration via
10398 Note that this interface does not inspect the
10400 flag of a message for the command
10404 generic spam filter support via freely configurable hooks.
10405 This interface is meant for programs like
10407 and requires according behaviour in respect to the hooks' exit
10408 status for at least the command
10411 meaning a message is spam,
10415 for unsure and any other return value indicating a hard error);
10416 since the hooks can include shell code snippets diverting behaviour
10417 can be intercepted as necessary.
10419 .Va spamfilter-ham , spamfilter-noham , spamfilter-nospam , \
10422 .Va spamfilter-spam ;
10424 .Sx "Handling spam"
10425 contains examples for some programs.
10426 The process environment of the hooks will have the variable
10427 .Ev MAILX_FILENAME_GENERATED
10429 Note that spam score support for
10431 is not supported unless the \*(OPtional regular expression support is
10433 .Va spamfilter-rate-scanscore
10439 .It Va spam-maxsize
10440 \*(OP Messages that exceed this size will not be passed through to the
10442 .Va spam-interface .
10443 If unset or 0, the default of 420000 bytes is used.
10446 .It Va spamc-command
10447 \*(OP The path to the
10451 .Va spam-interface .
10452 Note that the path is not expanded, but used
10454 A fallback path will have been compiled into the \*(UA binary if the
10455 executable had been found during compilation.
10458 .It Va spamc-arguments
10459 \*(OP Even though \*(UA deals with most arguments for the
10462 automatically, it may at least sometimes be desirable to specify
10463 connection-related ones via this variable, e.g.,
10464 .Ql -d server.example.com -p 783 .
10468 \*(OP Specify a username for per-user configuration files for the
10470 .Va spam-interface .
10471 If this is set to the empty string then \*(UA will use the name of the
10480 .It Va spamfilter-ham , spamfilter-noham , \
10481 spamfilter-nospam , spamfilter-rate , spamfilter-spam
10482 \*(OP Command and argument hooks for the
10484 .Va spam-interface .
10486 .Sx "Handling spam"
10487 contains examples for some programs.
10490 .It Va spamfilter-rate-scanscore
10491 \*(OP Because of the generic nature of the
10494 spam scores are not supported for it by default, but if the \*(OPnal
10495 regular expression support is available then setting this variable can
10496 be used to overcome this restriction.
10497 It is interpreted as follows: first a number (digits) is parsed that
10498 must be followed by a semicolon
10500 and an extended regular expression.
10501 Then the latter is used to parse the first output line of the
10502 .Va spamfilter-rate
10503 hook, and, in case the evaluation is successful, the group that has been
10504 specified via the number is interpreted as a floating point scan score.
10508 .It Va ssl-ca-dir , ssl-ca-file
10509 \*(OP Specify the location of trusted CA certificates in PEM (Privacy
10510 Enhanced Mail) format as a directory and a file, respectively, for the
10511 purpose of verification of SSL/TLS server certificates.
10512 It is possible to set both, the file will be loaded immediately, the
10513 directory will be searched whenever no match has yet been found.
10514 The set of CA certificates which are built into the SSL/TLS library can
10515 be explicitly turned off by setting
10516 .Va ssl-ca-no-defaults ,
10517 and further fine-tuning is possible via
10520 .Xr SSL_CTX_load_verify_locations 3
10521 for more information.
10522 \*(UA will try to use the TLS/SNI (ServerNameIndication) extension when
10523 establishing TLS connections to servers identified with hostnames.
10527 .It Va ssl-ca-flags
10528 \*(OP Can be used to fine-tune behaviour of the X509 CA certificate
10529 storage, and the certificate verification that is used (also see
10531 The value is expected to consist of a comma-separated list of
10532 configuration directives, with any intervening whitespace being ignored.
10533 The directives directly map to flags that can be passed to
10534 .Xr X509_STORE_set_flags 3 ,
10535 which are usually defined in a file
10536 .Pa openssl/x509_vfy.h ,
10537 and the availability of which depends on the used SSL/TLS library
10538 version: a directive without mapping is ignored (error log subject to
10540 Directives currently understood (case-insensitively) include:
10543 .Bl -tag -compact -width ".It Cd BaNg"
10544 .It Cd no-alt-chains
10545 If the initial chain is not trusted, do not attempt to build an
10547 Setting this flag will make OpenSSL certificate verification match that
10548 of older OpenSSL versions, before automatic building and checking of
10549 alternative chains has been implemented; also see
10550 .Cd trusted-first .
10551 .It Cd no-check-time
10552 Do not check certificate/CRL validity against current time.
10553 .It Cd partial-chain
10554 By default partial, incomplete chains which cannot be verified up to the
10555 chain top, a self-signed root certificate, will not verify.
10556 With this flag set, a chain succeeds to verify if at least one signing
10557 certificate of the chain is in any of the configured trusted stores of
10559 The OpenSSL manual page
10560 .Xr SSL_CTX_load_verify_locations 3
10561 gives some advise how to manage your own trusted store of CA certificates.
10563 Disable workarounds for broken certificates.
10564 .It Cd trusted-first
10565 Try building a chain using issuers in the trusted store first to avoid
10566 problems with server-sent legacy intermediate certificates.
10567 Newer versions of OpenSSL support alternative chain checking and enable
10568 it by default, resulting in the same behaviour; also see
10569 .Cd no-alt-chains .
10574 .It Va ssl-ca-no-defaults
10575 \*(BO\*(OP Do not load the default CA locations that are built into the
10576 used to SSL/TLS library to verify SSL/TLS server certificates.
10579 .It Va ssl-cert-USER@HOST , ssl-cert-HOST , ssl-cert
10580 \*(OP Variable chain that sets the filename for a SSL/TLS client
10581 certificate required by some servers.
10582 This is a direct interface to the
10586 function of the OpenSSL library, if available.
10588 .Mx Va ssl-cipher-list
10589 .It Va ssl-cipher-list-USER@HOST , ssl-cipher-list-HOST , ssl-cipher-list
10590 \*(OP Specifies a list of ciphers for SSL/TLS connections.
10591 This is a direct interface to the
10595 function of the OpenSSL library, if available; see
10598 .Xr SSL_CTX_set_cipher_list 3
10599 for more information.
10600 By default \*(UA does not set a list of ciphers, in effect using a
10602 specific cipher (protocol standards ship with a list of acceptable
10603 ciphers), possibly cramped to what the actually used SSL/TLS library
10604 supports \(en the manual section
10605 .Sx "An example configuration"
10606 also contains a SSL/TLS use case.
10609 .It Va ssl-config-file
10610 \*(OP If this variable is set \*(UA will call
10611 .Xr CONF_modules_load_file 3
10612 to allow OpenSSL to be configured according to the host system wide
10614 If a non-empty value is given then this will be used to specify the
10615 configuration file to be used instead of the global OpenSSL default;
10616 note that in this case it is an error if the file cannot be loaded.
10617 The application name will always be passed as
10621 .It Va ssl-curves-USER@HOST , ssl-curves-HOST , ssl-curves
10622 \*(OP Specifies a list of supported curves for SSL/TLS connections.
10623 This is a direct interface to the
10627 function of the OpenSSL library, if available; see
10628 .Xr SSL_CTX_set1_curves_list 3
10629 for more information.
10630 By default \*(UA does not set a list of curves.
10634 .It Va ssl-crl-dir , ssl-crl-file
10635 \*(OP Specify a directory / a file, respectively that contains a CRL in
10636 PEM format to use when verifying SSL/TLS server certificates.
10639 .It Va ssl-key-USER@HOST , ssl-key-HOST , ssl-key
10640 \*(OP Variable chain that sets the filename for the private key of
10641 a SSL/TLS client certificate.
10642 If unset, the name of the certificate file is used.
10643 The file is expected to be in PEM format.
10644 This is a direct interface to the
10648 function of the OpenSSL library, if available.
10650 .It Va ssl-method-USER@HOST , ssl-method-HOST , ssl-method
10651 \*(OB\*(OP Please use the newer and more flexible
10653 instead: if both values are set,
10655 will take precedence!
10656 Can be set to the following values, the actually used
10658 specification to which it is mapped is shown in parenthesis:
10660 .Pf ( Ql -ALL, TLSv1.2 ) ,
10662 .Pf ( Ql -ALL, TLSv1.1 ) ,
10664 .Pf ( Ql -ALL, TLSv1 )
10667 .Pf ( Ql -ALL, SSLv3 ) ;
10672 and thus includes the SSLv3 protocol.
10673 Note that SSLv2 is no longer supported at all.
10675 .Mx Va ssl-protocol
10676 .It Va ssl-protocol-USER@HOST , ssl-protocol-HOST , ssl-protocol
10677 \*(OP Specify the used SSL/TLS protocol.
10678 This is a direct interface to the
10682 function of the OpenSSL library, if available;
10683 otherwise an \*(UA internal parser is used which understands the
10684 following subset of (case-insensitive) command strings:
10690 as well as the special value
10692 Multiple specifications may be given via a comma-separated list which
10693 ignores any whitespace.
10696 plus sign prefix will enable a protocol, a
10698 hyphen-minus prefix will disable it, so that
10700 will enable only the TLSv1.2 protocol.
10702 It depends upon the used TLS/SSL library which protocols are actually
10703 supported and which protocols are used if
10705 is not set, but note that SSLv2 is no longer supported at all and
10707 Especially for older protocols explicitly securing
10708 .Va ssl-cipher-list
10709 may be worthwile, see
10710 .Sx "An example configuration" .
10713 .It Va ssl-rand-egd
10714 \*(OP Gives the pathname to an entropy daemon socket, see
10716 Not all SSL/TLS libraries support this.
10719 .It Va ssl-rand-file
10720 \*(OP Gives the filename to a file with random entropy data, see
10721 .Xr RAND_load_file 3 .
10722 If this variable is not set, or set to the empty string, or if the
10723 .Sx "Filename transformations"
10725 .Xr RAND_file_name 3
10726 will be used to create the filename if, and only if,
10728 documents that the SSL PRNG is not yet sufficiently seeded.
10729 If \*(UA successfully seeded the SSL PRNG then it will update the file
10730 .Pf ( Xr RAND_write_file 3 ) .
10731 This variable is only used if
10733 is not set (or not supported by the SSL/TLS library).
10736 .It Va ssl-verify-USER@HOST , ssl-verify-HOST , ssl-verify
10737 \*(OP Variable chain that sets the action to be performed if an error
10738 occurs during SSL/TLS server certificate validation against the
10739 specified or default trust stores
10742 or the SSL/TLS library built-in defaults (unless usage disallowed via
10743 .Va ssl-ca-no-defaults ) ,
10744 and as fine-tuned via
10746 Valid (case-insensitive) values are
10748 (fail and close connection immediately),
10750 (ask whether to continue on standard input),
10752 (show a warning and continue),
10754 (do not perform validation).
10760 If only set without an assigned value, then this setting inhibits the
10766 header fields that include obvious references to \*(UA.
10767 There are two pitfalls associated with this:
10768 First, the message id of outgoing messages is not known anymore.
10769 Second, an expert may still use the remaining information in the header
10770 to track down the originating mail user agent.
10771 If set to the value
10777 suppression does not occur.
10782 (\*(OP) This specifies a comma-separated list of
10787 .Sx "On terminal control and line editor" ,
10788 escape commas with reverse solidus) to be used to overwrite or define
10791 this variable will only be queried once at program startup and can
10792 thus only be specified in resource files or on the command line.
10795 String capabilities form
10797 pairs and are expected unless noted otherwise.
10798 Numerics have to be notated as
10800 where the number is expected in normal decimal notation.
10801 Finally, booleans do not have any value but indicate a true or false
10802 state simply by being defined or not; this indeed means that \*(UA
10803 does not support undefining an existing boolean.
10804 String capability values will undergo some expansions before use:
10805 for one notations like
10808 .Ql control-LETTER ,
10809 and for clarification purposes
10811 can be used to specify
10813 (the control notation
10815 could lead to misreadings when a left bracket follows, which it does for
10816 the standard CSI sequence);
10817 finally three letter octal sequences, as in
10820 To specify that a terminal supports 256-colours, and to define sequences
10821 that home the cursor and produce an audible bell, one might write:
10823 .Bd -literal -offset indent
10824 set termcap='Co#256,home=\eE[H,bel=^G'
10828 The following terminal capabilities are or may be meaningful for the
10829 operation of the built-in line editor or \*(UA in general:
10832 .Bl -tag -compact -width ".It Cd yay"
10834 .It Cd colors Ns \0or Cd Co
10836 numeric capability specifying the maximum number of colours.
10837 Note that \*(UA does not actually care about the terminal beside that,
10838 but always emits ANSI / ISO 6429 escape sequences.
10841 .It Cd rmcup Ns \0or Cd te Ns \0/ Cd smcup Ns \0or Cd ti
10844 .Cd enter_ca_mode ,
10845 respectively: exit and enter the alternative screen ca-mode,
10846 effectively turning \*(UA into a fullscreen application.
10847 This must be enabled explicitly by setting
10848 .Va termcap-ca-mode .
10850 .It Cd smkx Ns \0or Cd ks Ns \0/ Cd rmkx Ns \0or Cd ke
10854 respectively: enable and disable the keypad.
10855 This is always enabled if available, because it seems even keyboards
10856 without keypads generate other key codes for, e.g., cursor keys in that
10857 case, and only if enabled we see the codes that we are interested in.
10859 .It Cd ed Ns \0or Cd cd
10863 .It Cd clear Ns \0or Cd cl
10865 clear the screen and home cursor.
10866 (Will be simulated via
10871 .It Cd home Ns \0or Cd ho
10876 .It Cd el Ns \0or Cd ce
10878 clear to the end of line.
10879 (Will be simulated via
10881 plus repetitions of space characters.)
10883 .It Cd hpa Ns \0or Cd ch
10884 .Cd column_address :
10885 move the cursor (to the given column parameter) in the current row.
10886 (Will be simulated via
10892 .Cd carriage_return :
10893 move to the first column in the current row.
10894 The default built-in fallback is
10897 .It Cd cub1 Ns \0or Cd le
10899 move the cursor left one space (non-destructively).
10900 The default built-in fallback is
10903 .It Cd cuf1 Ns \0or Cd nd
10905 move the cursor right one space (non-destructively).
10906 The default built-in fallback is
10908 which is used by most terminals.
10916 Many more capabilities which describe key-sequences are documented for
10921 .It Va termcap-ca-mode
10922 \*(OP Allow usage of the
10926 terminal capabilities, effectively turning \*(UA into a fullscreen
10927 application, as documented for
10930 this variable will only be queried once at program startup and can
10931 thus only be specified in resource files or on the command line.
10934 .It Va termcap-disable
10935 \*(OP Disable any interaction with a terminal control library.
10936 If set only some generic fallback built-ins and possibly the content of
10938 describe the terminal to \*(UA.
10940 this variable will only be queried once at program startup and can
10941 thus only be specified in resource files or on the command line.
10945 If defined, gives the number of lines of a message to be displayed
10948 if unset, the first five lines are printed, if set to 0 the variable
10951 If the value is negative then its absolute value will be used for
10952 unsigned right shifting (see
10960 \*(BO If set then the
10962 command series will strip adjacent empty lines and quotations.
10966 The character set of the terminal \*(UA operates on,
10967 and the one and only supported character set that \*(UA can use if no
10968 character set conversion capabilities have been compiled into it,
10969 in which case it defaults to ISO-8859-1 unless it can deduce a value
10970 from the locale specified in the
10972 environment variable (if supported, see there for more).
10973 It defaults to UTF-8 if conversion is available.
10974 Refer to the section
10975 .Sx "Character sets"
10976 for the complete picture about character sets.
10979 .It Va typescript-mode
10980 \*(BO A special multiplex variable that disables all variables and
10981 settings which result in behaviour that interferes with running \*(UA in
10984 .Va colour-disable ,
10985 .Va line-editor-disable
10986 and (before startup completed only)
10987 .Va termcap-disable .
10988 Unsetting it does not restore the former state of the covered settings.
10992 For a safety-by-default policy \*(UA sets its process
10996 but this variable can be used to override that:
10997 set it to an empty value to do not change the (current) setting,
10998 otherwise the process file mode creation mask is updated to the new value.
10999 Child processes inherit the process file mode creation mask.
11002 .It Va user-HOST , user
11003 \*(IN Variable chain that sets a global fallback user name, which is
11004 used in case none has been given in the protocol and account-specific
11006 This variable defaults to the name of the user who runs \*(UA.
11010 \*(BO Setting this enables upward compatibility with \*(UA
11011 version 15.0 in respect to which configuration options are available and
11012 how they are handled.
11013 This manual uses \*(IN and \*(OU to refer to the new and the old way of
11014 doing things, respectively.
11018 \*(BO This setting, also controllable via the command line option
11020 causes \*(UA to be more verbose, e.g., it will display obsoletion
11021 warnings and SSL/TLS certificate chains.
11022 Even though marked \*(BO this option may be set twice in order to
11023 increase the level of verbosity even more, in which case even details of
11024 the actual message delivery and protocol conversations are shown.
11027 is sufficient to disable verbosity as such.
11034 .It Va version , version-date , version-major , version-minor , version-update
11035 \*(RO \*(UA version information: the first variable contains a string
11036 containing the complete version identification, the latter three contain
11037 only digits: the major, minor and update version numbers.
11038 The date is in ISO 8601 notation.
11039 The output of the command
11041 will include this information.
11044 .It Va writebackedited
11045 If this variable is set messages modified using the
11049 commands are written back to the current folder when it is quit;
11050 it is only honoured for writable folders in MBOX format, though.
11051 Note that the editor will be pointed to the raw message content in that
11052 case, i.e., neither MIME decoding nor decryption will have been
11053 performed, and proper RFC 4155
11055 quoting of newly added or edited content is also left as an excercise to
11058 .\" }}} (Variables)
11059 .\" }}} (INTERNAL VARIABLES)
11062 .\" .Sh ENVIRONMENT {{{
11066 .Dq environment variable
11067 should be considered an indication that these variables are either
11068 standardized as vivid parts of process environments, or that they are
11069 commonly found in there.
11070 The process environment is inherited from the
11072 once \*(UA is started, and unless otherwise explicitly noted handling of
11073 the following variables transparently integrates into that of the
11074 .Sx "INTERNAL VARIABLES"
11075 from \*(UA's point of view.
11076 This means that, e.g., they can be managed via
11080 causing automatic program environment updates (to be inherited by
11081 newly created child processes).
11084 In order to transparently integrate other environment variables equally
11085 they need to be imported (linked) with the command
11087 This command can also be used to set and unset non-integrated
11088 environment variables from scratch, sufficient system support provided.
11089 The following example, applicable to a POSIX shell, sets the
11091 environment variable for \*(UA only, and beforehand exports the
11093 in order to affect any further processing in the running shell:
11095 .Bd -literal -offset indent
11096 $ EDITOR="vim -u ${HOME}/.vimrc"
11098 $ COLUMNS=80 \*(uA -R
11101 .Bl -tag -width ".It Ev BaNg"
11104 The user's preferred width in column positions for the terminal screen
11106 Queried and used once on program startup, actively managed for child
11107 processes and the MLE (see
11108 .Sx "On terminal control and line editor" )
11109 in interactive mode thereafter.
11110 Ignored in non-interactive mode, which always uses 80 columns.
11114 The name of the (mailbox)
11116 to use for saving aborted messages if
11118 is set; this defaults to
11125 is set no output will be generated, otherwise the contents of the file
11130 Pathname of the text editor to use in the
11134 .Sx "COMMAND ESCAPES" .
11135 A default editor is used if this value is not defined.
11139 The user's home directory.
11140 This variable is only used when it resides in the process environment.
11145 .It Ev LC_ALL , LC_CTYPE , LANG
11146 \*(OP The (names in lookup order of the)
11150 which indicates the used
11151 .Sx "Character sets" .
11152 Runtime changes trigger automatic updates of the entire locale system,
11153 updating and overwriting also a
11159 The user's preferred number of lines on a page or the vertical screen
11160 or window size in lines.
11161 Queried and used once on program startup, actively managed for child
11162 processes in interactive mode thereafter.
11163 Ignored in non-interactive mode, which always uses 24 lines.
11167 Pathname of the directory lister to use in the
11169 command when operating on local mailboxes.
11172 (path search through
11177 Upon startup \*(UA will actively ensure that this variable refers to the
11178 name of the user who runs \*(UA, in order to be able to pass a verified
11179 name to any newly created child process.
11183 Is used as the users
11185 .Sx "primary system mailbox"
11189 This is assumed to be an absolute pathname.
11193 \*(OP Overrides the default path search for
11194 .Sx "The Mailcap files" ,
11195 which is defined in the standard RFC 1524 as
11196 .Ql ~/.mailcap:\:/etc/mailcap:\:/usr/etc/mailcap:\:/usr/local/etc/mailcap .
11197 .\" TODO we should have a mailcaps-default virtual RDONLY option!
11198 (\*(UA makes it a configuration option, however.)
11199 Note this is not a search path, but a path search.
11203 Is used as a startup file instead of
11206 When \*(UA scripts are invoked on behalf of other users,
11207 either this variable should be set to
11211 command line option should be used in order to avoid side-effects from
11212 reading their configuration files.
11213 This variable is only used when it resides in the process environment.
11216 .It Ev MAILX_NO_SYSTEM_RC
11217 If this variable is set then reading of
11219 at startup is inhibited, i.e., the same effect is achieved as if \*(UA
11220 had been started up with the option
11222 (and according argument) or
11224 This variable is only used when it resides in the process environment.
11228 The name of the users
11230 .Sx "secondary mailbox"
11232 A logical subset of the special
11233 .Sx "Filename transformations"
11239 Traditionally this MBOX is used as the file to save messages from the
11241 .Sx "primary system mailbox"
11242 that have been read.
11244 .Sx "Message states" .
11248 \*(IN\*(OP This variable overrides the default location of the user's
11254 Pathname of the program to use for backing the command
11258 variable enforces usage of a pager for output.
11259 The default paginator is
11261 (path search through
11264 \*(UA inspects the contents of this variable: if its contains the string
11266 then a non-existing environment variable
11273 dependent on whether terminal control support is available and whether
11274 that supports full (alternative) screen mode or not (also see
11275 .Sx "On terminal control and line editor" ) .
11279 will optionally be set to
11286 A colon-separated list of directories that is searched by the shell when
11287 looking for commands, e.g.,
11288 .Ql /bin:/usr/bin:/usr/local/bin .
11291 .It Ev POSIXLY_CORRECT
11292 This variable is automatically looked for upon startup, see
11298 The shell to use for the commands
11303 .Sx "COMMAND ESCAPES"
11304 and when starting subprocesses.
11305 A default shell is used if this environment variable is not defined.
11308 .It Ev SOURCE_DATE_EPOCH
11309 This specifies a time in seconds since the Unix epoch (1970-01-01) to be
11310 used in place of the current time.
11311 This variable is looked up upon program startup, and its existence will
11312 switch \*(UA to a completely reproducible mode which causes
11313 deterministic random numbers, a special fixed (non-existent?)
11315 and more to be used and set.
11316 It is to be used during development or by software packagers.
11317 \*(ID Currently an invalid setting is only ignored, rather than causing
11318 a program abortion.
11320 .Dl $ SOURCE_DATE_EPOCH=`date +%s` \*(uA
11324 \*(OP The terminal type for which output is to be prepared.
11325 For extended colour and font control please refer to
11326 .Sx "Coloured display" ,
11327 and for terminal management in general to
11328 .Sx "On terminal control and line editor" .
11332 Used as directory for temporary files instead of
11335 This variable is only used when it resides in the process environment,
11336 but \*(UA will ensure at startup that this environment variable is
11337 updated to contain a usable temporary directory.
11343 (see there), but this variable is not standardized, should therefore not
11344 be used, and is only corrected if already set.
11348 Pathname of the text editor to use in the
11352 .Sx "COMMAND ESCAPES" .
11360 .Bl -tag -width ".It Pa BaNg"
11362 File giving initial commands.
11365 System wide initialization file.
11369 \*(OP Personal MIME type handler definition file, see
11370 .Sx "The Mailcap files" .
11371 This location is part of the RFC 1524 standard search path, which is
11372 a configuration option and can be overridden via
11376 .It Pa /etc/mailcap
11377 \*(OP System wide MIME type handler definition file, see
11378 .Sx "The Mailcap files" .
11379 This location is part of the RFC 1524 standard search path, which is
11380 a configuration option and can be overridden via
11384 The default value for
11386 The actually used path is a configuration option.
11389 .It Pa ~/.mime.types
11390 Personal MIME types, see
11391 .Sx "The mime.types files" .
11392 The actually used path is a configuration option.
11395 .It Pa /etc/mime.types
11396 System wide MIME types, see
11397 .Sx "The mime.types files" .
11398 The actually used path is a configuration option.
11402 \*(IN\*(OP The default location of the users
11404 file \(en the section
11405 .Sx "The .netrc file"
11406 documents the file format.
11407 The actually used path is a configuration option and can be overridden via
11414 The actually used path is a compile-time constant.
11417 .\" .Ss "The mime.types files" {{{
11418 .Ss "The mime.types files"
11421 .Sx "HTML mail and MIME attachments"
11422 \*(UA needs to learn about MIME (Multipurpose Internet Mail Extensions)
11423 media types in order to classify message and attachment content.
11424 One source for them are
11426 files, the loading of which can be controlled by setting the variable
11427 .Va mimetypes-load-control .
11428 Another is the command
11430 which also offers access to \*(UAs MIME type cache.
11432 files have the following syntax:
11434 .Bd -literal -offset indent
11435 type/subtype extension [extension ...]
11436 # E.g., text/html html htm
11442 define the MIME media type, as standardized in RFC 2046:
11444 is used to declare the general type of data, while the
11446 specifies a specific format for that type of data.
11447 One or multiple filename
11449 s, separated by whitespace, can be bound to the media type format.
11450 Comments may be introduced anywhere on a line with a number sign
11452 causing the remaining line to be discarded.
11454 \*(UA also supports an extended, non-portable syntax in especially
11455 crafted files, which can be loaded via the alternative value syntax of
11456 .Va mimetypes-load-control ,
11457 and prepends an optional
11461 .Dl [type-marker ]type/subtype extension [extension ...]
11464 The following type markers are supported:
11467 .Bl -tag -compact -width ".It Ar _n_u"
11469 Treat message parts with this content as plain text.
11474 Treat message parts with this content as HTML tagsoup.
11475 If the \*(OPal HTML-tagsoup-to-text converter is not available treat
11476 the content as plain text instead.
11480 but instead of falling back to plain text require an explicit content
11481 handler to be defined.
11486 for sending messages:
11488 .Va mime-allow-text-controls ,
11489 .Va mimetypes-load-control .
11490 For reading etc. messages:
11491 .Sx "HTML mail and MIME attachments" ,
11492 .Sx "The Mailcap files" ,
11494 .Va mime-counter-evidence ,
11495 .Va mimetypes-load-control ,
11496 .Va pipe-TYPE/SUBTYPE ,
11497 .Va pipe-EXTENSION .
11500 .\" .Ss "The Mailcap files" {{{
11501 .Ss "The Mailcap files"
11503 .\" TODO MAILCAP DISABLED
11504 .Sy This feature is not available in v14.9.0, sorry!
11506 .Dq User Agent Configuration Mechanism
11507 which \*(UA \*(OPally supports (see
11508 .Sx "HTML mail and MIME attachments" ) .
11509 It defines a file format to be used to inform mail user agent programs
11510 about the locally-installed facilities for handling various data
11511 formats, i.e., about commands and how they can be used to display, edit
11512 et cetera MIME part contents, as well as a default path search that
11513 includes multiple possible locations of
11517 environment variable that can be used to overwrite that (repeating here
11518 that it is not a search path, but instead a path search specification).
11519 Any existing files will be loaded in sequence, appending any content to
11520 the list of MIME type handler directives.
11524 files consist of a set of newline separated entries.
11525 Comment lines start with a number sign
11527 (in the first column!) and are ignored.
11528 Empty lines are also ignored.
11529 All other lines form individual entries that must adhere to the syntax
11531 To extend a single entry (not comment) its line can be continued on
11532 follow lines if newline characters are
11534 by preceding them with the reverse solidus character
11536 The standard does not specify how leading whitespace of follow lines
11537 is to be treated, therefore \*(UA retains it.
11541 entries consist of a number of semicolon
11543 separated fields, and the reverse solidus
11545 character can be used to escape any following character including
11546 semicolon and itself.
11547 The first two fields are mandatory and must occur in the specified
11548 order, the remaining fields are optional and may appear in any order.
11549 Leading and trailing whitespace of content is ignored (removed).
11552 The first field defines the MIME
11554 the entry is about to handle (case-insensitively, and no reverse solidus
11555 escaping is possible in this field).
11556 If the subtype is specified as an asterisk
11558 the entry is meant to match all subtypes of the named type, e.g.,
11560 would match any audio type.
11561 The second field defines the shell command which shall be used to
11563 MIME parts of the given type; it is implicitly called the
11570 shell commands message (MIME part) data is passed via standard input
11571 unless the given shell command includes one or more instances of the
11574 in which case these instances will be replaced with a temporary filename
11575 and the data will have been stored in the file that is being pointed to.
11578 shell commands data is assumed to be generated on standard output unless
11579 the given command includes (one ore multiple)
11581 In any case any given
11583 format is replaced with a(n already) properly quoted filename.
11584 Note that when a command makes use of a temporary file via
11586 then \*(UA will remove it again, as if the
11587 .Cd x-mailx-tmpfile ,
11588 .Cd x-mailx-tmpfile-fill
11590 .Cd x-mailx-tmpfile-unlink
11591 flags had been set; see below for more.
11594 The optional fields either define a shell command or an attribute (flag)
11595 value, the latter being a single word and the former being a keyword
11596 naming the field followed by an equals sign
11598 succeeded by a shell command, and as usual for any
11600 content any whitespace surrounding the equals sign will be removed, too.
11601 Optional fields include the following:
11604 .Bl -tag -width ".It Cd BaNg"
11606 A program that can be used to compose a new body or body part in the
11608 (Currently unused.)
11610 .It Cd composetyped
11613 field, but is to be used when the composing program needs to specify the
11615 header field to be applied to the composed data.
11616 (Currently unused.)
11619 A program that can be used to edit a body or body part in the given
11621 (Currently unused.)
11624 A program that can be used to print a message or body part in the given
11626 (Currently unused.)
11629 Specifies a program to be run to test some condition, e.g., the machine
11630 architecture, or the window system in use, to determine whether or not
11631 this mailcap entry applies.
11632 If the test fails, a subsequent mailcap entry should be sought; also see
11633 .Cd x-mailx-test-once .
11636 .It Cd needsterminal
11637 This flag field indicates that the given shell command must be run on
11638 an interactive terminal.
11639 \*(UA will temporarily release the terminal to the given command in
11640 interactive mode, in non-interactive mode this entry will be entirely
11641 ignored; this flag implies
11642 .Cd x-mailx-noquote .
11645 .It Cd copiousoutput
11646 A flag field which indicates that the output of the
11648 command will be an extended stream of textual output that can be
11649 (re)integrated into \*(UA's normal visual display.
11650 It is mutually exclusive with
11651 .Cd needsterminal .
11653 .It Cd textualnewlines
11654 A flag field which indicates that this type of data is line-oriented and
11655 that, if encoded in
11657 all newlines should be converted to canonical form (CRLF) before
11658 encoding, and will be in that form after decoding.
11659 (Currently unused.)
11661 .It Cd nametemplate
11662 This field gives a filename format, in which
11664 will be replaced by a random string, the joined combination of which
11665 will be used as the filename denoted by
11666 .Ev MAILX_FILENAME_TEMPORARY .
11667 One could specify that a GIF file being passed to an image viewer should
11668 have a name ending in
11671 .Ql nametemplate=%s.gif .
11672 Note that \*(UA ignores the name template unless that solely specifies
11673 a filename suffix that consists of (ASCII) alphabetic and numeric
11674 characters, the underscore and dot only.
11677 Names a file, in X11 bitmap (xbm) format, which points to an appropriate
11678 icon to be used to visually denote the presence of this kind of data.
11679 This field is not used by \*(UA.
11682 A textual description that describes this type of data.
11685 .It Cd x-mailx-even-if-not-interactive
11686 An extension flag test field \(em by default handlers without
11688 are entirely ignored in non-interactive mode, but if this flag is set
11689 then their use will be considered.
11690 It is an error if this flag is set for commands that use the flag
11691 .Cd needsterminal .
11694 .It Cd x-mailx-noquote
11695 An extension flag field that indicates that even a
11698 command shall not be used to generate message quotes
11699 (as it would be by default).
11702 .It Cd x-mailx-async
11703 Extension flag field that denotes that the given
11705 command shall be executed asynchronously, without blocking \*(UA.
11706 Cannot be used in conjunction with
11707 .Cd needsterminal .
11710 .It Cd x-mailx-test-once
11711 Extension flag which denotes whether the given
11713 command shall be evaluated once only and the (boolean) result be cached.
11714 This is handy if some global unchanging condition is to be queried, like
11715 .Dq running under the X Window System .
11718 .It Cd x-mailx-tmpfile
11719 Extension flag field that requests creation of a zero-sized temporary
11720 file, the name of which is to be placed in the environment variable
11721 .Ev MAILX_FILENAME_TEMPORARY .
11722 It is an error to use this flag with commands that include a
11727 .It Cd x-mailx-tmpfile-fill
11728 Normally the MIME part content is passed to the handler via standard
11729 input; if this flag is set then the data will instead be written into
11731 .Cd x-mailx-tmpfile .
11732 In order to cause deletion of the temporary file you will have to set
11733 .Cd x-mailx-tmpfile-unlink
11735 It is an error to use this flag with commands that include a
11740 .It Cd x-mailx-tmpfile-unlink
11741 Extension flag field that requests that the temporary file shall be
11742 deleted automatically when the command loop is entered again at latest.
11743 (Do not use this for asynchronous handlers.)
11744 It is an error to use this flag with commands that include a
11746 format, or in conjunction with
11747 .Cd x-mailx-async ,
11748 or without also setting
11749 .Cd x-mailx-tmpfile
11751 .Cd x-mailx-tmpfile-fill .
11754 .It Cd x-mailx-tmpfile-keep
11757 implies the three tmpfile related flags above, but if you want, e.g.,
11759 and deal with the temporary file yourself, you can add in this flag to
11761 .Cd x-mailx-tmpfile-unlink .
11766 The standard includes the possibility to define any number of additional
11767 entry fields, prefixed by
11769 Flag fields apply to the entire
11771 entry \(em in some unusual cases, this may not be desirable, but
11772 differentiation can be accomplished via separate entries, taking
11773 advantage of the fact that subsequent entries are searched if an earlier
11774 one does not provide enough information.
11777 command needs to specify the
11781 command shall not, the following will help out the latter (with enabled
11785 level \*(UA will show information about handler evaluation):
11787 .Bd -literal -offset indent
11788 application/postscript; ps-to-terminal %s; needsterminal
11789 application/postscript; ps-to-terminal %s; compose=idraw %s
11793 In fields any occurrence of the format string
11795 will be replaced by the
11798 Named parameters from the
11800 field may be placed in the command execution line using
11802 followed by the parameter name and a closing
11805 The entire parameter should appear as a single command line argument,
11806 regardless of embedded spaces; thus:
11808 .Bd -literal -offset indent
11810 Content-type: multipart/mixed; boundary=42
11813 multipart/*; /usr/local/bin/showmulti \e
11814 %t %{boundary} ; composetyped = /usr/local/bin/makemulti
11816 # Executed shell command
11817 /usr/local/bin/showmulti multipart/mixed 42
11821 .\" TODO v15: Mailcap: %n,%F
11822 Note that \*(UA does not support handlers for multipart MIME parts as
11823 shown in this example (as of today).
11824 \*(UA does not support the additional formats
11828 An example file, also showing how to properly deal with the expansion of
11830 which includes any quotes that are necessary to make it a valid shell
11831 argument by itself and thus will cause undesired behaviour when placed
11832 in additional user-provided quotes:
11834 .Bd -literal -offset indent
11836 text/richtext; richtext %s; copiousoutput
11838 text/x-perl; perl -cWT %s
11840 application/pdf; \e
11842 trap "rm -f ${infile}" EXIT\e; \e
11843 trap "exit 75" INT QUIT TERM\e; \e
11845 x-mailx-async; x-mailx-tmpfile-keep
11847 application/*; echo "This is \e"%t\e" but \e
11848 is 50 \e% Greek to me" \e; < %s head -c 1024 | cat -vET; \e
11849 copiousoutput; x-mailx-noquote
11854 .Sx "HTML mail and MIME attachments" ,
11855 .Sx "The mime.types files" ,
11858 .Va mime-counter-evidence ,
11859 .Va pipe-TYPE/SUBTYPE ,
11860 .Va pipe-EXTENSION .
11863 .\" .Ss "The .netrc file" {{{
11864 .Ss "The .netrc file"
11868 file contains user credentials for machine accounts.
11869 The default location in the user's
11871 directory may be overridden by the
11873 environment variable.
11874 The file consists of space, tabulator or newline separated tokens.
11875 \*(UA implements a parser that supports a superset of the original BSD
11876 syntax, but users should nonetheless be aware of portability glitches
11877 of that file format, shall their
11879 be usable across multiple programs and platforms:
11882 .Bl -bullet -compact
11884 BSD does not support single, but only double quotation marks, e.g.,
11885 .Ql password="pass with spaces" .
11887 BSD (only?) supports escaping of single characters via a reverse solidus
11888 (e.g., a space can be escaped via
11890 in- as well as outside of a quoted string.
11892 BSD does not require a final quotation mark of the last user input token.
11894 The original BSD (Berknet) parser also supported a format which allowed
11895 tokens to be separated with commas \(en whereas at least Hewlett-Packard
11896 still seems to support this syntax, \*(UA does not!
11898 As a non-portable extension some widely-used programs support
11899 shell-style comments: if an input line starts, after any amount of
11900 whitespace, with a number sign
11902 then the rest of the line is ignored.
11904 Whereas other programs may require that the
11906 file is accessible by only the user if it contains a
11908 token for any other
11912 \*(UA will always require these strict permissions.
11916 Of the following list of supported tokens \*(UA only uses (and caches)
11921 At runtime the command
11923 can be used to control \*(UA's
11927 .Bl -tag -width ".It Cd BaNg"
11928 .It Cd machine Ar name
11929 The hostname of the entries' machine, lowercase-normalized by \*(UA
11931 Any further file content, until either end-of-file or the occurrence
11936 first-class token is bound (only related) to the machine
11939 As an extension that should not be the cause of any worries
11940 \*(UA supports a single wildcard prefix for
11942 .Bd -literal -offset indent
11943 machine *.example.com login USER password PASS
11944 machine pop3.example.com login USER password PASS
11945 machine smtp.example.com login USER password PASS
11951 .Ql pop3.example.com ,
11955 .Ql local.smtp.example.com .
11956 Note that in the example neither
11957 .Ql pop3.example.com
11959 .Ql smtp.example.com
11960 will be matched by the wildcard, since the exact matches take
11961 precedence (it is however faster to specify it the other way around).
11964 This is the same as
11966 except that it is a fallback entry that is used shall none of the
11967 specified machines match; only one default token may be specified,
11968 and it must be the last first-class token.
11970 .It Cd login Ar name
11971 The user name on the remote machine.
11973 .It Cd password Ar string
11974 The user's password on the remote machine.
11976 .It Cd account Ar string
11977 Supply an additional account password.
11978 This is merely for FTP purposes.
11980 .It Cd macdef Ar name
11982 A macro is defined with the specified
11984 it is formed from all lines beginning with the next line and continuing
11985 until a blank line is (consecutive newline characters are) encountered.
11988 entries cannot be utilized by multiple machines, too, but must be
11989 defined following the
11991 they are intended to be used with.)
11994 exists, it is automatically run as the last step of the login process.
11995 This is merely for FTP purposes.
12002 .\" .Sh EXAMPLES {{{
12005 .\" .Ss "An example configuration" {{{
12006 .Ss "An example configuration"
12008 .Bd -literal -offset indent
12009 # This example assumes v15.0 compatibility mode
12012 # Request strict transport security checks!
12013 set ssl-verify=strict
12015 # Where are the up-to-date SSL certificates?
12016 # (Since we manage up-to-date ones explicitly, do not use any,
12017 # possibly outdated, default certificates shipped with OpenSSL)
12018 #set ssl-ca-dir=/etc/ssl/certs
12019 set ssl-ca-file=/etc/ssl/certs/ca-certificates.crt
12020 set ssl-ca-no-defaults
12021 #set ssl-ca-flags=partial-chain
12022 wysh set smime-ca-file="${ssl-ca-file}" \e
12023 smime-ca-no-defaults #smime-ca-flags="${ssl-ca-flags}"
12025 # Do not use protocols older than TLS v1.2.
12026 # Change this only when the remote server does not support it:
12027 # maybe use ssl-protocol-HOST (or -USER@HOST) syntax to define
12028 # such explicit exceptions, then, e.g.
12029 # set ssl-protocol-exam.ple='-ALL,+TLSv1.1'
12030 set ssl-protocol='-ALL,+TLSv1.2'
12032 # Explicitly define the list of ciphers, which may improve security,
12033 # especially with protocols older than TLS v1.2. See ciphers(1).
12034 # Including "@STRENGTH" will sort the final list by algorithm strength.
12035 # In reality it is possibly best to only use ssl-cipher-list-HOST
12036 # (or -USER@HOST), as necessary, again..
12037 set ssl-cipher-list=TLSv1.2:!aNULL:!eNULL:@STRENGTH
12038 # - TLSv1.2:!aNULL:!eNULL:\e
12039 # ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:\e
12040 # DHE-RSA-AES256-SHA:@STRENGTH
12041 # -ALL:!aNULL:!eNULL:!MEDIUM:!LOW:!MD5:!RC4:!EXPORT:@STRENGTH
12042 # Especially with TLSv1.3 curves selection may be desired:
12043 #set ssl-curves=P-521:P-384:P-256
12045 # Essential setting: select allowed character sets
12046 set sendcharsets=utf-8,iso-8859-1
12048 # A very kind option: when replying to a message, first try to
12049 # use the same encoding that the original poster used herself!
12050 set reply-in-same-charset
12052 # When replying, do not merge From: and To: of the original message
12053 # into To:. Instead old From: -> new To:, old To: -> merge Cc:.
12054 set recipients-in-cc
12056 # When sending messages, wait until the Mail-Transfer-Agent finishs.
12057 # Only like this you will be able to see errors reported through the
12058 # exit status of the MTA (including the built-in SMTP one)!
12061 # Only use built-in MIME types, no mime.types(5) files
12062 set mimetypes-load-control
12064 # Default directory where we act in (relative to $HOME)
12066 # A leading "+" (often) means: under *folder*
12067 # *record* is used to save copies of sent messages
12068 set MBOX=+mbox.mbox DEAD=+dead.txt \e
12069 record=+sent.mbox record-files record-resent
12071 # Make "file mymbox" and "file myrec" go to..
12072 shortcut mymbox %:+mbox.mbox myrec +sent.mbox
12074 # Not really optional, e.g., for S/MIME
12075 set from='Your Name <address@exam.ple>'
12077 # It may be necessary to set hostname and/or smtp-hostname
12078 # if the "SERVER" of mta and "domain" of from do not match.
12079 # The `urlencode' command can be used to encode USER and PASS
12080 set mta=(smtps?|submission)://[USER[:PASS]@]SERVER[:PORT] \e
12081 smtp-auth=login/plain... \e
12084 # Never refuse to start into interactive mode, and more
12086 colour-pager crt= \e
12087 followup-to followup-to-honour=ask-yes \e
12088 history-file=+.\*(uAhist history-size=-1 history-gabby \e
12089 mime-counter-evidence=0xE \e
12090 prompt='?\e?!\e![\e${account}#\e${mailbox-display}]? ' \e
12091 reply-to-honour=ask-yes \e
12094 # Only include the selected header fields when typing messages
12095 headerpick type retain from_ date from to cc subject \e
12096 message-id mail-followup-to reply-to
12097 # ...when forwarding messages
12098 headerpick forward retain subject date from to cc
12099 # ...when saving message, etc.
12100 #headerpick save ignore ^Original-.*$ ^X-.*$
12102 # Some mailing lists
12103 mlist '@xyz-editor\e.xyz$' '@xyzf\e.xyz$'
12104 mlsubscribe '^xfans@xfans\e.xyz$'
12106 # Handle a few file extensions (to store MBOX databases)
12107 filetype bz2 'bzip2 -dc' 'bzip2 -zc' \e
12108 gz 'gzip -dc' 'gzip -c' xz 'xz -dc' 'xz -zc' \e
12109 zst 'zstd -dc' 'zstd -19 -zc' \e
12110 zst.pgp 'gpg -d | zstd -dc' 'zstd -19 -zc | gpg -e'
12112 # A real life example of a very huge free mail provider
12113 # Instead of directly placing content inside `account',
12114 # we `define' a macro: like that we can switch "accounts"
12115 # from within *on-compose-splice*, for example!
12117 set folder=~/spool/XooglX inbox=+syste.mbox sent=+sent
12118 set from='Your Name <address@examp.ple>'
12119 set mta=smtp://USER:PASS@smtp.gmXil.com smtp-use-starttls
12125 # Here is a pretty large one which does not allow sending mails
12126 # if there is a domain name mismatch on the SMTP protocol level,
12127 # which would bite us if the value of from does not match, e.g.,
12128 # for people who have a sXXXXeforge project and want to speak
12129 # with the mailing list under their project account (in from),
12130 # still sending the message through their normal mail provider
12132 set folder=~/spool/XandeX inbox=+syste.mbox sent=+sent
12133 set from='Your Name <address@exam.ple>'
12134 set mta=smtps://USER:PASS@smtp.yaXXex.ru:465 \e
12135 hostname=yaXXex.com smtp-hostname=
12141 # Create some new commands so that, e.g., `ls /tmp' will..
12142 commandalias lls '!ls ${LS_COLOR_FLAG} -aFlrS'
12143 commandalias llS '!ls ${LS_COLOR_FLAG} -aFlS'
12145 # We do not support gpg(1) directly yet. But simple --clearsign'd
12146 # message parts can be dealt with as follows:
12149 wysh set pipe-text/plain=$'@*#++=@\e
12150 < "${MAILX_FILENAME_TEMPORARY}" awk \e
12151 -v TMPFILE="${MAILX_FILENAME_TEMPORARY}" \e'\e
12153 /^-----BEGIN PGP SIGNED MESSAGE-----/,/^$/ {\e
12156 print "--- GPG --verify ---";\e
12157 system("gpg --verify " TMPFILE " 2>&1");\e
12158 print "--- GPG --verify ---";\e
12162 /^-----BEGIN PGP SIGNATURE-----/,\e
12163 /^-----END PGP SIGNATURE-----/{\e
12170 commandalias V '\e'call V
12174 When storing passwords in
12176 appropriate permissions should be set on this file with
12177 .Ql $ chmod 0600 \*(ur .
12180 is available user credentials can be stored in the central
12182 file instead; e.g., here is a different version of the example account
12183 that sets up SMTP and POP3:
12185 .Bd -literal -offset indent
12187 set folder=~/spool/XandeX inbox=+syste.mbox sent=+sent
12188 set from='Your Name <address@exam.ple>'
12190 # Load an encrypted ~/.netrc by uncommenting the next line
12191 #set netrc-pipe='gpg -qd ~/.netrc.pgp'
12193 set mta=smtps://smtp.yXXXXx.ru:465 \e
12194 smtp-hostname= hostname=yXXXXx.com
12195 set pop3-keepalive=240 pop3-no-apop-pop.yXXXXx.ru
12196 commandalias xp fi pop3s://pop.yXXXXx.ru
12208 .Bd -literal -offset indent
12209 machine *.yXXXXx.ru login USER password PASS
12213 This configuration should now work just fine:
12216 .Dl $ echo text | \*(uA -dvv -AXandeX -s Subject user@exam.ple
12219 .\" .Ss "Signed and encrypted messages with S/MIME" {{{
12220 .Ss "Signed and encrypted messages with S/MIME"
12222 \*(OP S/MIME provides two central mechanisms:
12223 message signing and message encryption.
12224 A signed message contains some data in addition to the regular text.
12225 The data can be used to verify that the message was sent using a valid
12226 certificate, that the sender's address in the message header matches
12227 that in the certificate, and that the message text has not been altered.
12228 Signing a message does not change its regular text;
12229 it can be read regardless of whether the recipient's software is able to
12233 It is thus usually possible to sign all outgoing messages if so desired.
12234 Encryption, in contrast, makes the message text invisible for all people
12235 except those who have access to the secret decryption key.
12236 To encrypt a message, the specific recipient's public encryption key
12238 It is therefore not possible to send encrypted mail to people unless their
12239 key has been retrieved from either previous communication or public key
12241 A message should always be signed before it is encrypted.
12242 Otherwise, it is still possible that the encrypted message text is
12246 A central concept to S/MIME is that of the certification authority (CA).
12247 A CA is a trusted institution that issues certificates.
12248 For each of these certificates it can be verified that it really
12249 originates from the CA, provided that the CA's own certificate is
12251 A set of CA certificates is usually delivered with OpenSSL and installed
12253 If you trust the source of your OpenSSL software installation,
12254 this offers reasonable security for S/MIME on the Internet.
12256 .Va smime-ca-no-defaults
12257 to avoid using the default certificate and point
12261 to a trusted pool of certificates.
12262 In general, a certificate cannot be more secure than the method its CA
12263 certificate has been retrieved with.
12266 The first thing you need for participating in S/MIME message exchange is
12267 your personal certificate, including a private key.
12268 The certificate contains public information, in particular your name and
12269 your email address(es), and the public key that is used by others to
12270 encrypt messages for you,
12271 and to verify signed messages they supposedly received from you.
12272 The certificate is included in each signed message you send.
12273 The private key must be kept secret.
12274 It is used to decrypt messages that were previously encrypted with your
12275 public key, and to sign messages.
12278 For personal use it is recommended that you get a S/MIME certificate
12279 from one of the major CAs on the Internet using your WWW browser.
12280 Many CAs offer such certificates for free.
12282 .Lk https://www.CAcert.org
12283 which issues client and server certificates to members of their
12284 community for free; their root certificate
12285 .Pf ( Lk https://\:www.cacert.org/\:certs/\:root.crt )
12286 is often not in the default set of trusted CA root certificates, though,
12287 which means you will have to download their root certificate separately
12288 and ensure it is part of our S/MIME certificate validation chain by
12291 or as a vivid member of the
12292 .Va smime-ca-file .
12293 But let us take a step-by-step tour on how to setup S/MIME with
12294 a certificate from CAcert.org despite this situation!
12297 First of all you will have to become a member of the CAcert.org
12298 community, simply by registrating yourself via the web interface.
12299 Once you are, create and verify all email addresses you want to be able
12300 to create signed and encrypted messages for/with using the corresponding
12301 entries of the web interface.
12302 Now ready to create S/MIME certificates, so let us create a new
12303 .Dq client certificate ,
12304 ensure to include all email addresses that should be covered by the
12305 certificate in the following web form, and also to use your name as the
12309 Create a private key and a certificate request on your local computer
12310 (please see the manual pages of the used commands for more in-depth
12311 knowledge on what the used arguments etc. do):
12314 .Dl openssl req -nodes -newkey rsa:4096 -keyout key.pem -out creq.pem
12317 Afterwards copy-and-paste the content of
12319 into the certificate-request (CSR) field of the web form on the
12320 CAcert.org website (you may need to unfold some
12321 .Dq advanced options
12322 to see the corresponding text field).
12323 This last step will ensure that your private key (which never left your
12324 box) and the certificate belong together (through the public key that
12325 will find its way into the certificate via the certificate-request).
12326 You are now ready and can create your CAcert certified certificate.
12327 Download and store or copy-and-paste it as
12332 In order to use your new S/MIME setup a combined private key/public key
12333 (certificate) file has to be created:
12336 .Dl cat key.pem pub.crt > ME@HERE.com.paired
12339 This is the file \*(UA will work with.
12340 If you have created your private key with a passphrase then \*(UA will
12341 ask you for it whenever a message is signed or decrypted.
12342 Set the following variables to henceforth use S/MIME (setting
12344 is of interest for verification only):
12346 .Bd -literal -offset indent
12347 set smime-ca-file=ALL-TRUSTED-ROOT-CERTS-HERE \e
12348 smime-sign-cert=ME@HERE.com.paired \e
12349 smime-sign-message-digest=SHA256 \e
12354 From each signed message you send, the recipient can fetch your
12355 certificate and use it to send encrypted mail back to you.
12356 Accordingly if somebody sends you a signed message, you can do the same,
12359 command to check the validity of the certificate.
12362 Variables of interest for S/MIME signing:
12364 .Va smime-ca-file ,
12365 .Va smime-ca-flags ,
12366 .Va smime-ca-no-defaults ,
12367 .Va smime-crl-dir ,
12368 .Va smime-crl-file ,
12370 .Va smime-sign-cert ,
12371 .Va smime-sign-include-certs
12373 .Va smime-sign-message-digest .
12376 After it has been verified save the certificate via
12378 and tell \*(UA that it should use it for encryption for further
12379 communication with that somebody:
12381 .Bd -literal -offset indent
12383 set smime-encrypt-USER@HOST=FILENAME \e
12384 smime-cipher-USER@HOST=AES256
12388 Additional variables of interest for S/MIME en- and decryption:
12391 .Va smime-encrypt-USER@HOST .
12394 You should carefully consider if you prefer to store encrypted messages
12396 If you do, anybody who has access to your mail folders can read them,
12397 but if you do not, you might be unable to read them yourself later if
12398 you happen to lose your private key.
12401 command saves messages in decrypted form, while the
12405 commands leave them encrypted.
12408 Note that neither S/MIME signing nor encryption applies to message
12409 subjects or other header fields yet.
12410 Thus they may not contain sensitive information for encrypted messages,
12411 and cannot be trusted even if the message content has been verified.
12412 When sending signed messages,
12413 it is recommended to repeat any important header information in the
12417 .\" .Ss "Using CRLs with S/MIME or SSL/TLS" {{{
12418 .Ss "Using CRLs with S/MIME or SSL/TLS"
12420 \*(OP Certification authorities (CAs) issue certificate revocation
12421 lists (CRLs) on a regular basis.
12422 These lists contain the serial numbers of certificates that have been
12423 declared invalid after they have been issued.
12424 Such usually happens because the private key for the certificate has
12426 because the owner of the certificate has left the organization that is
12427 mentioned in the certificate, etc.
12428 To seriously use S/MIME or SSL/TLS verification,
12429 an up-to-date CRL is required for each trusted CA.
12430 There is otherwise no method to distinguish between valid and
12431 invalidated certificates.
12432 \*(UA currently offers no mechanism to fetch CRLs, nor to access them on
12433 the Internet, so they have to be retrieved by some external mechanism.
12436 \*(UA accepts CRLs in PEM format only;
12437 CRLs in DER format must be converted, like, e.\|g.:
12440 .Dl $ openssl crl \-inform DER \-in crl.der \-out crl.pem
12443 To tell \*(UA about the CRLs, a directory that contains all CRL files
12444 (and no other files) must be created.
12449 variables, respectively, must then be set to point to that directory.
12450 After that, \*(UA requires a CRL to be present for each CA that is used
12451 to verify a certificate.
12454 .\" .Ss "Handling spam" {{{
12455 .Ss "Handling spam"
12457 \*(OP \*(UA can make use of several spam interfaces for the purpose of
12458 identification of, and, in general, dealing with spam messages.
12459 A precondition of most commands in order to function is that the
12461 variable is set to one of the supported interfaces.
12462 Once messages have been identified as spam their (volatile)
12464 state can be prompted: the
12468 message specifications will address respective messages and their
12470 entries will be used when displaying the
12472 in the header display.
12477 rates the given messages and sets their
12480 If the spam interface offers spam scores those can also be displayed in
12481 the header display by including the
12491 will interact with the Bayesian filter of the chosen interface and learn
12492 the given messages as
12496 respectively; the last command can be used to cause
12498 of messages; it adheres to their current
12500 state and thus reverts previous teachings.
12505 will simply set and clear, respectively, the mentioned volatile
12507 message flag, without any interface interaction.
12516 requires a running instance of the
12518 server in order to function, started with the option
12520 shall Bayesian filter learning be possible.
12522 .Bd -literal -offset indent
12523 $ spamd -i localhost:2142 -i /tmp/.spamsock -d [-L] [-l]
12524 $ spamd --listen=localhost:2142 --listen=/tmp/.spamsock \e
12525 --daemonize [--local] [--allow-tell]
12529 Thereafter \*(UA can make use of these interfaces:
12531 .Bd -literal -offset indent
12532 $ \*(uA -Sspam-interface=spamc -Sspam-maxsize=500000 \e
12533 -Sspamc-command=/usr/local/bin/spamc \e
12534 -Sspamc-arguments="-U /tmp/.spamsock" -Sspamc-user=
12536 $ \*(uA -Sspam-interface=spamc -Sspam-maxsize=500000 \e
12537 -Sspamc-command=/usr/local/bin/spamc \e
12538 -Sspamc-arguments="-d localhost -p 2142" -Sspamc-user=
12542 Using the generic filter approach allows usage of programs like
12544 Here is an example, requiring it to be accessible via
12547 .Bd -literal -offset indent
12548 $ \*(uA -Sspam-interface=filter -Sspam-maxsize=500000 \e
12549 -Sspamfilter-ham="bogofilter -n" \e
12550 -Sspamfilter-noham="bogofilter -N" \e
12551 -Sspamfilter-nospam="bogofilter -S" \e
12552 -Sspamfilter-rate="bogofilter -TTu 2>/dev/null" \e
12553 -Sspamfilter-spam="bogofilter -s" \e
12554 -Sspamfilter-rate-scanscore="1;^(.+)$"
12558 Because messages must exist on local storage in order to be scored (or
12559 used for Bayesian filter training), it is possibly a good idea to
12560 perform the local spam check last:
12562 .Bd -literal -offset indent
12563 define spamdelhook {
12565 spamset (header x-dcc-brand-metrics "bulk")
12566 # Server-side spamassassin(1)
12567 spamset (header x-spam-flag "YES")
12568 del :s # TODO we HAVE to be able to do `spamrate :u ! :sS'
12569 move :S +maybe-spam
12572 move :S +maybe-spam
12574 set folder-hook-FOLDER=spamdelhook
12578 See also the documentation for the variables
12579 .Va spam-interface , spam-maxsize ,
12580 .Va spamc-command , spamc-arguments , spamc-user ,
12581 .Va spamfilter-ham , spamfilter-noham , spamfilter-nospam , \
12584 .Va spamfilter-rate-scanscore .
12592 In general it is a good idea to turn on
12598 twice) if something does not work well.
12599 Very often a diagnostic message can be produced that leads to the
12600 problems' solution.
12602 .\" .Ss "\*(UA shortly hangs on startup" {{{
12603 .Ss "\*(UA shortly hangs on startup"
12605 This can have two reasons, one is the necessity to wait for a file lock
12606 and cannot be helped, the other being that \*(UA calls the function
12608 in order to query the nodename of the box (sometimes the real one is
12609 needed instead of the one represented by the internal variable
12611 One may have varying success by ensuring that the real hostname and
12615 or, more generally, that the name service is properly setup \(en
12618 return the expected value?
12619 Does this local hostname have a domain suffix?
12620 RFC 6762 standardized the link-local top-level domain
12622 try again after adding an (additional) entry with this extension.
12625 .\" .Ss "I cannot login to Google mail aka GMail" {{{
12626 .Ss "I cannot login to Google mail aka GMail"
12628 Since 2014 some free service providers classify programs as
12630 unless they use a special authentification method (OAuth 2.0) which
12631 was not standardized for non-HTTP protocol authentication token query
12632 until August 2015 (RFC 7628).
12635 Different to Kerberos / GSSAPI, which is developed since the mid of the
12636 1980s, where a user can easily create a local authentication ticket for
12637 her- and himself with the locally installed
12639 program, that protocol has no such local part but instead requires
12640 a world-wide-web query to create or fetch a token; since there is no
12641 local cache this query would have to be performed whenever \*(UA is
12642 invoked (in interactive sessions situation may differ).
12645 \*(UA does not support OAuth.
12646 Because of this it is necessary to declare \*(UA a
12647 .Dq less secure app
12648 (on the providers account web page) in order to read and send mail.
12649 However, it also seems possible to take the following steps instead:
12654 give the provider the number of a mobile phone,
12657 .Dq 2-Step Verification ,
12659 create an application specific password (16 characters), and
12661 use that special password instead of the real Google account password in
12662 \*(UA (for more on that see the section
12663 .Sx "On URL syntax and credential lookup" ) .
12667 .\" .Ss "Not \(dqdefunctional\(dq, but the editor key does not work" {{{
12668 .Ss "Not \(dqdefunctional\(dq, but the editor key does not work"
12670 It can happen that the terminal library (see
12671 .Sx "On terminal control and line editor",
12674 reports different codes than the terminal really sends, in which case
12675 \*(UA will tell that a key binding is functional, but will not be able to
12676 recognize it because the received data does not match anything expected.
12681 ings will show the byte sequences that are expected.
12684 To overcome the situation, use, e.g., the program
12686 in conjunction with the command line option
12688 if available, to see the byte sequences which are actually produced
12689 by keypresses, and use the variable
12691 to make \*(UA aware of them.
12692 E.g., the terminal this is typed on produces some false sequences, here
12693 an example showing the shifted home key:
12695 .Bd -literal -offset indent
12698 # 1B 5B=[ 31=1 3B=; 32=2 48=H
12703 ? \*(uA -v -Stermcap='kHOM=\eE[H'
12712 .\" .Sh "IMAP CLIENT" {{{
12715 \*(OPally there is IMAP client support available.
12716 This part of the program is obsolete and will vanish in v15 with the
12717 large MIME and I/O layer rewrite, because it uses old-style blocking I/O
12718 and makes excessive use of signal based long code jumps.
12719 Support can hopefully be readded later based on a new-style I/O, with
12720 SysV signal handling.
12721 In fact the IMAP support had already been removed from the codebase, but
12722 was reinstantiated on user demand: in effect the IMAP code is at the
12723 level of \*(UA v14.8.16 (with
12725 being the sole exception), and should be treated with some care.
12732 protocol prefixes, and an IMAP-based
12735 IMAP URLs (paths) undergo inspections and possible transformations
12736 before use (and the command
12738 can be used to manually apply them to any given argument).
12739 Hierarchy delimiters are normalized, a step which is configurable via the
12741 variable chain, but defaults to the first seen delimiter otherwise.
12742 \*(UA supports internationalised IMAP names, and en- and decodes the
12743 names from and to the
12745 as necessary and possible.
12746 If a mailbox name is expanded (see
12747 .Sx "Filename transformations" )
12748 to an IMAP mailbox, all names that begin with `+' then refer to IMAP
12749 mailboxes below the
12751 target box, while folder names prefixed by `@' refer to folders below
12752 the hierarchy base.
12755 Note: some IMAP servers do not accept the creation of mailboxes in
12756 the hierarchy base, but require that they are created as subfolders of
12757 `INBOX' \(en with such servers a folder name of the form
12759 .Dl imaps://mylogin@imap.myisp.example/INBOX.
12761 should be used (the last character is the server's hierarchy
12763 The following IMAP-specific commands exist:
12766 .Bl -tag -width ".It Ic BaNg"
12769 Only applicable to cached IMAP mailboxes;
12770 takes a message list and reads the specified messages into the IMAP
12775 If operating in disconnected mode on an IMAP mailbox,
12776 switch to online mode and connect to the mail server while retaining
12777 the mailbox status.
12778 See the description of the
12780 variable for more information.
12784 If operating in online mode on an IMAP mailbox,
12785 switch to disconnected mode while retaining the mailbox status.
12786 See the description of the
12789 A list of messages may optionally be given as argument;
12790 the respective messages are then read into the cache before the
12791 connection is closed, thus
12793 makes the entire mailbox available for disconnected use.
12797 Sends command strings directly to the current IMAP server.
12798 \*(UA operates always in IMAP `selected state' on the current mailbox;
12799 commands that change this will produce undesirable results and should be
12801 Useful IMAP commands are:
12802 .Bl -tag -offset indent -width ".Ic getquotearoot"
12804 Takes the name of an IMAP mailbox as an argument and creates it.
12806 (RFC 2087) Takes the name of an IMAP mailbox as an argument
12807 and prints the quotas that apply to the mailbox.
12808 Not all IMAP servers support this command.
12810 (RFC 2342) Takes no arguments and prints the Personal Namespaces,
12811 the Other User's Namespaces and the Shared Namespaces.
12812 Each namespace type is printed in parentheses;
12813 if there are multiple namespaces of the same type,
12814 inner parentheses separate them.
12815 For each namespace a prefix and a hierarchy separator is listed.
12816 Not all IMAP servers support this command.
12821 Perform IMAP path transformations.
12825 .Sx "Command modifiers" ) ,
12826 and manages the error number
12828 The first argument specifies the operation:
12830 normalizes hierarchy delimiters (see
12832 and converts the strings from the locale
12834 to the internationalized variant used by IMAP,
12836 performs the reverse operation.
12841 The following IMAP-specific internal variables exist:
12844 .Bl -tag -width ".It Va BaNg"
12846 .It Va disconnected
12847 \*(BO When an IMAP mailbox is selected and this variable is set,
12848 no connection to the server is initiated.
12849 Instead, data is obtained from the local cache (see
12852 Mailboxes that are not present in the cache
12853 and messages that have not yet entirely been fetched from the server
12855 to fetch all messages in a mailbox at once,
12857 .No ` Ns Li copy * /dev/null Ns '
12858 can be used while still in connected mode.
12859 Changes that are made to IMAP mailboxes in disconnected mode are queued
12860 and committed later when a connection to that server is made.
12861 This procedure is not completely reliable since it cannot be guaranteed
12862 that the IMAP unique identifiers (UIDs) on the server still match the
12863 ones in the cache at that time.
12866 when this problem occurs.
12868 .It Va disconnected-USER@HOST
12869 The specified account is handled as described for the
12872 but other accounts are not affected.
12875 .It Va imap-auth-USER@HOST , imap-auth
12876 Sets the IMAP authentication method.
12877 Valid values are `login' for the usual password-based authentication
12879 `cram-md5', which is a password-based authentication that does not send
12880 the password over the network in clear text,
12881 and `gssapi' for GSS-API based authentication.
12885 Enables caching of IMAP mailboxes.
12886 The value of this variable must point to a directory that is either
12887 existent or can be created by \*(UA.
12888 All contents of the cache can be deleted by \*(UA at any time;
12889 it is not safe to make assumptions about them.
12892 .It Va imap-delim-USER@HOST , imap-delim-HOST , imap-delim
12893 The hierarchy separator used by the IMAP server.
12894 Whenever an IMAP path is specified it will undergo normalization.
12895 One of the normalization steps is the squeezing and adjustment of
12896 hierarchy separators.
12897 If this variable is set, any occurrence of any character of the given
12898 value that exists in the path will be replaced by the first member of
12899 the value; an empty value will cause the default to be used, it is
12901 If not set, we will reuse the first hierarchy separator character that
12902 is discovered in a user-given mailbox name.
12904 .Mx Va imap-keepalive
12905 .It Va imap-keepalive-USER@HOST , imap-keepalive-HOST , imap-keepalive
12906 IMAP servers may close the connection after a period of
12907 inactivity; the standard requires this to be at least 30 minutes,
12908 but practical experience may vary.
12909 Setting this variable to a numeric `value' greater than 0 causes
12910 a `NOOP' command to be sent each `value' seconds if no other operation
12914 .It Va imap-list-depth
12915 When retrieving the list of folders on an IMAP server, the
12917 command stops after it has reached a certain depth to avoid possible
12919 The value of this variable sets the maximum depth allowed.
12921 If the folder separator on the current IMAP server is a slash `/',
12922 this variable has no effect and the
12924 command does not descend to subfolders.
12926 .Mx Va imap-use-starttls
12927 .It Va imap-use-starttls-USER@HOST , imap-use-starttls-HOST , imap-use-starttls
12928 Causes \*(UA to issue a `STARTTLS' command to make an unencrypted
12929 IMAP session SSL/TLS encrypted.
12930 This functionality is not supported by all servers,
12931 and is not used if the session is already encrypted by the IMAPS method.
12936 .\" .Sh "SEE ALSO" {{{
12946 .Xr spamassassin 1 ,
12955 .Xr mailwrapper 8 ,
12960 .\" .Sh HISTORY {{{
12963 M. Douglas McIlroy writes in his article
12964 .Dq A Research UNIX Reader: Annotated Excerpts \
12965 from the Programmer's Manual, 1971-1986
12968 command already appeared in First Edition
12972 .Bd -ragged -offset indent
12973 Electronic mail was there from the start.
12974 Never satisfied with its exact behavior, everybody touched it at one
12975 time or another: to assure the safety of simultaneous access, to improve
12976 privacy, to survive crashes, to exploit uucp, to screen out foreign
12977 freeloaders, or whatever.
12978 Not until v7 did the interface change (Thompson).
12979 Later, as mail became global in its reach, Dave Presotto took charge and
12980 brought order to communications with a grab-bag of external networks
12986 Mail was written in 1978 by Kurt Shoens and developed as part of the
12989 distribution until 1995.
12990 Mail has then seen further development in open source
12992 variants, noticeably by Christos Zoulas in
12994 Based upon this Nail, later Heirloom Mailx, was developed by Gunnar
12995 Ritter in the years 2000 until 2008.
12996 Since 2012 S-nail is maintained by Steffen (Daode) Nurpmeso.
12997 This man page is derived from
12998 .Dq The Mail Reference Manual
12999 that was originally written by Kurt Shoens.
13005 .An "Kurt Shoens" ,
13006 .An "Edward Wang" ,
13007 .An "Keith Bostic" ,
13008 .An "Christos Zoulas" ,
13009 .An "Gunnar Ritter" ,
13010 .An "Steffen Nurpmeso" .
13017 provide contact addresses:
13019 .\" v15-compat: drop eval as `mail' will expand variable?
13020 .Dl ? echo $contact-web; eval mail $contact-mail
13023 .\" .Sh CAVEATS {{{
13026 \*(ID Interrupting an operation via
13030 from anywhere else but a command prompt is very problematic and likely
13031 to leave the program in an undefined state: many library functions
13032 cannot deal with the
13034 that this software (still) performs; even though efforts have been taken
13035 to address this, no sooner but in v15 it will have been worked out:
13036 interruptions have not been disabled in order to allow forceful breakage
13037 of hanging network connections, for example (all this is unrelated to
13041 The SMTP and POP3 protocol support of \*(UA is very basic.
13042 Also, if it fails to contact its upstream SMTP server, it will not make
13043 further attempts to transfer the message at a later time (setting
13048 If this is a concern, it might be better to set up a local SMTP server
13049 that is capable of message queuing.
13055 After deleting some message of a POP3 mailbox the header summary falsely
13056 claims that there are no messages to display, one needs to perform
13057 a scroll or dot movement to restore proper state.
13059 In threaded display a power user may encounter crashes very
13060 occasionally (this is may and very).
13064 in the source repository lists future directions.