1. Acknowledgments
+ Index
+
List of Tables
2.1. Default Menu Movement Keys
|----------+----------+---------------------------------------------|
| <Return> | | display-message |
|----------+----------+---------------------------------------------|
- | <Tab> | | jump to the next new message |
+ | <Tab> | | jump to the next new or unread message |
|----------+----------+---------------------------------------------|
| @ | | show the author's full e-mail address |
|----------+----------+---------------------------------------------|
To:
-
After you've finished entering the recipient(s), press return. If you want
to send an email to more than one recipient, separate the email addresses
using the comma ",". Mutt-ng then asks you for the email subject. Again,
set editor = "nano"
set editor = "emacs"
-
If you don't set your preferred editor in your configuration, mutt-ng
first looks whether the environment variable $VISUAL is set, and if so, it
takes its value as editor command. Otherwise, it has a look at $EDITOR and
set edit_headers
-
Once you have finished editing the body of your mail message, you are
returned to the compose menu. The following options are available:
> production server that we want to set up before our customer's
> project will go live.
-
You can start editing the email message. It is strongly recommended to put
your answer below the quoted text and to only quote what is really
necessary and that you refer to. Putting your answer on top of the quoted
set attribution = "On %d, %n wrote:"
-
It can also be set to something more compact, e.g.
set attribution = "attribution="* %n <%a> [%(%y-%m-%d %H:%M)]:"
-
The example above results in the following attribution:
* Michael Svensson <svensson@foobar.com> [05-03-06 17:02]:
> production server that we want to set up before our customer's
> project will go live.
-
Generally, try to keep your attribution short yet information-rich. It is
not the right place for witty quotes, long "attribution" novels or
anything like that: the right place for such things is - if at all - the
lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@
-
Nowadays, most mailing list software like GNU Mailman adds a
Mail-Followup-To: header to their emails anyway, so setting lists is
hardly ever necessary in practice.
----- End forwarded message -----
-
When you're done with editing the mail, save and quit the editor, and you
will return to the compose menu, the same menu you also encounter when
composing or replying to mails.
set realname='Mutt-ng user' ; ignore x-
-
The hash mark, or pound sign (``#''), is used as a ``comment'' character.
You can use it to annotate your initialization file. All text after the
comment character to the end of the line is ignored. For example,
my_hdr X-Disclaimer: Why are you listening to me? # This is a comment
-
Single quotes (') and double quotes (") can be used to quote strings which
contain spaces or other special characters. The difference between the two
types of quotes is similar to that of many popular shell programs, namely
set realname="Michael \"MuttDude\" Elkins"
-
``\\'' means to insert a literal ``\'' into the line. ``\n'' and ``\r''
have their usual C meanings of linefeed and carriage-return, respectively.
# folder-hook . \
set realname="Michael \"MuttDude\" Elkins"
-
When testing your config files, beware the following caveat. The backslash
at the end of the commented line extends the current line with the next
line - then referred to as a ``continuation line''. As the first line is
line4
line5
-
line1 ``continues'' until line4. however, the part after the # is a
comment which includes line3 and line4. line5 is a new line of its own and
thus is interpreted again.
my_hdr X-Operating-System: `uname -a`
-
The output of the Unix command ``uname -a'' will be substituted before the
line is parsed. Note that since initialization files are line oriented,
only the first line of output from the Unix command will be substituted.
set record=+sent_on_$HOSTNAME
-
sets the record variable to the string +sent_on_ and appends the value of
the evironment variable $HOSTNAME.
set imap_home_namespace = $folder
-
would set the value of imap-home-namespace to the value to which folder is
currently set to.
macro generic <F1> "!less -r /path/to/manual" "Show manual"
macro pager <F1> "!less -r /path/to/manual" "Show manual"
-
for generic, pager and index .The alternative is to define a custom
variable like so:
macro pager <F1> "$user_manualcmd<enter>" "Show manual"
macro index <F1> "$user_manualcmd<enter>" "Show manual"
-
to re-use the command sequence as in:
macro index <F2> "$user_manualcmd | grep '\^[ ]\\+~. '" "Show Patterns"
-
Using this feature, arbitrary sequences can be defined once and recalled
and reused where necessary. More advanced scenarios could include to save
a variable's value at the beginning of macro sequence and restore it at
set user_foo = 42
set user_foo = 666
-
the variable $user_foo has a current value of 666 and an initial of 42.
The query
set ?user_foo
-
will show 666. After doing the reset via
reset user_foo
-
a following query will give 42 as the result. After unsetting it via
unset user_foo
-
any query or operation (except the noted expansion within other
statements) will lead to an error message.
muttng -Q muttng_docdir
-
To extend the example for viewing the manual via self-defined variables,
it can be made more readable and more portable by changing the real path
in:
set user_manualcmd = '!less -r /path/to_manual'
-
to:
set user_manualcmd = "!less -r $muttng_docdir/manual.txt"
-
which works everywhere if a manual is installed.
Please note that by the type of quoting, muttng determines when to expand
folder-hook . "set user_current_folder = $muttng_folder_name"
-
will be already be translated to the following when reading the startup
files:
folder-hook . "set user_current_folder = some_folder"
-
with some_folder being the name of the first folder muttng opens. On the
contrary,
folder-hook . 'set user_current_folder = $muttng_folder_name'
-
will be executed at runtime because of the single quotes so that
user_current_folder will always have the value of the currently opened
folder.
folder-hook . 'source ~/.mutt/score-$muttng_folder_name'
-
which can be used to source files containing score commands depending on
the folder the user enters.
set user_magic_number = 42
set folder = $user_magic_number
-
4. Defining/Using aliases
- Usage: alias key address [ , address, ... ]
+ Usage: alias key address[ , address, ... ]
+
It's usually very cumbersome to remember or type out the address of
someone you are communicating with. Mutt-ng allows you to create
alias muttdude me@cs.hmc.edu (Michael Elkins)
alias theguys manny, moe, jack
-
Unlike other mailers, Mutt-ng doesn't require aliases to be defined in a
special file. The alias command can appear anywhere in a configuration
file, as long as this file is source .Consequently, you can have multiple
source ~/.mail_aliases
set alias_file=~/.mail_aliases
-
To use aliases, you merely use the alias at any place in mutt where
muttprompts for addresses, such as the To: or Cc: prompt. You can also
enter aliases in your editor at the appropriate headers if you have the
Usage: bind map key function
+
This command allows you to change the default key bindings (operation
invoked when pressing a key).
6. Defining aliases for character sets
- Usage: charset-hook alias charset Usage: iconv-hook charset local-charset
+ Usage: charset-hook alias charset
+ Usage: iconv-hook charset local-charset
+
The charset-hook command defines an alias for a character set. This is
useful to properly display messages which are tagged with a character set
Usage: folder-hook [!]regexp command
+
It is often desirable to change settings based on which mailbox you are
reading. The folder-hook command provides a method by which you can
execute any configuration command. regexp is a regular expression
folder-hook mutt set sort=threads
-
However, the sorting method is not restored to its previous value when
reading a different mailbox. To specify a default command, use the pattern
``.'':
folder-hook . set sort=date-sent
-
8. Keyboard macros
- Usage: macro menu key sequence [ description ]
+ Usage: macro menu key sequence [ description ]
+
Macros are useful when you would like a single key to perform a series of
actions. When you press key in menu menu ,Mutt-ng will behave as if you
9. Using color and mono video attributes
- Usage: color object foreground background [ regexp ] Usage: color index
- foreground background pattern Usage: uncolor index pattern [ pattern ... ]
+ Usage: color object foregroundbackground [ regexp]
+ Usage: color index foreground backgroundpattern
+ Usage: uncolor index pattern[ pattern ... ]
+
If your terminal supports color, you can spice up Mutt-ng by creating your
own color scheme. To define the color of an object (type of information),
set COLORFGBG="green;black"
export COLORFGBG
-
Note: The S-Lang library requires you to use the lightgray and brown
keywords instead of white and yellow when setting this variable.
If your terminal does not support color, it is still possible change the
video attributes through the use of the ``mono'' command:
- Usage: mono <object> <attribute> [ regexp ] Usage: mono index attribute
- pattern Usage: unmono index pattern [ pattern ... ]
+ Usage: mono <object> <attribute>[ regexp ]
+ Usage: mono index attribute pattern
+ Usage: unmono index pattern[ pattern ... ]
where attribute is one of the following:
10. Ignoring (weeding) unwanted message headers
- Usage: [un]ignore pattern [ pattern ... ]
+ Usage: [un]ignore pattern [ pattern... ]
+
Messages often have many header fields added by automatic processing
systems, or which may not seem useful to display on the screen. This
unignore organization organisation x-mailer: x-newsreader: x-mailing-list:
unignore posted-to:
-
11. Alternative addresses
Usage: [un]alternates regexp [ regexp ... ]
whether you sent them or whether you received them from someone else. For
instance, when replying to a message that you sent to a different party,
mutt will automatically suggest to send the response to the original
- message's recipients -- responding to yourself won't make much sense in
- many cases. (See reply-to .)
+ message's recipients--responding to yourself won't make much sense in many
+ cases. (See reply-to .)
Many users receive e-mail under a number of different addresses. To fully
use mutt's features here, the program must be able to recognize what
format that can also be displayed nicely on old fixed-size terminals.
For introductory information on format=flowed messages, see
- <http://www.joeclark.org/ffaq.html> .
+ <http://www.joeclark.org/ffaq.html>.
12.2. Receiving: Display Setup
set wrapmargin = 10
-
The code above makes the line break 10 columns before the right side of
the terminal.
set max_line_length = 120
-
The example above will give you lines not longer than 120 characters.
When you view at format=flowed messages, you will often see the quoting
>production server that we want to set up before our customer's
>project will go live.
-
This obviously doesn't look very nice, and it makes it very hard to
differentiate between text and quoting character. The solution is to
configure mutt-ng to "stuff" the quoting:
set stuff_quoted
-
This will lead to a nicer result that is easier to read:
> Bill, can you please send last month's progress report to Mr.
> production server that we want to set up before our customer's
> project will go live.
-
12.3. Sending
If you want mutt-ng to send emails with format=flowed set, you need to
set text_flowed
-
Additionally, you have to use an editor which supports writing
format=flowed-conforming emails. For vim, this is done by adding w to the
formatoptions (see :h formatoptions and :h fo-table) when writing emails.
13. Mailing lists
- Usage: [un]lists regexp [ regexp ... ] Usage: [un]subscribe regexp [
- regexp ... ]
+ Usage: [un]lists regexp [ regexp... ]
+ Usage: [un]subscribe regexp [ regexp... ]
+
Mutt-ng has a few nice features for using-lists .In order to take
advantage of them, you must specify which addresses belong to mailing
Usage: mbox-hook [!]pattern mailbox
+
This command is used to move read messages from a specified mailbox to
adifferent mailbox automatically when you quit or change folders. pattern
is a regular expression specifying the mailbox to treat as a ``spool''
15. Defining mailboxes which receive mail
- Usage: [un]mailboxes [!]filename [ filename ... ]
+ Usage: [un]mailboxes [!]filename[ filename ... ]
+
This command specifies folders which can receive mail and which will be
checked for new messages. By default, the main menu status bar displays
16. User defined headers
- Usage: my_hdr string unmy_hdr field [ field ... ]
+ Usage: my_hdr string
+ Usage: unmy_hdr field [ field... ]
+
The ``my_hdr'' command allows you to create your own header fields which
will be added to every message you send.
my_hdr Organization: A Really Big Company, Anytown, USA
-
in your .muttrc.
Note: space characters are not allowed between the keyword and the colon
unmy_hdr to cc
-
17. Defining the order of headers when viewing messages
- Usage: hdr_order header1 header2 header3
+ Usage: hdr_order header1header2 header3
+
With this command, you can specify an order in which mutt will attempt to
present headers to you when viewing messages.
hdr_order From Date: From: To: Cc: Subject:
-
18. Specify default save filename
Usage: save-hook [!]pattern filename
+
This command is used to override the default filename used when saving
messages. filename will be used as the default filename if the message is
From: an address matching regexp or if you are the author and the message
save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
save-hook aol\\.com$ +spam
-
Also see the fcc-save-hook command.
19. Specify default Fcc: mailbox when composing
Usage: fcc-hook [!]pattern mailbox
+
This command is used to save outgoing mail in a mailbox other than record.
Mutt-ng searches the initial list of message recipients for the first
matching regexp and uses mailbox as the default Fcc: mailbox. If no match
Usage: fcc-save-hook [!]pattern mailbox
+
This command is a shortcut, equivalent to doing both a fcc-hook and a
save-hook with its arguments.
21. Change settings based upon message recipients
- Usage: reply-hook [!]pattern command Usage: send-hook [!]pattern command
+ Usage: reply-hook [!]pattern command
+ Usage: send-hook [!]pattern command
Usage: send2-hook [!]pattern command
+
+ v
+
These commands can be used to execute arbitrary configuration commands
based upon recipients of the message. pattern is a regular expression
matching the desired address. command is executed when regexp matches
Usage: message-hook [!]pattern command
+
This command can be used to execute arbitrary configuration commands
before viewing or formatting a message based upon information about the
message. command is executed if the pattern matches the message to be
message-hook ~A 'set pager=builtin'
message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject:.*\""'
-
23. Choosing the cryptographic key of the recipient
Usage: crypt-hook pattern keyid
+
When encrypting messages with PGP or OpenSSL, you may want to associate a
certain key with a given e-mail address automatically, either because the
recipient's public key can't be deduced from the destination address, or
Usage: push string
+
This command adds the named string to the keyboard buffer. The string may
contain control characters, key names and function names like the sequence
string in the macro command. You may use it to automatically run a
- sequence of commands at startup, or when entering certain folders.
+ sequence of commands at startup, or when entering certain folders. For
+ example, the following command will automatically collapse all threads
+ when entering a folder:
+
+ folder-hook . 'push <collapse-all>'
+
25. Executing functions
- Usage: exec function [ function ... ]
+ Usage: exec function [ function ... ]
+
This command can be used to execute any function. Functions are listed in
the functions. ``exec function'' is equivalent to ``push <function>''.
26. Message Scoring
- Usage: score pattern value Usage: unscore pattern [ pattern ... ]
+ Usage: score pattern value
+ Usage: unscore pattern [ pattern... ]
+
In situations where you have to cope with a lot of emails, e.g. when you
read many different mailing lists, and take part in discussions, it is
score "~f nion@muttng\.org" 50
score "~f @sco\.com" -100
-
If the pattern matches, it is also possible to set the score value of the
current message to a certain value and then stop evaluation:
score "~f santaclaus@northpole\.int" =666
-
What is important to note is that negative score values will be rounded up
to 0.
color index black yellow "~n 10-"
color index red yellow "~n 100-"
-
The rules above mark all messages with a score between 10 and 99 with
black and yellow, and messages with a score greater or equal 100 with red
and yellow. This might be unusual to you if you're used to e.g. slrn's
27. Spam detection
- Usage: spam pattern format Usage: nospam pattern
+ Usage: spam pattern format
+ Usage: nospam pattern
+
Mutt-ng has generalized support for external spam-scoring filters. By
defining your spam patterns with the spam and nospam commands, you can
spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM"
set spam_separator=", "
-
If I then received a message that DCC registered with ``many'' hits under
the ``Fuz2'' checksum, and that PureMessage registered with a 97%
probability of being spam, that message's spam tag would read90+/DCC-Fuz2,
spam "^From: .*MAILER-DAEMON" "999"
-
28. Setting variables
- Usage: set [no|inv]variable [=value] [ variable ... ] Usage: toggle
- variable [variable ... ] Usage: unset variable [variable ... ] Usage:
- reset variable [variable ... ]
+ Usage: set [no|inv]variable[=value] [ variable ... ]
+ Usage: toggle variable [variable... ]
+ Usage: unset variable [variable... ]
+ Usage: reset variable [variable... ]
+
This command is used to set (and unset) variables .There are four basic
types of variables: boolean, number, string and quadoption. boolean
set ?allow_8bit
-
The question mark is actually only required for boolean and quadoption
variables.
29. Reading initialization commands from another file
- Usage: source filename [ filename ... ]
+ Usage: source filename [ filename... ]
+
This command allows the inclusion of initialization commands from other
files. For example, I place all of my aliases in ˜/.mail_aliases so that
30. Removing hooks
- Usage: unhook [ * | hook-type ]
+ Usage: unhook [ * | hook-type ]
+
This command permits you to flush hooks you have previously defined. You
can either remove all hooks by giving the ``*'' character as an argument,
set config_charset = "..."
-
and replacing the dots with the actual character set. To avoid problems
while maintaining the setup, vim user's may want to use modelines as show
in:
# vim:fileencoding=...:
-
while, again, replacing the dots with the appropriate name. This tells vim
as which character set to read and save the file.
ifdef <item> <command>
ifndef <item> <command>
-
...whereby <item> can be one of:
o a function name
ifdef feature_pop 'source ~/.mutt-ng/setup-pop'
ifdef feature_nntp 'source ~/.mutt-ng/setup-nntp'
-
...to only source ˜/.mutt-ng/setup-imap if IMAP support is built in, only
source ˜/.mutt-ng/setup-pop if POP support is built in and only source
˜/.mutt-ng/setup-nntp if NNTP support is built in.
ifdef imap_mail_check 'set imap_mail_check = 300'
-
Provided for completeness is the test for menu names. To set
pager-index-lines only if the pager menu is available, use:
ifdef pager 'set pager_index_lines = 10'
-
For completeness, too, the opposite of ifdef is provided: ifndef which
only executes the command if the test fails. For example, the following
two examples are equivalent:
ifdef feature_ncurses 'source ~/.mutt-ng/setup-ncurses'
ifndef feature_ncurses 'source ~/.mutt-ng/setup-slang'
-
...and...
ifdef feature_slang 'source ~/.mutt-ng/setup-slang'
ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses'
-
32. Obsolete Variables
In the process of ensuring and creating more consistency, many variables
grouped, ORed, and negated. For a complete listing of these patterns,
please refer to table patterns in the Reference chapter.
- It must be noted that in this table, EXPR, USER , ID and SUBJECT are
- regular expressions. For ranges, the forms <[MAX], >>[MIN], [MIN]- and
- -[MAX] are also possible.
+ It must be noted that in this table, EXPR is a regular expression. For
+ ranges, the forms <[MAX], >>[MIN], [MIN]- and -[MAX] are also possible.
2.1. Complex Patterns
~s 'SPAM' ~U
-
The pattern above matches all messages that contain ``SPAM'' in the
subject and are unread.
(~b mutt-ng|~s Mutt-ng)
!~x '@synflood\.at'
-
The first pattern matches all messages that were sent by one of the
mutt-ng maintainers, while the seconds pattern matches all messages that
contain ``mutt-ng'' in the message body or ``Mutt-ng'' in the subject. The
~d 18/10/2004-2w
~d 28/12/2004*1d
-
The first pattern matches all dates between January 1st, 2005 and January
1st 2006. The second pattern matches all dates between October 18th, 2004
and October 4th 2004 (2 weeks before 18/10/2004), while the third pattern
~d <3d # messages newer than 3 days
~d =1m # messages that are exactly one month old
-
3. Format Strings
3.1. Introduction
set status_format = "%v on %h: ..."
-
mutt-ng will replace the sequence %v with the version string and %h with
the host's name. When you are, for example, running mutt-ng version 1.5.9i
on host mailhost, you'll see the following when you're in the index:
Mutt-ng 1.5.9i on mailhost: ...
-
In the index, there're more useful information one could want to see:
o which mailbox is open
set status_format = "%v on %h: %B: ...
-
When the currently opened mailbox is Inbox, this will be expanded to:
Mutt-ng 1.5.9i on mailhost: Inbox: ...
-
For the number of certain types of messages, one more feature of the
format strings is extremely useful. If there aren't messages of a certain
type, it may not be desired to print just that there aren't any but
set status_format = "%v on %h: %B %?n?%n new? ...
-
This feature is called nonzero-printing and works as this: some expandos
may be optionally printed nonzero, i.e. a portion of the format string is
only evaluated if the value of the expando is different from zero. The
%?<item>?<string if nonzero>?
-
which tells mutt-ng to only look at <string if nonzero> if the value of
the %<item%gt; expando is different from zero. In our example, we used n
as the expando to check for and %n new as the optional nonzero string.
%?<item>?<string if nonzero>&<string if zero>?
-
Using this we can make mutt-ng to do the following:
o make it print ``n new messages'' whereby n is the count but only if
set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ...
-
This doubles the use of the ``new messages'' string because it'll get
always printed. Thus, it can be shortened to:
set status_format = "%v on %h: %B: %?n?%n&no? new messages ...
-
As you might see from this rather simple example, one can create very
complex but fancy status messages. Please see the reference chapter for
expandos and those which may be printed nonzero.
set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-"
-
%>X
Since the previous expando stops at the end of line, there must be
set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)"
-
4. Using Tags
Sometimes it is desirable to perform an operation on a group of messages
send-hook . 'unmy_hdr From:'
send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
-
5.1. Message Matching in Hooks
Hooks that act upon messages (send-hook, save-hook, fcc-hook,message-hook
send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt-ng User <user@host>'
-
which would execute the given command when sending mail to me@cs.hmc.edu.
However, it is not required that you write the pattern to match using the
set sidebar_visible="yes"
set sidebar_width=25
-
If you want to specify the mailboxes you can do so with:
set mbox='=INBOX'
MBOX2 \
...
-
You can also specify the colors for mailboxes with new mails by using:
color sidebar_new red black
color sidebar white black
-
The available functions are:
Table 4.1. Default Sidebar Function Bindings
macro index B ':toggle sidebar_visible^M'
macro pager B ':toggle sidebar_visible^M'
-
You can then go up and down by pressing Ctrl-P and Ctrl-N, and switch on
and off the sidebar simply by pressing 'B'.
set query_command = "mutt_ldap_query.pl '%s'"
-
The wrapper script should accept the query on the command-line. It should
return a one line message, then each matching response on a single line,
each line containing a tab separated address then name thensome other
blong@fiction.net Brandon Long mutt and more
roessler@guug.de Thomas Roessler mutt pgp
-
There are two mechanisms for accessing the query function of mutt. One is
to do a query from the index menu using the query function (default: Q).
This will prompt for a query, then bring up the query menu which will list
From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
-
to denote the start of a new message (this is often referred to as the
``From_'' line).
score ~* =42
-
This tells mutt-ng to apply a score of 42 to all messages whose sender
specified a valid realname and a valid email address. Using
score !~* =42
-
on the contrary applies a score of 42 to all messages not matching those
criteria which are very strict:
account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'
account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
-
18. Start a WWW Browser on URLs (EXTERNAL)
If a message contains URLs (unified resource locator = address in the WWW
macro index \cb |urlview\n
macro pager \cb |urlview\n
-
19. Compressed folders Support (OPTIONAL)
If Mutt-ng was compiled with compressed folders support (by running the
close-hook \\.gz$ "gzip -c %t > %f"
append-hook \\.gz$ "gzip -c %t >> %f"
-
You do not have to specify all of the commands. If you omit append-hook
,the folder will be open and closed again each time you will add to it. If
you omit close-hook (or give empty command) , the folder will be open in
open-hook \\.gz$ "gzip -cd %f > %t"
-
If the command is empty, this operation is disabled for this file type.
19.2. Write a compressed mailbox
- Usage: close-hook regexp "command"
+ Usage: close-hook regexp"command"
This is used to close the folder that was open with the open-hook command
after some changes were made to it.
close-hook \\.gz$ "gzip -c %t > %f"
-
If the command is empty, this operation is disabled for this file type,
and the file can only be open in the readonly mode.
19.3. Append a message to a compressed mailbox
- Usage: append-hook regexp "command"
+ Usage: append-hook regexp"command"
This command is used for saving to an existing compressed folder. The
command is the command that can be used for appending to the folders whose
append-hook \\.gz$ "gzip -c %t >> %f"
-
When append-hook is used, the folder is not opened, which saves time, but
this means that we can not find out what the folder type is. Thus the
default ( mbox-type )type is always supposed (i.e. this is the format used
open-hook \\.pgp$ "pgp -f < %f > %t"
close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
-
Please note, that PGP does not support appending to an encrypted folder,
so there is no append-hook defined.
[-- Attachment #1: Description --]
[-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
-
Where the Description is the description or filename given for the
attachment, and the Encoding is one of
7bit/8bit/quoted-printable/base64/binary.
[-- image/gif is unsupported (use 'v' to view this part) --]
-
1.2. The Attachment Menu
The default binding for view-attachments is `v', which displays the
1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 <no description>
2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz <no description>
-
The '-' denotes that Mutt-ng will delete the file after sending (or
postponing, or canceling) the message. It can be toggled with the
toggle-unlink command (default: u). The next field is the MIME
application/pgp pgp
audio/x-aiff aif aifc aiff
-
A sample mime.types file comes with the Mutt-ng distribution, and should
contain most of the MIME types you are likely to use.
${HOME}/.mailcap:/usr/local/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap
-
where $HOME is your home directory.
In particular, the metamail distribution will install a mailcap file,
text/plain; more
-
Or, you could send the message as a file:
text/plain; more %s
-
Perhaps you would like to use lynx to interactively view a text/html
message:
text/html; lynx %s
-
In this case, lynx does not support viewing a file from stdin, so you must
use the %s syntax. Note: Some older versions of lynx contain a bug where
they will check the mailcap file for a viewer for text/html. They will
text/html; lynx -dump %s | more
-
Perhaps you wish to use lynx to view text/html files, and a pager on all
other text formats, then you would use the following:
text/html; lynx %s
text/*; more
-
This is the simplest form of a mailcap file.
3.2. Secure use of mailcap
text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
&& test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
-
3.3. Advanced mailcap Usage
3.3.1. Optional Fields
text/html; lynx -dump %s ; copiousoutput
-
This will cause lynx to format the text/html output as text/plain
and Mutt-ng will use your standard pager to display the results.
text/html; lynx %s; nametemplate=%s.html
-
test=<command>
This field specifies a command to run to test whether this mailcap
text/html; netscape -remote 'openURL(%s)' ; test=RunningX
text/html; lynx %s
-
In this example, Mutt-ng will run the program RunningX which will
return 0 if the X Window manager is running, and non-zero if it
isn't. If RunningX returns 0, then Mutt-ng will call netscape to
image/gif; ; print= anytopnm %s | pnmtops | lpr; \
nametemplate=%s.gif
-
Mutt-ng will skip the image/* entry and use the image/gif entry with the
print command.
text/html; lynx %s; nametemplate=%s.html
text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
-
For auto-view, Mutt-ng will choose the third entry because of the
copiousoutput tag. For interactive viewing, Mutt will run the program
RunningX to determine if it should use the first entry. If the program
Content-Type: text/plain; charset=iso-8859-1
-
then Mutt-ng will expand %{charset} to iso-8859-1. The default
metamail mailcap file uses this feature to test the charset to
spawn an xterm using the right charset to view the message.
# I'm always running netscape (if my computer had more memory, maybe)
text/html; netscape -remote 'openURL(%s)'
-
This mailcap file shows quite a number of examples:
# Use xanim to view all videos Xanim produces a header on startup,
# Send excel spreadsheets to my NT box
application/ms-excel; open.pl %s
-
4. MIME Autoview
In addition to explicitly telling Mutt-ng to view an attachment with
auto_view text/html application/x-gunzip application/postscript
image/gif application/x-tar-gz
-
Mutt-ng could use the following mailcap entries to automatically view
attachments of these types.
application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput
application/postscript; ps2ascii %s; copiousoutput
-
``unauto_view'' can be used to remove previous entries from the autoview
list. This can be used with message-hook to autoview messages based on
size, etc. ``unauto_view *'' will remove all previous entries.
alternative_order text/enriched text/plain text
application/postscript image/*
-
Next, mutt will check if any of the types have a defined auto-view, and
use that. Failing that, Mutt-ng will look for any text type. As a last
attempt, mutt willlook for any type it knows how to handle.
mime_lookup application/octet-stream application/X-Lotus-Manuscript
-
In addition, the unmime_lookup command may be used to disable this feature
for any particular mime-type if it had been set, for example, in a global
muttrc.
mailto:joe@host?Attach=~/.gnupg/secring.gpg
-
will send out the user's private gnupg keyring to joe@host if the user
doesn't follow the information on screen carefully enough.
| ~B | EXPR | messages which contain EXPR in the |
| | | whole message |
|------------------+-------------+---------------------------------------|
- | ~c | USER | messages carbon-copied to USER |
+ | ~c | EXPR | messages carbon-copied to EXPR |
|------------------+-------------+---------------------------------------|
| ~C | EXPR | message is either to: or cc: EXPR |
|------------------+-------------+---------------------------------------|
|------------------+-------------+---------------------------------------|
| ~F | | flagged messages |
|------------------+-------------+---------------------------------------|
- | ~f | USER | messages originating from USER |
+ | ~f | EXPR | messages originating from EXPR |
|------------------+-------------+---------------------------------------|
| ~g | | cryptographically signed messages |
|------------------+-------------+---------------------------------------|
|------------------+-------------+---------------------------------------|
| ~k | | message contains PGP key material |
|------------------+-------------+---------------------------------------|
- | ~i | ID | message which match ID in the |
+ | ~i | EXPR | message which match ID in the |
| | | ``Message-ID'' field |
|------------------+-------------+---------------------------------------|
| ~L | EXPR | message is either originated or |
|------------------+-------------+---------------------------------------|
| ~S | | superseded messages |
|------------------+-------------+---------------------------------------|
- | ~s | SUBJECT | messages having SUBJECT in the |
+ | ~s | EXPR | messages having EXPR in the |
| | | ``Subject'' field. |
|------------------+-------------+---------------------------------------|
| ~T | | tagged messages |
|------------------+-------------+---------------------------------------|
- | ~t | USER | messages addressed to USER |
+ | ~t | EXPR | messages addressed to EXPR |
|------------------+-------------+---------------------------------------|
| ~U | | unread messages |
|------------------+-------------+---------------------------------------|
+ | ~u | | message is addressed to a subscribed |
+ | | | mailing list |
+ |------------------+-------------+---------------------------------------|
| ~v | | message is part of a collapsed |
| | | thread. |
|------------------+-------------+---------------------------------------|
| | | against alternates or any alias) |
+------------------------------------------------------------------------+
- Where EXPR, USER, ID, and SUBJECT are regexp. Special attention has to be
- made when using regular expressions inside of patterns. Specifically,
- Mutt-ng's parser for these patterns will strip one level of backslash (\),
- which is normally used for quoting. If it is your intention to use a
- backslash in the regular expression, you will need to use two backslashes
- instead (\\).
+ Where EXPR are regexp. Special attention has to be made when using regular
+ expressions inside of patterns. Specifically, Mutt-ng's parser for these
+ patterns will strip one level of backslash (\), which is normally used for
+ quoting. If it is your intention to use a backslash in the regular
+ expression, you will need to use two backslashes instead (\\).
*) The forms <[MAX], >[MIN] , [MIN]- and -[MAX] are allowed, too.
Type: number
- Default: 0
+ Default: 1
Availability: debug
Type: system property
- Value: 475
+ Value: 503
This is a read-only system property and specifies muttng's subversion
revision string.
This variable, when set, makes the thread tree narrower, allowing deeper
threads to fit on the screen.
-160. nntp_ask_followup_to
+160. net_inc
+
+ Type: number
+
+ Default: 10
+
+ Operations that expect to transfer a large amount of data over the network
+ will update their progress every net_inc kilobytes. If set to 0, no
+ progress messages will be displayed.
+
+ See also ``$read_inc'' and ``$write_inc''.
+
+161. nntp_ask_followup_to
Type: boolean
If set, Mutt-ng will prompt you for the Followup-To: header field before
editing the body of an outgoing news article.
-161. nntp_ask_x_comment_to
+162. nntp_ask_x_comment_to
Type: boolean
If set, Mutt-ng will prompt you for the X-Comment-To: header field before
editing the body of an outgoing news article.
-162. nntp_cache_dir
+163. nntp_cache_dir
Type: path
As for the header caching in connection with IMAP and/or Maildir, this
drastically increases speed and lowers traffic.
-163. nntp_catchup
+164. nntp_catchup
Type: quadoption
If this variable is set, Mutt-ng will mark all articles in a newsgroup as
read when you leaving it.
-164. nntp_context
+165. nntp_context
Type: number
If there're more articles than defined with $nntp_context, all older ones
will be removed/not shown in the index.
-165. nntp_followup_to_poster
+166. nntp_followup_to_poster
Type: quadoption
Followup-To: header field, a follow-up to the newsgroup is not permitted.
The message will be mailed to the submitter of the message via mail.
-166. nntp_group_index_format
+167. nntp_group_index_format
Type: string
%|X pad to the end of the line with character "X"
-167. nntp_host
+168. nntp_host
Type: string
presents a security risk since the superuser of your machine may read it
regardless of the file's permissions.
-168. nntp_inews
+169. nntp_inews
Type: path
Example: set inews="/usr/local/bin/inews -hS"
-169. nntp_load_description
+170. nntp_load_description
Type: boolean
This variable controls whether or not descriptions for newsgroups are to
be loaded when subscribing to a newsgroup.
-170. nntp_mail_check
+171. nntp_mail_check
Type: number
new article will cause a recheck for new news. If set to 0, Mutt-ng will
recheck on each operation in index (stepping, read article, etc.).
-171. nntp_mime_subject
+172. nntp_mime_subject
Type: boolean
Note: Only change this setting if you know what you are doing.
-172. nntp_newsrc
+173. nntp_newsrc
Type: path
%s newsserver name
-173. nntp_pass
+174. nntp_pass
Type: string
since the superuser of your machine may read it regardless of the file's
permissions.
-174. nntp_post_moderated
+175. nntp_post_moderated
Type: quadoption
Note: if the newsserver does not support posting to that newsgroup or a
group is totally read-only, that posting will not have any effect.
-175. nntp_reconnect
+176. nntp_reconnect
Type: quadoption
Controls whether or not Mutt-ng will try to reconnect to a newsserver when
the was connection lost.
-176. nntp_save_unsubscribed
+177. nntp_save_unsubscribed
Type: boolean
When set, info about unsubscribed newsgroups will be saved into the
``newsrc'' file and into the news cache.
-177. nntp_show_new_news
+178. nntp_show_new_news
Type: boolean
controls whether or not the number of new articles of subscribed
newsgroups will be checked.
-178. nntp_show_only_unread
+179. nntp_show_only_unread
Type: boolean
If set, only subscribed newsgroups that contain unread articles will be
displayed in the newsgroup browser.
-179. nntp_user
+180. nntp_user
Type: string
Your login name on the NNTP server. If unset and the server requires
authentification, Mutt-ng will prompt you for your account name.
-180. nntp_x_comment_to
+181. nntp_x_comment_to
Type: boolean
full name of the original article author) to articles that you followup
to.
-181. operating_system
+182. operating_system
Type: string
It may, for example, look as: ``mutt-ng 1.5.9i (Linux)''.
-182. pager
+183. pager
Type: path
pager, and screen resizes cause lines longer than the screen width to be
badly formatted in the help menu.
-183. pager_context
+184. pager_context
Type: number
Mutt-ng will display the line after the last one on the screen at the top
of the next page (0 lines of context).
-184. pager_format
+185. pager_format
Type: string
displayed before each message in either the internal or an external pager.
The valid sequences are listed in the ``$index_format'' section.
-185. pager_index_lines
+186. pager_index_lines
Type: number
of messages in the current folder is less than pager_index_lines, then the
index will only use as many lines as it needs.
-186. pager_stop
+187. pager_stop
Type: boolean
When set, the internal-pager will not move to the next message when you
are at the end of a message and invoke the next-page function.
-187. pgp_auto_decode
+188. pgp_auto_decode
Type: boolean
checked with the check-traditional-pgp function, Mutt-ng will
automatically check the message for traditional pgp.
-188. pgp_autoinline
+189. pgp_autoinline
Type: boolean
Also note that using the old-style PGP message format is strongly
deprecated. (PGP only)
-189. pgp_check_exit
+190. pgp_check_exit
Type: boolean
signing or encrypting. A non-zero exit code means that the subprocess
failed. (PGP only)
-190. pgp_clearsign_command
+191. pgp_clearsign_command
Type: string
Note that the use of this format is strongly deprecated. (PGP only)
-191. pgp_decode_command
+192. pgp_decode_command
Type: string
samples/ subdirectory which has been installed on your system alongside
the documentation. (PGP only)
-192. pgp_decrypt_command
+193. pgp_decrypt_command
Type: string
This command is used to decrypt a PGP encrypted message. (PGP only)
-193. pgp_encrypt_only_command
+194. pgp_encrypt_only_command
Type: string
This command is used to encrypt a body part without signing it. (PGP only)
-194. pgp_encrypt_sign_command
+195. pgp_encrypt_sign_command
Type: string
This command is used to both sign and encrypt a body part. (PGP only)
-195. pgp_entry_format
+196. pgp_entry_format
Type: string
(PGP only)
-196. pgp_export_command
+197. pgp_export_command
Type: string
This command is used to export a public key from the user's key ring. (PGP
only)
-197. pgp_getkeys_command
+198. pgp_getkeys_command
Type: string
This command is invoked whenever Mutt-ng will need public key information.
%r is the only printf(3)-like sequence used with this format. (PGP only)
-198. pgp_good_sign
+199. pgp_good_sign
Type: regular expression
text. Use this variable if the exit code from the command is 0 even for
bad signatures. (PGP only)
-199. pgp_ignore_subkeys
+200. pgp_ignore_subkeys
Type: boolean
Instead, the principal key will inherit the subkeys' capabilities. Unset
this if you want to play interesting key selection games. (PGP only)
-200. pgp_import_command
+201. pgp_import_command
Type: string
This command is used to import a key from a message into the user's public
key ring. (PGP only)
-201. pgp_list_pubring_command
+202. pgp_list_pubring_command
Type: string
This format is also generated by the pgpring utility which comes with
Mutt-ng. (PGP only)
-202. pgp_list_secring_command
+203. pgp_list_secring_command
Type: string
This format is also generated by the pgpring utility which comes with
Mutt-ng. (PGP only)
-203. pgp_long_ids
+204. pgp_long_ids
Type: boolean
If set, use 64 bit PGP key IDs. Unset uses the normal 32 bit Key IDs. (PGP
only)
-204. pgp_mime_auto
+205. pgp_mime_auto
Type: quadoption
Also note that using the old-style PGP message format is strongly
deprecated. (PGP only)
-205. pgp_replyinline
+206. pgp_replyinline
Type: boolean
Also note that using the old-style PGP message format is strongly
deprecated. (PGP only)
-206. pgp_retainable_sigs
+207. pgp_retainable_sigs
Type: boolean
where the outer layer (multipart/encrypted) can be easily removed, while
the inner multipart/signed part is retained. (PGP only)
-207. pgp_show_unusable
+208. pgp_show_unusable
Type: boolean
menu. This includes keys which have been revoked, have expired, or have
been marked as ``disabled'' by the user. (PGP only)
-208. pgp_sign_as
+209. pgp_sign_as
Type: string
which of your private keys to use. It is recommended that you use the
keyid form to specify your key (e.g., ``0x00112233''). (PGP only)
-209. pgp_sign_command
+210. pgp_sign_command
Type: string
This command is used to create the detached PGP signature for a
multipart/signed PGP/MIME body part. (PGP only)
-210. pgp_sort_keys
+211. pgp_sort_keys
Type: sort order
If you prefer reverse order of the above values, prefix it with
``reverse-''. (PGP only)
-211. pgp_strict_enc
+212. pgp_strict_enc
Type: boolean
problems with non-verifyable PGP signatures, so only change this if you
know what you are doing. (PGP only)
-212. pgp_timeout
+213. pgp_timeout
Type: number
The number of seconds after which a cached passphrase will expire if not
used. Default: 300. (PGP only)
-213. pgp_use_gpg_agent
+214. pgp_use_gpg_agent
Type: boolean
If set, Mutt-ng will use a possibly-running gpg-agent process. (PGP only)
-214. pgp_verify_command
+215. pgp_verify_command
Type: string
This command is used to verify PGP signatures. (PGP only)
-215. pgp_verify_key_command
+216. pgp_verify_key_command
Type: string
This command is used to verify key information from the key selection
menu. (PGP only)
-216. pipe_decode
+217. pipe_decode
Type: boolean
pipe the messages without any preprocessing. When set, Mutt-ng will weed
headers and will attempt to PGP/MIME decode the messages first.
-217. pipe_sep
+218. pipe_sep
Type: string
The separator to add between messages when piping a list of tagged
messages to an external Unix command.
-218. pipe_split
+219. pipe_split
Type: boolean
by one. In both cases the messages are piped in the current sorted order,
and the ``$pipe_sep'' separator is added after each message.
-219. pop_auth_try_all
+220. pop_auth_try_all
Type: boolean
unavailable. If a method is available but authentication fails, Mutt-ng
will not connect to the POP server.
-220. pop_authenticators
+221. pop_authenticators
Type: string
Example: set pop_authenticators="digest-md5:apop:user"
-221. pop_delete
+222. pop_delete
Type: quadoption
server when using the ``fetch-mail'' function. When unset, Mutt-ng will
download messages but also leave them on the POP server.
-222. pop_host
+223. pop_host
Type: string
since the superuser of your machine may read it regardless of the file's
permissions.
-223. pop_last
+224. pop_last
Type: boolean
for retrieving only unread messages from the POP server when using the
``fetch-mail'' function.
-224. pop_mail_check
+225. pop_mail_check
Type: number
This variable configures how often (in seconds) POP should look for new
mail.
-225. pop_pass
+226. pop_pass
Type: string
since the superuser of your machine may read it regardless of the file's
permissions.
-226. pop_reconnect
+227. pop_reconnect
Type: quadoption
Controls whether or not Mutt-ng will try to reconnect to a POP server when
the connection is lost.
-227. pop_user
+228. pop_user
Type: string
This variable defaults to your user name on the local machine.
-228. post_indent_string
+229. post_indent_string
Type: string
Similar to the ``$attribution'' variable, Mutt-ng will append this string
after the inclusion of a message which is being replied to.
-229. postpone
+230. postpone
Type: quadoption
Controls whether or not messages are saved in the ``$postponed'' mailbox
when you elect not to send immediately.
-230. postponed
+231. postponed
Type: path
in the mailbox specified by this variable. Also see the ``$postpone''
variable.
-231. preconnect
+232. preconnect
Type: string
Note: For this example to work, you must be able to log in to the remote
machine without having to enter a password.
-232. print
+233. print
Type: quadoption
Controls whether or not Mutt-ng really prints messages. This is set to
ask-no by default, because some people accidentally hit ``p'' often.
-233. print_command
+234. print_command
Type: path
This specifies the command pipe that should be used to print messages.
-234. print_decode
+235. print_decode
Type: boolean
useful if you are using some advanced printer filter which is able to
properly format e-mail messages for printing.
-235. print_split
+236. print_split
Type: boolean
Those who use the enscript(1) program's mail-printing mode will most
likely want to set this option.
-236. prompt_after
+237. prompt_after
Type: boolean
returning to the index menu. If unset, Mutt-ng will return to the index
menu when the external pager exits.
-237. query_command
+238. query_command
Type: path
queries. The string should contain a %s, which will be substituted with
the query string the user types. See ``query'' for more information.
-238. quit
+239. quit
Type: quadoption
effect, and if it is set to ask-yes or ask-no, you are prompted for
confirmation when you try to quit.
-239. quote_empty
+240. quote_empty
Type: boolean
Controls whether or not empty lines will be quoted using
``indent_string''.
-240. quote_quoted
+241. quote_quoted
Type: boolean
be added to the end of existing prefix. Otherwise, quoted lines will be
prepended by ``indent_string''.
-241. quote_regexp
+242. quote_regexp
Type: regular expression
to set this to a regular expression that matches exactly the quote
characters at the beginning of quoted lines.
-242. read_inc
+243. read_inc
Type: number
Also see the ``$write_inc'' variable.
-243. read_only
+244. read_only
Type: boolean
If set, all folders are opened in read-only mode.
-244. realname
+245. realname
Type: string
Note: This variable will not be used when the user has set a real name in
the $from variable.
-245. recall
+246. recall
Type: quadoption
Setting this variable to yes is not generally useful, and thus not
recommended.
-246. record
+247. record
Type: path
The value of $record is overridden by the ``$force_name'' and
``$save_name'' variables, and the ``fcc-hook'' command.
-247. reply_regexp
+248. reply_regexp
Type: regular expression
replying. The default value corresponds to the English ``Re:'' and the
German ``Aw:''.
-248. reply_self
+249. reply_self
Type: boolean
assume that you want to reply to the recipients of that message rather
than to yourself.
-249. reply_to
+250. reply_to
Type: quadoption
``Reply-To:'' header field to the list address and you want to send a
private message to the author of a message.
-250. resolve
+251. resolve
Type: boolean
undeleted) message whenever a command that modifies the current message is
executed.
-251. reverse_alias
+252. reverse_alias
Type: boolean
``abd30425@somewhere.net.'' This is useful when the person's e-mail
address is not human friendly (like CompuServe addresses).
-252. reverse_name
+253. reverse_name
Type: boolean
is unset, or the address that would be used doesn't match your alternates,
the From: line will use your address on the current machine.
-253. reverse_realname
+254. reverse_realname
Type: boolean
possibly including eventual real names. When it is unset, Mutt-ng will
override any such real names with the setting of the realname variable.
-254. rfc2047_parameters
+255. rfc2047_parameters
Type: boolean
Mutt-ng generates this kind of encoding. Instead, Mutt-ng will
unconditionally use the encoding specified in RFC 2231.
-255. save_address
+256. save_address
Type: boolean
default folder for saving a mail. If ``$save_name'' or ``$force_name'' is
set too, the selection of the fcc folder will be changed as well.
-256. save_empty
+257. save_empty
Type: boolean
Note: This only applies to mbox and MMDF folders, Mutt-ng does not delete
MH and Maildir directories.
-257. save_name
+258. save_name
Type: boolean
Also see the ``$force_name'' variable.
-258. score
+259. score
Type: boolean
selectively disable scoring for certain folders when the
``$score_threshold_delete'' variable and friends are used.
-259. score_threshold_delete
+260. score_threshold_delete
Type: number
Mutt-ng scores are always greater than or equal to zero, the default
setting of this variable will never mark a message for deletion.
-260. score_threshold_flag
+261. score_threshold_flag
Type: number
Messages which have been assigned a score greater than or equal to this
variable's value are automatically marked ``flagged''.
-261. score_threshold_read
+262. score_threshold_read
Type: number
Mutt-ng scores are always greater than or equal to zero, the default
setting of this variable will never mark a message read.
-262. send_charset
+263. send_charset
Type: string
character set (such as iso-8859-2, koi8-r or iso-2022-jp) either instead
of or after iso-8859-1.
-263. sendmail
+264. sendmail
Type: path
Mutt-ng expects that the specified program interprets additional arguments
as recipient addresses.
-264. sendmail_wait
+265. sendmail_wait
Type: number
process will be put in a temporary file. If there is some error, you will
be informed as to where to find the output.
-265. shell
+266. shell
Type: path
Command to use when spawning a subshell. By default, the user's login
shell from /etc/passwd is used.
-266. sidebar_boundary
+267. sidebar_boundary
Type: string
variable specifies the characters at which to split a folder name into
``hierarchy items.''
-267. sidebar_delim
+268. sidebar_delim
Type: string
This specifies the delimiter between the sidebar (if visible) and other
screens.
-268. sidebar_newmail_only
+269. sidebar_newmail_only
Type: boolean
If set, only folders with new mail will be shown in the sidebar.
-269. sidebar_number_format
+270. sidebar_number_format
Type: string
1) These expandos only have a non-zero value for the current mailbox and
will always be zero otherwise.
-270. sidebar_shorten_hierarchy
+271. sidebar_shorten_hierarchy
Type: boolean
At which characters this compression is done is controled via the
$sidebar_boundary variable.
-271. sidebar_visible
+272. sidebar_visible
Type: boolean
This specifies whether or not to show the sidebar (a list of folders
specified with the ``mailboxes'' command).
-272. sidebar_width
+273. sidebar_width
Type: number
The width of the sidebar.
-273. sig_dashes
+274. sig_dashes
Type: boolean
For example, Mutt-ng has the ability to highlight the signature in a
different color in the builtin pager.
-274. sig_on_top
+275. sig_on_top
Type: boolean
you really know what you are doing, and are prepared to take some heat
from netiquette guardians.
-275. signature
+276. signature
Type: path
outgoing messages. If the filename ends with a pipe (``|''), it is assumed
that filename is a shell command and input should be read from its stdout.
-276. signoff_string
+277. signoff_string
Type: string
or witty quotes into your mails, better use a signature file instead of
the signoff string.
-277. simple_search
+278. simple_search
Type: string
Ëœf joe | Ëœs joe
-278. sleep_time
+279. sleep_time
Type: number
expunging messages from the current folder. The default is to pause one
second, so a value of zero for this option suppresses the pause.
-279. smart_wrap
+280. smart_wrap
Type: boolean
pager. If set, long lines are wrapped at a word boundary. If unset, lines
are simply wrapped at the screen edge. Also see the ``$markers'' variable.
-280. smileys
+281. smileys
Type: regular expression
The pager uses this variable to catch some common false positives of
``$quote_regexp'', most notably smileys in the beginning of a line
-281. smime_ask_cert_label
+282. smime_ask_cert_label
Type: boolean
certificate about to be added to the database or not. It is set by
default. (S/MIME only)
-282. smime_ca_location
+283. smime_ca_location
Type: path
This variable contains the name of either a directory, or a file which
contains trusted certificates for use with OpenSSL. (S/MIME only)
-283. smime_certificates
+284. smime_certificates
Type: path
contains mailbox-address keyid pairs, and which can be manually edited.
This one points to the location of the certificates. (S/MIME only)
-284. smime_decrypt_command
+285. smime_decrypt_command
Type: string
samples/ subdirectory which has been installed on your system alongside
the documentation. (S/MIME only)
-285. smime_decrypt_use_default_key
+286. smime_decrypt_use_default_key
Type: boolean
use the mailbox-address to determine the key to use. It will ask you to
supply a key, if it can't find one. (S/MIME only)
-286. smime_default_key
+287. smime_default_key
Type: string
keyid (the hash-value that OpenSSL generates) to work properly (S/MIME
only)
-287. smime_encrypt_command
+288. smime_encrypt_command
Type: string
This command is used to create encrypted S/MIME messages. (S/MIME only)
-288. smime_encrypt_with
+289. smime_encrypt_with
Type: string
If unset ``3des'' (TripleDES) is used. (S/MIME only)
-289. smime_get_cert_command
+290. smime_get_cert_command
Type: string
This command is used to extract X509 certificates from a PKCS7 structure.
(S/MIME only)
-290. smime_get_cert_email_command
+291. smime_get_cert_email_command
Type: string
certificates, and for verification purposes (to check whether the
certificate was issued for the sender's mailbox). (S/MIME only)
-291. smime_get_signer_cert_command
+292. smime_get_signer_cert_command
Type: string
S/MIME signature, so that the certificate's owner may get compared to the
email's ``From:'' header field. (S/MIME only)
-292. smime_import_cert_command
+293. smime_import_cert_command
Type: string
This command is used to import a certificate via smime_keysng. (S/MIME
only)
-293. smime_is_default
+294. smime_is_default
Type: boolean
(Note that this variable can be overridden by unsetting $crypt_autosmime.)
(S/MIME only)
-294. smime_keys
+295. smime_keys
Type: path
which contains mailbox-address keyid pair, and which can be manually
edited. This one points to the location of the private keys. (S/MIME only)
-295. smime_pk7out_command
+296. smime_pk7out_command
Type: string
This command is used to extract PKCS7 structures of S/MIME signatures, in
order to extract the public X509 certificate(s). (S/MIME only)
-296. smime_sign_command
+297. smime_sign_command
Type: string
This command is used to created S/MIME signatures of type
multipart/signed, which can be read by all mail clients. (S/MIME only)
-297. smime_sign_opaque_command
+298. smime_sign_opaque_command
Type: string
application/x-pkcs7-signature, which can only be handled by mail clients
supporting the S/MIME extension. (S/MIME only)
-298. smime_timeout
+299. smime_timeout
Type: number
The number of seconds after which a cached passphrase will expire if not
used. (S/MIME only)
-299. smime_verify_command
+300. smime_verify_command
Type: string
This command is used to verify S/MIME signatures of type multipart/signed.
(S/MIME only)
-300. smime_verify_opaque_command
+301. smime_verify_opaque_command
Type: string
This command is used to verify S/MIME signatures of type
application/x-pkcs7-mime. (S/MIME only)
-301. smtp_envelope
+302. smtp_envelope
Type: string
as the envelope sender but only a particular one which may not be the same
as the user's desired From: header.
-302. smtp_host
+303. smtp_host
Type: string
invoking the sendmail binary. Setting this variable overrides the value of
``$sendmail'', and any associated variables.
-303. smtp_pass
+304. smtp_pass
Type: string
since the superuser of your machine may read it regardless of the file's
permissions.
-304. smtp_port
+305. smtp_port
Type: number
Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP
servers will probably desire 587, the mail submission port.
-305. smtp_use_tls
+306. smtp_use_tls
Type: string
to start TLS and continue without TLS in case of an error. Muttng still
needs to have SSL support enabled in order to use it.
-306. smtp_user
+307. smtp_user
Type: string
Defines the username to use with SMTP AUTH. Setting this variable will
cause Mutt-ng to attempt to use SMTP AUTH when sending.
-307. sort
+308. sort
Type: sort order
You may optionally use the ``reverse-'' prefix to specify reverse sorting
order (example: set sort=reverse-date-sent).
-308. sort_alias
+309. sort_alias
Type: sort order
unsorted (leave in order specified in .muttrc)
-309. sort_aux
+310. sort_aux
Type: sort order
not the right thing to do, but kept to not break any existing
configuration setting).
-310. sort_browser
+311. sort_browser
Type: sort order
You may optionally use the ``reverse-'' prefix to specify reverse sorting
order (example: set sort_browser=reverse-date).
-311. sort_re
+312. sort_re
Type: boolean
whether or not this is the case, as long as the non-``$reply_regexp''
parts of both messages are identical.
-312. spam_separator
+313. spam_separator
Type: string
matches value for the spam label. If set, each successive match will
append to the previous, using ``spam_separator'' as a separator.
-313. spoolfile
+314. spoolfile
Type: path
automatically set this variable to the value of the environment variable
$MAIL if it is not set.
-314. ssl_ca_certificates_file
+315. ssl_ca_certificates_file
Type: path
Example: set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
-315. ssl_client_cert
+316. ssl_client_cert
Type: path
The file containing a client certificate and its associated private key.
-316. ssl_force_tls
+317. ssl_force_tls
Type: boolean
otherwise have to abort the connection anyway. This option supersedes
``$ssl_starttls''.
-317. ssl_min_dh_prime_bits
+318. ssl_min_dh_prime_bits
Type: number
use in any Diffie-Hellman key exchange. A value of 0 will use the default
from the GNUTLS library.
-318. ssl_starttls
+319. ssl_starttls
Type: quadoption
advertising the capability. When unset, Mutt-ng will not attempt to use
STARTTLS regardless of the server's capabilities.
-319. ssl_use_sslv2
+320. ssl_use_sslv2
Type: boolean
This variables specifies whether to attempt to use SSLv2 in the SSL
authentication process.
-320. ssl_use_sslv3
+321. ssl_use_sslv3
Type: boolean
This variables specifies whether to attempt to use SSLv3 in the SSL
authentication process.
-321. ssl_use_tlsv1
+322. ssl_use_tlsv1
Type: boolean
This variables specifies whether to attempt to use TLSv1 in the SSL
authentication process.
-322. ssl_usesystemcerts
+323. ssl_usesystemcerts
Type: boolean
certificate store when checking if server certificate is signed by a
trusted CA.
-323. status_chars
+324. status_chars
Type: string
(Certain operations like composing a new mail, replying, forwarding, etc.
are not permitted in this mode).
-324. status_format
+325. status_format
Type: string
will replace any dots in the expansion by underscores. This might be
helpful with IMAP folders that don't like dots in folder names.
-325. status_on_top
+326. status_on_top
Type: boolean
Setting this variable causes the ``status bar'' to be displayed on the
first line of the screen rather than near the bottom.
-326. strict_mailto
+327. strict_mailto
Type: boolean
``X-Mailto-'' and the message including headers will be shown in the
editor regardless of what ``$edit_headers'' is set to.
-327. strict_mime
+328. strict_mime
Type: boolean
*text to a single space to prevent the display of MIME-encoded
``Subject:'' header field from being devided into multiple lines.
-328. strict_threads
+329. strict_threads
Type: boolean
default, messages with the same subject are grouped together in ``pseudo
threads.'' This may not always be desirable, such as in a personal mailbox
where you might have several unrelated messages with the subject ``hi''
- which will get grouped together.
+ which will get grouped together. See also ``$sort_re'' for a less drastic
+ way of controlling this behaviour.
-329. strip_was
+330. strip_was
Type: boolean
which matches $strip_was_regex when replying. This is useful to properly
react on subject changes and reduce ``subject noise.'' (esp. in Usenet)
-330. strip_was_regex
+331. strip_was_regex
Type: regular expression
part of the ``Subject'' line when replying if it won't be empty
afterwards.
-331. stuff_quoted
+332. stuff_quoted
Type: boolean
``stuffed'', i.e. a space will be inserted between the quote characters
and the actual text.
-332. suspend
+333. suspend
Type: boolean
key, usually CTRL+Z. This is useful if you run Mutt-ng inside an xterm
using a command like ``xterm -e muttng.''
-333. text_flowed
+334. text_flowed
Type: boolean
Note that $indent_string is ignored when this option is set.
-334. thorough_search
+335. thorough_search
Type: boolean
searched are decoded before searching. If unset, messages are searched as
they appear in the folder.
-335. thread_received
+336. thread_received
Type: boolean
When set, Mutt-ng uses the date received rather than the date sent to
thread messages by subject.
-336. tilde
+337. tilde
Type: boolean
When set, the internal-pager will pad blank lines to the bottom of the
screen with a tilde (˜).
-337. timeout
+338. timeout
Type: number
to be pressed in the main menu before timing out and checking for new
mail. A value of zero or less will cause Mutt-ng to never time out.
-338. tmpdir
+339. tmpdir
Type: path
not set, the environment variable $TMPDIR is used. If $TMPDIR is not set
then "/tmp" is used.
-339. to_chars
+340. to_chars
Type: string
character is used to indicate when a mail was sent to a mailing-list
you're subscribe to (default: L).
-340. trash
+341. trash
Type: path
Note: When you delete a message in the trash folder, it is really deleted,
so that there is no way to recover mail.
-341. tunnel
+342. tunnel
Type: string
Note: For this example to work you must be able to log in to the remote
machine without having to enter a password.
-342. umask
+343. umask
Type: number
This sets the umask that will be used by Mutt-ng when creating all kinds
of files. If unset, the default value is 077.
-343. uncollapse_jump
+344. uncollapse_jump
Type: boolean
When set, Mutt-ng will jump to the next unread message, if any, when the
current thread is uncollapsed.
-344. use_8bitmime
+345. use_8bitmime
Type: boolean
flag when sending 8-bit messages to enable ESMTP negotiation or tell
libESMTP to do so.
-345. use_domain
+346. use_domain
Type: boolean
portion) with the value of ``$hostname''. If unset, no addresses will be
qualified.
-346. use_from
+347. use_from
Type: boolean
messages. If unset, no ``From:'' header field will be generated unless the
user explicitly sets one using the ``my_hdr'' command.
-347. use_idn
+348. use_idn
Type: boolean
Note: You can use IDNs for addresses even if this is unset. This variable
only affects decoding.
-348. use_ipv6
+349. use_ipv6
Type: boolean
contact. If this option is unset, Mutt-ng will restrict itself to IPv4
addresses. Normally, the default should work.
-349. visual
+350. visual
Type: path
Specifies the visual editor to invoke when the Ëœv command is given in the
builtin editor.
-350. wait_key
+351. wait_key
Type: boolean
When set, Mutt-ng will always ask for a key. When unset, Mutt-ng will wait
for a key only if the external command returned a non-zero status.
-351. weed
+352. weed
Type: boolean
When set, Mutt-ng will weed headers when displaying, forwarding, printing,
or replying to messages.
-352. wrap_search
+353. wrap_search
Type: boolean
When set, searches will wrap around the first (or last) message. When
unset, searches will not wrap.
-353. wrapmargin
+354. wrapmargin
Type: number
Controls the size of the margin remaining at the right side of the
terminal when Mutt-ng's pager does smart wrapping.
-354. write_bcc
+355. write_bcc
Type: boolean
Controls whether Mutt-ng writes out the Bcc header when preparing messages
to be sent. Exim users may wish to unset this.
-355. write_inc
+356. write_inc
Type: number
Also see the ``$read_inc'' variable.
-356. xterm_icon
+357. xterm_icon
Type: string
set. This string is identical in formatting to the one used by
``$status_format''.
-357. xterm_leave
+358. xterm_leave
Type: string
set xterm_leave = "`test x$DISPLAY != x && xprop -id $WINDOWID | grep
WM_NAME | cut -d '"' -f 2`"
-358. xterm_set_titles
+359. xterm_set_titles
Type: boolean
as you're in an appropriate terminal). The default must be unset to force
in the validity checking.
-359. xterm_title
+360. xterm_title
Type: string
list
mail m compose a new mail message
mail-key ESC k mail a PGP public key
- next-new TAB jump to the next new message
+ next-new not bound jump to the next new message
+ next-new-then-unread TAB jump to the next new or unread message
next-subthread ESC n jump to the next subthread
next-thread ^N jump to the next thread
next-undeleted j move to the next undeleted message
parent-message P jump to parent message in thread
pipe-message | pipe message/attachment to a shell
command
- previous-new ESC TAB jump to the previous new message
+ previous-new not bound jump to the previous new message
+ previous-new-then-unread
+ ESC TAB jump to the previous new or unread message
+
previous-page Z move to the previous page
previous-subthread ESC p jump to previous subthread
previous-thread ^P jump to previous thread
mark-as-new N toggle a message's 'new' flag
next-line RET scroll down one line
next-entry J move to the next entry
- next-new TAB jump to the next new message
+ next-new not bound jump to the next new message
+ next-new-then-unread TAB jump to the next new or unread message
next-page move to the next page
next-subthread ESC n jump to the next subthread
next-thread ^N jump to the next thread
previous-line BackSpace scroll up one line
previous-entry K move to the previous entry
previous-new not bound jump to the previous new message
+ previous-new-then-unread
+ not bound jump to the previous new or unread message
previous-page - move to the previous page
previous-subthread ESC p jump to previous subthread
previous-thread ^P jump to previous thread
o Andreas Kneib <akneib@gmx.net>
o Carsten Schoelzki <cjs@weisshuhn.de>
o Elimar Riesebieter <riesebie@lxtec.de>
+
+Index
+
+ C
+
+ Configuration Variables
+
+ abort_noattach, abort_noattach
+
+ abort_nosubject, abort_nosubject
+
+ abort_unmodified, abort_unmodified
+
+ agent_string, agent_string
+
+ alias_file, alias_file
+
+ alias_format, alias_format
+
+ allow_8bit, allow_8bit
+
+ allow_ansi, allow_ansi
+
+ arrow_cursor, arrow_cursor
+
+ ascii_chars, ascii_chars
+
+ askbcc, askbcc
+
+ askcc, askcc
+
+ assumed_charset, assumed_charset
+
+ attach_format, attach_format
+
+ attach_remind_regexp, attach_remind_regexp
+
+ attach_sep, attach_sep
+
+ attach_split, attach_split
+
+ attribution, attribution
+
+ autoedit, autoedit
+
+ auto_tag, auto_tag
+
+ beep, beep
+
+ beep_new, beep_new
+
+ bounce, bounce
+
+ bounce_delivered, bounce_delivered
+
+ braille_friendly, braille_friendly
+
+ certificate_file, certificate_file
+
+ charset, charset
+
+ check_new, check_new
+
+ collapse_unread, collapse_unread
+
+ compose_format, compose_format
+
+ config_charset, config_charset
+
+ confirmappend, confirmappend
+
+ confirmcreate, confirmcreate
+
+ connect_timeout, connect_timeout
+
+ content_type, content_type
+
+ copy, copy
+
+ crypt_autoencrypt, crypt_autoencrypt
+
+ crypt_autopgp, crypt_autopgp
+
+ crypt_autosign, crypt_autosign
+
+ crypt_autosmime, crypt_autosmime
+
+ crypt_replyencrypt, crypt_replyencrypt
+
+ crypt_replysign, crypt_replysign
+
+ crypt_replysignencrypted, crypt_replysignencrypted
+
+ crypt_timestamp, crypt_timestamp
+
+ crypt_use_gpgme, crypt_use_gpgme
+
+ crypt_verify_sig, crypt_verify_sig
+
+ date_format, date_format
+
+ debug_level, debug_level
+
+ default_hook, default_hook
+
+ delete, delete
+
+ delete_space, delete_space
+
+ delete_untag, delete_untag
+
+ digest_collapse, digest_collapse
+
+ display_filter, display_filter
+
+ dotlock_program, dotlock_program
+
+ dsn_notify, dsn_notify
+
+ dsn_return, dsn_return
+
+ duplicate_threads, duplicate_threads
+
+ editor, editor
+
+ editor_headers, editor_headers
+
+ edit_headers, edit_headers
+
+ encode_from, encode_from
+
+ entropy_file, entropy_file
+
+ envelope_from, envelope_from
+
+ escape, escape
+
+ fast_reply, fast_reply
+
+ fcc_attach, fcc_attach
+
+ fcc_clear, fcc_clear
+
+ file_charset, file_charset
+
+ folder, folder
+
+ folder_format, folder_format
+
+ followup_to, followup_to
+
+ force_buffy_check, force_buffy_check
+
+ force_name, force_name
+
+ forward_decode, forward_decode
+
+ forward_decrypt, forward_decrypt
+
+ forward_edit, forward_edit
+
+ forward_format, forward_format
+
+ forward_quote, forward_quote
+
+ from, from
+
+ gecos_mask, gecos_mask
+
+ hdrs, hdrs
+
+ header, header
+
+ header_cache, header_cache
+
+ header_cache_compress, header_cache_compress
+
+ help, help
+
+ hidden_host, hidden_host
+
+ hide_limited, hide_limited
+
+ hide_missing, hide_missing
+
+ hide_thread_subject, hide_thread_subject
+
+ hide_top_limited, hide_top_limited
+
+ hide_top_missing, hide_top_missing
+
+ history, history
+
+ honor_followup_to, honor_followup_to
+
+ hostname, hostname
+
+ ignore_list_reply_to, ignore_list_reply_to
+
+ imap_authenticators, imap_authenticators
+
+ imap_check_subscribed, imap_check_subscribed
+
+ imap_delim_chars, imap_delim_chars
+
+ imap_headers, imap_headers
+
+ imap_home_namespace, imap_home_namespace
+
+ imap_keepalive, imap_keepalive
+
+ imap_list_subscribed, imap_list_subscribed
+
+ imap_login, imap_login
+
+ imap_mail_check, imap_mail_check
+
+ imap_pass, imap_pass
+
+ imap_passive, imap_passive
+
+ imap_peek, imap_peek
+
+ imap_reconnect, imap_reconnect
+
+ imap_servernoise, imap_servernoise
+
+ imap_user, imap_user
+
+ implicit_autoview, implicit_autoview
+
+ include, include
+
+ include_onlyfirst, include_onlyfirst
+
+ indent_string, indent_string
+
+ index_format, index_format
+
+ ispell, ispell
+
+ keep_flagged, keep_flagged
+
+ list_reply, list_reply
+
+ locale, locale
+
+ mailcap_path, mailcap_path
+
+ mailcap_sanitize, mailcap_sanitize
+
+ maildir_header_cache_verify, maildir_header_cache_verify
+
+ maildir_trash, maildir_trash
+
+ mail_check, mail_check
+
+ markers, markers
+
+ mark_old, mark_old
+
+ mask, mask
+
+ max_display_recips, max_display_recips
+
+ max_line_length, max_line_length
+
+ mbox, mbox
+
+ mbox_type, mbox_type
+
+ menu_context, menu_context
+
+ menu_move_off, menu_move_off
+
+ menu_scroll, menu_scroll
+
+ message_format, message_format
+
+ meta_key, meta_key
+
+ metoo, metoo
+
+ mh_purge, mh_purge
+
+ mh_seq_flagged, mh_seq_flagged
+
+ mh_seq_replied, mh_seq_replied
+
+ mh_seq_unseen, mh_seq_unseen
+
+ mime_forward, mime_forward
+
+ mime_forward_decode, mime_forward_decode
+
+ mime_forward_rest, mime_forward_rest
+
+ mixmaster, mixmaster
+
+ mix_entry_format, mix_entry_format
+
+ move, move
+
+ msgid_format, msgid_format
+
+ muttng_bindir, muttng_bindir
+
+ muttng_docdir, muttng_docdir
+
+ muttng_folder_name, muttng_folder_name
+
+ muttng_folder_path, muttng_folder_path
+
+ muttng_hcache_backend, muttng_hcache_backend
+
+ muttng_pwd, muttng_pwd
+
+ muttng_revision, muttng_revision
+
+ muttng_sysconfdir, muttng_sysconfdir
+
+ muttng_version, muttng_version
+
+ narrow_tree, narrow_tree
+
+ net_inc, net_inc
+
+ nntp_ask_followup_to, nntp_ask_followup_to
+
+ nntp_ask_x_comment_to, nntp_ask_x_comment_to
+
+ nntp_cache_dir, nntp_cache_dir
+
+ nntp_catchup, nntp_catchup
+
+ nntp_context, nntp_context
+
+ nntp_followup_to_poster, nntp_followup_to_poster
+
+ nntp_group_index_format, nntp_group_index_format
+
+ nntp_host, nntp_host
+
+ nntp_inews, nntp_inews
+
+ nntp_load_description, nntp_load_description
+
+ nntp_mail_check, nntp_mail_check
+
+ nntp_mime_subject, nntp_mime_subject
+
+ nntp_newsrc, nntp_newsrc
+
+ nntp_pass, nntp_pass
+
+ nntp_post_moderated, nntp_post_moderated
+
+ nntp_reconnect, nntp_reconnect
+
+ nntp_save_unsubscribed, nntp_save_unsubscribed
+
+ nntp_show_new_news, nntp_show_new_news
+
+ nntp_show_only_unread, nntp_show_only_unread
+
+ nntp_user, nntp_user
+
+ nntp_x_comment_to, nntp_x_comment_to
+
+ operating_system, operating_system
+
+ pager, pager
+
+ pager_context, pager_context
+
+ pager_format, pager_format
+
+ pager_index_lines, pager_index_lines
+
+ pager_stop, pager_stop
+
+ pgp_autoinline, pgp_autoinline
+
+ pgp_auto_decode, pgp_auto_decode
+
+ pgp_check_exit, pgp_check_exit
+
+ pgp_clearsign_command, pgp_clearsign_command
+
+ pgp_decode_command, pgp_decode_command
+
+ pgp_decrypt_command, pgp_decrypt_command
+
+ pgp_encrypt_only_command, pgp_encrypt_only_command
+
+ pgp_encrypt_sign_command, pgp_encrypt_sign_command
+
+ pgp_entry_format, pgp_entry_format
+
+ pgp_export_command, pgp_export_command
+
+ pgp_getkeys_command, pgp_getkeys_command
+
+ pgp_good_sign, pgp_good_sign
+
+ pgp_ignore_subkeys, pgp_ignore_subkeys
+
+ pgp_import_command, pgp_import_command
+
+ pgp_list_pubring_command, pgp_list_pubring_command
+
+ pgp_list_secring_command, pgp_list_secring_command
+
+ pgp_long_ids, pgp_long_ids
+
+ pgp_mime_auto, pgp_mime_auto
+
+ pgp_replyinline, pgp_replyinline
+
+ pgp_retainable_sigs, pgp_retainable_sigs
+
+ pgp_show_unusable, pgp_show_unusable
+
+ pgp_sign_as, pgp_sign_as
+
+ pgp_sign_command, pgp_sign_command
+
+ pgp_sort_keys, pgp_sort_keys
+
+ pgp_strict_enc, pgp_strict_enc
+
+ pgp_timeout, pgp_timeout
+
+ pgp_use_gpg_agent, pgp_use_gpg_agent
+
+ pgp_verify_command, pgp_verify_command
+
+ pgp_verify_key_command, pgp_verify_key_command
+
+ pipe_decode, pipe_decode
+
+ pipe_sep, pipe_sep
+
+ pipe_split, pipe_split
+
+ pop_authenticators, pop_authenticators
+
+ pop_auth_try_all, pop_auth_try_all
+
+ pop_delete, pop_delete
+
+ pop_host, pop_host
+
+ pop_last, pop_last
+
+ pop_mail_check, pop_mail_check
+
+ pop_pass, pop_pass
+
+ pop_reconnect, pop_reconnect
+
+ pop_user, pop_user
+
+ postpone, postpone
+
+ postponed, postponed
+
+ post_indent_string, post_indent_string
+
+ preconnect, preconnect
+
+ print, print
+
+ print_command, print_command
+
+ print_decode, print_decode
+
+ print_split, print_split
+
+ prompt_after, prompt_after
+
+ query_command, query_command
+
+ quit, quit
+
+ quote_empty, quote_empty
+
+ quote_quoted, quote_quoted
+
+ quote_regexp, quote_regexp
+
+ read_inc, read_inc
+
+ read_only, read_only
+
+ realname, realname
+
+ recall, recall
+
+ record, record
+
+ reply_regexp, reply_regexp
+
+ reply_self, reply_self
+
+ reply_to, reply_to
+
+ resolve, resolve
+
+ reverse_alias, reverse_alias
+
+ reverse_name, reverse_name
+
+ reverse_realname, reverse_realname
+
+ rfc2047_parameters, rfc2047_parameters
+
+ save_address, save_address
+
+ save_empty, save_empty
+
+ save_name, save_name
+
+ score, score
+
+ score_threshold_delete, score_threshold_delete
+
+ score_threshold_flag, score_threshold_flag
+
+ score_threshold_read, score_threshold_read
+
+ sendmail, sendmail
+
+ sendmail_wait, sendmail_wait
+
+ send_charset, send_charset
+
+ shell, shell
+
+ sidebar_boundary, sidebar_boundary
+
+ sidebar_delim, sidebar_delim
+
+ sidebar_newmail_only, sidebar_newmail_only
+
+ sidebar_number_format, sidebar_number_format
+
+ sidebar_shorten_hierarchy, sidebar_shorten_hierarchy
+
+ sidebar_visible, sidebar_visible
+
+ sidebar_width, sidebar_width
+
+ signature, signature
+
+ signoff_string, signoff_string
+
+ sig_dashes, sig_dashes
+
+ sig_on_top, sig_on_top
+
+ simple_search, simple_search
+
+ sleep_time, sleep_time
+
+ smart_wrap, smart_wrap
+
+ smileys, smileys
+
+ smime_ask_cert_label, smime_ask_cert_label
+
+ smime_ca_location, smime_ca_location
+
+ smime_certificates, smime_certificates
+
+ smime_decrypt_command, smime_decrypt_command
+
+ smime_decrypt_use_default_key, smime_decrypt_use_default_key
+
+ smime_default_key, smime_default_key
+
+ smime_encrypt_command, smime_encrypt_command
+
+ smime_encrypt_with, smime_encrypt_with
+
+ smime_get_cert_command, smime_get_cert_command
+
+ smime_get_cert_email_command, smime_get_cert_email_command
+
+ smime_get_signer_cert_command, smime_get_signer_cert_command
+
+ smime_import_cert_command, smime_import_cert_command
+
+ smime_is_default, smime_is_default
+
+ smime_keys, smime_keys
+
+ smime_pk7out_command, smime_pk7out_command
+
+ smime_sign_command, smime_sign_command
+
+ smime_sign_opaque_command, smime_sign_opaque_command
+
+ smime_timeout, smime_timeout
+
+ smime_verify_command, smime_verify_command
+
+ smime_verify_opaque_command, smime_verify_opaque_command
+
+ smtp_envelope, smtp_envelope
+
+ smtp_host, smtp_host
+
+ smtp_pass, smtp_pass
+
+ smtp_port, smtp_port
+
+ smtp_user, smtp_user
+
+ smtp_use_tls, smtp_use_tls
+
+ sort, sort
+
+ sort_alias, sort_alias
+
+ sort_aux, sort_aux
+
+ sort_browser, sort_browser
+
+ sort_re, sort_re
+
+ spam_separator, spam_separator
+
+ spoolfile, spoolfile
+
+ ssl_ca_certificates_file, ssl_ca_certificates_file
+
+ ssl_client_cert, ssl_client_cert
+
+ ssl_force_tls, ssl_force_tls
+
+ ssl_min_dh_prime_bits, ssl_min_dh_prime_bits
+
+ ssl_starttls, ssl_starttls
+
+ ssl_usesystemcerts, ssl_usesystemcerts
+
+ ssl_use_sslv2, ssl_use_sslv2
+
+ ssl_use_sslv3, ssl_use_sslv3
+
+ ssl_use_tlsv1, ssl_use_tlsv1
+
+ status_chars, status_chars
+
+ status_format, status_format
+
+ status_on_top, status_on_top
+
+ strict_mailto, strict_mailto
+
+ strict_mime, strict_mime
+
+ strict_threads, strict_threads
+
+ strip_was, strip_was
+
+ strip_was_regex, strip_was_regex
+
+ stuff_quoted, stuff_quoted
+
+ suspend, suspend
+
+ text_flowed, text_flowed
+
+ thorough_search, thorough_search
+
+ thread_received, thread_received
+
+ tilde, tilde
+
+ timeout, timeout
+
+ tmpdir, tmpdir
+
+ to_chars, to_chars
+
+ trash, trash
+
+ tunnel, tunnel
+
+ umask, umask
+
+ uncollapse_jump, uncollapse_jump
+
+ use_8bitmime, use_8bitmime
+
+ use_domain, use_domain
+
+ use_from, use_from
+
+ use_idn, use_idn
+
+ use_ipv6, use_ipv6
+
+ visual, visual
+
+ wait_key, wait_key
+
+ weed, weed
+
+ wrapmargin, wrapmargin
+
+ wrap_search, wrap_search
+
+ write_bcc, write_bcc
+
+ write_inc, write_inc
+
+ xterm_icon, xterm_icon
+
+ xterm_leave, xterm_leave
+
+ xterm_set_titles, xterm_set_titles
+
+ xterm_title, xterm_title
projects / apps / madmutt.git / blobdiff