X-Git-Url: http://git.madism.org/?p=apps%2Fmadmutt.git;a=blobdiff_plain;f=doc%2Fmanual.txt;h=1da723318b1c7bc0a9d1c0a65dce670bef5df681;hp=f6dd5afd370bce6985f42d777c94a7cfc0610795;hb=f98da767a1df0098d7b8a343e8416e489484fb85;hpb=5bba49f1904801c2221426a7d8e2cc5cce055f02

diff --git a/doc/manual.txt b/doc/manual.txt
index f6dd5af..1da7233 100644
--- a/doc/manual.txt
+++ b/doc/manual.txt
@@ -1,12390 +1,11209 @@
-                     The Mutt Next Generation E-Mail Client
 
-  Andreas Krennmair
+The Mutt Next Generation E-Mail Client
 
-   <ak@synflood.at>
+Andreas Krennmair
 
-  Michael Elkins
+   <aakk@@ssyynnfflloooodd..aatt>
 
-   <me@cs.hmc.edu>
+Michael Elkins
 
-   version devel-r541
+   <mmee@@ccss..hhmmcc..eedduu>
 
-   Abstract
+   version devel-r790
 
-   Michael Elinks on mutt, circa 1995: ``All mail clients suck. This one just
-   sucks less.''
+   _A_b_s_t_r_a_c_t
+
+   Michael Elinks on mutt, circa 1995: ``All mail clients suck. This one
+   just sucks less.''
 
    Sven Guckes on mutt, ca. 2003: ``But it still sucks!''
+     _________________________________________________________________
+
+   _T_a_b_l_e_ _o_f_ _C_o_n_t_e_n_t_s
+
+   11..  IInnttrroodduuccttiioonn
+
+        11..  OOvveerrvviieeww
+        22..  MMuutttt--nngg  HHoommee  PPaaggee
+        33..  MMaaiilliinngg  LLiissttss
+        44..  SSooffttwwaarree  DDiissttrriibbuuttiioonn  SSiitteess
+        55..  IIRRCC
+        66..  WWeebblloogg
+        77..  CCooppyyrriigghhtt
+        88..  MMaannuuaall  CCoonnvveennttiioonnss
+
+   22..  GGeettttiinngg  SSttaarrtteedd
+
+        11..  BBaassiicc  CCoonncceeppttss
+
+              11..11..  SSccrreeeennss  aanndd  MMeennuuss
+              11..22..  CCoonnffiigguurraattiioonn
+              11..33..  FFuunnccttiioonnss
+              11..44..  IInntteerraaccttiioonn
+              11..55..  MMoodduullaarriizzaattiioonn
+              11..66..  PPaatttteerrnnss
+
+        22..  SSccrreeeennss  aanndd  MMeennuuss
+
+              22..11..  IInnddeexx
+              22..22..  PPaaggeerr
+              22..33..  FFiillee  BBrroowwsseerr
+              22..44..  SSiiddeebbaarr
+              22..55..  HHeellpp
+              22..66..  CCoommppoossee  MMeennuu
+              22..77..  AAlliiaass  MMeennuu
+              22..88..  AAttttaacchhmmeenntt  MMeennuu
+              22..99..  KKeeyy  MMeennuu
+
+        33..  MMoovviinngg  AArroouunndd  iinn  MMeennuuss
+        44..  EEddiittiinngg  IInnppuutt  FFiieellddss
+        55..  RReeaaddiinngg  MMaaiill  --  TThhee  IInnddeexx  aanndd  PPaaggeerr
+
+              55..11..  TThhee  MMeessssaaggee  IInnddeexx
+              55..22..  TThhee  PPaaggeerr
+              55..33..  TThhrreeaaddeedd  MMooddee
+              55..44..  MMiisscceellllaanneeoouuss  FFuunnccttiioonnss
+
+        66..  SSeennddiinngg  MMaaiill
+
+              66..11..  CCoommppoossiinngg  nneeww  mmeessssaaggeess
+              66..22..  RReeppllyyiinngg
+              66..33..  EEddiittiinngg  tthhee  mmeessssaaggee  hheeaaddeerr
+              66..44..  UUssiinngg  MMuutttt--nngg  wwiitthh  PPGGPP
+              66..55..  SSeennddiinngg  aannoonnyymmoouuss  mmeessssaaggeess  vviiaa  mmiixxmmaasstteerr
+
+        77..  FFoorrwwaarrddiinngg  aanndd  BBoouunncciinngg  MMaaiill
+        88..  PPoossttppoonniinngg  MMaaiill
+
+   33..  CCoonnffiigguurraattiioonn
+
+        11..  LLooccaattiioonnss  ooff  CCoonnffiigguurraattiioonn  FFiilleess
+        22..  BBaassiicc  SSyynnttaaxx  ooff  IInniittiiaalliizzaattiioonn  FFiilleess
+        33..  EExxppaannssiioonn  wwiitthhiinn  vvaarriiaabblleess
+
+              33..11..  CCoommmmaannddss''  OOuuttppuutt
+              33..22..  EEnnvviirroonnmmeenntt  VVaarriiaabblleess
+              33..33..  CCoonnffiigguurraattiioonn  VVaarriiaabblleess
+              33..44..  SSeellff--DDeeffiinneedd  VVaarriiaabblleess
+              33..55..  PPrree--DDeeffiinneedd  VVaarriiaabblleess
+              33..66..  TTyyppee  CCoonnvveerrssiioonnss
+
+        44..  DDeeffiinniinngg//UUssiinngg  aalliiaasseess
+        55..  CChhaannggiinngg  tthhee  ddeeffaauulltt  kkeeyy  bbiinnddiinnggss
+        66..  DDeeffiinniinngg  aalliiaasseess  ffoorr  cchhaarraacctteerr  sseettss
+        77..  SSeettttiinngg  vvaarriiaabblleess  bbaasseedd  uuppoonn  mmaaiillbbooxx
+        88..  KKeeyybbooaarrdd  mmaaccrrooss
+        99..  UUssiinngg  ccoolloorr  aanndd  mmoonnoo  vviiddeeoo  aattttrriibbuutteess
+        1100..  IIggnnoorriinngg  ((wweeeeddiinngg))  uunnwwaanntteedd  mmeessssaaggee  hheeaaddeerrss
+        1111..  AAlltteerrnnaattiivvee  aaddddrreesssseess
+        1122..  FFoorrmmaatt  ==  FFlloowweedd
+
+              1122..11..  IInnttrroodduuccttiioonn
+              1122..22..  RReecceeiivviinngg::  DDiissppllaayy  SSeettuupp
+              1122..33..  SSeennddiinngg
+              1122..44..  AAddddiittiioonnaall  NNootteess
+
+        1133..  MMaaiilliinngg  lliissttss
+        1144..  UUssiinngg  MMuullttiippllee  ssppooooll  mmaaiillbbooxxeess
+        1155..  DDeeffiinniinngg  mmaaiillbbooxxeess  wwhhiicchh  rreecceeiivvee  mmaaiill
+        1166..  UUsseerr  ddeeffiinneedd  hheeaaddeerrss
+        1177..  DDeeffiinniinngg  tthhee  oorrddeerr  ooff  hheeaaddeerrss  wwhheenn  vviieewwiinngg  mmeessssaaggeess
+        1188..  SSppeecciiffyy  ddeeffaauulltt  ssaavvee  ffiilleennaammee
+        1199..  SSppeecciiffyy  ddeeffaauulltt  FFcccc::  mmaaiillbbooxx  wwhheenn  ccoommppoossiinngg
+        2200..  SSppeecciiffyy  ddeeffaauulltt  ssaavvee  ffiilleennaammee  aanndd  ddeeffaauulltt  FFcccc::  mmaaiillbbooxx  aatt
+                oonnccee
+
+        2211..  CChhaannggee  sseettttiinnggss  bbaasseedd  uuppoonn  mmeessssaaggee  rreecciippiieennttss
+        2222..  CChhaannggee  sseettttiinnggss  bbeeffoorree  ffoorrmmaattttiinngg  aa  mmeessssaaggee
+        2233..  CChhoooossiinngg  tthhee  ccrryyppttooggrraapphhiicc  kkeeyy  ooff  tthhee  rreecciippiieenntt
+        2244..  AAddddiinngg  kkeeyy  sseeqquueenncceess  ttoo  tthhee  kkeeyybbooaarrdd  bbuuffffeerr
+        2255..  EExxeeccuuttiinngg  ffuunnccttiioonnss
+        2266..  MMeessssaaggee  SSccoorriinngg
+        2277..  SSppaamm  ddeetteeccttiioonn
+        2288..  SSeettttiinngg  vvaarriiaabblleess
+        2299..  RReeaaddiinngg  iinniittiiaalliizzaattiioonn  ccoommmmaannddss  ffrroomm  aannootthheerr  ffiillee
+        3300..  RReemmoovviinngg  hhooookkss
+        3311..  SShhaarriinngg  SSeettuuppss
+
+              3311..11..  CChhaarraacctteerr  SSeettss
+              3311..22..  MMoodduullaarriizzaattiioonn
+              3311..33..  CCoonnddiittiioonnaall  ppaarrttss
+
+        3322..  OObbssoolleettee  VVaarriiaabblleess
+
+   44..  AAddvvaanncceedd  UUssaaggee
+
+        11..  RReegguullaarr  EExxpprreessssiioonnss
+        22..  PPaatttteerrnnss
+
+              22..11..  CCoommpplleexx  PPaatttteerrnnss
+              22..22..  PPaatttteerrnnss  aanndd  DDaatteess
+
+        33..  FFoorrmmaatt  SSttrriinnggss
+
+              33..11..  IInnttrroodduuccttiioonn
+              33..22..  CCoonnddiittiioonnaall  EExxppaannssiioonn
+              33..33..  MMooddiiffiiccaattiioonnss  aanndd  PPaaddddiinngg
+
+        44..  UUssiinngg  TTaaggss
+        55..  UUssiinngg  HHooookkss
+
+              55..11..  MMeessssaaggee  MMaattcchhiinngg  iinn  HHooookkss
+
+        66..  UUssiinngg  tthhee  ssiiddeebbaarr
+        77..  EExxtteerrnnaall  AAddddrreessss  QQuueerriieess
+        88..  MMaaiillbbooxx  FFoorrmmaattss
+        99..  MMaaiillbbooxx  SShhoorrttccuuttss
+        1100..  HHaannddlliinngg  MMaaiilliinngg  LLiissttss
+        1111..  EEddiittiinngg  tthhrreeaaddss
+
+              1111..11..  LLiinnkkiinngg  tthhrreeaaddss
+              1111..22..  BBrreeaakkiinngg  tthhrreeaaddss
+
+        1122..  DDeelliivveerryy  SSttaattuuss  NNoottiiffiiccaattiioonn  ((DDSSNN))  SSuuppppoorrtt
+        1133..  PPOOPP33  SSuuppppoorrtt  ((OOPPTTIIOONNAALL))
+        1144..  IIMMAAPP  SSuuppppoorrtt  ((OOPPTTIIOONNAALL))
+
+              1144..11..  TThhee  FFoollddeerr  BBrroowwsseerr
+              1144..22..  AAuutthheennttiiccaattiioonn
+
+        1155..  NNNNTTPP  SSuuppppoorrtt  ((OOPPTTIIOONNAALL))
+
+              1155..11..  AAggaaiinn::  SSccoorriinngg
+
+        1166..  SSMMTTPP  SSuuppppoorrtt  ((OOPPTTIIOONNAALL))
+        1177..  MMaannaaggiinngg  mmuullttiippllee  IIMMAAPP//PPOOPP//NNNNTTPP  aaccccoouunnttss  ((OOPPTTIIOONNAALL))
+        1188..  SSttaarrtt  aa  WWWWWW  BBrroowwsseerr  oonn  UURRLLss  ((EEXXTTEERRNNAALL))
+        1199..  CCoommpprreesssseedd  ffoollddeerrss  SSuuppppoorrtt  ((OOPPTTIIOONNAALL))
+
+              1199..11..  OOppeenn  aa  ccoommpprreesssseedd  mmaaiillbbooxx  ffoorr  rreeaaddiinngg
+              1199..22..  WWrriittee  aa  ccoommpprreesssseedd  mmaaiillbbooxx
+              1199..33..  AAppppeenndd  aa  mmeessssaaggee  ttoo  aa  ccoommpprreesssseedd  mmaaiillbbooxx
+              1199..44..  EEnnccrryypptteedd  ffoollddeerrss
+
+   55..  MMuutttt--nngg''ss  MMIIMMEE  SSuuppppoorrtt
+
+        11..  UUssiinngg  MMIIMMEE  iinn  MMuutttt
+
+              11..11..  VViieewwiinngg  MMIIMMEE  mmeessssaaggeess  iinn  tthhee  ppaaggeerr
+              11..22..  TThhee  AAttttaacchhmmeenntt  MMeennuu
+              11..33..  TThhee  CCoommppoossee  MMeennuu
+
+        22..  MMIIMMEE  TTyyppee  ccoonnffiigguurraattiioonn  wwiitthh  mmiimmee..ttyyppeess
+        33..  MMIIMMEE  VViieewweerr  ccoonnffiigguurraattiioonn  wwiitthh  mmaaiillccaapp
+
+              33..11..  TThhee  BBaassiiccss  ooff  tthhee  mmaaiillccaapp  ffiillee
+              33..22..  SSeeccuurree  uussee  ooff  mmaaiillccaapp
+              33..33..  AAddvvaanncceedd  mmaaiillccaapp  UUssaaggee
+              33..44..  EExxaammppllee  mmaaiillccaapp  ffiilleess
+
+        44..  MMIIMMEE  AAuuttoovviieeww
+        55..  MMIIMMEE  MMuullttiippaarrtt//AAlltteerrnnaattiivvee
+        66..  AAttttaacchhmmeenntt  SSeeaarrcchhiinngg  aanndd  CCoouunnttiinngg
+        77..  MMIIMMEE  LLooookkuupp
+
+   66..  SSeeccuurriittyy  CCoonnssiiddeerraattiioonnss
+
+        11..  PPaasssswwoorrddss
+        22..  TTeemmppoorraarryy  FFiilleess
+        33..  IInnffoorrmmaattiioonn  LLeeaakkss
+
+              33..11..  MMeessssaaggee--IIDD::  hheeaaddeerrss
+              33..22..  mmaaiillttoo::--ssttyyllee  lliinnkkss
+
+        44..  EExxtteerrnnaall  aapppplliiccaattiioonnss
+
+              44..11..  mmaaiillccaapp
+              44..22..  OOtthheerr
+
+   77..  RReeffeerreennccee
+
+        11..  CCoommmmaanndd  lliinnee  ooppttiioonnss
+        22..  PPaatttteerrnnss
+        33..  CCoonnffiigguurraattiioonn  CCoommmmaannddss
+        44..  CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+        55..  FFuunnccttiioonnss
+
+              55..11..  ggeenneerriicc
+              55..22..  iinnddeexx
+              55..33..  ppaaggeerr
+              55..44..  aalliiaass
+              55..55..  qquueerryy
+              55..66..  aattttaacchh
+              55..77..  ccoommppoossee
+              55..88..  ppoossttppoonnee
+              55..99..  bbrroowwsseerr
+              55..1100..  ppggpp
+              55..1111..  eeddiittoorr
+              55..1122..  ssiiddeebbaarr
+
+   AA..  AAcckknnoowwlleeddggmmeennttss
+   BB..  HHaacckkiinngg  DDooccuummeennttaattiioonn
+   IInnddeexx
+
+   _L_i_s_t_ _o_f_ _T_a_b_l_e_s
+
+   2.1. MMoosstt  ccoommmmoonnllyy  uusseedd  mmoovveemmeenntt  bbiinnddiinnggss
+   2.2. LLiinnee  EEddiittoorr  FFuunnccttiioonnss
+   2.3. MMoosstt  ccoommmmoonnllyy  uusseedd  IInnddeexx  BBiinnddiinnggss
+   2.4. MMoosstt  ccoommmmoonnllyy  uusseedd  PPaaggeerr  BBiinnddiinnggss
+   2.5. AANNSSII  EEssccaappee  SSeeqquueenncceess
+   2.6. AANNSSII  CCoolloorrss
+   2.7. MMoosstt  ccoommmmoonnllyy  uusseedd  tthhrreeaadd--rreellaatteedd  bbiinnddiinnggss
+   2.8. MMoosstt  ccoommmmoonnllyy  uusseedd  MMaaiill  CCoommppoossiittiioonn  BBiinnddiinnggss
+   2.9. MMoosstt  ccoommmmoonnllyy  uusseedd  CCoommppoossee  MMeennuu  BBiinnddiinnggss
+   2.10. PPGGPP  KKeeyy  MMeennuu  FFllaaggss
+   3.1. AAlltteerrnnaattiivvee  KKeeyy  NNaammeess
+   7.1. RReeffeerreennccee::  CCoommmmaanndd  LLiinnee  OOppttiioonnss
+   7.2. RReeffeerreennccee::  PPaatttteerrnnss
+   7.3. RReeffeerreennccee::  OObbssoolleettee  VVaarriiaabblleess
+   7.4. RReeffeerreennccee::  DDeeffaauulltt  GGeenneerriicc  FFuunnccttiioonn  BBiinnddiinnggss
+   7.5. RReeffeerreennccee::  DDeeffaauulltt  IInnddeexx  FFuunnccttiioonn  BBiinnddiinnggss
+   7.6. RReeffeerreennccee::  DDeeffaauulltt  PPaaggeerr  FFuunnccttiioonn  BBiinnddiinnggss
+   7.7. RReeffeerreennccee::  DDeeffaauulltt  AAlliiaass  MMeennuu  FFuunnccttiioonn  BBiinnddiinnggss
+   7.8. RReeffeerreennccee::  DDeeffaauulltt  QQuueerryy  MMeennuu  FFuunnccttiioonn  BBiinnddiinnggss
+   7.9. RReeffeerreennccee::  DDeeffaauulltt  AAttttaacchhmmeenntt  MMeennuu  FFuunnccttiioonn  BBiinnddiinnggss
+   7.10. RReeffeerreennccee::  DDeeffaauulltt  CCoommppoossee  MMeennuu  FFuunnccttiioonn  BBiinnddiinnggss
+   7.11. RReeffeerreennccee::  DDeeffaauulltt  PPoossttppoonnee  MMeennuu  FFuunnccttiioonn  BBiinnddiinnggss
+   7.12. RReeffeerreennccee::  DDeeffaauulltt  BBrroowwsseerr  MMeennuu  FFuunnccttiioonn  BBiinnddiinnggss
+   7.13. RReeffeerreennccee::  DDeeffaauulltt  PPGGPP  MMeennuu  FFuunnccttiioonn  BBiinnddiinnggss
+   7.14. RReeffeerreennccee::  DDeeffaauulltt  EEddiittoorr  FFuunnccttiioonn  BBiinnddiinnggss
+   7.15. RReeffeerreennee::  DDeeffaauulltt  SSiiddeebbaarr  FFuunnccttiioonn  BBiinnddiinnggss
 
-   --------------------------------------------------------------------------
+Chapter 1. Introduction
 
-   Table of Contents
+   _T_a_b_l_e_ _o_f_ _C_o_n_t_e_n_t_s
 
-   1. Introduction
+   11..  OOvveerrvviieeww
+   22..  MMuutttt--nngg  HHoommee  PPaaggee
+   33..  MMaaiilliinngg  LLiissttss
+   44..  SSooffttwwaarree  DDiissttrriibbuuttiioonn  SSiitteess
+   55..  IIRRCC
+   66..  WWeebblloogg
+   77..  CCooppyyrriigghhtt
+   88..  MMaannuuaall  CCoonnvveennttiioonnss
 
-                1. Overview
+1. Overview
 
-                2. Mutt-ng Home Page
+   _M_u_t_t_-_n_g is a small but very powerful text-based MIME mail client.
+   Mutt-ng is highly configurable, and is well suited to the mail power
+   user with advanced features like key bindings, keyboard macros, mail
+   threading, regular expression searches and a powerful pattern matching
+   language for selecting groups of messages.
 
-                3. Mailing Lists
+   This documentation additionally contains documentation to _M_u_t_t_-_N_G ,a
+   fork from Mutt with the goal to fix all the little annoyances of Mutt,
+   to integrate all the Mutt patches that are floating around in the web,
+   and to add other new features. Features specific to Mutt-ng will be
+   discussed in an extra section. Don't be confused when most of the
+   documentation talk about Mutt and not Mutt-ng, Mutt-ng contains all
+   Mutt features, plus many more.
 
-                4. Software Distribution Sites
+2. Mutt-ng Home Page
 
-                5. IRC
+   <<hhttttpp::////wwwwww..mmuuttttnngg..oorrgg//>>
 
-                6. Weblog
+3. Mailing Lists
 
-                7. Copyright
+     * <mmuutttt--nngg--uusseerrss@@lliissttss..bbeerrlliiooss..ddee>: This is where the mutt-ng user
+       support happens.
+     * <mmuutttt--nngg--ddeevveell@@lliissttss..bbeerrlliiooss..ddee>: The development mailing list for
+       mutt-ng
 
-                8. Manual Conventions
+4. Software Distribution Sites
 
-   2. Getting Started
+   So far, there are no official releases of Mutt-ng, but you can
+   download daily snapshots from <<hhttttpp::////mmuutttt--nngg..bbeerrlliiooss..ddee//ssnnaappsshhoottss//>>
 
-                1. Basic Concepts
+5. IRC
 
-                             1.1. Screens and Menus
+   Visit channel _#_m_u_t_t_n_g on iirrcc..ffrreeeennooddee..nneett  ((wwwwww..ffrreeeennooddee..nneett)) to chat
+   with other people interested in Mutt-ng.
 
-                             1.2. Configuration
+6. Weblog
 
-                             1.3. Functions
+   If you want to read fresh news about the latest development in
+   Mutt-ng, and get informed about stuff like interesting,
+   Mutt-ng-related articles and packages for your favorite distribution,
+   you can read and/or subscribe to our MMuutttt--nngg  ddeevveellooppmmeenntt  wweebblloogg.
 
-                             1.4. Interaction
+7. Copyright
 
-                             1.5. Modularization
+   Mutt is Copyright (C) 1996-2000 Michael R. Elkins <me@cs.hmc.edu> and
+   others
 
-                             1.6. Patterns
+   This program is free software; you can redistribute it and/or modify
+   it under the terms of the GNU General Public License as published by
+   the Free Software Foundation; either version 2 of the License, or (at
+   your option) any later version.
 
-                2. Screens and Menus
+   This program is distributed in the hope that it will be useful, but
+   WITHOUT ANY WARRANTY; without even the implied warranty of
+   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+   General Public License for more details.
 
-                             2.1. Index
+   You should have received a copy of the GNU General Public License
+   along with this program; if not, write to the Free Software
+   Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
+   02110-1301, USA.
 
-                             2.2. Pager
+8. Manual Conventions
 
-                             2.3. File Browser
+   This manual contains several (hopefully consistent) conventions to
+   specially layout different items in different fashions.
 
-                             2.4. Sidebar
+     * Configuration and environment variables will be printed in a
+       typewriter font and both prefixed with a dollar sign as it's
+       common for UNIX-like environments. Configuration variables are
+       lower-case only while environment variables are upper-case only.
+       $$iimmaapp__mmaaiill__cchheecckk is a configuration variable while $EDITOR is an
+       environment variable.
+     * Muttng-specific functions are enclosed in <> and printed in a
+       typewriter font, too, as in <sync-mailbox>.
+     * As common for UNIX-like environments, references to manual pages
+       are printed with the section enclosed in braces, as in vi(1) or
+       muttngrc(5). Execute man [section] [name] to view the manual page.
+     * Keys are presented in the following way: ordinary keys are just
+       given as-is, e.g. q. Control characters are prefixed with C- (e.g.
+       the screen can be redraw by pressing C-L) and E- for Escape, e.g.
+       a folder can be opened read-only with E-c.
 
-                             2.5. Help
+   If, while reading this fine manual, you find any inconsistencies of
+   whatever kind, please contact the developers via
+   <mmuutttt--nngg--ddeevveell@@lliissttss..bbeerrlliiooss..ddee> to report it.
 
-                             2.6. Compose Menu
+Chapter 2. Getting Started
 
-                             2.7. Alias Menu
+   _T_a_b_l_e_ _o_f_ _C_o_n_t_e_n_t_s
 
-                             2.8. Attachment Menu
+   11..  BBaassiicc  CCoonncceeppttss
 
-                             2.9. Key Menu
+        11..11..  SSccrreeeennss  aanndd  MMeennuuss
+        11..22..  CCoonnffiigguurraattiioonn
+        11..33..  FFuunnccttiioonnss
+        11..44..  IInntteerraaccttiioonn
+        11..55..  MMoodduullaarriizzaattiioonn
+        11..66..  PPaatttteerrnnss
 
-                3. Moving Around in Menus
+   22..  SSccrreeeennss  aanndd  MMeennuuss
 
-                4. Editing Input Fields
+        22..11..  IInnddeexx
+        22..22..  PPaaggeerr
+        22..33..  FFiillee  BBrroowwsseerr
+        22..44..  SSiiddeebbaarr
+        22..55..  HHeellpp
+        22..66..  CCoommppoossee  MMeennuu
+        22..77..  AAlliiaass  MMeennuu
+        22..88..  AAttttaacchhmmeenntt  MMeennuu
+        22..99..  KKeeyy  MMeennuu
 
-                5. Reading Mail - The Index and Pager
+   33..  MMoovviinngg  AArroouunndd  iinn  MMeennuuss
+   44..  EEddiittiinngg  IInnppuutt  FFiieellddss
+   55..  RReeaaddiinngg  MMaaiill  --  TThhee  IInnddeexx  aanndd  PPaaggeerr
 
-                             5.1. The Message Index
+        55..11..  TThhee  MMeessssaaggee  IInnddeexx
+        55..22..  TThhee  PPaaggeerr
+        55..33..  TThhrreeaaddeedd  MMooddee
+        55..44..  MMiisscceellllaanneeoouuss  FFuunnccttiioonnss
 
-                             5.2. The Pager
+   66..  SSeennddiinngg  MMaaiill
 
-                             5.3. Threaded Mode
+        66..11..  CCoommppoossiinngg  nneeww  mmeessssaaggeess
+        66..22..  RReeppllyyiinngg
+        66..33..  EEddiittiinngg  tthhee  mmeessssaaggee  hheeaaddeerr
+        66..44..  UUssiinngg  MMuutttt--nngg  wwiitthh  PPGGPP
+        66..55..  SSeennddiinngg  aannoonnyymmoouuss  mmeessssaaggeess  vviiaa  mmiixxmmaasstteerr
 
-                             5.4. Miscellaneous Functions
+   77..  FFoorrwwaarrddiinngg  aanndd  BBoouunncciinngg  MMaaiill
+   88..  PPoossttppoonniinngg  MMaaiill
 
-                6. Sending Mail
+1. Basic Concepts
 
-                             6.1. Composing new messages
+1.1. Screens and Menus
 
-                             6.2. Replying
+   mutt-ng offers different screens of which every has its special
+   purpose:
 
-                             6.3. Editing the message header
+     * The _i_n_d_e_x displays the contents of the currently opened mailbox.
+     * The _p_a_g_e_r is responsible for displaying messages, that is, the
+       header, the body and all attached parts.
+     * The _f_i_l_e_ _b_r_o_w_s_e_r offers operations on and displays information of
+       all folders mutt-ng should watch for mail.
+     * The _s_i_d_e_b_a_r offers a permanent view of which mailboxes contain how
+       many total, new and/or flagged mails.
+     * The _h_e_l_p_ _s_c_r_e_e_n lists for all currently available commands how to
+       invoke them as well as a short description.
+     * The _c_o_m_p_o_s_e menu is a comfortable interface take last actions
+       before sending mail: change subjects, attach files, remove
+       attachements, etc.
+     * The _a_t_t_a_c_h_e_m_e_n_t menu gives a summary and the tree structure of the
+       attachements of the current message.
+     * The _a_l_i_a_s menu lists all or a fraction of the aliases a user has
+       defined.
+     * The _k_e_y menu used in connection with encryption lets users choose
+       the right key to encrypt with.
 
-                             6.4. Using Mutt-ng with PGP
+   When mutt-ng is started without any further options, it'll open the
+   users default mailbox and display the index.
 
-                             6.5. Sending anonymous messages via mixmaster
+1.2. Configuration
 
-                7. Forwarding and Bouncing Mail
+   Mutt-ng does _n_o_t feature an internal configuration interface or menu
+   due to the simple fact that this would be too complex to handle
+   (currently there are several _h_u_n_d_r_e_d variables which fine-tune the
+   behaviour.)
 
-                8. Postponing Mail
+   Mutt-ng is configured using configuration files which allow users to
+   add comments or manage them via version control systems to ease
+   maintenance.
 
-   3. Configuration
+   Also, mutt-ng comes with a shell script named grml-muttng kindly
+   contributed by users which really helps and eases the creation of a
+   user's configuration file. When downloading the source code via a
+   snapshot or via subversion, it can be found in the contrib directory.
 
-                1. Locations of Configuration Files
+1.3. Functions
 
-                2. Basic Syntax of Initialization Files
+   Mutt-ng offers great flexibility due to the use of functions:
+   internally, every action a user can make mutt-ng perform is named
+   ``function.'' Those functions are assigned to keys (or even key
+   sequences) and may be completely adjusted to user's needs. The basic
+   idea is that the impatient users get a very intuitive interface to
+   start off with and advanced users virtually get no limits to
+   adjustments.
 
-                3. Expansion within variables
+1.4. Interaction
 
-                             3.1. Commands' Output
+   Mutt-ng has two basic concepts of user interaction:
 
-                             3.2. Environment Variables
+    1. There is one dedicated line on the screen used to query the user
+       for input, issue any command, query variables and display error
+       and informational messages. As for every type of user input, this
+       requires manual action leading to the need of input.
+    2. The automatized interface for interaction are the so called _h_o_o_k_s.
+       Hooks specify actions the user wants to be performed at
+       well-defined situations: what to do when entering which folder,
+       what to do when displaying or replying to what kind of message,
+       etc. These are optional, i.e. a user doesn't need to specify them
+       but can do so.
 
-                             3.3. Configuration Variables
+1.5. Modularization
 
-                             3.4. Self-Defined Variables
+   Although mutt-ng has many functionality built-in, many features can be
+   delegated to external tools to increase flexibility: users can define
+   programs to filter a message through before displaying, users can use
+   any program they want for displaying a message, message types (such as
+   PDF or PostScript) for which mutt-ng doesn't have a built-in filter
+   can be rendered by arbitrary tools and so forth. Although mutt-ng has
+   an alias mechanism built-in, it features using external tools to query
+   for nearly every type of addresses from sources like LDAP, databases
+   or just the list of locally known users.
 
-                             3.5. Pre-Defined Variables
+1.6. Patterns
 
-                             3.6. Type Conversions
+   Mutt-ng has a built-in pattern matching ``language'' which is as
+   widely used as possible to present a consistent interface to users.
+   The same ``pattern terms'' can be used for searching, scoring, message
+   selection and much more.
 
-                4. Defining/Using aliases
+2. Screens and Menus
 
-                5. Changing the default key bindings
+2.1. Index
 
-                6. Defining aliases for character sets
+   The index is the screen that you usually see first when you start
+   mutt-ng. It gives an overview over your emails in the currently opened
+   mailbox. By default, this is your system mailbox. The information you
+   see in the index is a list of emails, each with its number on the
+   left, its flags (new email, important email, email that has been
+   forwarded or replied to, tagged email, ...), the date when email was
+   sent, its sender, the email size, and the subject. Additionally, the
+   index also shows thread hierarchies: when you reply to an email, and
+   the other person replies back, you can see the other's person email in
+   a "sub-tree" below. This is especially useful for personal email
+   between a group of people or when you've subscribed to mailing lists.
 
-                7. Setting variables based upon mailbox
+2.2. Pager
 
-                8. Keyboard macros
+   The pager is responsible for showing the email content. On the top of
+   the pager you have an overview over the most important email headers
+   like the sender, the recipient, the subject, and much more
+   information. How much information you actually see depends on your
+   configuration, which we'll describe below.
 
-                9. Using color and mono video attributes
+   Below the headers, you see the email body which usually contains the
+   message. If the email contains any attachments, you will see more
+   information about them below the email body, or, if the attachments
+   are text files, you can view them directly in the pager.
+
+   To give the user a good overview, it is possible to configure mutt-ng
+   to show different things in the pager with different colors. Virtually
+   everything that can be described with a regular expression can be
+   colored, e.g. URLs, email addresses or smileys.
+
+2.3. File Browser
+
+   The file browser is the interface to the local or remote file system.
+   When selecting a mailbox to open, the browser allows custom sorting of
+   items, limiting the items shown by a regular expression and a freely
+   adjustable format of what to display in which way. It also allows for
+   easy navigation through the file system when selecting file(s) to
+   attach to a message, select multiple files to attach and many more.
+
+2.4. Sidebar
+
+   The sidebar comes in handy to manage mails which are spread over
+   different folders. All folders users setup mutt-ng to watch for new
+   mail will be listed. The listing includes not only the name but also
+   the number of total messages, the number of new and flagged messages.
+   Items with new mail may be colored different from those with flagged
+   mail, items may be shortened or compress if they're they to long to be
+   printed in full form so that by abbreviated names, user still now what
+   the name stands for.
+
+2.5. Help
+
+   The help screen is meant to offer a quick help to the user. It lists
+   the current configuration of key bindings and their associated
+   commands including a short description, and currently unbound
+   functions that still need to be associated with a key binding (or
+   alternatively, they can be called via the mutt-ng command prompt).
+
+2.6. Compose Menu
+
+   The compose menu features a split screen containing the information
+   which really matter before actually sending a message by mail or
+   posting an article to a newsgroup: who gets the message as what
+   (recipient, newsgroup, who gets what kind of copy). Additionally,
+   users may set security options like deciding whether to sign, encrypt
+   or sign and encrypt a message with/for what keys.
+
+   Also, it's used to attach messages, news articles or files to a
+   message, to re-edit any attachment including the message itself.
+
+2.7. Alias Menu
+
+   The alias menu is used to help users finding the recipients of
+   messages. For users who need to contact many people, there's no need
+   to remember addresses or names completely because it allows for
+   searching, too. The alias mechanism and thus the alias menu also
+   features grouping several addresses by a shorter nickname, the actual
+   alias, so that users don't have to select each single recipient
+   manually.
+
+2.8. Attachment Menu
+
+   As will be later discussed in detail, mutt-ng features a good and
+   stable MIME implementation, that is, is greatly supports sending and
+   receiving messages of arbitrary type. The attachment menu displays a
+   message's structure in detail: what content parts are attached to
+   which parent part (which gives a true tree structure), which type is
+   of what type and what size. Single parts may saved, deleted or
+   modified to offer great and easy access to message's internals.
+
+2.9. Key Menu
 
-                10. Ignoring (weeding) unwanted message headers
+   FIXME
 
-                11. Alternative addresses
+3. Moving Around in Menus
 
-                12. Format = Flowed
+   Information is presented in menus, very similar to ELM. Here is a
+   tableshowing the common keys used to navigate menus in Mutt-ng.
 
-                             12.1. Introduction
+   _T_a_b_l_e_ _2_._1_._ _M_o_s_t_ _c_o_m_m_o_n_l_y_ _u_s_e_d_ _m_o_v_e_m_e_n_t_ _b_i_n_d_i_n_g_s
+   Key         Function         Description
+   j or Down   <next-entry>     move to the next entry
+   k or Up     <previous-entry> move to the previous entry
+   z or PageDn <page-down>      go to the next page
+   Z or PageUp <page-up>        go to the previous page
+   = or Home   <first-entry>    jump to the first entry
+   * or End    <last-entry>     jump to the last entry
+   q           <quit>           exit the current menu
+   ?           <help>           list all key bindings for the current menu
 
-                             12.2. Receiving: Display Setup
+4. Editing Input Fields
 
-                             12.3. Sending
+   Mutt-ng has a builtin line editor which is used as the primary way to
+   input textual data such as email addresses or filenames. The keys used
+   to move around while editing are very similar to those of Emacs.
 
-                             12.4. Additional Notes
+   _T_a_b_l_e_ _2_._2_._ _L_i_n_e_ _E_d_i_t_o_r_ _F_u_n_c_t_i_o_n_s
+   Key           Function          Description
+   C-A or Home   <bol>             move to the start of the line
+   C-B or Left   <backward-char>   move back one char
+   E-B           <backward-word>   move back one word
+   C-D or Delete <delete-char>     delete the char under the cursor
+   C-E or End    <eol>             move to the end of the line
+   C-F or Right  <forward-char>    move forward one char
+   E-F           <forward-word>    move forward one word
+   Tab           <complete>        complete filename or alias
+   C-T           <complete-query>  complete address with query
+   C-K           <kill-eol>        delete to the end of the line
+   E-d           <kill-eow>        delete to the end of the word
+   C-W           <kill-word>       kill the word in front of the cursor
+   C-U           <kill-line>       delete entire line
+   C-V           <quote-char>      quote the next typed key
+   Up            <history-up>      recall previous string from history
+   Down          <history-down>    recall next string from history
+   BackSpace     <backspace>       kill the char in front of the cursor
+   E-u           <upcase-word>     convert word to upper case
+   E-l           <downcase-word>   convert word to lower case
+   E-c           <capitalize-word> capitalize the word
+   C-G                             abort
+   Return                          finish editing
 
-                13. Mailing lists
+   You can remap the _e_d_i_t_o_r functions using the bbiinndd command. For
+   example, to make the _D_e_l_e_t_e key delete the character in front of the
+   cursor rather than under, you could use
 
-                14. Using Multiple spool mailboxes
+   bind editor <delete> backspace
 
-                15. Defining mailboxes which receive mail
+5. Reading Mail - The Index and Pager
 
-                16. User defined headers
+   Similar to many other mail clients, there are two modes in which mail
+   isread in Mutt-ng. The first is the index of messages in the mailbox,
+   which is called the ``index'' in Mutt-ng. The second mode is the
+   display of the message contents. This is called the ``pager.''
 
-                17. Defining the order of headers when viewing messages
+   The next few sections describe the functions provided in each of these
+   modes.
 
-                18. Specify default save filename
+5.1. The Message Index
 
-                19. Specify default Fcc: mailbox when composing
+   _T_a_b_l_e_ _2_._3_._ _M_o_s_t_ _c_o_m_m_o_n_l_y_ _u_s_e_d_ _I_n_d_e_x_ _B_i_n_d_i_n_g_s
+   Key    Function Description
+   c               change to a different mailbox
+   E-c             change to a folder in read-only mode
+   C               copy the current message to another mailbox
+   E-C             decode a message and copy it to a folder
+   E-s             decode a message and save it to a folder
+   D               delete messages matching a pattern
+   d               delete the current message
+   F               mark as important
+   l               show messages matching a pattern
+   N               mark message as new
+   o               change the current sort method
+   O               reverse sort the mailbox
+   q               save changes and exit
+   s               save-message
+   T               tag messages matching a pattern
+   t               toggle the tag on a message
+   E-t             toggle tag on entire message thread
+   U               undelete messages matching a pattern
+   u               undelete-message
+   v               view-attachments
+   x               abort changes and exit
+   Return          display-message
+   Tab             jump to the next new or unread message
+   @               show the author's full e-mail address
+   $               save changes to mailbox
+   /               search
+   E-/             search-reverse
+   C-L             clear and redraw the screen
+   C-T             untag messages matching a pattern
 
-                20. Specify default save filename and default Fcc: mailbox at
-                once
+5.1.1. Status Flags
 
-                21. Change settings based upon message recipients
+   In addition to who sent the message and the subject, a short summary
+   of the disposition of each message is printed beside the message
+   number. Zero or more of the following ``flags'' may appear, which
+   mean:
 
-                22. Change settings before formatting a message
+   D
+          message is deleted (is marked for deletion)
 
-                23. Choosing the cryptographic key of the recipient
+   d
+          message have attachments marked for deletion
 
-                24. Adding key sequences to the keyboard buffer
+   K
+          contains a PGP public key
 
-                25. Executing functions
+   N
+          message is new
 
-                26. Message Scoring
+   O
+          message is old
 
-                27. Spam detection
+   P
+          message is PGP encrypted
 
-                28. Setting variables
+   r
+          message has been replied to
 
-                29. Reading initialization commands from another file
+   S
+          message is signed, and the signature is succesfully verified
 
-                30. Removing hooks
+   s
+          message is signed
 
-                31. Sharing Setups
+   !
+          message is flagged
 
-                             31.1. Character Sets
+   *
+          message is tagged
 
-                             31.2. Modularization
+   Some of the status flags can be turned on or off using
+     * _s_e_t_-_f_l_a_g (default: w)
+     * _c_l_e_a_r_-_f_l_a_g (default: W)
 
-                             31.3. Conditional parts
+   Furthermore, the following flags reflect who the message is addressed
+   to. They can be customized with the $$ttoo__cchhaarrss variable.
 
-                32. Obsolete Variables
+   +
+          message is to you and you only
 
-   4. Advanced Usage
+   T
+          message is to you, but also to or cc'ed to others
 
-                1. Regular Expressions
+   C
+          message is cc'ed to you
 
-                2. Patterns
+   F
+          message is from you
 
-                             2.1. Complex Patterns
+   L
+          message is sent to a subscribed mailing list
 
-                             2.2. Patterns and Dates
+5.2. The Pager
 
-                3. Format Strings
+   By default, Mutt-ng uses its builtin pager to display the body of
+   messages. The pager is very similar to the Unix program _l_e_s_s though
+   not nearly as featureful.
+
+   _T_a_b_l_e_ _2_._4_._ _M_o_s_t_ _c_o_m_m_o_n_l_y_ _u_s_e_d_ _P_a_g_e_r_ _B_i_n_d_i_n_g_s
+   Key Function Description
+   Return go down one line
+   Space display the next page (or next message if at the end of a
+   message)
+   - go back to the previous page
+   n search for next match
+   S skip beyond quoted text
+   T toggle display of quoted text
+   ? show key bindings
+   / search for a regular expression (pattern)
+   E-/ search backwards for a regular expression
+   \ toggle search pattern coloring
+   ^ jump to the top of the message
+
+   In addition, many of the functions from the _i_n_d_e_x are available in the
+   pager, such as _d_e_l_e_t_e_-_m_e_s_s_a_g_e or _c_o_p_y_-_m_e_s_s_a_g_e (this is one advantage
+   over using an external pager to view messages).
+
+   Also, the internal pager supports a couple other advanced features.
+   For one, it will accept and translate the ``standard'' nroff sequences
+   forbold and underline. These sequences are a series of either the
+   letter, backspace (C-H), the letter again for bold or the letter,
+   backspace, _ for denoting underline. Mutt-ng will attempt to display
+   these in bold and underline respectively if your terminal supports
+   them. If not, you can use the bold and underline ccoolloorr objects to
+   specify a color or mono attribute for them.
+
+   Additionally, the internal pager supports the ANSI escape sequences
+   for character attributes. Mutt-ng translates them into the correct
+   color and character settings. The sequences Mutt-ng supports are: ESC
+   [ Ps;Ps;Ps;...;Ps m (see table below for possible values for Ps).
+
+   _T_a_b_l_e_ _2_._5_._ _A_N_S_I_ _E_s_c_a_p_e_ _S_e_q_u_e_n_c_e_s
+   Value Attribute
+   0     All Attributes Off
+   1     Bold on
+   4     Underline on
+   5     Blink on
+   7     Reverse video on
+   3x    Foreground color is x (see table below)
+   4x    Background color is x (see table below)
 
-                             3.1. Introduction
+   _T_a_b_l_e_ _2_._6_._ _A_N_S_I_ _C_o_l_o_r_s
+   Number Color
+   0      black
+   1      red
+   2      green
+   3      yellow
+   4      blue
+   5      magenta
+   6      cyan
+   7      white
 
-                             3.2. Conditional Expansion
+   Mutt-ng uses these attributes for handling text/enriched messages, and
+   they can also be used by an external aauuttoo__vviieeww script for highlighting
+   purposes. _N_o_t_e_: If you change the colors for your display, for example
+   by changing the color associated with color2 for your xterm, then that
+   color will be used instead of green.
+
+5.3. Threaded Mode
+
+   When the mailbox is ssoorrtteedd by _t_h_r_e_a_d_s ,there are a few additional
+   functions available in the _i_n_d_e_x and _p_a_g_e_r modes.
+
+   _T_a_b_l_e_ _2_._7_._ _M_o_s_t_ _c_o_m_m_o_n_l_y_ _u_s_e_d_ _t_h_r_e_a_d_-_r_e_l_a_t_e_d_ _b_i_n_d_i_n_g_s
+   Key Function Description
+   C-D <delete-thread> delete all messages in the current thread
+   C-U <undelete-thread> undelete all messages in the current thread
+   C-N <next-thread> jump to the start of the next thread
+   C-P <previous-thread> jump to the start of the previous thread
+   C-R <read-thread> mark the current thread as read
+   E-d <delete-subthread> delete all messages in the current subthread
+   E-u <undelete-subthread> undelete all messages in the current
+   subthread
+   E-n <next-subthread> jump to the start of the next subthread
+   E-p <previous-subthread> jump to the start of the previous subthread
+   E-r <read-subthread> mark the current subthread as read
+   E-t <tag-thread> toggle the tag on the current thread
+   E-v <collapse-thread> toggle collapse for the current thread
+   E-V <collapse-all> toggle collapse for all threads
+   P <parent-message> jump to parent message in thread
+
+   _N_o_t_e_: Collapsing a thread displays only the first message in the
+   thread and hides the others. This is useful when threads contain so
+   many messages that you can only see a handful of threads onthe screen.
+   See %M in $$iinnddeexx__ffoorrmmaatt.
+
+   For example, you could use %?M?(#%03M)&(%4l)? in $$iinnddeexx__ffoorrmmaatt to
+   optionally display the number of hidden messages if the thread is
+   collapsed.
 
-                             3.3. Modifications and Padding
+   See also the $$ssttrriicctt__tthhrreeaaddss variable.
 
-                4. Using Tags
+5.4. Miscellaneous Functions
 
-                5. Using Hooks
+   <create-alias> (default: a)
 
-                             5.1. Message Matching in Hooks
+   Creates a new alias based upon the current message (or prompts for a
+   new one). Once editing is complete, an aalliiaass command is added to the
+   file specified by the $$aalliiaass__ffiillee variable for future use. _N_o_t_e_:
+   Specifying an $$aalliiaass__ffiillee does not add the aliases specified there-in,
+   you must also ssoouurrccee the file.
 
-                6. Using the sidebar
+   <check-traditional-pgp> (default: E-P)
 
-                7. External Address Queries
+   This function will search the current message for content signed or
+   encrypted with PGP the "traditional" way, that is, without proper MIME
+   tagging. Technically, this function will temporarily change the MIME
+   content types of the body parts containing PGP data; this is similar
+   to the <edit-type> function's effect.
 
-                8. Mailbox Formats
+   <display-toggle-weed> (default: h)
 
-                9. Mailbox Shortcuts
+   Toggles the weeding of message header fields specified by iiggnnoorree
+   commands.
 
-                10. Handling Mailing Lists
+   <edit> (default: e)
 
-                11. Editing threads
+   This command (available in the ``index'' and ``pager'') allows you to
+   edit the raw current message as it's present in the mail folder. After
+   you have finished editing, the changed message will be appended to the
+   current folder, and the original message will be marked for deletion.
 
-                             11.1. Linking threads
+   <edit-type> (default: ) (default: C-E on the attachment menu, and in
+   the pager and index menus; C-T on the compose menu)
 
-                             11.2. Breaking threads
+   This command is used to temporarily edit an attachment's content type
+   to fix, for instance, bogus character set parameters. When invoked
+   from the index or from the pager, you'll have the opportunity to edit
+   the top-level attachment's content type. On the aattttaacchh--mmeennuu, you can
+   change any attachment's content type. These changes are not
+   persistent, and get lost upon changing folders.
 
-                12. Delivery Status Notification (DSN) Support
+   Note that this command is also available on the ccoommppoossee--mmeennuu .There,
+   it's used to fine-tune the properties of attachments you are going to
+   send.
 
-                13. POP3 Support (OPTIONAL)
+   <enter-command> (default: :)
 
-                14. IMAP Support (OPTIONAL)
+   This command is used to execute any command you would normally put in
+   a configuration file. A common use is to check the settings of
+   variables, or in conjunction with mmaaccrroo to change settings on the fly.
 
-                             14.1. The Folder Browser
+   <extract-keys> (default: C-K)
 
-                             14.2. Authentication
+   This command extracts PGP public keys from the current or tagged
+   message(s) and adds them to your PGP public key ring.
 
-                15. NNTP Support (OPTIONAL)
+   <forget-passphrase> (default: C-F)
 
-                             15.1. Again: Scoring
+   This command wipes the passphrase(s) from memory. It is useful, if you
+   misspelled the passphrase.
 
-                16. SMTP Support (OPTIONAL)
+   <list-reply> (default: L)
 
-                17. Managing multiple IMAP/POP/NNTP accounts (OPTIONAL)
+   Reply to the current or tagged message(s) by extracting any addresses
+   which match the regular expressions given by the lliissttss commands, but
+   also honor any Mail-Followup-To header(s) if the $$hhoonnoorr__ffoolllloowwuupp__ttoo
+   configuration variable is set. Using this when replying to messages
+   posted to mailing lists helps avoid duplicate copies being sent to the
+   author of the message you are replying to.
 
-                18. Start a WWW Browser on URLs (EXTERNAL)
+   <pipe-message> (default: )
 
-                19. Compressed folders Support (OPTIONAL)
+   Asks for an external Unix command and pipes the current or tagged
+   message(s) to it. The variables $$ppiippee__ddeeccooddee, $$ppiippee__sspplliitt,
+   $$ppiippee__ddeeccooddee and $$wwaaiitt__kkeeyy control the exact behavior of this
+   function.
 
-                             19.1. Open a compressed mailbox for reading
+   <resend-message> (default: E-e)
 
-                             19.2. Write a compressed mailbox
+   With resend-message, mutt takes the current message as a template for
+   a new message. This function is best described as "recall from
+   arbitrary folders". It can conveniently be used to forward MIME
+   messages while preserving the original mail structure. Note that the
+   amount of headers included here depends on the value of the $$wweeeedd
+   variable.
 
-                             19.3. Append a message to a compressed mailbox
+   This function is also available from the attachment menu. You can use
+   this to easily resend a message which was included with a bounce
+   message as a message/rfc822 body part.
 
-                             19.4. Encrypted folders
+   <shell-escape> (default: !)
 
-   5. Mutt-ng's MIME Support
+   Asks for an external Unix command and executes it. The $$wwaaiitt__kkeeyy can
+   be used to control whether Mutt-ng will wait for a key to be pressed
+   when the command returns (presumably to let the user read the output
+   of the command), based on the return status of the named command.
 
-                1. Using MIME in Mutt
+   <toggle-quoted> (default: T)
 
-                             1.1. Viewing MIME messages in the pager
+   The _p_a_g_e_r uses the $$qquuoottee__rreeggeexxpp variable to detect quoted text when
+   displaying the body of the message. This function toggles the
+   displayof the quoted material in the message. It is particularly
+   useful when are interested in just the response and there is a large
+   amount of quoted text in the way.
 
-                             1.2. The Attachment Menu
+   <skip-quoted> (default: S)
 
-                             1.3. The Compose Menu
+   This function will go to the next line of non-quoted text which come
+   after a line of quoted text in the internal pager.
 
-                2. MIME Type configuration with mime.types
+6. Sending Mail
 
-                3. MIME Viewer configuration with mailcap
+   The following bindings are available in the _i_n_d_e_x for sending
+   messages.
 
-                             3.1. The Basics of the mailcap file
+   _T_a_b_l_e_ _2_._8_._ _M_o_s_t_ _c_o_m_m_o_n_l_y_ _u_s_e_d_ _M_a_i_l_ _C_o_m_p_o_s_i_t_i_o_n_ _B_i_n_d_i_n_g_s
+   Key Function      Description
+   m   <compose>     compose a new message
+   r   <reply>       reply to sender
+   g   <group-reply> reply to all recipients
+   L   <list-reply>  reply to mailing list address
+   f   <forward>     forward message
+   b   <bounce>      bounce (remail) message
+   E-k <mail-key>    mail a PGP public key to someone
 
-                             3.2. Secure use of mailcap
+   Bouncing a message sends the message as is to the recipient you
+   specify. Forwarding a message allows you to add comments or modify the
+   message you are forwarding. These items are discussed in greater
+   detail in the next chapter ffoorrwwaarrddiinngg--mmaaiill.
 
-                             3.3. Advanced mailcap Usage
+6.1. Composing new messages
 
-                             3.4. Example mailcap files
+   When you want to send an email using mutt-ng, simply press m on your
+   keyboard. Then, mutt-ng asks for the recipient via a prompt in the
+   last line:
 
-                4. MIME Autoview
+To:
 
-                5. MIME Multipart/Alternative
+   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, press return after you've entered it. After that,
+   mutt-ng got the most important information from you, and starts up an
+   editor where you can then enter your email.
 
-                6. Attachment Searching and Counting
+   The editor that is called is selected in the following way: you can
+   e.g. set it in the mutt-ng configuration:
 
-                7. MIME Lookup
+set editor = "vim +/^$/ -c ':set tw=72'"
+set editor = "nano"
+set editor = "emacs"
 
-   6. Security Considerations
+   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 takes its value if it is set. If no editor command can be
+   found, mutt-ng simply assumes vi(1) to be the default editor, since
+   it's the most widespread editor in the Unix world and it's pretty safe
+   to assume that it is installed and available.
+
+   When you've finished entering your message, save it and quit your
+   editor. Mutt-ng will then present you with a summary screen, the
+   compose menu. On the top, you see a summary of the most important
+   available key commands. Below that, you see the sender, the
+   recipient(s), Cc and/or Bcc recipient(s), the subject, the reply-to
+   address, and optionally information where the sent email will be
+   stored and whether it should be digitally signed and/or encrypted.
+
+   Below that, you see a list of "attachments". The mail you've just
+   entered before is also an attachment, but due to its special type
+   (it's plain text), it will be displayed as the normal message on the
+   receiver's side.
+
+   At this point, you can add more attachments, pressing a, you can edit
+   the recipient addresses, pressing t for the "To:" field, c for the
+   "Cc:" field, and b for the "Bcc: field. You can also edit the subject
+   the subject by simply pressing s or the email message that you've
+   entered before by pressing e. You will then again return to the
+   editor. You can even edit the sender, by pressing <esc>f, but this
+   shall only be used with caution.
+
+   Alternatively, you can configure mutt-ng in a way that most of the
+   above settings can be edited using the editor. Therefore, you only
+   need to add the following to your configuration:
+
+set edit_headers
 
-                1. Passwords
+   Once you have finished editing the body of your mail message, you are
+   returned to the _c_o_m_p_o_s_e menu. The following options are available:
 
-                2. Temporary Files
+   _T_a_b_l_e_ _2_._9_._ _M_o_s_t_ _c_o_m_m_o_n_l_y_ _u_s_e_d_ _C_o_m_p_o_s_e_ _M_e_n_u_ _B_i_n_d_i_n_g_s
+   Key Function            Description
+   a   <attach-file>       attach a file
+   A   <attach-message>    attach message(s) to the message
+   E-k <attach-key>        attach a PGP public key
+   d   <edit-description>  edit description on attachment
+   D   <detach-file>       detach a file
+   t   <edit-to>           edit the To field
+   E-f <edit-from>         edit the From field
+   r   <edit-reply-to>     edit the Reply-To field
+   c   <edit-cc>           edit the Cc field
+   b   <edit-bcc>          edit the Bcc field
+   y   <send-message>      send the message
+   s   <edit-subject>      edit the Subject
+   S   <smime-menu>        select S/MIME options
+   f   <edit-fcc>          specify an ``Fcc'' mailbox
+   p   <pgp-menu>          select PGP options
+   P   <postpone-message>  postpone this message until later
+   q   <quit>              quit (abort) sending the message
+   w   <write-fcc>         write the message to a folder
+   i   <ispell>            check spelling (if available on your system)
+   C-F <forget-passphrase> wipe passphrase(s) from memory
 
-                3. Information Leaks
+   _N_o_t_e_: The attach-message function will prompt you for a folder to
+   attach messages from. You can now tag messages in that folder and
+   theywill be attached to the message you are sending. Note that
+   certainoperations like composing a new mail, replying, forwarding,
+   etc. are not permitted when you are in that folder. The %r in
+   $$ssttaattuuss__ffoorrmmaatt will change to a 'A' to indicate that you are in
+   attach-message mode.
+
+6.2. Replying
+
+6.2.1. Simple Replies
+
+   When you want to reply to an email message, select it in the index
+   menu and then press r. Mutt-ng's behaviour is then similar to the
+   behaviour when you compose a message: first, you will be asked for the
+   recipient, then for the subject, and then, mutt-ng will start the
+   editor with the quote attribution and the quoted message. This can
+   e.g. look like the example below.
+
+On Mon, Mar 07, 2005 at 05:02:12PM +0100, Michael Svensson wrote:
+> Bill, can you please send last month's progress report to Mr.
+> Morgan? We also urgently need the cost estimation for the new
+> 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 _b_e_l_o_w the quoted text and to only quote what is really
+   necessary and that you refer to. Putting your answer on top of the
+   quoted message, is, although very widespread, very often not
+   considered to be a polite way to answer emails.
 
-                             3.1. Message-ID: headers
+   The quote attribution is configurable, by default it is set to
+set attribution = "On %d, %n wrote:"
 
-                             3.2. mailto:-style links
+   It can also be set to something more compact, e.g.
+set attribution = "attribution="* %n <%a> [%(%y-%m-%d %H:%M)]:"
 
-                4. External applications
+   The example above results in the following attribution:
+* Michael Svensson <svensson@foobar.com> [05-03-06 17:02]:
+> Bill, can you please send last month's progress report to Mr.
+> Morgan? We also urgently need the cost estimation for the new
+> production server that we want to set up before our customer's
+> project will go live.
 
-                             4.1. mailcap
+   Generally, try to keep your attribution short yet information-rich. It
+   is _n_o_t the right place for witty quotes, long "attribution" novels or
+   anything like that: the right place for such things is - if at all -
+   the email signature at the very bottom of the message.
 
-                             4.2. Other
+   When you're done with writing your message, save and quit the editor.
+   As before, you will return to the compose menu, which is used in the
+   same way as before.
 
-   7. Reference
+6.2.2. Group Replies
 
-                1. Command line options
+   In the situation where a group of people uses email as a discussion,
+   most of the emails will have one or more recipients, and probably
+   several "Cc:" recipients. The group reply functionalityensures that
+   when you press g instead of r to do a reply, each and every recipient
+   that is contained in the original message will receive a copy of the
+   message, either as normal recipient or as "Cc:" recipient.
 
-                2. Patterns
+6.2.3. List Replies
 
-                3. Configuration Commands
+   When you use mailing lists, it's generally better to send your reply
+   to a message only to the list instead of the list and the original
+   author. To make this easy to use, mutt-ng features list replies.
 
-                4. Configuration variables
+   To do a list reply, simply press L. If the email contains a
+   Mail-Followup-To: header, its value will be used as reply address.
+   Otherwise, mutt-ng searches through all mail addresses in the original
+   message and tries to match them a list of regular expressions which
+   can be specified using the lists command. If any of the regular
+   expression matches, a mailing list address has been found, and it will
+   be used as reply address.
 
-                5. Functions
+lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@
 
-                             5.1. generic
+   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.
 
-                             5.2. index
+6.3. Editing the message header
 
-                             5.3. pager
+   When editing the header of your outgoing message, there are a couple
+   of special features available.
 
-                             5.4. alias
+   If you specify Fcc:_f_i_l_e_n_a_m_e Mutt-ng will pick up _f_i_l_e_n_a_m_e just as if
+   you had used the _e_d_i_t_-_f_c_c function in the _c_o_m_p_o_s_e menu.
 
-                             5.5. query
+   You can also attach files to your message by specifying
+Attach: filename [description]
 
-                             5.6. attach
+   where _f_i_l_e_n_a_m_e is the file to attach and _d_e_s_c_r_i_p_t_i_o_n is an optional
+   string to use as the description of the attached file.
 
-                             5.7. compose
+   When replying to messages, if you remove the _I_n_-_R_e_p_l_y_-_T_o_: field from
+   the header field, Mutt-ng will not generate a _R_e_f_e_r_e_n_c_e_s_: field, which
+   allows you to create a new message thread.
 
-                             5.8. postpone
+   Also see the $$eeddiitt__hheeaaddeerrss and $$eeddiittoorr__hheeaaddeerrss variables
 
-                             5.9. browser
+6.4. Using Mutt-ng with PGP
 
-                             5.10. pgp
+   If you want to use PGP, you can specify
+Pgp: [E | S | S id]
 
-                             5.11. editor
+   ``E'' encrypts, ``S'' signs and ``S<id>'' signs with the given key,
+   setting $$ppggpp__ssiiggnn__aass permanently.
 
-                             5.12. sidebar
+   If you have told mutt to PGP encrypt a message, it will guide you
+   through a key selection process when you try to send the message.
+   Mutt-ng will not ask you any questions about keys which have a
+   certified user ID matching one of the message recipients' mail
+   addresses. However, there may be situations in which there are several
+   keys, weakly certified user ID fields, or where no matching keys can
+   be found.
 
-   A. Acknowledgments
+   In these cases, you are dropped into a menu with a list of keys from
+   which you can select one. When you quit this menu, or mutt can't find
+   any matching keys, you are prompted for a user ID. You can, as
+   usually, abort this prompt using C-G. When you do so, mutt will return
+   to the compose screen.
 
-   B. Hacking Documentation
+   Once you have successfully finished the key selection, the message
+   will be encrypted using the selected public keys, and sent out.
 
-   Index
+   Most fields of the entries in the key selection menu (see also
+   $$ppggpp__eennttrryy__ffoorrmmaatt) have obvious meanings. But some explanations on the
+   capabilities, flags, and validity fields are in order.
 
-   List of Tables
+   The flags sequence (%f) will expand to one of the following flags:
 
-   2.1. Most commonly used movement bindings
+   _T_a_b_l_e_ _2_._1_0_._ _P_G_P_ _K_e_y_ _M_e_n_u_ _F_l_a_g_s
+   Flag Description
+   R    The key has been revoked and can't be used.
+   X    The key is expired and can't be used.
+   d    You have marked the key as disabled.
+   c    There are unknown critical self-signature packets.
 
-   2.2. Line Editor Functions
+   The capabilities field (%c) expands to a two-character
+   sequencerepresenting a key's capabilities. The first character gives
+   the key's encryption capabilities: A minus sign (_- )means that the key
+   cannot be used for encryption. A dot (_. )means that it's marked as a
+   signature key in one of the user IDs, but may also be used for
+   encryption. The letter _e indicates that this key can be used for
+   encryption.
+
+   The second character indicates the key's signing capabilities. Once
+   again, a ``_-'' implies ``not for signing'', ``_.'' implies that the key
+   is marked as an encryption key in one of the user-ids, and ``_s''
+   denotes a key which can be used for signing.
+
+   Finally, the validity field (%t) indicates how well-certified a
+   user-id is. A question mark (_?) indicates undefined validity, a minus
+   character (_-) marks an untrusted association, a space character means
+   a partially trusted association, and a plus character (_+ ) indicates
+   complete validity.
+
+6.5. Sending anonymous messages via mixmaster
 
-   2.3. Most commonly used Index Bindings
+   You may also have configured mutt to co-operate with Mixmaster, an
+   anonymous remailer. Mixmaster permits you to send your messages
+   anonymously using a chain of remailers. Mixmaster support in mutt is
+   for mixmaster version 2.04 (beta 45 appears to be the latest) and
+   2.03. It does not support earlier versions or the later so-called
+   version 3 betas, of which the latest appears to be called 2.9b23.
 
-   2.4. Most commonly used Pager Bindings
+   To use it, you'll have to obey certain restrictions. Most important,
+   you cannot use the Cc and Bcc headers. To tell Mutt-ng to use
+   mixmaster, you have to select a remailer chain, using the mix function
+   on the compose menu.
 
-   2.5. ANSI Escape Sequences
+   The chain selection screen is divided into two parts. In the (larger)
+   upper part, you get a list of remailers you may use. In the lower
+   part, you see the currently selected chain of remailers.
 
-   2.6. ANSI Colors
+   You can navigate in the chain using the chain-prev and chain-next
+   functions, which are by default bound to the left and right arrows and
+   to the h and l keys (think vi keyboard bindings). To insert a remailer
+   at the current chain position, use the insert function. To append a
+   remailer behind the current chain position, use select-entry or append
+   . You can also delete entries from the chain, using the corresponding
+   function. Finally, to abandon your changes, leave the menu, or accept
+   them pressing (by default) the Return key.
+
+   Note that different remailers do have different capabilities,
+   indicated in the %c entry of the remailer menu lines (see
+   $$mmiixx__eennttrryy__ffoorrmmaatt). Most important is the ``middleman'' capability,
+   indicated by a capital ``M'': This means that the remailer in question
+   cannot be used as the final element of a chain, but will only forward
+   messages to other mixmaster remailers. For details on the other
+   capabilities, please have a look at the mixmaster documentation.
 
-   2.7. Most commonly used thread-related bindings
+7. Forwarding and Bouncing Mail
 
-   2.8. Most commonly used Mail Composition Bindings
+   Often, it is necessary to forward mails to other people. Therefore,
+   mutt-ng supports forwarding messages in two different ways.
 
-   2.9. Most commonly used Compose Menu Bindings
+   The first one is regular forwarding, as you probably know it from
+   other mail clients. You simply press f, enter the recipient email
+   address, the subject of the forwarded email, and then you can edit the
+   message to be forwarded in the editor. The forwarded message is
+   separated from the rest of the message via the two following markers:
 
-   2.10. PGP Key Menu Flags
+----- Forwarded message from Lucas User <luser@example.com> -----
 
-   3.1. Alternative Key Names
+From: Lucas User <luser@example.com>
+Date: Thu, 02 Dec 2004 03:08:34 +0100
+To: Michael Random <mrandom@example.com>
+Subject: Re: blackmail
 
-   7.1. Reference: Command Line Options
+Pay me EUR 50,000.- cash or your favorite stuffed animal will die
+a horrible death.
 
-   7.2. Reference: Patterns
+----- End forwarded message -----
 
-   7.3. Reference: Obsolete Variables
+   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.
 
-   7.4. Reference: Default Generic Function Bindings
+   The second mode of forwarding emails with mutt-ng is the so-called
+   _b_o_u_n_c_i_n_g: when you bounce an email to another address, it will be sent
+   in practically the same format you send it (except for headers that
+   are created during transporting the message). To bounce a message,
+   press b and enter the recipient email address. By default, you are
+   then asked whether you really want to bounce the message to the
+   specified recipient. If you answer with yes, the message will then be
+   bounced.
 
-   7.5. Reference: Default Index Function Bindings
+   To the recipient, the bounced email will look as if he got it like a
+   regular email where he was Bcc: recipient. The only possibility to
+   find out whether it was a bounced email is to carefully study the
+   email headers and to find out which host really sent the email.
 
-   7.6. Reference: Default Pager Function Bindings
+8. Postponing Mail
 
-   7.7. Reference: Default Alias Menu Function Bindings
+   At times it is desirable to delay sending a message that you have
+   already begun to compose. When the _p_o_s_t_p_o_n_e_-_m_e_s_s_a_g_e function is used
+   in the _c_o_m_p_o_s_e menu, the body of your message and attachments are
+   stored in the mailbox specified by the $$ppoossttppoonneedd variable. This means
+   that you can recall the message even if you exit Mutt-ng and then
+   restart it at a later time.
 
-   7.8. Reference: Default Query Menu Function Bindings
+   Once a message is postponed, there are several ways to resume it. From
+   the command line you can use the ``-p'' option, or if you _c_o_m_p_o_s_e a
+   new message from the _i_n_d_e_x or _p_a_g_e_r you will be prompted if postponed
+   messages exist. If multiple messages are currently postponed, the
+   _p_o_s_t_p_o_n_e_d menu will pop up and you can select which message you would
+   like to resume.
 
-   7.9. Reference: Default Attachment Menu Function Bindings
+   _N_o_t_e_: If you postpone a reply to a message, the reply setting of the
+   message is only updated when you actually finish the message and send
+   it. Also, you must be in the same folder with the message you replied
+   to for the status of the message to be updated.
 
-   7.10. Reference: Default Compose Menu Function Bindings
+   See also the $$ppoossttppoonnee quad-option.
 
-   7.11. Reference: Default Postpone Menu Function Bindings
+Chapter 3. Configuration
 
-   7.12. Reference: Default Browser Menu Function Bindings
+   _T_a_b_l_e_ _o_f_ _C_o_n_t_e_n_t_s
+
+   11..  LLooccaattiioonnss  ooff  CCoonnffiigguurraattiioonn  FFiilleess
+   22..  BBaassiicc  SSyynnttaaxx  ooff  IInniittiiaalliizzaattiioonn  FFiilleess
+   33..  EExxppaannssiioonn  wwiitthhiinn  vvaarriiaabblleess
+
+        33..11..  CCoommmmaannddss''  OOuuttppuutt
+        33..22..  EEnnvviirroonnmmeenntt  VVaarriiaabblleess
+        33..33..  CCoonnffiigguurraattiioonn  VVaarriiaabblleess
+        33..44..  SSeellff--DDeeffiinneedd  VVaarriiaabblleess
+        33..55..  PPrree--DDeeffiinneedd  VVaarriiaabblleess
+        33..66..  TTyyppee  CCoonnvveerrssiioonnss
+
+   44..  DDeeffiinniinngg//UUssiinngg  aalliiaasseess
+   55..  CChhaannggiinngg  tthhee  ddeeffaauulltt  kkeeyy  bbiinnddiinnggss
+   66..  DDeeffiinniinngg  aalliiaasseess  ffoorr  cchhaarraacctteerr  sseettss
+   77..  SSeettttiinngg  vvaarriiaabblleess  bbaasseedd  uuppoonn  mmaaiillbbooxx
+   88..  KKeeyybbooaarrdd  mmaaccrrooss
+   99..  UUssiinngg  ccoolloorr  aanndd  mmoonnoo  vviiddeeoo  aattttrriibbuutteess
+   1100..  IIggnnoorriinngg  ((wweeeeddiinngg))  uunnwwaanntteedd  mmeessssaaggee  hheeaaddeerrss
+   1111..  AAlltteerrnnaattiivvee  aaddddrreesssseess
+   1122..  FFoorrmmaatt  ==  FFlloowweedd
+
+        1122..11..  IInnttrroodduuccttiioonn
+        1122..22..  RReecceeiivviinngg::  DDiissppllaayy  SSeettuupp
+        1122..33..  SSeennddiinngg
+        1122..44..  AAddddiittiioonnaall  NNootteess
+
+   1133..  MMaaiilliinngg  lliissttss
+   1144..  UUssiinngg  MMuullttiippllee  ssppooooll  mmaaiillbbooxxeess
+   1155..  DDeeffiinniinngg  mmaaiillbbooxxeess  wwhhiicchh  rreecceeiivvee  mmaaiill
+   1166..  UUsseerr  ddeeffiinneedd  hheeaaddeerrss
+   1177..  DDeeffiinniinngg  tthhee  oorrddeerr  ooff  hheeaaddeerrss  wwhheenn  vviieewwiinngg  mmeessssaaggeess
+   1188..  SSppeecciiffyy  ddeeffaauulltt  ssaavvee  ffiilleennaammee
+   1199..  SSppeecciiffyy  ddeeffaauulltt  FFcccc::  mmaaiillbbooxx  wwhheenn  ccoommppoossiinngg
+   2200..  SSppeecciiffyy  ddeeffaauulltt  ssaavvee  ffiilleennaammee  aanndd  ddeeffaauulltt  FFcccc::  mmaaiillbbooxx  aatt  oonnccee
+   2211..  CChhaannggee  sseettttiinnggss  bbaasseedd  uuppoonn  mmeessssaaggee  rreecciippiieennttss
+   2222..  CChhaannggee  sseettttiinnggss  bbeeffoorree  ffoorrmmaattttiinngg  aa  mmeessssaaggee
+   2233..  CChhoooossiinngg  tthhee  ccrryyppttooggrraapphhiicc  kkeeyy  ooff  tthhee  rreecciippiieenntt
+   2244..  AAddddiinngg  kkeeyy  sseeqquueenncceess  ttoo  tthhee  kkeeyybbooaarrdd  bbuuffffeerr
+   2255..  EExxeeccuuttiinngg  ffuunnccttiioonnss
+   2266..  MMeessssaaggee  SSccoorriinngg
+   2277..  SSppaamm  ddeetteeccttiioonn
+   2288..  SSeettttiinngg  vvaarriiaabblleess
+   2299..  RReeaaddiinngg  iinniittiiaalliizzaattiioonn  ccoommmmaannddss  ffrroomm  aannootthheerr  ffiillee
+   3300..  RReemmoovviinngg  hhooookkss
+   3311..  SShhaarriinngg  SSeettuuppss
+
+        3311..11..  CChhaarraacctteerr  SSeettss
+        3311..22..  MMoodduullaarriizzaattiioonn
+        3311..33..  CCoonnddiittiioonnaall  ppaarrttss
+
+   3322..  OObbssoolleettee  VVaarriiaabblleess
 
-   7.13. Reference: Default PGP Menu Function Bindings
+1. Locations of Configuration Files
 
-   7.14. Reference: Default Editor Function Bindings
+   While the default configuration (or ``preferences'') make Mutt-ng
+   usable right out of the box, it is often desirable to tailor Mutt-ng
+   to suit your own tastes. When Mutt-ng is first invoked, it will
+   attempt to read the ``system'' configuration file (defaults set by
+   your local system administrator), unless the ``-n'' ccoommmmaannddlliinnee option
+   is specified. This file is typically /usr/local/share/muttng/Muttngrc
+   or /etc/Muttngrc , Mutt-ng users will find this file in
+   /usr/local/share/muttng/Muttrc or /etc/Muttngrc. Mutt will next look
+   for a file named .muttrc in your home directory, Mutt-ng will look for
+   .muttngrc. If this file does not exist and your home directory has a
+   subdirectory named .mutt , mutt try to load a file named
+   .muttng/muttngrc.
 
-   7.15. Referene: Default Sidebar Function Bindings
+   .muttrc (or .muttngrc for Mutt-ng) is the file where you will usually
+   place your ccoommmmaannddss to configure Mutt-ng.
 
-Chapter 1. Introduction
+2. Basic Syntax of Initialization Files
 
-   Table of Contents
+   An initialization file consists of a series of ccoommmmaannddss. Each line of
+   the file may contain one or more commands. When multiple commands are
+   used, they must be separated by a semicolon (;).
+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 that a single quote is used to specify a
+   literal string (one that is not interpreted for shell variables or
+   quoting with a backslash (see next paragraph), while double quotes
+   indicate a string for which should be evaluated. For example, backtics
+   are evaluated inside of double quotes, but _n_o_t for single quotes.
+
+   \ quotes the next character, just as in shells such as bash and zsh.
+   For example, if want to put quotes ``"'' inside of a string, you can
+   use ``\'' to force the next character to be a literal instead of
+   interpreted character.
+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.
 
-   1. Overview
+   A \ at the end of a line can be used to split commands over multiple
+   lines, provided that the split points don't appear in the middle of
+   command names.
 
-   2. Mutt-ng Home Page
+   Please note that, unlike the various shells, mutt-ng interprets a
+   ``\'' at the end of a line also in comments. This allows you to
+   disable a command split over multiple lines with only one ``#''.
 
-   3. Mailing Lists
+# folder-hook . \
+set realname="Michael \"MuttDude\" Elkins"
 
-   4. Software Distribution Sites
+   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 commented with a hash (#) all following continuation
+   lines are also part of a comment and therefore are ignored, too. So
+   take care of comments when continuation lines are involved within your
+   setup files!
 
-   5. IRC
+   Abstract example:
 
-   6. Weblog
+line1\
+line2a # line2b\
+line3\
+line4
+line5
 
-   7. Copyright
+   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.
 
-   8. Manual Conventions
+   The commands understood by mutt are explained in the next paragraphs.
+   For a complete list, see the ccoommmmaannddss.
 
-1. Overview
+3. Expansion within variables
 
-   Mutt-ng is a small but very powerful text-based MIME mail client. Mutt-ng
-   is highly configurable, and is well suited to the mail power user with
-   advanced features like key bindings, keyboard macros, mail threading,
-   regular expression searches and a powerful pattern matching language for
-   selecting groups of messages.
+   Besides just assign static content to variables, there's plenty of
+   ways of adding external and more or less dynamic content.
 
-   This documentation additionally contains documentation to Mutt-NG ,a fork
-   from Mutt with the goal to fix all the little annoyances of Mutt, to
-   integrate all the Mutt patches that are floating around in the web, and to
-   add other new features. Features specific to Mutt-ng will be discussed in
-   an extra section. Don't be confused when most of the documentation talk
-   about Mutt and not Mutt-ng, Mutt-ng contains all Mutt features, plus many
-   more.
+3.1. Commands' Output
 
-2. Mutt-ng Home Page
+   It is possible to substitute the output of a Unix command in an
+   initialization file. This is accomplished by enclosing the command in
+   backquotes (``) as in, for example:
 
-   <http://www.muttng.org/>
+my_hdr X-Operating-System: `uname -a`
 
-3. Mailing Lists
+   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.
 
-     o <mutt-ng-users@lists.berlios.de>: This is where the mutt-ng user
-       support happens.
+3.2. Environment Variables
 
-     o <mutt-ng-devel@lists.berlios.de>: The development mailing list for
-       mutt-ng
+   UNIX environments can be accessed like the way it is done in shells
+   like sh and bash: Prepend the name of the environment by a ``$'' sign.
+   For example,
 
-4. Software Distribution Sites
-
-   So far, there are no official releases of Mutt-ng, but you can download
-   daily snapshots from <http://mutt-ng.berlios.de/snapshots/>
-
-5. IRC
-
-   Visit channel #muttng on irc.freenode.net (www.freenode.net) to chat with
-   other people interested in Mutt-ng.
-
-6. Weblog
-
-   If you want to read fresh news about the latest development in Mutt-ng,
-   and get informed about stuff like interesting, Mutt-ng-related articles
-   and packages for your favorite distribution, you can read and/or subscribe
-   to our Mutt-ng development weblog.
-
-7. Copyright
-
-   Mutt is Copyright (C) 1996-2000 Michael R. Elkins <me@cs.hmc.edu> and
-   others
-
-   This program is free software; you can redistribute it and/or modify it
-   under the terms of the GNU General Public License as published by the Free
-   Software Foundation; either version 2 of the License, or (at your option)
-   any later version.
-
-   This program is distributed in the hope that it will be useful, but
-   WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
-   or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
-   for more details.
-
-   You should have received a copy of the GNU General Public License along
-   with this program; if not, write to the Free Software Foundation, Inc., 51
-   Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-
-8. Manual Conventions
-
-   This manual contains several (hopefully consistent) conventions to
-   specially layout different items in different fashions.
-
-     o Configuration and environment variables will be printed in a
-       typewriter font and both prefixed with a dollar sign as it's common
-       for UNIX-like environments. Configuration variables are lower-case
-       only while environment variables are upper-case only. $imap_mail_check
-       is a configuration variable while $EDITOR is an environment variable.
-
-     o Muttng-specific functions are enclosed in <> and printed in a
-       typewriter font, too, as in <sync-mailbox>.
-
-     o As common for UNIX-like environments, references to manual pages are
-       printed with the section enclosed in braces, as in vi(1) or
-       muttngrc(5). Execute man [section] [name] to view the manual page.
-
-     o Keys are presented in the following way: ordinary keys are just given
-       as-is, e.g. q. Control characters are prefixed with C- (e.g. the
-       screen can be redraw by pressing C-L) and E- for Escape, e.g. a folder
-       can be opened read-only with E-c.
-
-   If, while reading this fine manual, you find any inconsistencies of
-   whatever kind, please contact the developers via
-   <mutt-ng-devel@lists.berlios.de> to report it.
-
-Chapter 2. Getting Started
-
-   Table of Contents
-
-   1. Basic Concepts
-
-                1.1. Screens and Menus
-
-                1.2. Configuration
-
-                1.3. Functions
-
-                1.4. Interaction
-
-                1.5. Modularization
-
-                1.6. Patterns
-
-   2. Screens and Menus
-
-                2.1. Index
-
-                2.2. Pager
-
-                2.3. File Browser
-
-                2.4. Sidebar
-
-                2.5. Help
-
-                2.6. Compose Menu
-
-                2.7. Alias Menu
-
-                2.8. Attachment Menu
-
-                2.9. Key Menu
-
-   3. Moving Around in Menus
-
-   4. Editing Input Fields
-
-   5. Reading Mail - The Index and Pager
-
-                5.1. The Message Index
-
-                5.2. The Pager
-
-                5.3. Threaded Mode
-
-                5.4. Miscellaneous Functions
-
-   6. Sending Mail
-
-                6.1. Composing new messages
-
-                6.2. Replying
-
-                6.3. Editing the message header
-
-                6.4. Using Mutt-ng with PGP
-
-                6.5. Sending anonymous messages via mixmaster
-
-   7. Forwarding and Bouncing Mail
-
-   8. Postponing Mail
-
-1. Basic Concepts
-
-  1.1. Screens and Menus
-
-   mutt-ng offers different screens of which every has its special purpose:
-
-     o The index displays the contents of the currently opened mailbox.
-
-     o The pager is responsible for displaying messages, that is, the header,
-       the body and all attached parts.
-
-     o The file browser offers operations on and displays information of all
-       folders mutt-ng should watch for mail.
-
-     o The sidebar offers a permanent view of which mailboxes contain how
-       many total, new and/or flagged mails.
-
-     o The help screen lists for all currently available commands how to
-       invoke them as well as a short description.
-
-     o The compose menu is a comfortable interface take last actions before
-       sending mail: change subjects, attach files, remove attachements, etc.
-
-     o The attachement menu gives a summary and the tree structure of the
-       attachements of the current message.
-
-     o The alias menu lists all or a fraction of the aliases a user has
-       defined.
-
-     o The key menu used in connection with encryption lets users choose the
-       right key to encrypt with.
-
-   When mutt-ng is started without any further options, it'll open the users
-   default mailbox and display the index.
-
-  1.2. Configuration
-
-   Mutt-ng does not feature an internal configuration interface or menu due
-   to the simple fact that this would be too complex to handle (currently
-   there are several hundred variables which fine-tune the behaviour.)
-
-   Mutt-ng is configured using configuration files which allow users to add
-   comments or manage them via version control systems to ease maintenance.
-
-   Also, mutt-ng comes with a shell script named grml-muttng kindly
-   contributed by users which really helps and eases the creation of a user's
-   configuration file. When downloading the source code via a snapshot or via
-   subversion, it can be found in the contrib directory.
-
-  1.3. Functions
-
-   Mutt-ng offers great flexibility due to the use of functions: internally,
-   every action a user can make mutt-ng perform is named ``function.'' Those
-   functions are assigned to keys (or even key sequences) and may be
-   completely adjusted to user's needs. The basic idea is that the impatient
-   users get a very intuitive interface to start off with and advanced users
-   virtually get no limits to adjustments.
-
-  1.4. Interaction
-
-   Mutt-ng has two basic concepts of user interaction:
-
-    1. There is one dedicated line on the screen used to query the user for
-       input, issue any command, query variables and display error and
-       informational messages. As for every type of user input, this requires
-       manual action leading to the need of input.
-
-    2. The automatized interface for interaction are the so called hooks.
-       Hooks specify actions the user wants to be performed at well-defined
-       situations: what to do when entering which folder, what to do when
-       displaying or replying to what kind of message, etc. These are
-       optional, i.e. a user doesn't need to specify them but can do so.
-
-  1.5. Modularization
-
-   Although mutt-ng has many functionality built-in, many features can be
-   delegated to external tools to increase flexibility: users can define
-   programs to filter a message through before displaying, users can use any
-   program they want for displaying a message, message types (such as PDF or
-   PostScript) for which mutt-ng doesn't have a built-in filter can be
-   rendered by arbitrary tools and so forth. Although mutt-ng has an alias
-   mechanism built-in, it features using external tools to query for nearly
-   every type of addresses from sources like LDAP, databases or just the list
-   of locally known users.
-
-  1.6. Patterns
-
-   Mutt-ng has a built-in pattern matching ``language'' which is as widely
-   used as possible to present a consistent interface to users. The same
-   ``pattern terms'' can be used for searching, scoring, message selection
-   and much more.
-
-2. Screens and Menus
-
-  2.1. Index
-
-   The index is the screen that you usually see first when you start mutt-ng.
-   It gives an overview over your emails in the currently opened mailbox. By
-   default, this is your system mailbox. The information you see in the index
-   is a list of emails, each with its number on the left, its flags (new
-   email, important email, email that has been forwarded or replied to,
-   tagged email, ...), the date when email was sent, its sender, the email
-   size, and the subject. Additionally, the index also shows thread
-   hierarchies: when you reply to an email, and the other person replies
-   back, you can see the other's person email in a "sub-tree" below. This is
-   especially useful for personal email between a group of people or when
-   you've subscribed to mailing lists.
-
-  2.2. Pager
-
-   The pager is responsible for showing the email content. On the top of the
-   pager you have an overview over the most important email headers like the
-   sender, the recipient, the subject, and much more information. How much
-   information you actually see depends on your configuration, which we'll
-   describe below.
-
-   Below the headers, you see the email body which usually contains the
-   message. If the email contains any attachments, you will see more
-   information about them below the email body, or, if the attachments are
-   text files, you can view them directly in the pager.
-
-   To give the user a good overview, it is possible to configure mutt-ng to
-   show different things in the pager with different colors. Virtually
-   everything that can be described with a regular expression can be colored,
-   e.g. URLs, email addresses or smileys.
-
-  2.3. File Browser
-
-   The file browser is the interface to the local or remote file system. When
-   selecting a mailbox to open, the browser allows custom sorting of items,
-   limiting the items shown by a regular expression and a freely adjustable
-   format of what to display in which way. It also allows for easy navigation
-   through the file system when selecting file(s) to attach to a message,
-   select multiple files to attach and many more.
-
-  2.4. Sidebar
-
-   The sidebar comes in handy to manage mails which are spread over different
-   folders. All folders users setup mutt-ng to watch for new mail will be
-   listed. The listing includes not only the name but also the number of
-   total messages, the number of new and flagged messages. Items with new
-   mail may be colored different from those with flagged mail, items may be
-   shortened or compress if they're they to long to be printed in full form
-   so that by abbreviated names, user still now what the name stands for.
-
-  2.5. Help
-
-   The help screen is meant to offer a quick help to the user. It lists the
-   current configuration of key bindings and their associated commands
-   including a short description, and currently unbound functions that still
-   need to be associated with a key binding (or alternatively, they can be
-   called via the mutt-ng command prompt).
-
-  2.6. Compose Menu
-
-   The compose menu features a split screen containing the information which
-   really matter before actually sending a message by mail or posting an
-   article to a newsgroup: who gets the message as what (recipient,
-   newsgroup, who gets what kind of copy). Additionally, users may set
-   security options like deciding whether to sign, encrypt or sign and
-   encrypt a message with/for what keys.
-
-   Also, it's used to attach messages, news articles or files to a message,
-   to re-edit any attachment including the message itself.
-
-  2.7. Alias Menu
-
-   The alias menu is used to help users finding the recipients of messages.
-   For users who need to contact many people, there's no need to remember
-   addresses or names completely because it allows for searching, too. The
-   alias mechanism and thus the alias menu also features grouping several
-   addresses by a shorter nickname, the actual alias, so that users don't
-   have to select each single recipient manually.
-
-  2.8. Attachment Menu
-
-   As will be later discussed in detail, mutt-ng features a good and stable
-   MIME implementation, that is, is greatly supports sending and receiving
-   messages of arbitrary type. The attachment menu displays a message's
-   structure in detail: what content parts are attached to which parent part
-   (which gives a true tree structure), which type is of what type and what
-   size. Single parts may saved, deleted or modified to offer great and easy
-   access to message's internals.
-
-  2.9. Key Menu
-
-   FIXME
-
-3. Moving Around in Menus
-
-   Information is presented in menus, very similar to ELM. Here is a
-   tableshowing the common keys used to navigate menus in Mutt-ng.
-
-   Table 2.1. Most commonly used movement bindings
-
-   Key         Function         Description
-   j or Down   <next-entry>     move to the next entry
-   k or Up     <previous-entry> move to the previous entry
-   z or PageDn <page-down>      go to the next page
-   Z or PageUp <page-up>        go to the previous page
-   = or Home   <first-entry>    jump to the first entry
-   * or End    <last-entry>     jump to the last entry
-   q           <quit>           exit the current menu
-   ?           <help>           list all key bindings for the current menu
-
-4. Editing Input Fields
-
-   Mutt-ng has a builtin line editor which is used as the primary way to
-   input textual data such as email addresses or filenames. The keys used to
-   move around while editing are very similar to those of Emacs.
-
-   Table 2.2. Line Editor Functions
-
-   Key           Function          Description
-   C-A or Home   <bol>             move to the start of the line
-   C-B or Left   <backward-char>   move back one char
-   E-B           <backward-word>   move back one word
-   C-D or Delete <delete-char>     delete the char under the cursor
-   C-E or End    <eol>             move to the end of the line
-   C-F or Right  <forward-char>    move forward one char
-   E-F           <forward-word>    move forward one word
-   Tab           <complete>        complete filename or alias
-   C-T           <complete-query>  complete address with query
-   C-K           <kill-eol>        delete to the end of the line
-   E-d           <kill-eow>        delete to the end of the word
-   C-W           <kill-word>       kill the word in front of the cursor
-   C-U           <kill-line>       delete entire line
-   C-V           <quote-char>      quote the next typed key
-   Up            <history-up>      recall previous string from history
-   Down          <history-down>    recall next string from history
-   BackSpace     <backspace>       kill the char in front of the cursor
-   E-u           <upcase-word>     convert word to upper case
-   E-l           <downcase-word>   convert word to lower case
-   E-c           <capitalize-word> capitalize the word
-   C-G                             abort
-   Return                          finish editing
-
-   You can remap the editor functions using the bind command. For example, to
-   make the Delete key delete the character in front of the cursor rather
-   than under, you could use
-
-   bind editor <delete> backspace
-
-5. Reading Mail - The Index and Pager
-
-   Similar to many other mail clients, there are two modes in which mail
-   isread in Mutt-ng. The first is the index of messages in the mailbox,
-   which is called the ``index'' in Mutt-ng. The second mode is the display
-   of the message contents. This is called the ``pager.''
-
-   The next few sections describe the functions provided in each of these
-   modes.
-
-  5.1. The Message Index
-
-   Table 2.3. Most commonly used Index Bindings
-
-   Key    Function Description
-   c               change to a different mailbox
-   E-c             change to a folder in read-only mode
-   C               copy the current message to another mailbox
-   E-C             decode a message and copy it to a folder
-   E-s             decode a message and save it to a folder
-   D               delete messages matching a pattern
-   d               delete the current message
-   F               mark as important
-   l               show messages matching a pattern
-   N               mark message as new
-   o               change the current sort method
-   O               reverse sort the mailbox
-   q               save changes and exit
-   s               save-message
-   T               tag messages matching a pattern
-   t               toggle the tag on a message
-   E-t             toggle tag on entire message thread
-   U               undelete messages matching a pattern
-   u               undelete-message
-   v               view-attachments
-   x               abort changes and exit
-   Return          display-message
-   Tab             jump to the next new or unread message
-   @               show the author's full e-mail address
-   $               save changes to mailbox
-   /               search
-   E-/             search-reverse
-   C-L             clear and redraw the screen
-   C-T             untag messages matching a pattern
-
-    5.1.1. Status Flags
-
-   In addition to who sent the message and the subject, a short summary of
-   the disposition of each message is printed beside the message number. Zero
-   or more of the following ``flags'' may appear, which mean:
-
-   D
-
-           message is deleted (is marked for deletion)
-
-   d
-
-           message have attachments marked for deletion
-
-   K
-
-           contains a PGP public key
-
-   N
-
-           message is new
-
-   O
-
-           message is old
-
-   P
-
-           message is PGP encrypted
-
-   r
-
-           message has been replied to
-
-   S
-
-           message is signed, and the signature is succesfully verified
-
-   s
-
-           message is signed
-
-   !
-
-           message is flagged
-
-   *
-
-           message is tagged
-
-   Some of the status flags can be turned on or off using
-
-     o set-flag (default: w)
-
-     o clear-flag (default: W)
-
-   Furthermore, the following flags reflect who the message is addressed to.
-   They can be customized with the $to_chars variable.
-
-   +
-
-           message is to you and you only
-
-   T
-
-           message is to you, but also to or cc'ed to others
-
-   C
-
-           message is cc'ed to you
-
-   F
-
-           message is from you
-
-   L
-
-           message is sent to a subscribed mailing list
-
-  5.2. The Pager
-
-   By default, Mutt-ng uses its builtin pager to display the body of
-   messages. The pager is very similar to the Unix program less though not
-   nearly as featureful.
-
-   Table 2.4. Most commonly used Pager Bindings
-
-   Key    Function Description
-   Return          go down one line
-   Space           display the next page (or next message if at the end of a
-                   message)
-   -               go back to the previous page
-   n               search for next match
-   S               skip beyond quoted text
-   T               toggle display of quoted text
-   ?               show key bindings
-   /               search for a regular expression (pattern)
-   E-/             search backwards for a regular expression
-   \               toggle search pattern coloring
-   ^               jump to the top of the message
-
-   In addition, many of the functions from the index are available in the
-   pager, such as delete-message or copy-message (this is one advantage over
-   using an external pager to view messages).
-
-   Also, the internal pager supports a couple other advanced features. For
-   one, it will accept and translate the ``standard'' nroff sequences forbold
-   and underline. These sequences are a series of either the letter,
-   backspace (C-H), the letter again for bold or the letter, backspace, _ for
-   denoting underline. Mutt-ng will attempt to display these in bold and
-   underline respectively if your terminal supports them. If not, you can use
-   the bold and underline color objects to specify a color or mono attribute
-   for them.
-
-   Additionally, the internal pager supports the ANSI escape sequences for
-   character attributes. Mutt-ng translates them into the correct color and
-   character settings. The sequences Mutt-ng supports are: ESC [
-   Ps;Ps;Ps;...;Ps m (see table below for possible values for Ps).
-
-   Table 2.5. ANSI Escape Sequences
-
-   Value Attribute
-   0     All Attributes Off
-   1     Bold on
-   4     Underline on
-   5     Blink on
-   7     Reverse video on
-   3x    Foreground color is x (see table below)
-   4x    Background color is x (see table below)
-
-   Table 2.6. ANSI Colors
-
-   Number Color
-   0      black
-   1      red
-   2      green
-   3      yellow
-   4      blue
-   5      magenta
-   6      cyan
-   7      white
-
-   Mutt-ng uses these attributes for handling text/enriched messages, and
-   they can also be used by an external auto_view script for highlighting
-   purposes. Note: If you change the colors for your display, for example by
-   changing the color associated with color2 for your xterm, then that color
-   will be used instead of green.
-
-  5.3. Threaded Mode
-
-   When the mailbox is sorted by threads ,there are a few additional
-   functions available in the index and pager modes.
-
-   Table 2.7. Most commonly used thread-related bindings
-
-   Key Function             Description
-   C-D <delete-thread>      delete all messages in the current thread
-   C-U <undelete-thread>    undelete all messages in the current thread
-   C-N <next-thread>        jump to the start of the next thread
-   C-P <previous-thread>    jump to the start of the previous thread
-   C-R <read-thread>        mark the current thread as read
-   E-d <delete-subthread>   delete all messages in the current subthread
-   E-u <undelete-subthread> undelete all messages in the current subthread
-   E-n <next-subthread>     jump to the start of the next subthread
-   E-p <previous-subthread> jump to the start of the previous subthread
-   E-r <read-subthread>     mark the current subthread as read
-   E-t <tag-thread>         toggle the tag on the current thread
-   E-v <collapse-thread>    toggle collapse for the current thread
-   E-V <collapse-all>       toggle collapse for all threads
-   P   <parent-message>     jump to parent message in thread
-
-   Note: Collapsing a thread displays only the first message in the thread
-   and hides the others. This is useful when threads contain so many messages
-   that you can only see a handful of threads onthe screen. See %M in
-   $index_format.
-
-   For example, you could use %?M?(#%03M)&(%4l)? in $index_format to
-   optionally display the number of hidden messages if the thread is
-   collapsed.
-
-   See also the $strict_threads variable.
-
-  5.4. Miscellaneous Functions
-
-   <create-alias> (default: a)
-
-   Creates a new alias based upon the current message (or prompts for a new
-   one). Once editing is complete, an alias command is added to the file
-   specified by the $alias_file variable for future use. Note: Specifying an
-   $alias_file does not add the aliases specified there-in, you must also
-   source the file.
-
-   <check-traditional-pgp> (default: E-P)
-
-   This function will search the current message for content signed or
-   encrypted with PGP the "traditional" way, that is, without proper MIME
-   tagging. Technically, this function will temporarily change the MIME
-   content types of the body parts containing PGP data; this is similar to
-   the <edit-type> function's effect.
-
-   <display-toggle-weed> (default: h)
-
-   Toggles the weeding of message header fields specified by ignore commands.
-
-   <edit> (default: e)
-
-   This command (available in the ``index'' and ``pager'') allows you to edit
-   the raw current message as it's present in the mail folder. After you have
-   finished editing, the changed message will be appended to the current
-   folder, and the original message will be marked for deletion.
-
-   <edit-type> (default: ) (default: C-E on the attachment menu, and in the
-   pager and index menus; C-T on the compose menu)
-
-   This command is used to temporarily edit an attachment's content type to
-   fix, for instance, bogus character set parameters. When invoked from the
-   index or from the pager, you'll have the opportunity to edit the top-level
-   attachment's content type. On the attach-menu, you can change any
-   attachment's content type. These changes are not persistent, and get lost
-   upon changing folders.
-
-   Note that this command is also available on the compose-menu .There, it's
-   used to fine-tune the properties of attachments you are going to send.
-
-   <enter-command> (default: :)
-
-   This command is used to execute any command you would normally put in a
-   configuration file. A common use is to check the settings of variables, or
-   in conjunction with macro to change settings on the fly.
-
-   <extract-keys> (default: C-K)
-
-   This command extracts PGP public keys from the current or tagged
-   message(s) and adds them to your PGP public key ring.
-
-   <forget-passphrase> (default: C-F)
-
-   This command wipes the passphrase(s) from memory. It is useful, if you
-   misspelled the passphrase.
-
-   <list-reply> (default: L)
-
-   Reply to the current or tagged message(s) by extracting any addresses
-   which match the regular expressions given by the lists commands, but also
-   honor any Mail-Followup-To header(s) if the $honor_followup_to
-   configuration variable is set. Using this when replying to messages posted
-   to mailing lists helps avoid duplicate copies being sent to the author of
-   the message you are replying to.
-
-   <pipe-message> (default: )
-
-   Asks for an external Unix command and pipes the current or tagged
-   message(s) to it. The variables $pipe_decode, $pipe_split, $pipe_decode
-   and $wait_key control the exact behavior of this function.
-
-   <resend-message> (default: E-e)
-
-   With resend-message, mutt takes the current message as a template for a
-   new message. This function is best described as "recall from arbitrary
-   folders". It can conveniently be used to forward MIME messages while
-   preserving the original mail structure. Note that the amount of headers
-   included here depends on the value of the $weed variable.
-
-   This function is also available from the attachment menu. You can use this
-   to easily resend a message which was included with a bounce message as a
-   message/rfc822 body part.
-
-   <shell-escape> (default: !)
-
-   Asks for an external Unix command and executes it. The $wait_key can be
-   used to control whether Mutt-ng will wait for a key to be pressed when the
-   command returns (presumably to let the user read the output of the
-   command), based on the return status of the named command.
-
-   <toggle-quoted> (default: T)
-
-   The pager uses the $quote_regexp variable to detect quoted text when
-   displaying the body of the message. This function toggles the displayof
-   the quoted material in the message. It is particularly useful when are
-   interested in just the response and there is a large amount of quoted text
-   in the way.
-
-   <skip-quoted> (default: S)
-
-   This function will go to the next line of non-quoted text which come after
-   a line of quoted text in the internal pager.
-
-6. Sending Mail
-
-   The following bindings are available in the index for sending messages.
-
-   Table 2.8. Most commonly used Mail Composition Bindings
-
-   Key Function      Description
-   m   <compose>     compose a new message
-   r   <reply>       reply to sender
-   g   <group-reply> reply to all recipients
-   L   <list-reply>  reply to mailing list address
-   f   <forward>     forward message
-   b   <bounce>      bounce (remail) message
-   E-k <mail-key>    mail a PGP public key to someone
-
-   Bouncing a message sends the message as is to the recipient you specify.
-   Forwarding a message allows you to add comments or modify the message you
-   are forwarding. These items are discussed in greater detail in the next
-   chapter forwarding-mail.
-
-  6.1. Composing new messages
-
-   When you want to send an email using mutt-ng, simply press m on your
-   keyboard. Then, mutt-ng asks for the recipient via a prompt in the last
-   line:
-
- 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,
-   press return after you've entered it. After that, mutt-ng got the most
-   important information from you, and starts up an editor where you can then
-   enter your email.
-
-   The editor that is called is selected in the following way: you can e.g.
-   set it in the mutt-ng configuration:
-
- set editor = "vim +/^$/ -c ':set tw=72'"
- 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
-   takes its value if it is set. If no editor command can be found, mutt-ng
-   simply assumes vi(1) to be the default editor, since it's the most
-   widespread editor in the Unix world and it's pretty safe to assume that it
-   is installed and available.
-
-   When you've finished entering your message, save it and quit your editor.
-   Mutt-ng will then present you with a summary screen, the compose menu. On
-   the top, you see a summary of the most important available key commands.
-   Below that, you see the sender, the recipient(s), Cc and/or Bcc
-   recipient(s), the subject, the reply-to address, and optionally
-   information where the sent email will be stored and whether it should be
-   digitally signed and/or encrypted.
-
-   Below that, you see a list of "attachments". The mail you've just entered
-   before is also an attachment, but due to its special type (it's plain
-   text), it will be displayed as the normal message on the receiver's side.
-
-   At this point, you can add more attachments, pressing a, you can edit the
-   recipient addresses, pressing t for the "To:" field, c for the "Cc:"
-   field, and b for the "Bcc: field. You can also edit the subject the
-   subject by simply pressing s or the email message that you've entered
-   before by pressing e. You will then again return to the editor. You can
-   even edit the sender, by pressing <esc>f, but this shall only be used with
-   caution.
-
-   Alternatively, you can configure mutt-ng in a way that most of the above
-   settings can be edited using the editor. Therefore, you only need to add
-   the following to your configuration:
-
- 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:
-
-   Table 2.9. Most commonly used Compose Menu Bindings
-
-   Key Function            Description
-   a   <attach-file>       attach a file
-   A   <attach-message>    attach message(s) to the message
-   E-k <attach-key>        attach a PGP public key
-   d   <edit-description>  edit description on attachment
-   D   <detach-file>       detach a file
-   t   <edit-to>           edit the To field
-   E-f <edit-from>         edit the From field
-   r   <edit-reply-to>     edit the Reply-To field
-   c   <edit-cc>           edit the Cc field
-   b   <edit-bcc>          edit the Bcc field
-   y   <send-message>      send the message
-   s   <edit-subject>      edit the Subject
-   S   <smime-menu>        select S/MIME options
-   f   <edit-fcc>          specify an ``Fcc'' mailbox
-   p   <pgp-menu>          select PGP options
-   P   <postpone-message>  postpone this message until later
-   q   <quit>              quit (abort) sending the message
-   w   <write-fcc>         write the message to a folder
-   i   <ispell>            check spelling (if available on your system)
-   C-F <forget-passphrase> wipe passphrase(s) from memory
-
-   Note: The attach-message function will prompt you for a folder to attach
-   messages from. You can now tag messages in that folder and theywill be
-   attached to the message you are sending. Note that certainoperations like
-   composing a new mail, replying, forwarding, etc. are not permitted when
-   you are in that folder. The %r in $status_format will change to a 'A' to
-   indicate that you are in attach-message mode.
-
-  6.2. Replying
-
-    6.2.1. Simple Replies
-
-   When you want to reply to an email message, select it in the index menu
-   and then press r. Mutt-ng's behaviour is then similar to the behaviour
-   when you compose a message: first, you will be asked for the recipient,
-   then for the subject, and then, mutt-ng will start the editor with the
-   quote attribution and the quoted message. This can e.g. look like the
-   example below.
-
- On Mon, Mar 07, 2005 at 05:02:12PM +0100, Michael Svensson wrote:
- > Bill, can you please send last month's progress report to Mr.
- > Morgan? We also urgently need the cost estimation for the new
- > 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
-   message, is, although very widespread, very often not considered to be a
-   polite way to answer emails.
-
-   The quote attribution is configurable, by default it is set to
-
- 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]:
- > Bill, can you please send last month's progress report to Mr.
- > Morgan? We also urgently need the cost estimation for the new
- > 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
-   email signature at the very bottom of the message.
-
-   When you're done with writing your message, save and quit the editor. As
-   before, you will return to the compose menu, which is used in the same way
-   as before.
-
-    6.2.2. Group Replies
-
-   In the situation where a group of people uses email as a discussion, most
-   of the emails will have one or more recipients, and probably several "Cc:"
-   recipients. The group reply functionalityensures that when you press g
-   instead of r to do a reply, each and every recipient that is contained in
-   the original message will receive a copy of the message, either as normal
-   recipient or as "Cc:" recipient.
-
-    6.2.3. List Replies
-
-   When you use mailing lists, it's generally better to send your reply to a
-   message only to the list instead of the list and the original author. To
-   make this easy to use, mutt-ng features list replies.
-
-   To do a list reply, simply press L. If the email contains a
-   Mail-Followup-To: header, its value will be used as reply address.
-   Otherwise, mutt-ng searches through all mail addresses in the original
-   message and tries to match them a list of regular expressions which can be
-   specified using the lists command. If any of the regular expression
-   matches, a mailing list address has been found, and it will be used as
-   reply address.
-
- 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.
-
-  6.3. Editing the message header
-
-   When editing the header of your outgoing message, there are a couple of
-   special features available.
-
-   If you specify Fcc:filename Mutt-ng will pick up filename just as if you
-   had used the edit-fcc function in the compose menu.
-
-   You can also attach files to your message by specifying
-
- Attach: filename [description]
-
-   where filename is the file to attach and description is an optional string
-   to use as the description of the attached file.
-
-   When replying to messages, if you remove the In-Reply-To: field from the
-   header field, Mutt-ng will not generate a References: field, which allows
-   you to create a new message thread.
-
-   Also see the $edit_headers and $editor_headers variables
-
-  6.4. Using Mutt-ng with PGP
-
-   If you want to use PGP, you can specify
-
- Pgp: [E | S | S id]
-
-   ``E'' encrypts, ``S'' signs and ``S<id>'' signs with the given key,
-   setting $pgp_sign_as permanently.
-
-   If you have told mutt to PGP encrypt a message, it will guide you through
-   a key selection process when you try to send the message. Mutt-ng will not
-   ask you any questions about keys which have a certified user ID matching
-   one of the message recipients' mail addresses. However, there may be
-   situations in which there are several keys, weakly certified user ID
-   fields, or where no matching keys can be found.
-
-   In these cases, you are dropped into a menu with a list of keys from which
-   you can select one. When you quit this menu, or mutt can't find any
-   matching keys, you are prompted for a user ID. You can, as usually, abort
-   this prompt using C-G. When you do so, mutt will return to the compose
-   screen.
-
-   Once you have successfully finished the key selection, the message will be
-   encrypted using the selected public keys, and sent out.
-
-   Most fields of the entries in the key selection menu (see also
-   $pgp_entry_format) have obvious meanings. But some explanations on the
-   capabilities, flags, and validity fields are in order.
-
-   The flags sequence (%f) will expand to one of the following flags:
-
-   Table 2.10. PGP Key Menu Flags
-
-   Flag Description
-   R    The key has been revoked and can't be used.
-   X    The key is expired and can't be used.
-   d    You have marked the key as disabled.
-   c    There are unknown critical self-signature packets.
-
-   The capabilities field (%c) expands to a two-character
-   sequencerepresenting a key's capabilities. The first character gives the
-   key's encryption capabilities: A minus sign (- )means that the key cannot
-   be used for encryption. A dot (. )means that it's marked as a signature
-   key in one of the user IDs, but may also be used for encryption. The
-   letter e indicates that this key can be used for encryption.
-
-   The second character indicates the key's signing capabilities. Once again,
-   a ``-'' implies ``not for signing'', ``.'' implies that the key is marked
-   as an encryption key in one of the user-ids, and ``s'' denotes a key which
-   can be used for signing.
-
-   Finally, the validity field (%t) indicates how well-certified a user-id
-   is. A question mark (?) indicates undefined validity, a minus character
-   (-) marks an untrusted association, a space character means a partially
-   trusted association, and a plus character (+ ) indicates complete
-   validity.
-
-  6.5. Sending anonymous messages via mixmaster
-
-   You may also have configured mutt to co-operate with Mixmaster, an
-   anonymous remailer. Mixmaster permits you to send your messages
-   anonymously using a chain of remailers. Mixmaster support in mutt is for
-   mixmaster version 2.04 (beta 45 appears to be the latest) and 2.03. It
-   does not support earlier versions or the later so-called version 3 betas,
-   of which the latest appears to be called 2.9b23.
-
-   To use it, you'll have to obey certain restrictions. Most important, you
-   cannot use the Cc and Bcc headers. To tell Mutt-ng to use mixmaster, you
-   have to select a remailer chain, using the mix function on the compose
-   menu.
-
-   The chain selection screen is divided into two parts. In the (larger)
-   upper part, you get a list of remailers you may use. In the lower part,
-   you see the currently selected chain of remailers.
-
-   You can navigate in the chain using the chain-prev and chain-next
-   functions, which are by default bound to the left and right arrows and to
-   the h and l keys (think vi keyboard bindings). To insert a remailer at the
-   current chain position, use the insert function. To append a remailer
-   behind the current chain position, use select-entry or append . You can
-   also delete entries from the chain, using the corresponding function.
-   Finally, to abandon your changes, leave the menu, or accept them pressing
-   (by default) the Return key.
-
-   Note that different remailers do have different capabilities, indicated in
-   the %c entry of the remailer menu lines (see $mix_entry_format). Most
-   important is the ``middleman'' capability, indicated by a capital ``M'':
-   This means that the remailer in question cannot be used as the final
-   element of a chain, but will only forward messages to other mixmaster
-   remailers. For details on the other capabilities, please have a look at
-   the mixmaster documentation.
-
-7. Forwarding and Bouncing Mail
-
-   Often, it is necessary to forward mails to other people. Therefore,
-   mutt-ng supports forwarding messages in two different ways.
-
-   The first one is regular forwarding, as you probably know it from other
-   mail clients. You simply press f, enter the recipient email address, the
-   subject of the forwarded email, and then you can edit the message to be
-   forwarded in the editor. The forwarded message is separated from the rest
-   of the message via the two following markers:
-
- ----- Forwarded message from Lucas User <luser@example.com> -----
-
- From: Lucas User <luser@example.com>
- Date: Thu, 02 Dec 2004 03:08:34 +0100
- To: Michael Random <mrandom@example.com>
- Subject: Re: blackmail
-
- Pay me EUR 50,000.- cash or your favorite stuffed animal will die
- a horrible death.
-
- ----- 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.
-
-   The second mode of forwarding emails with mutt-ng is the so-called
-   bouncing: when you bounce an email to another address, it will be sent in
-   practically the same format you send it (except for headers that are
-   created during transporting the message). To bounce a message, press b and
-   enter the recipient email address. By default, you are then asked whether
-   you really want to bounce the message to the specified recipient. If you
-   answer with yes, the message will then be bounced.
-
-   To the recipient, the bounced email will look as if he got it like a
-   regular email where he was Bcc: recipient. The only possibility to find
-   out whether it was a bounced email is to carefully study the email headers
-   and to find out which host really sent the email.
-
-8. Postponing Mail
-
-   At times it is desirable to delay sending a message that you have already
-   begun to compose. When the postpone-message function is used in the
-   compose menu, the body of your message and attachments are stored in the
-   mailbox specified by the $postponed variable. This means that you can
-   recall the message even if you exit Mutt-ng and then restart it at a later
-   time.
-
-   Once a message is postponed, there are several ways to resume it. From the
-   command line you can use the ``-p'' option, or if you compose a new
-   message from the index or pager you will be prompted if postponed messages
-   exist. If multiple messages are currently postponed, the postponed menu
-   will pop up and you can select which message you would like to resume.
-
-   Note: If you postpone a reply to a message, the reply setting of the
-   message is only updated when you actually finish the message and send it.
-   Also, you must be in the same folder with the message you replied to for
-   the status of the message to be updated.
-
-   See also the $postpone quad-option.
-
-Chapter 3. Configuration
-
-   Table of Contents
-
-   1. Locations of Configuration Files
-
-   2. Basic Syntax of Initialization Files
-
-   3. Expansion within variables
-
-                3.1. Commands' Output
-
-                3.2. Environment Variables
-
-                3.3. Configuration Variables
-
-                3.4. Self-Defined Variables
-
-                3.5. Pre-Defined Variables
-
-                3.6. Type Conversions
-
-   4. Defining/Using aliases
-
-   5. Changing the default key bindings
-
-   6. Defining aliases for character sets
-
-   7. Setting variables based upon mailbox
-
-   8. Keyboard macros
-
-   9. Using color and mono video attributes
-
-   10. Ignoring (weeding) unwanted message headers
-
-   11. Alternative addresses
-
-   12. Format = Flowed
-
-                12.1. Introduction
-
-                12.2. Receiving: Display Setup
-
-                12.3. Sending
-
-                12.4. Additional Notes
-
-   13. Mailing lists
-
-   14. Using Multiple spool mailboxes
-
-   15. Defining mailboxes which receive mail
-
-   16. User defined headers
-
-   17. Defining the order of headers when viewing messages
-
-   18. Specify default save filename
-
-   19. Specify default Fcc: mailbox when composing
-
-   20. Specify default save filename and default Fcc: mailbox at once
-
-   21. Change settings based upon message recipients
-
-   22. Change settings before formatting a message
-
-   23. Choosing the cryptographic key of the recipient
-
-   24. Adding key sequences to the keyboard buffer
-
-   25. Executing functions
-
-   26. Message Scoring
-
-   27. Spam detection
-
-   28. Setting variables
-
-   29. Reading initialization commands from another file
-
-   30. Removing hooks
-
-   31. Sharing Setups
-
-                31.1. Character Sets
-
-                31.2. Modularization
-
-                31.3. Conditional parts
-
-   32. Obsolete Variables
-
-1. Locations of Configuration Files
-
-   While the default configuration (or ``preferences'') make Mutt-ng usable
-   right out of the box, it is often desirable to tailor Mutt-ng to suit your
-   own tastes. When Mutt-ng is first invoked, it will attempt to read the
-   ``system'' configuration file (defaults set by your local system
-   administrator), unless the ``-n'' commandline option is specified. This
-   file is typically /usr/local/share/muttng/Muttngrc or /etc/Muttngrc ,
-   Mutt-ng users will find this file in /usr/local/share/muttng/Muttrc or
-   /etc/Muttngrc. Mutt will next look for a file named .muttrc in your home
-   directory, Mutt-ng will look for .muttngrc. If this file does not exist
-   and your home directory has a subdirectory named .mutt , mutt try to load
-   a file named .muttng/muttngrc.
-
-   .muttrc (or .muttngrc for Mutt-ng) is the file where you will usually
-   place your commands to configure Mutt-ng.
-
-2. Basic Syntax of Initialization Files
-
-   An initialization file consists of a series of commands. Each line of the
-   file may contain one or more commands. When multiple commands are used,
-   they must be separated by a semicolon (;).
-
- 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
-   that a single quote is used to specify a literal string (one that is not
-   interpreted for shell variables or quoting with a backslash (see next
-   paragraph), while double quotes indicate a string for which should be
-   evaluated. For example, backtics are evaluated inside of double quotes,
-   but not for single quotes.
-
-   \ quotes the next character, just as in shells such as bash and zsh. For
-   example, if want to put quotes ``"'' inside of a string, you can use ``\''
-   to force the next character to be a literal instead of interpreted
-   character.
-
- 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.
-
-   A \ at the end of a line can be used to split commands over multiple
-   lines, provided that the split points don't appear in the middle of
-   command names.
-
-   Please note that, unlike the various shells, mutt-ng interprets a ``\'' at
-   the end of a line also in comments. This allows you to disable a command
-   split over multiple lines with only one ``#''.
-
- # 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
-   commented with a hash (#) all following continuation lines are also part
-   of a comment and therefore are ignored, too. So take care of comments when
-   continuation lines are involved within your setup files!
-
-   Abstract example:
-
- line1\
- line2a # line2b\
- line3\
- 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.
-
-   The commands understood by mutt are explained in the next paragraphs. For
-   a complete list, see the commands.
-
-3. Expansion within variables
-
-   Besides just assign static content to variables, there's plenty of ways of
-   adding external and more or less dynamic content.
-
-  3.1. Commands' Output
-
-   It is possible to substitute the output of a Unix command in an
-   initialization file. This is accomplished by enclosing the command in
-   backquotes (``) as in, for example:
-
- 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.
-
-  3.2. Environment Variables
-
-   UNIX environments can be accessed like the way it is done in shells like
-   sh and bash: Prepend the name of the environment by a ``$'' sign. For
-   example,
-
- set record=+sent_on_$HOSTNAME
-
-   sets the $record variable to the string +sent_on_ and appends the value of
-   the evironment variable $HOSTNAME.
-
-   Note: There will be no warning if an environment variable is not defined.
-   The result will of the expansion will then be empty.
-
-  3.3. Configuration Variables
-
-   As for environment variables, the values of all configuration variables as
-   string can be used in the same way, too. For example,
-
- set imap_home_namespace = $folder
-
-   would set the value of $imap_home_namespace to the value to which $folder
-   is currently set to.
-
-   Note: There're no logical links established in such cases so that the the
-   value for $imap_home_namespace won't change even if $folder gets changed.
-
-   Note: There will be no warning if a configuration variable is not defined
-   or is empty. The result will of the expansion will then be empty.
-
-  3.4. Self-Defined Variables
-
-   Mutt-ng flexibly allows users to define their own variables. To avoid
-   conflicts with the standard set and to prevent misleading error messages,
-   there's a reserved namespace for them: all user-defined variables must be
-   prefixed with user_ and can be used just like any ordinary configuration
-   or environment variable.
-
-   For example, to view the manual, users can either define two macros like
-   the following
-
- 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:
-
- set user_manualcmd = "!less -r /path/to_manual"
- macro generic <F1> "$user_manualcmd<enter>" "Show manual"
- 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
-   end.
-
-   When the variable is first defined, the first value it gets assigned is
-   also the initial value to which it can be reset using the reset command.
-
-   The complete removal is done via the unset keyword.
-
-   After the following sequence:
-
- 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.
-
-  3.5. Pre-Defined Variables
-
-   In order to allow users to share one setup over a number of different
-   machines without having to change its contents, there's a number of
-   pre-defined variables. These are prefixed with muttng_ and are read-only,
-   i.e. they cannot be set, unset or reset. The reference chapter lists all
-   available variables.
-
-   Please consult the local copy of your manual for their values as they may
-   differ from different manual sources. Where the manual is installed in can
-   be queried (already using such a variable) by running:
-
- $ 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
-   these values: when it finds double quotes, the value will be expanded
-   during reading the setup files but when it finds single quotes, it'll
-   expand it at runtime as needed.
-
-   For example, the statement
-
- 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.
-
-   A more practical example is:
-
- 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.
-
-  3.6. Type Conversions
-
-   A note about variable's types during conversion: internally values are
-   stored in internal types but for any dump/query or set operation they're
-   converted to and from string. That means that there's no need to worry
-   about types when referencing any variable. As an example, the following
-   can be used without harm (besides makeing muttng very likely behave
-   strange):
-
- set read_inc = 100
- set folder = $read_inc
- set read_inc = $folder
- set user_magic_number = 42
- set folder = $user_magic_number
-
-4. Defining/Using aliases
-
-   Usage: aliaskey 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
-   ``aliases'' which map a short string to a full address.
-
-   Note: if you want to create an alias for a group (by specifying more than
-   one address), you must separate the addresses with a comma (``,'').
-
-   To remove an alias or aliases (``*'' means all aliases):
-
-   Usage: unalias[* | key ... ]
-
- 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
-   alias files, or you can have all aliases defined in your muttrc.
-
-   On the other hand, the <create-alias> function can use only one file, the
-   one pointed to by the $alias_file variable (which is ~/.muttrc by
-   default). This file is not special either, in the sense that Mutt-ng will
-   happily append aliases to any file, but in order for the new aliases to
-   take effect you need to explicitly source this file too.
-
-   For example:
-
- source /usr/local/share/Mutt-ng.aliases
- 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
-   $editor_headers variable set.
-
-   In addition, at the various address prompts, you can use the tab character
-   to expand a partial alias to the full alias. If there are multiple
-   matches, mutt will bring up a menu with the matching aliases. In order to
-   be presented with the full list of aliases, you must hit tab with out a
-   partial alias, such as at the beginning of the prompt or after a comma
-   denoting multiple addresses.
-
-   In the alias menu, you can select as many aliases as you want with the
-   select-entry key (default: RET), and use the exit key (default: q) to
-   return to the address prompt.
-
-5. Changing the default key bindings
-
-   Usage: bindmap key function
-
-   This command allows you to change the default key bindings (operation
-   invoked when pressing a key).
-
-   map specifies in which menu the binding belongs. Multiple maps may be
-   specified by separating them with commas (no additional whitespace
-   isallowed). The currently defined maps are:
-
-   generic
-
-           This is not a real menu, but is used as a fallback for all of the
-           other menus except for the pager and editor modes. If a key is not
-           defined in another menu, Mutt-ng will look for a binding to use in
-           this menu. This allows you to bind a key to a certain function in
-           multiple menus instead of having multiple bind statements to
-           accomplish the same task.
-
-   alias
-
-           The alias menu is the list of your personal aliases as defined in
-           your muttrc. It is the mapping from a short alias name to the full
-           email address(es) of the recipient(s).
-
-   attach
-
-           The attachment menu is used to access the attachments on received
-           messages.
-
-   browser
-
-           The browser is used for both browsing the local directory
-           structure, and for listing all of your incoming mailboxes.
-
-   editor
-
-           The editor is the line-based editor the user enters text data.
-
-   index
-
-           The index is the list of messages contained in a mailbox.
-
-   compose
-
-           The compose menu is the screen used when sending a new message.
-
-   pager
-
-           The pager is the mode used to display message/attachment data, and
-           help listings.
-
-   pgp
-
-           The pgp menu is used to select the OpenPGP keys used for
-           encrypting outgoing messages.
-
-   postpone
-
-           The postpone menu is similar to the index menu, except is used
-           when recalling a message the user was composing, but saved until
-           later.
-
-   key is the key (or key sequence) you wish to bind. To specify a control
-   character, use the sequence \Cx, where x is the letter of the control
-   character (for example, to specify control-A use ``\Ca''). Note that the
-   case of x as well as \C is ignored, so that \CA, \Ca, \cA and \ca are all
-   equivalent. An alternative form is to specify the key as a three digit
-   octal number prefixed with a ``\'' (for example \177 is equivalent to
-   \c?).
-
-   In addition, key may consist of:
-
-   Table 3.1. Alternative Key Names
-
-   Sequence    Description
-   \t          tab
-   <tab>       tab
-   <backtab>   backtab / shift-tab
-   \r          carriage return
-   \n          newline
-   \e          escape
-   <esc>       escape
-   <up>        up arrow
-   <down>      down arrow
-   <left>      left arrow
-   <right>     right arrow
-   <pageup>    Page Up
-   <pagedown>  Page Down
-   <backspace> Backspace
-   <delete>    Delete
-   <insert>    Insert
-   <enter>     Enter
-   <return>    Return
-   <home>      Home
-   <end>       End
-   <space>     Space bar
-   <f1>        function key 1
-   <f10>       function key 10
-
-   key does not need to be enclosed in quotes unless it contains a space (``
-   '').
-
-   function specifies which action to take when key is pressed. For a
-   complete list of functions, see the functions. The special function noop
-   unbinds the specified key sequence.
-
-6. Defining aliases for character sets
-
-   Usage: charset-hookaliascharset
-
-   Usage: iconv-hookcharsetlocal-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
-   name not known to mutt.
-
-   The iconv-hook command defines a system-specific name for a character set.
-   This is helpful when your systems character conversion library insists on
-   using strange, system-specific names for character sets.
-
-7. Setting variables based upon mailbox
-
-   Usage: folder-hook [!]regexpcommand
-
-   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
-   specifying in which mailboxes to execute command before loading. If a
-   mailbox matches multiple folder-hook's, they are executed in the order
-   given in the muttrc.
-
-   Note: if you use the ``!'' shortcut for $spoolfile at the beginning of the
-   pattern, you must place it inside of double or single quotes in order to
-   distinguish it from the logical not operator for the expression.
-
-   Note that the settings are not restored when you leave the mailbox. For
-   example, a command action to perform is to change the sorting methodbased
-   upon the mailbox being read:
-
- 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: macromenu 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
-   had typed sequence. So if you have a common sequence of commands you type,
-   you can create a macro to execute those commands with a singlekey.
-
-   menu is the maps which the macro will be bound. Multiple maps may be
-   specified by separating multiple menu arguments by commas. Whitespace may
-   not be used in between the menu arguments and thecommas separating them.
-
-   key and sequence are expanded by the same rules as the bind. There are
-   some additions however. The first is that control characters in sequence
-   can also be specified as ^x. In order to get a caret (`^'') you need to
-   specify it twice. Secondly, to specify a certain key such as up or to
-   invoke a function directly, you can use the format <key name> and
-   <function name> .For a listing of key names see the section on bind.
-   Functions are listed in the functions.
-
-   The advantage with using function names directly is that the macros
-   willwork regardless of the current key bindings, so they are not dependent
-   on the user having particular key definitions. This makes them more
-   robustand portable, and also facilitates defining of macros in files used
-   by more than one user (eg. the system Muttngrc).
-
-   Optionally you can specify a descriptive text after sequence, which is
-   shown in the help screens.
-
-   Note: Macro definitions (if any) listed in the help screen(s), are
-   silently truncated at the screen width, and are not wrapped.
-
-9. Using color and mono video attributes
-
-   Usage: colorobject foreground background [regexp]
-
-   Usage: colorindex foreground pattern
-
-   Usage: uncolorindex 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),
-   you must specify both a foreground color and a background color (it is not
-   possible to only specify one or the other).
-
-   object can be one of:
-
-     o attachment
-
-     o body (match regexp in the body of messages)
-
-     o bold (highlighting bold patterns in the body of messages)
-
-     o error (error messages printed by Mutt-ng)
-
-     o header (match regexp in the message header)
-
-     o hdrdefault (default color of the message header in the pager)
-
-     o index (match pattern in the message index)
-
-     o indicator (arrow or bar used to indicate the current item in a menu)
-
-     o markers (the ``+'' markers at the beginning of wrapped lines in the
-       pager)
-
-     o message (informational messages)
-
-     o normal
-
-     o quoted (text matching $quote_regexp in the body of a message)
-
-     o quoted1, quoted2, ..., quotedN (higher levels of quoting)
-
-     o search (highlighting of words in the pager)
-
-     o signature
-
-     o status (mode lines used to display info about the mailbox or message)
-
-     o tilde (the ``~'' used to pad blank lines in the pager)
-
-     o tree (thread tree drawn in the message index and attachment menu)
-
-     o underline (highlighting underlined patterns in the body of messages)
-
-   foreground and background can be one of the following:
-
-     o white
-
-     o black
-
-     o green
-
-     o magenta
-
-     o blue
-
-     o cyan
-
-     o yellow
-
-     o red
-
-     o default
-
-     o colorx
-
-   foreground can optionally be prefixed with the keyword bright to make the
-   foreground color boldfaced (e.g., brightred).
-
-   If your terminal supports it, the special keyword default can be used as a
-   transparent color. The value brightdefault is also valid. If Mutt-ng is
-   linked against the S-Lang library, you also need to set the $COLORFGBG
-   environment variable to the default colors of your terminal for this to
-   work; for example (for Bourne-like shells):
-
- 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.
-
-   Note: The uncolor command can be applied to the index object only. It
-   removes entries from the list. You must specify the same pattern specified
-   in the color command for it to be removed. The pattern ``*'' is a special
-   token which means to clear the color index list of all entries.
-
-   Mutt-ng also recognizes the keywords color0, color1 ,..., colorN-1 (N
-   being the number of colors supported by your terminal). This is useful
-   when you remap the colors for your display (for example by changing the
-   color associated with color2 for your xterm), since color names may then
-   lose their normal meaning.
-
-   If your terminal does not support color, it is still possible change the
-   video attributes through the use of the ``mono'' command:
-
-   Usage: monoobject attribute [regexp]
-
-   Usage: monoindex attribute pattern
-
-   Usage: unmonoindex pattern [pattern ...]
-
-   where attribute is one of the following:
-
-     o none
-
-     o bold
-
-     o underline
-
-     o reverse
-
-     o standout
-
-10. Ignoring (weeding) unwanted message headers
-
-   Usage: ignorepattern [pattern ...]
-
-   Usage: unignorepattern [pattern ...]
-
-   Messages often have many header fields added by automatic processing
-   systems, or which may not seem useful to display on the screen. This
-   command allows you to specify header fields which you don't normally want
-   to see.
-
-   You do not need to specify the full header field name. For example,
-   ``ignore content-'' will ignore all header fields that begin with the
-   pattern ``content-''. ``ignore *'' will ignore all headers.
-
-   To remove a previously added token from the list, use the ``unignore''
-   command. The ``unignore'' command will make Mutt-ng display headers with
-   the given pattern. For example, if you do ``ignore x-'' it is possible to
-   ``unignore x-mailer''.
-
-   ``unignore *'' will remove all tokens from the ignore list.
-
-   For example:
-
- # Sven's draconian header weeding
- ignore *
- unignore from date subject to cc
- unignore organization organisation x-mailer: x-newsreader: x-mailing-list:
- unignore posted-to:
-
-11. Alternative addresses
-
-   Usage: alternatesregexp [regexp ...]
-
-   Usage: unalternatesregexp [regexp ...]
-
-   With various functions, mutt will treat messages differently, depending on
-   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.)
-
-   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
-   e-mail addresses you receive mail under. That's the purpose of the
-   alternates command: It takes a list of regular expressions, each of which
-   can identify an address under which you receive e-mail.
-
-   The unalternates command can be used to write exceptions to alternates
-   patterns. If an address matches something in an alternates command, but
-   you nonetheless do not think it is from you, you can list a more precise
-   pattern under an unalternates command.
-
-   To remove a regular expression from the alternates list, use the
-   unalternates command with exactly the same regexp . Likewise, if the
-   regexp for a alternates command matches an entry on the unalternates list,
-   that unalternates entry will be removed. If the regexp for unalternates is
-   ``*'', all entries on alternates will be removed.
-
-12. Format = Flowed
-
-  12.1. Introduction
-
-   Mutt-ng contains support for so-called format=flowed messages. In the
-   beginning of email, each message had a fixed line width, and it was enough
-   for displaying them on fixed-size terminals. But times changed, and
-   nowadays hardly anybody still uses fixed-size terminals: more people
-   nowaydays use graphical user interfaces, with dynamically resizable
-   windows. This led to the demand of a new email format that makes it
-   possible for the email client to make the email look nice in a resizable
-   window without breaking quoting levels and creating an incompatible email
-   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>.
-
-  12.2. Receiving: Display Setup
-
-   When you receive emails that are marked as format=flowed messages, and is
-   formatted correctly, mutt-ng will try to reformat the message to optimally
-   fit on your terminal. If you want a fixed margin on the right side of your
-   terminal, you can set the following:
-
- set wrapmargin = 10
-
-   The code above makes the line break 10 columns before the right side of
-   the terminal.
-
-   If your terminal is so wide that the lines are embarrassingly long, you
-   can also set a maximum line length:
-
- 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
-   hierarchy like in the following example:
-
- >Bill, can you please send last month's progress report to Mr.
- >Morgan? We also urgently need the cost estimation for the new
- >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.
- > Morgan? We also urgently need the cost estimation for the new
- > 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
-   explicitly set it:
-
- set text_flowed
-
-   Additionally, you have to use an editor which supports writing
-   format=flowed-conforming emails. For vim(1), this is done by adding w to
-   the formatoptions (see :h formatoptions and :h fo-table) when writing
-   emails.
-
-   Also note that format=flowed knows about ``space-stuffing'', that is, when
-   sending messages, some kinds of lines have to be indented with a single
-   space on the sending side. On the receiving side, the first space (if any)
-   is removed. As a consequence and in addition to the above simple setting,
-   please keep this in mind when making manual formattings within the editor.
-   Also note that mutt-ng currently violates the standard (RfC 3676) as it
-   does not space-stuff lines starting with:
-
-     o > This is not the quote character but a right angle used for other
-       reasons
-
-   Please make sure that you manually prepend a space to each of them.
-
-  12.4. Additional Notes
-
-   For completeness, the $delete_space variable provides the mechanism to
-   generate a DelSp=yes parameter on outgoing messages. According to the
-   standard, clients receiving a format=flowed messages should delete the
-   last space of a flowed line but still interpret the line as flowed.
-   Because flowed lines usually contain only one space at the end, this
-   parameter would make the receiving client concatenate the last word of the
-   previous with the first of the current line without a space. This makes
-   ordinary text unreadable and is intended for languages rarely using
-   spaces. So please use this setting only if you're sure what you're doing.
-
-13. Mailing lists
-
-   Usage: listsregexp [regexp ...]
-
-   Usage: unlistsregexp [regexp ...]
-
-   Usage: subscriberegexp [regexp ...]
-
-   Usage: unsubscriberegexp [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
-   lists, and which mailing lists you are subscribed to. Once you have done
-   this, the list-reply function will work for all known lists. Additionally,
-   when you send a message to a subscribed list, mutt will add a
-   Mail-Followup-To header to tell other users' mail user agents not to send
-   copies of replies to your personal address. Note that the Mail-Followup-To
-   header is a non-standard extension which is not supported by all mail user
-   agents. Adding it is not bullet-proof against receiving personal CCs of
-   list messages. Also note that the generation of the Mail-Followup-To
-   header is controlled by the $followup_to configuration variable.
-
-   More precisely, Mutt-ng maintains lists of patterns for the addresses of
-   known and subscribed mailing lists. Every subscribed mailing list is
-   known. To mark a mailing list as known, use the ``lists'' command. To mark
-   it as subscribed, use ``subscribe''.
-
-   You can use regular expressions with both commands. To mark all messages
-   sent to a specific bug report's address on mutt's bug tracking system as
-   list mail, for instance, you could say ``subscribe [0-9]*@bugs.guug.de''.
-   Often, it's sufficient to just give a portion of the list's e-mail
-   address.
-
-   Specify as much of the address as you need to to remove ambiguity. For
-   example, if you've subscribed to the Mutt-ng mailing list, you will
-   receive mail addressed to mutt-users@mutt.org. So, to tell Mutt-ng that
-   this is a mailing list, you could add ``lists mutt-users'' to your
-   initialization file. To tell mutt that you are subscribed to it, add
-   ``subscribe mutt-users'' to your initialization file instead. If you also
-   happen to get mail from someone whose address is mutt-users@example.com,
-   you could use ``lists mutt-users@mutt\\.org'' or ``subscribe
-   mutt-users@mutt\\.org'' to match only mail from the actual list.
-
-   The ``unlists'' command is used to remove a token from the list of known
-   and subscribed mailing-lists. Use ``unlists *'' to remove all tokens.
-
-   To remove a mailing list from the list of subscribed mailing lists, but
-   keep it on the list of known mailing lists, use ``unsubscribe''.
-
-14. Using Multiple spool mailboxes
-
-   Usage: mbox-hook [!]patternmailbox
-
-   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''
-   mailbox and mailbox specifies where mail should be saved when read.
-
-   Unlike some of the other hook commands, only the first matching pattern is
-   used (it is not possible to save read mail in more than a single mailbox).
-
-15. Defining mailboxes which receive mail
-
-   Usage: mailboxes[!]filename [filename ... ]
-
-   Usage: unmailboxes[!]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
-   how many of these folders have new messages.
-
-   When changing folders, pressing space will cycle through folders with new
-   mail.
-
-   Pressing TAB in the directory browser will bring up a menu showing the
-   files specified by the mailboxes command, and indicate which contain new
-   messages. Mutt-ng will automatically enter this mode when invoked from the
-   command line with the -y option.
-
-   The ``unmailboxes'' command is used to remove a token from the list of
-   folders which receive mail. Use ``unmailboxes *'' to remove all tokens.
-
-   Note: new mail is detected by comparing the last modification time to the
-   last access time. Utilities like biff or frm or any other program which
-   accesses the mailbox might cause Mutt-ng to never detect new mail for that
-   mailbox if they do not properly reset the access time. Backup tools are
-   another common reason for updated access times.
-
-   Note: the filenames in the mailboxes command are resolved when the command
-   is executed, so if these names contain shortcuts (such as ``='' and
-   ``!''), any variable definition that affect these characters (like $folder
-   and $spoolfile) should be executed before the mailboxes command.
-
-16. User defined headers
-
-   Usage: my_hdrstring
-
-   Usage: unmy_hdrfield [field ...]
-
-   The ``my_hdr'' command allows you to create your own header fields which
-   will be added to every message you send.
-
-   For example, if you would like to add an ``Organization:'' header field to
-   all of your outgoing messages, you can put the command
-
- my_hdr Organization: A Really Big Company, Anytown, USA
-
-   in your .muttrc.
-
-   Note: space characters are not allowed between the keyword and the colon
-   (``:''). The standard for electronic mail (RfC 822) says that space is
-   illegal there, so Mutt-ng enforces the rule.
-
-   If you would like to add a header field to a single message, you should
-   either set the $edit_headers variable, or use the edit-headers function
-   (default: ``E'') in the send-menu so that you can edit the header of your
-   message along with the body.
-
-   To remove user defined header fields, use the ``unmy_hdr'' command. You
-   may specify an asterisk (``*'') to remove all header fields, or the fields
-   to remove. For example, to remove all ``To'' and ``Cc'' header fields, you
-   could use:
-
- unmy_hdr to cc
-
-17. Defining the order of headers when viewing messages
-
-   Usage: hdr_orderheader header [header ...]
-
-   Usage: unhdr_order[ * | header header ...]
-
-   With this command, you can specify an order in which mutt will attempt to
-   present headers to you when viewing messages.
-
-   ``unhdr_order *'' will clear all previous headers from the order list,
-   thus removing the header order effects set by the system-wide startup
-   file.
-
- hdr_order From Date: From: To: Cc: Subject:
-
-18. Specify default save filename
-
-   Usage: save-hook [!]patternfilename
-
-   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
-   is addressed to: something matching regexp .
-
-   See pattern-hook for information on the exact format of pattern.
-
-   Examples:
-
- 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 [!]patternmailbox
-
-   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 is found the message will be saved to $record mailbox.
-
-   See pattern-hook for information on the exact format of pattern.
-
-   Example:
-
- fcc-hook [@.]aol\\.com$ +spammers
-
-   The above will save a copy of all messages going to the aol.com domain to
-   the `+spammers' mailbox by default. Also see the fcc-save-hook command.
-
-20. Specify default save filename and default Fcc: mailbox at once
-
-   Usage: fcc-save-hook [!]patternmailbox
-
-   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 [!]patterncommand
-
-   Usage: send-hook [!]patterncommand
-
-   Usage: send2-hook [!]patterncommand
-
-   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
-   recipients of the message.
-
-   reply-hook is matched against the message you are replying to, instead of
-   the message you are sending .send-hook is matched against all messages,
-   both new and replies .Note:reply-hooks are matched before the send-hook,
-   regardless of the order specified in the users's configuration file.
-
-   send2-hook is matched every time a message is changed, either by editing
-   it, or by using the compose menu to change its recipients or subject.
-   send2-hook is executed after send-hook ,and can, e.g., be used to set
-   parameters such as the $sendmail variable depending on the message's
-   sender address.
-
-   For each type of send-hook or reply-hook, when multiple matches occur,
-   commands are executed in the order they are specified in the muttrc (for
-   that type of hook).
-
-   See pattern-hook for information on the exact format of pattern.
-
-   Example: send-hook mutt "set mime_forward signature=''"
-
-   Another typical use for this command is to change the values of the
-   $attribution, $signature and $locale variables in order to change the
-   language of the attributions and signatures based upon the recipients.
-
-   Note: the send-hook's are only executed ONCE after getting the initial
-   list of recipients. Adding a recipient after replying or editing the
-   message will NOT cause any send-hook to be executed. Also note that my_hdr
-   commands which modify recipient headers, or the message's subject, don't
-   have any effect on the current message when executed from a send-hook.
-
-22. Change settings before formatting a message
-
-   Usage: message-hook [!]patterncommand
-
-   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
-   displayed. When multiple matches occur, commands are executed in the order
-   they are specified in the muttrc.
-
-   See pattern-hook for information on the exact format of pattern.
-
-   Example:
-
- 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-hookpatternkeyid
-
-   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
-   because, for some reasons, you need to override the key Mutt-ng
-   wouldnormally use. The crypt-hook command provides a method by which you
-   can specify the ID of the public key to be used when encrypting messages
-   to a certain recipient.
-
-   The meaning of "key id" is to be taken broadly in this context: You can
-   either put a numerical key ID here, an e-mail address, or even just a real
-   name.
-
-24. Adding key sequences to the keyboard buffer
-
-   Usage: pushstring
-
-   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. For
-   example, the following command will automatically collapse all threads
-   when entering a folder:
-
- folder-hook . 'push <collapse-all>'
-
-25. Executing functions
-
-   Usage: execfunction [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: scorepattern value
-
-   Usage: unscorepattern [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
-   always useful to have the important messages marked and the annoying
-   messages or the ones that you aren't interested in deleted. For this
-   purpose, mutt-ng features a mechanism called ``scoring''.
-
-   When you use scoring, every message has a base score of 0. You can then
-   use the score command to define patterns and a positive or negative value
-   associated with it. When a pattern matches a message, the message's score
-   will be raised or lowered by the amount of the value associated with the
-   pattern.
-
- 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.
-
-   To make scoring actually useful, the score must be applied in some way.
-   That's what the score thresholds are for. Currently, there are three score
-   thresholds:
-
-     o flag threshold: when a message has a score value equal or higher than
-       the flag threshold, it will be flagged.
-
-     o read threshold: when a message has a score value equal or lower than
-       the read threshold, it will be marked as read.
-
-     o delete threshold: when a message has a score value equal or lower than
-       the delete threshold, it will be marked as deleted.
-
-   These three thresholds can be set via the variables $score_threshold_read,
-   $score_threshold_flag and $score_threshold_delete.
-
-   By default, $score_threshold_read and $score_threshold_delete are set to
-   -1, which means that in the default threshold configuration no message
-   will ever get marked as read or deleted.
-
-   Scoring gets especially interesting when combined with the color command
-   and the ~n pattern:
-
- 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
-   scoring mechanism, but it is more flexible, as it visually marks different
-   scores.
-
-27. Spam detection
-
-   Usage: spampattern format
-
-   Usage: nospampattern
-
-   Mutt-ng has generalized support for external spam-scoring filters. By
-   defining your spam patterns with the spam and nospam commands, you can
-   limit, search, and sort your mail based on its spam attributes, as
-   determined by the external filter. You also can display the spam
-   attributes in your index display using the %H selector in the
-   $index_format variable. (Tip: try %?H?[%H] ? to display spam tags only
-   when they are defined for a given message.)
-
-   Your first step is to define your external filter's spam patterns using
-   the spam command. pattern should be a regular expression that matches a
-   header in a mail message. If any message in the mailbox matches this
-   regular expression, it will receive a ``spam tag'' or ``spam attribute''
-   (unless it also matches a nospam pattern -- see below.) The appearance of
-   this attribute is entirely up to you, and is governed by the format
-   parameter. format can be any static text, but it also can include
-   back-references from the pattern expression. (A regular expression
-   ``back-reference'' refers to a sub-expression contained within
-   parentheses.) %1 is replaced with the first back-reference in the regex,
-   %2 with the second, etc.
-
-   If you're using multiple spam filters, a message can have more than one
-   spam-related header. You can define spam patterns for each filter you use.
-   If a message matches two or more of these patterns, and the
-   $spam_separator variable is set to a string, then the message's spam tag
-   will consist of all the format strings joined together, with the value of
-   $spam_separator separating them.
-
-   For example, suppose I use DCC, SpamAssassin, and PureMessage. I might
-   define these spam settings:
-
- spam "X-DCC-.*-Metrics:.*(....)=many"         "90+/DCC-%1"
- spam "X-Spam-Status: Yes"                     "90+/SA"
- 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,
-   97/PM. (The four characters before ``=many'' in a DCC report indicate the
-   checksum used -- in this case, ``Fuz2''.)
-
-   If the $spam_separator variable is unset, then each spam pattern match
-   supersedes the previous one. Instead of getting joined format strings,
-   you'll get only the last one to match.
-
-   The spam tag is what will be displayed in the index when you use %H in the
-   $index_format variable. It's also the string that the ~H pattern-matching
-   expression matches against for search and limit functions. And it's what
-   sorting by spam attribute will use as a sort key.
-
-   That's a pretty complicated example, and most people's actual environments
-   will have only one spam filter. The simpler your configuration, the more
-   effective mutt can be, especially when it comes to sorting.
-
-   Generally, when you sort by spam tag, mutt will sort lexically -- that is,
-   by ordering strings alphnumerically. However, if a spam tag begins with a
-   number, mutt will sort numerically first, and lexically only when two
-   numbers are equal in value. (This is like UNIX's sort -n.) A message with
-   no spam attributes at all -- that is, one that didn't match any of your
-   spam patterns -- is sorted at lowest priority. Numbers are sorted next,
-   beginning with 0 and ranging upward. Finally, non-numeric strings are
-   sorted, with ``a'' taking lowerpriority than ``z''. Clearly, in general,
-   sorting by spam tags is most effective when you can coerce your filter to
-   give you a raw number. But in case you can't, mutt can still do something
-   useful.
-
-   The nospam command can be used to write exceptions to spam patterns. If a
-   header pattern matches something in a spam command, but you nonetheless do
-   not want it to receive a spam tag, you can list amore precise pattern
-   under a nospam command.
-
-   If the pattern given to nospam is exactly the same as the pattern on an
-   existing spam list entry, the effect will be to remove the entry from the
-   spam list, instead of adding an exception. Likewise, if the pattern for a
-   spam command matches an entry on the nospam list, that nospam entry will
-   be removed. If the pattern for nospam is ``*'', all entries on both lists
-   will be removed. This might be the default action if you use spam and
-   nospam in conjunction with a folder-hook.
-
-   You can have as many spam or nospam commands as you like. You can even do
-   your own primitive spam detection within mutt -- for example, if you
-   consider all mail from MAILER-DAEMON to be spam, you can use a spam
-   command like this:
-
- spam "^From: .*MAILER-DAEMON"       "999"
-
-28. Setting variables
-
-   Usage: set[no|inv]variable [=value] [variable...]
-
-   Usage: togglevariable [variable ...]
-
-   Usage: unsetvariable [variable ...]
-
-   Usage: resetvariable [variable ...]
-
-   This command is used to set (and unset) variables. There are four basic
-   types of variables: boolean, number, string and quadoption. boolean
-   variables can be set (true) or unset (false). number variables can be
-   assigned a positive integer value.
-
-   string variables consist of any number of printable characters. strings
-   must be enclosed in quotes if they contain spaces or tabs. You may also
-   use the ``C'' escape sequences \n and \t for newline and tab,
-   respectively.
-
-   quadoption variables are used to control whether or not to be prompted for
-   certain actions, or to specify a default action. A value of yes will cause
-   the action to be carried out automatically as if you had answered yes to
-   the question. Similarly, a value of no will cause the the action to be
-   carried out as if you had answered ``no.'' A value of ask-yes will cause a
-   prompt with a default answer of ``yes'' and ask-no will provide a default
-   answer of ``no.''
-
-   Prefixing a variable with ``no'' will unset it. Example: set noaskbcc .
-
-   For boolean variables, you may optionally prefix the variable name with
-   inv to toggle the value (on or off). This is useful when writing macros.
-   Example: set invsmart_wrap.
-
-   The toggle command automatically prepends the inv prefix to all specified
-   variables.
-
-   The unset command automatically prepends the no prefix to all specified
-   variables.
-
-   Using the enter-command function in the index menu, you can query the
-   value of a variable by prefixing the name of the variable with a question
-   mark:
-
- set ?allow_8bit
-
-   The question mark is actually only required for boolean and quadoption
-   variables.
-
-   The reset command resets all given variables to the compile time defaults
-   (hopefully mentioned in this manual). If you use the command set and
-   prefix the variable with ``&'' this has the same behavior as the reset
-   command.
-
-   With the reset command there exists the special variable ``all'', which
-   allows you to reset all variables to their system defaults.
-
-29. Reading initialization commands from another file
-
-   Usage: sourcefilename [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 I
-   can make my ~/.muttrc readable and keep my aliases private.
-
-   If the filename begins with a tilde (``~''), it will be expanded to the
-   path of your home directory.
-
-   If the filename ends with a vertical bar (|), then filename is considered
-   to be an executable program from which to read input (eg. source
-   ~/bin/myscript|).
-
-30. Removing hooks
-
-   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,
-   or you can remove all hooks of a specific type by saying something like
-   unhook send.
-
-31. Sharing Setups
-
-  31.1. Character Sets
-
-   As users may run mutt-ng on different systems, the configuration must be
-   maintained because it's likely that people want to use the setup
-   everywhere they use mutt-ng. And mutt-ng tries to help where it can.
-
-   To not produce conflicts with different character sets, mutt-ng allows
-   users to specify in which character set their configuration files are
-   encoded. Please note that while reading the configuration files, this is
-   only respected after the corresponding declaration appears. It's advised
-   to put the following at the very beginning of a users muttngrc:
-
- set config_charset = "..."
-
-   and replacing the dots with the actual character set. To avoid problems
-   while maintaining the setup, vim(1) user's may want to use modelines as
-   show in:
-
- # vim:fileencoding=...:
-
-   while, again, replacing the dots with the appropriate name. This tells
-   vim(1) as which character set to read and save the file.
-
-  31.2. Modularization
-
-   ``Modularization'' means to divide the setup into several files while
-   sorting the options or commands by topic. Especially for longer setups
-   (e.g. with many hooks), this helps maintaining it and solving trouble.
-
-   When using separation, setups may be, as a whole or in fractions, shared
-   over different systems.
-
-  31.3. Conditional parts
-
-   When using a configuration on different systems, the user may not always
-   have influence on how mutt-ng is installed and which features it includes.
-
-   To solve this, mutt-ng contain a feature based on the ``ifdef'' patch
-   written for mutt. Its basic syntax is:
-
- ifdef <item> <command>
- ifndef <item> <command>
-
-   ...whereby <item> can be one of:
-
-     o a function name
-
-     o a variable name
-
-     o a menu name
-
-     o a feature name
-
-   All available functions, variables and menus are documented elsewhere in
-   this manual but ``features'' is specific to these two commands. To test
-   for one, prefix one of the following keywords with feature_: ncurses,
-   slang, iconv, idn, dotlock, standalone, pop, nntp, imap, ssl, gnutls,
-   sasl, sasl2, libesmtp, compressed, color, classic_pgp, classic_smime,
-   gpgme, header_cache
-
-   As an example, one can use the following in ~/.muttngrc:
-
- ifdef feature_imap 'source ~/.mutt-ng/setup-imap'
- 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.
-
-   An example for testing for variable names can be used if users use
-   different revisions of mutt-ng whereby the older one may not have a
-   certain variable. To test for the availability of $imap_mail_check use:
-
- 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
-   have been renamed and some of the old names were already removed. Please
-   see sect-obsolete for a complete list.
-
-Chapter 4. Advanced Usage
-
-   Table of Contents
-
-   1. Regular Expressions
-
-   2. Patterns
-
-                2.1. Complex Patterns
-
-                2.2. Patterns and Dates
-
-   3. Format Strings
-
-                3.1. Introduction
-
-                3.2. Conditional Expansion
-
-                3.3. Modifications and Padding
-
-   4. Using Tags
-
-   5. Using Hooks
-
-                5.1. Message Matching in Hooks
-
-   6. Using the sidebar
-
-   7. External Address Queries
-
-   8. Mailbox Formats
-
-   9. Mailbox Shortcuts
-
-   10. Handling Mailing Lists
-
-   11. Editing threads
-
-                11.1. Linking threads
-
-                11.2. Breaking threads
-
-   12. Delivery Status Notification (DSN) Support
-
-   13. POP3 Support (OPTIONAL)
-
-   14. IMAP Support (OPTIONAL)
-
-                14.1. The Folder Browser
-
-                14.2. Authentication
-
-   15. NNTP Support (OPTIONAL)
-
-                15.1. Again: Scoring
-
-   16. SMTP Support (OPTIONAL)
-
-   17. Managing multiple IMAP/POP/NNTP accounts (OPTIONAL)
-
-   18. Start a WWW Browser on URLs (EXTERNAL)
-
-   19. Compressed folders Support (OPTIONAL)
-
-                19.1. Open a compressed mailbox for reading
-
-                19.2. Write a compressed mailbox
-
-                19.3. Append a message to a compressed mailbox
-
-                19.4. Encrypted folders
-
-1. Regular Expressions
-
-   All string patterns in Mutt-ng including those in more complex patterns
-   must be specified using regular expressions (regexp) in the ``POSIX
-   extended'' syntax (which is more or less the syntax used by egrep and GNU
-   awk). For your convenience, we have included below a brief description of
-   this syntax.
-
-   The search is case sensitive if the pattern contains at least one upper
-   case letter, and case insensitive otherwise. Note that ``\'' must be
-   quoted if used for a regular expression in an initialization command:
-   ``\\''.
-
-   A regular expression is a pattern that describes a set of strings. Regular
-   expressions are constructed analogously to arithmetic expressions, by
-   using various operators to combine smaller expressions.
-
-   Note that the regular expression can be enclosed/delimited by either " or
-   ' which is useful if the regular expression includes a white-space
-   character. See muttrc-syntax for more information on " and ' delimiter
-   processing. To match a literal " or ' you must preface it with \
-   (backslash).
-
-   The fundamental building blocks are the regular expressions that match a
-   single character. Most characters, including all letters and digits, are
-   regular expressions that match themselves. Any metacharacter with special
-   meaning may be quoted by preceding it with a backslash.
-
-   The period ``.'' matches any single character. The caret ``^'' andthe
-   dollar sign ``$'' are metacharacters that respectively match the empty
-   string at the beginning and end of a line.
-
-   A list of characters enclosed by ``]'' and ``]'' matches any single
-   character in that list; if the first character of the list is a caret
-   ``^'' then it matches any character not in the list. For example, the
-   regular expression ]0123456789] matches any single digit. A range of ASCII
-   characters may be specified by giving the first and last characters,
-   separated by a hyphen ``-''. Most metacharacters lose their special
-   meaning inside lists. To include a literal ``]'' place it first in the
-   list. Similarly, to include a literal ``^'' place it anywhere but first.
-   Finally, to include a literal hyphen ``-'' place it last.
-
-   Certain named classes of characters are predefined. Character classes
-   consist of ``[:'', a keyword denoting the class, and ``:]''. The following
-   classes are defined by the POSIX standard:
-
-   [:alnum:]
-
-           Alphanumeric characters.
-
-   [:alpha:]
-
-           Alphabetic characters.
-
-   [:blank:]
-
-           Space or tab characters.
-
-   [:cntrl:]
-
-           Control characters.
-
-   [:digit:]
-
-           Numeric characters.
-
-   [:graph:]
-
-           Characters that are both printable and visible. (A space is
-           printable, but not visible, while an ``a'' is both.)
-
-   [:lower:]
-
-           Lower-case alphabetic characters.
-
-   [:print:]
-
-           Printable characters (characters that are not control characters.)
-
-   [:punct:]
-
-           Punctuation characters (characters that are not letter, digits,
-           control characters, or space characters).
-
-   [:space:]
-
-           Space characters (such as space, tab and formfeed, to name a few).
-
-   [:upper:]
-
-           Upper-case alphabetic characters.
-
-   [:xdigit:]
-
-           Characters that are hexadecimal digits.
-
-   A character class is only valid in a regular expression inside the
-   brackets of a character list. Note that the brackets in these class names
-   are part of the symbolic names, and must be included in addition to the
-   brackets delimiting the bracket list. For example, [[:digit:]] is
-   equivalent to [0-9].
-
-   Two additional special sequences can appear in character lists. These
-   apply to non-ASCII character sets, which can have single symbols
-   (calledcollating elements) that are represented with more than one
-   character, as well as several characters that are equivalent for collating
-   or sorting purposes:
-
-   Collating Symbols
-
-           A collating symbol is a multi-character collating element enclosed
-           in ``[.'' and ``.]''. For example, if ``ch'' is a collating
-           element, then [[.ch.]] is a regexp that matches this collating
-           element, while [ch] is a regexp that matches either ``c'' or
-           ``h''.
-
-   Equivalence Classes
-
-           An equivalence class is a locale-specific name for a list of
-           characters that are equivalent. The name is enclosed in ``[='' and
-           ``=]''. For example, the name ``e'' might be used to represent all
-           of ``Ã¨'' ``Ã©'' and ``e''. In this case, [[=e=]] is a regexp that
-           matches any of ``Ã¨'', ``Ã©'' and ``e''.
-
-   A regular expression matching a single character may be followed by one of
-   several repetition operators:
-
-   ?
-
-           The preceding item is optional and matched at most once.
-
-   *
-
-           The preceding item will be matched zero or more times.
-
-   +
-
-           The preceding item will be matched one or more times.
-
-   {n}
-
-           The preceding item is matched exactly n times.
-
-   {n,}
-
-           The preceding item is matched n or more times.
-
-   {,m}
-
-           The preceding item is matched at most m times.
-
-   {n,m}
-
-           The preceding item is matched at least n times, but no more than m
-           times.
-
-   Two regular expressions may be concatenated; the resulting regular
-   expression matches any string formed by concatenating two substrings that
-   respectively match the concatenated subexpressions.
-
-   Two regular expressions may be joined by the infix operator ``|''; the
-   resulting regular expression matches any string matching either
-   subexpression.
-
-   Repetition takes precedence over concatenation, which in turn takes
-   precedence over alternation. A whole subexpression may be enclosed in
-   parentheses to override these precedence rules.
-
-   Note: If you compile Mutt-ng with the GNU rx package, the following
-   operators may also be used in regular expressions:
-
-   \\y
-
-           Matches the empty string at either the beginning or the end of a
-           word.
-
-   \\B
-
-           Matches the empty string within a word.
-
-   \\<
-
-           Matches the empty string at the beginning of a word.
-
-   \\>
-
-           Matches the empty string at the end of a word.
-
-   \\w
-
-           Matches any word-constituent character (letter, digit, or
-           underscore).
-
-   \\W
-
-           Matches any character that is not word-constituent.
-
-   \\`
-
-           Matches the empty string at the beginning of a buffer (string).
-
-   \\'
-
-           Matches the empty string at the end of a buffer.
-
-   Please note however that these operators are not defined by POSIX, so they
-   may or may not be available in stock libraries on various systems.
-
-2. Patterns
-
-   Mutt-ng's pattern language provides a simple yet effective way to set up
-   rules to match messages, e.g. for operations like tagging and scoring. A
-   pattern consists of one or more sub-pattern, which can be logically
-   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 is a regular expression. For
-   ranges, the forms <[MAX], >>[MIN], [MIN]- and -[MAX] are also possible.
-
-  2.1. Complex Patterns
-
-   It is possible to combine several sub-patterns to a more complex pattern.
-   The most simple possibility is to logically AND several patterns by
-   stringing them together:
-
- ~s 'SPAM' ~U
-
-   The pattern above matches all messages that contain ``SPAM'' in the
-   subject and are unread.
-
-   To logical OR patterns, simply use the | operator. This one especially
-   useful when using local groups:
-
- ~f ("nion@muttng\.org"|"ak@muttng\.org"|"pdmef@muttng\.org")
- (~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
-   third pattern matches all messages that do not contain ``@synflood\.at''
-   in the References: header, i.e. messages that are not an (indirect) reply
-   to one of my messages. A pattern can be logicall negated using the !
-   operator.
-
-  2.2. Patterns and Dates
-
-   When using dates in patterns, the dates must be specified in a special
-   format, i.e. DD/MM/YYYY. If you don't specify month or year, they default
-   to the current month or year. When using date ranges, and you specify only
-   the minimum or the maximum, the specified date will be excluded, e.g.
-   01/06/2005- matches against all messages after Juni 1st, 2005.
-
-   It is also possible to use so-called ``error margins'' when specifying
-   date ranges. You simply specify a date, and then the error margin. This
-   margin needs to contain the information whether it goes ``forth'' or
-   ``back'' in time, by using + and -. Then follows a number and a unit, i.e.
-   y for years, m for months, w for weeks and d for days. If you use the
-   special * sign, it means that the error margin goes to both``directions''
-   in time.
-
- ~d 01/01/2005+1y
- ~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
-   matches all dates 1 day around December 28th, 2004 (i.e. Dec 27th, 28th
-   and 29th).
-
-   Relative dates are also very important, as they make it possible to
-   specify date ranges between a fixed number of units and the current date.
-   How this works can be seen in the following example:
-
- ~d >2w # messages older than two weeks
- ~d <3d # messages newer than 3 days
- ~d =1m # messages that are exactly one month old
-
-3. Format Strings
-
-  3.1. Introduction
-
-   The so called Format Strings offer great flexibility when configuring
-   mutt-ng. In short, they describe what items to print out how in menus and
-   status messages.
-
-   Basically, they work as this: for different menus and bars, there's a
-   variable specifying the layout. For every item available, there is a so
-   called expando.
-
-   For example, when running mutt-ng on different machines or different
-   versions for testing purposes, it may be interesting to have the following
-   information always printed on screen when one is in the index:
-
-     o the current hostname
-
-     o the current mutt-ng version number
-
-   The setting for the status bar of the index is controlled via the
-   $status_format variable. For the hostname and version string, there's an
-   expando for $status_format: %h expands to the hostname and %v to the
-   version string. When just configuring:
-
- 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
-
-     o how man new, flagged or postponed messages
-
-     o ...
-
-   To include the mailbox' name is as easy as:
-
- 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
-   instead only print something if there are any.
-
-  3.2. Conditional Expansion
-
-   To only print the number of messages if there are new messages in the
-   current mailbox, further extend $status_format to:
-
- 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
-   basic syntax is:
-
- %?<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.
-
-   But this is not all: this feature only offers one alternative: ``print
-   something if not zero.'' Mutt-ng does, as you might guess, also provide a
-   logically complete version: ``if zero, print something and else print
-   something else.'' This is achieved by the following syntax for those
-   expandos which may be printed nonzero:
-
- %?<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
-       there new ones
-
-     o and make it print ``no new messages'' if there aren't any
-
-   The corresponding configuration is:
-
- 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.
-
-  3.3. Modifications and Padding
-
-   Besides the information given so far, there're even more features of
-   format strings:
-
-     o When specifying %_<item> instead of just %<item>, mutt-ng will convert
-       all characters in the expansion of <item> to lowercase.
-
-     o When specifying %:<item> instead of just %<item>, mutt-ng will convert
-       all dots in the expansion of <item> to underscores (_).
-
-   Also, there's a feature called Padding supplied by the following two
-   expandos: %|X and %>X .
-
-   %|X
-
-           When this occurs, mutt-ng will fill the rest of the line with the
-           character X. In our example, filling the rest of the line with
-           dashes is done by setting:
-
- 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
-           a way to fill the gap between two items via the %>X expando: it
-           puts as many characters X in between two items so that the rest of
-           the line will be right-justified. For example, to not put the
-           version string and hostname of our example on the left but on the
-           right and fill the gap with spaces, one might use (note the space
-           after %>):
-
- 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
-   all at once rather than one at a time. An example might be to save
-   messages to a mailing list to a separate folder, or to delete all messages
-   with a given subject. To tag all messages matching a pattern, use the
-   tag-pattern function, which is bound to ``shift-T'' by default. Or you can
-   select individual messages by hand using the ``tag-message'' function,
-   which is bound to ``t'' by default. See patterns for Mutt-ng's pattern
-   matching syntax.
-
-   Once you have tagged the desired messages, you can use the ``tag-prefix''
-   operator, which is the ``;'' (semicolon) key by default. When the
-   ``tag-prefix'' operator is used, the next operation will be applied to all
-   tagged messages if that operation can be used in that manner. If the
-   $auto_tag variable is set, the next operation applies to the tagged
-   messages automatically, without requiring the ``tag-prefix''.
-
-   In macro or push commands, you can use the ``tag-prefix-cond'' operator.
-   If there are no tagged messages, mutt will "eat" the rest of the macro to
-   abort it's execution.Mutt-ng will stop "eating" the macro when it
-   encounters the ``end-cond'' operator; after this operator the rest of the
-   macro will be executed asnormal.
-
-5. Using Hooks
-
-   A hook is a concept borrowed from the EMACS editor which allows you to
-   execute arbitrary commands before performing some operation. For example,
-   you may wish to tailor your configuration based upon which mailbox you are
-   reading, or to whom you are sending mail. In the Mutt-ng world, a hook
-   consists of a regexp or patterns along with a configuration
-   option/command. See
-
-     o folder-hook
-
-     o send-hook
-
-     o message-hook
-
-     o save-hook
-
-     o mbox-hook
-
-     o fcc-hook
-
-     o fcc-save-hook
-
-   for specific details on each type of hook available.
-
-   Note: if a hook changes configuration settings, these changes remain
-   effective until the end of the current mutt session. As this is generally
-   not desired, a default hook needs to be added before all other hooks to
-   restore configuration defaults. Here is an example with send-hook and the
-   my_hdr directive:
-
- 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
-   )are evaluated in a slightly different manner. For the other types of
-   hooks, a regexp is sufficient. But in dealing with messages a finer grain
-   of control is needed for matching since for different purposes you want to
-   match different criteria.
-
-   Mutt-ng allows the use of the patterns language for matching messages in
-   hook commands. This works in exactly the same way as it would when
-   limiting orsearching the mailbox, except that you are restricted to those
-   operators which match information mutt extracts from the header of the
-   message (i.e. from, to, cc, date, subject, etc.).
-
-   For example, if you wanted to set your return address based upon sending
-   mail to a specific address, you could do something like:
-
- 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
-   full searching language. You can still specify a simple regular expression
-   like the other hooks, in which case Mutt-ng will translate your pattern
-   into the full language, using the translation specified by the
-   default-hook variable. The pattern is translated at the time the hook is
-   declared, so the value of default-hook that is in effect at that time will
-   be used.
-
-6. Using the sidebar
-
-   The sidebar, a feature specific to Mutt-ng, allows you to use a mailbox
-   listing which looks very similar to the ones you probably know from GUI
-   mail clients. The sidebar lists all specified mailboxes, shows the number
-   in each and highlights the ones with new email Use the following
-   configuration commands:
-
- set sidebar_visible="yes"
- set sidebar_width=25
-
-   If you want to specify the mailboxes you can do so with:
-
- set mbox='=INBOX'
- mailboxes INBOX \
- MBOX1 \
- MBOX2 \
- ...
-
-   You can also specify the colors for mailboxes with new mails by using:
-
- color sidebar_new red black
- color sidebar white black
-
-   Reasonable key bindings look e.g. like this:
-
- bind index \Cp sidebar-prev
- bind index \Cn sidebar-next
- bind index \Cb sidebar-open
- bind pager \Cp sidebar-prev
- bind pager \Cn sidebar-next
- bind pager \Cb sidebar-open
-
- 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'.
-
-7. External Address Queries
-
-   Mutt-ng supports connecting to external directory databases such as LDAP,
-   ph/qi, bbdb, or NIS through a wrapper script which connects to mutt using
-   a simple interface. Using the $query_command variable, you specify the
-   wrapper command to use. For example:
-
- 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
-   optional information. On error, or if there are no matching addresses,
-   return a non-zero exit code and a one line error message.
-
-   An example multiple response output:
-
- Searching database ... 20 entries ... 3 matching:
- me@cs.hmc.edu           Michael Elkins  mutt dude
- 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
-   the matching responses. From the query menu, you can select addresses to
-   create aliases, or to mail. You can tag multiple addressesto mail, start a
-   new query, or have a new query appended to the current responses.
-
-   The other mechanism for accessing the query function is for address
-   completion, similar to the alias completion. In any prompt for address
-   entry, you can use the complete-query function (default: ^T) to run a
-   query based on the current address you have typed. Like aliases, mutt will
-   look for what you have typed back to the last space or comma. If there is
-   a single response for that query, mutt will expand the address in place.
-   If there are multiple responses, mutt will activate the querymenu. At the
-   query menu, you can select one or more addresses to be added to the
-   prompt.
-
-8. Mailbox Formats
-
-   Mutt-ng supports reading and writing of four different mailbox formats:
-   mbox, MMDF, MH and Maildir. The mailbox type is autodetected, so there is
-   no need to use a flag for different mailbox types. When creating
-   newmailboxes, Mutt-ng uses the default specified with the $mbox_type
-   variable.
-
-   mbox. This is the most widely used mailbox format for UNIX. All messages
-   are stored in a single file. Each message has a line of the form:
-
- 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).
-
-   MMDF. This is a variant of the mbox format. Each message is surrounded by
-   lines containing ``^A^A^A^A'' (four control-A's).
-
-   MH. A radical departure from mbox and MMDF, a mailbox consists of a
-   directory and each message is stored in a separate file. The filename
-   indicates the message number (however, this is may not correspond to the
-   message number Mutt-ng displays). Deleted messages arerenamed with a comma
-   (,) prepended to the filename. Note: Mutt detects this type of mailbox by
-   looking for either .mh_sequences or .xmhcache (needed to distinguish
-   normal directories from MH mailboxes).
-
-   Maildir. The newest of the mailbox formats, used by the Qmail MTA (a
-   replacement for sendmail). Similar to MH, except that it adds three
-   subdirectories of the mailbox: tmp, new and cur .Filenames for the
-   messages are chosen in such a way they are unique, even when twoprograms
-   are writing the mailbox over NFS, which means that no file locking is
-   needed.
-
-9. Mailbox Shortcuts
-
-   There are a number of built in shortcuts which refer to specific
-   mailboxes. These shortcuts can be used anywhere you are prompted for a
-   file or mailbox path.
-
-     o ! -- refers to your $spoolfile (incoming) mailbox
-
-     o > -- refers to your $mbox file
-
-     o < -- refers to your $record file
-
-     o ^ -- refers to the current mailbox
-
-     o - or !! -- refers to the file you've last visited
-
-     o ~ -- refers to your home directory
-
-     o = or + -- refers to your $folder directory
-
-     o @alias -- refers to the save-hook as determined by the address of the
-       alias
-
-10. Handling Mailing Lists
-
-   Mutt-ng has a few configuration options that make dealing with large
-   amounts of mail easier. The first thing you must do is to let Mutt know
-   what addresses you consider to be mailing lists (technically this does not
-   have to be a mailing list, but that is what it is most often used for),
-   and what lists you are subscribed to. This is accomplished through the use
-   of the lists commands in your muttrc.
-
-   Now that Mutt-ng knows what your mailing lists are, it can do several
-   things, the first of which is the ability to show the name of a list
-   through which you received a message (i.e., of a subscribed list) in the
-   index menu display. This is useful to distinguish between personal and
-   list mail in the same mailbox. In the $index_format variable, the escape
-   ``%L'' will return the string ``To <list>'' when ``list'' appears in the
-   ``To'' field, and ``Cc <list>'' when it appears in the ``Cc'' field
-   (otherwise it returns the name of the author).
-
-   Often times the ``To'' and ``Cc'' fields in mailing list messages tend to
-   get quite large. Most people do not bother to remove the author of the
-   message they are reply to from the list, resulting in two or more copies
-   being sent to that person. The ``list-reply'' function, which by default
-   is bound to ``L'' in the index menu and pager, helps reduce the clutter by
-   only replying to the known mailing list addresses instead of all
-   recipients (except as specified by Mail-Followup-To, see below).
-
-   Mutt-ng also supports the Mail-Followup-To header. When you send a message
-   to a list of recipients which includes one or several subscribed mailing
-   lists, and if the $followup_to option is set, mutt will generate a
-   Mail-Followup-To header which contains all the recipients to whom you send
-   this message, but not your address. This indicates that group-replies or
-   list-replies (also known as ``followups'') to this message should only be
-   sent to the original recipients of the message, and not separately to you
-   - you'll receive your copy through one of the mailing lists you are
-   subscribed to.
-
-   Conversely, when group-replying or list-replying to a message which has a
-   Mail-Followup-To header, mutt will respect this header if the
-   $honor_followup_to configuration variable is set. Using list-reply will in
-   this case also make sure that the reply goes to the mailing list, even if
-   it's not specified in the list of recipients in the Mail-Followup-To.
-
-   Note that, when header editing is enabled, you can create a
-   Mail-Followup-To header manually. Mutt-ng will only auto-generate this
-   header if it doesn't exist when you send the message.
-
-   The other method some mailing list admins use is to generate a
-   ``Reply-To'' field which points back to the mailing list address rather
-   than the author of the message. This can create problems when trying to
-   reply directly to the author in private, since most mail clients will
-   automatically reply to the address given in the ``Reply-To'' field.
-   Mutt-ng uses the $reply_to variable to help decide which address to use.
-   If set to ask-yes or ask-no, you will be prompted as to whether or not you
-   would like to use the address given inthe ``Reply-To'' field, or reply
-   directly to the address given in the ``From'' field. When set to yes, the
-   ``Reply-To'' field will be used when present.
-
-   The ``X-Label:'' header field can be used to further identify mailing
-   lists or list subject matter (or just to annotate messages individually).
-   The $index_format variable's ``%y'' and ``%Y'' escapes can be used to
-   expand ``X-Label:'' fields in the index, and Mutt-ng's pattern-matcher can
-   match regular expressions to ``X-Label:'' fields with the ``~y'' selector.
-   ``X-Label:'' is not a standard message header field, but it can easily be
-   inserted by procmailand other mail filtering agents.
-
-   Lastly, Mutt-ng has the ability to sort the mailbox into threads. A thread
-   is a group of messages which all relate to the same subject. This is
-   usually organized into a tree-like structure where a message and all of
-   its replies are represented graphically. If you've ever used a threaded
-   news client, this is the same concept. It makes dealingwith large volume
-   mailing lists easier because you can easily delete uninteresting threads
-   and quickly find topics of value.
-
-11. Editing threads
-
-   Mutt-ng has the ability to dynamically restructure threads that are broken
-   either by misconfigured software or bad behavior from some correspondents.
-   This allows to clean your mailboxes formats) from these annoyances which
-   make it hard to follow a discussion.
-
-  11.1. Linking threads
-
-   Some mailers tend to "forget" to correctly set the "In-Reply-To:" and
-   "References:" headers when replying to a message. This results in broken
-   discussions because Mutt-ng has not enough information to guess the
-   correct threading. You can fix this by tagging the reply, then moving to
-   the parent message and using the ``link-threads'' function (bound to & by
-   default). The reply will then be connected to this "parent" message.
-
-   You can also connect multiple children at once, tagging them and using the
-   tag-prefix command (';') or the auto_tag option.
-
-  11.2. Breaking threads
-
-   On mailing lists, some people are in the bad habit of starting a new
-   discussion by hitting "reply" to any message from the list and changing
-   the subject to a totally unrelated one. You can fix such threads by using
-   the ``break-thread'' function (boundby default to #), which will turn the
-   subthread starting from the current message into a whole different thread.
-
-12. Delivery Status Notification (DSN) Support
-
-   RfC 1894 defines a set of MIME content types for relaying information
-   about the status of electronic mail messages. These can be thought of as
-   ``return receipts.''
-
-   Users can make use of it in one of the following two ways:
-
-     o Berkeley sendmail 8.8.x currently has some command line options in
-       which the mail client can make requests as to what type of status
-       messages should be returned.
-
-     o The SMTP support via libESMTP supports it, too.
-
-   To support this, there are two variables:
-
-     o $dsn_notify is used to request receipts for different results (such as
-       failed message,message delivered, etc.).
-
-     o $dsn_return requests how much of your message should be returned with
-       the receipt (headers or full message).
-
-   Please see the reference chapter for possible values.
-
-13. POP3 Support (OPTIONAL)
-
-   If Mutt-ng was compiled with POP3 support (by running the configure script
-   with the --enable-pop flag), it has the ability to work with mailboxes
-   located on a remote POP3 server and fetch mail for local browsing.
-
-   You can access the remote POP3 mailbox by selecting the folder
-   pop://popserver/.
-
-   You can select an alternative port by specifying it with the server, i.e.:
-   pop://popserver:port/.
-
-   You can also specify different username for each folder, i.e.:
-   pop://username@popserver[:port]/.
-
-   Polling for new mail is more expensive over POP3 than locally. For this
-   reason the frequency at which Mutt-ng will check for mail remotely can be
-   controlled by the $pop_mail_check variable, which defaults to every 60
-   seconds.
-
-   If Mutt-ng was compiled with SSL support (by running the configure script
-   with the --with-ssl flag), connections to POP3 servers can be encrypted.
-   This naturally requires that the server supports SSL encrypted
-   connections. To access a folder with POP3/SSL, you should use pops:
-   prefix, ie: pops://[username@]popserver[:port]/.
-
-   Another way to access your POP3 mail is the fetch-mail function (default:
-   G). It allows to connect to pop-host ,fetch all your new mail and place it
-   in the local $spoolfile. After this point, Mutt-ng runs exactly as if the
-   mail had always been local.
-
-   Note: If you only need to fetch all messages to local mailbox you should
-   consider using a specialized program, such as fetchmail(1).
-
-14. IMAP Support (OPTIONAL)
-
-   If Mutt-ng was compiled with IMAP support (by running the configure script
-   with the --enable-imap flag), it has the ability to work with folders
-   located on a remote IMAP server.
-
-   You can access the remote inbox by selecting the folder via its URL:
-
- imap://imapserver/INBOX
-
-   where imapserver is the name of the IMAP server and INBOX is the special
-   name for your spool mailbox on the IMAP server. If you want to access
-   another mail folder at the IMAP server, you should use
-
- imap://imapserver/path/to/folder
-
-   where path/to/folder is the path of the folder you want to access. You can
-   select an alternative port by specifying it with the server, i.e.:
-
- imap://imapserver:port/INBOX
-
-   You can also specify different username for each folder by prenpending
-   your username and an @ symbol to the server's name.
-
-   If Mutt-ng was compiled with SSL support (by running the configure script
-   with the --with-ssl flag), connections to IMAP servers can be encrypted.
-   This naturally requires that the server supports SSL encrypted
-   connections. To access a folder with IMAP/SSL, you only need to substitute
-   the initial imap:// by imaps:// in the above examples.
-
-   Note that not all servers use / as the hierarchy separator. Mutt-ng should
-   correctly notice which separator is being used by the server and
-   convertpaths accordingly.
-
-   When browsing folders on an IMAP server, you can toggle whether to look at
-   only the folders you are subscribed to, or all folders with the
-   toggle-subscribed command. See also the $imap_list_subscribed variable.
-
-   Polling for new mail on an IMAP server can cause noticeable delays. So,
-   you'll want to carefully tune the $imap_mail_check and $timeout variables.
-
-   Note that if you are using mbox as the mail store on UW servers prior
-   tov12.250, the server has been reported to disconnect a client if another
-   client selects the same folder.
-
-  14.1. The Folder Browser
-
-   As of version 1.2, mutt supports browsing mailboxes on an IMAP server.
-   This is mostly the same as the local file browser, with the following
-   differences:
-
-     o Instead of file permissions, mutt displays the string "IMAP", possibly
-       followed by the symbol "+", indicating that the entry contains both
-       messages and subfolders. On Cyrus-like servers folders will often
-       contain both messages and subfolders.
-
-     o For the case where an entry can contain both messages and subfolders,
-       the selection key (bound to enter by default) will choose to descend
-       into the subfolder view. If you wish to view the messages in that
-       folder, you must use view-file instead (bound to space by default).
-
-     o You can create, delete and rename mailboxes with the create-mailbox,
-       delete-mailbox, and rename-mailbox commands (default bindings: C , d
-       and r, respectively). You may also subscribe and unsubscribe to
-       mailboxes (normally these are bound to s and u, respectively).
-
-  14.2. Authentication
-
-   Mutt-ng supports four authentication methods with IMAP servers: SASL,
-   GSSAPI, CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add NTLM
-   authentication for you poor exchange users out there, but it has yet to be
-   integrated into the main tree). There is also support for the
-   pseudo-protocol ANONYMOUS, which allows you to log in to a public IMAP
-   server without having an account. To use ANONYMOUS, simply make your
-   username blank or "anonymous".
-
-   SASL is a special super-authenticator, which selects among several
-   protocols (including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most
-   secure method available on your host and the server. Using some of these
-   methods (including DIGEST-MD5 and possibly GSSAPI), your entire session
-   will be encrypted and invisible to those teeming network snoops. It is the
-   best option if you have it. To use it, you must have the Cyrus SASL
-   libraryinstalled on your system and compile mutt with the --with-sasl
-   flag.
-
-   Mutt-ng will try whichever methods are compiled in and available on the
-   server, in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
-
-   There are a few variables which control authentication:
-
-     o $imap_user - controls the username under which you request
-       authentication on the IMAP server, for all authenticators. This is
-       overridden by an explicit username in the mailbox path (i.e. by using
-       a mailbox name of the form {user@host}).
-
-     o $imap_pass - a password which you may preset, used by all
-       authentication methods where a password is needed.
-
-     o $imap_authenticators - a colon-delimited list of IMAP authentication
-       methods to try, in the order you wish to try them. If specified, this
-       overrides mutt's default (attempt everything, in the order listed
-       above).
-
-15. NNTP Support (OPTIONAL)
-
-   If compiled with ``--enable-nntp'' option, Mutt-ng can read news from a
-   newsserver via NNTP. You can open a newsgroup with the
-   ``change-newsgroup'' function from the index/pager which is by default
-   bound to i.
-
-   The Default newsserver can be obtained from the $NNTPSERVER environment
-   variable. Like other news readers, info about subscribed newsgroups is
-   saved in a file as specified by the $nntp_newsrc variable. Article headers
-   are cached and can be loaded from a file when a newsgroup is entered
-   instead loading from newsserver; currently, this caching mechanism still
-   is different from the header caching for maildir/IMAP.
-
-  15.1. Again: Scoring
-
-   Especially for Usenet, people often ask for advanced filtering and scoring
-   functionality. Of course, mutt-ng has scoring and allows a killfile, too.
-   How to use a killfile has been discussed in Message Scoring.
-
-   What has not been discusses in detail is mutt-ng's built-in realname
-   filter. For may newsreaders including those for ``advanced users'' like
-   slrn or tin, there are frequent request for such functionality. The
-   solutions offered often are complicated regular expressions.
-
-   In mutt-ng this is as easy as
-
- 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:
-
-     o Email addresses must be valid according to RfC 2822
-
-     o the name must consist of at least 2 fields whereby a field must not
-       end in a dot. This means that ``Joe User'' and ``Joe A.User'' are
-       valid while ``J. User'' and ``J. A. User'' aren't.
-
-     o it's assumed that users are interested in reading their own mail and
-       mail from people who they have defined an alias forso that those 2
-       groups of messages are excluded from the strict rules.
-
-16. SMTP Support (OPTIONAL)
-
-   Mutt-ng can be built using a library called ``libESMTP'' which provides
-   SMTP functionality. When configure was called with --with-libesmtp or the
-   output muttng -v contains +USE_LIBESMTP, this will be or is the case
-   already. The SMTP support includes support for Delivery Status
-   Notification (see dsn section) as well as handling the 8BITMIME flag
-   controlled via $use_8bitmime.
-
-   To enable sending mail directly via SMTP without an MTA such as Postfix or
-   SSMTP and the like, simply set the $smtp_host variable pointing to your
-   SMTP server.
-
-   Authentication mechanisms are available via the $smtp_user and $smtp_pass
-   variables.
-
-   Transport Encryption via the StartTLS command is also available. For this
-   to work, first of all Mutt-ng must be built with SSL or GNUTLS. Secondly,
-   the $smtp_use_tls variable must be either set to ``enabled'' or
-   ``required.'' In both cases, StartTLS will be used if the server supports
-   it: for the second case, the connection will fail ifit doesn't while
-   switching back to unencrypted communication for the first one.
-
-   Some mail providers require user's to set a particular envelope sender,
-   i.e. they allow for only one value which may not be what the user wants to
-   send as the From: header. In this case, the variable $smtp_envelope may be
-   used to set the envelope different from the From: header.
-
-17. Managing multiple IMAP/POP/NNTP accounts (OPTIONAL)
-
-   If you happen to have accounts on multiple IMAP and/or POP servers, you
-   may find managing all the authentication settings inconvenient and
-   error-prone. The account-hook command may help. This hook works like
-   folder-hook but is invoked whenever you access a remote mailbox (including
-   inside the folder browser), not just when you open the mailbox.
-
-   Some examples:
-
- account-hook . 'unset imap_user; unset imap_pass; unset tunnel'
- 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
-   space like http://www.mutt.org/), it is efficient to get a menu with all
-   the URLs and start a WWW browser on one of them. This functionality is
-   provided by the external urlview program which can be retrieved at
-   <ftp://ftp.mutt.org/mutt/contrib/> and the configuration commands:
-
- 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
-   configure script with the --enable-compressed flag), Mutt can open folders
-   stored in an arbitrary format, provided that the user has a script to
-   convert from/to this format to one of the accepted.
-
-   The most common use is to open compressed archived folders e.g. with gzip.
-
-   In addition, the user can provide a script that gets a folder in an
-   accepted format and appends its context to the folder in the user-defined
-   format, which may be faster than converting the entire folder to the
-   accepted format, appending to it and converting back to the user-defined
-   format.
-
-   There are three hooks defined (open-hook, close-hook and append-hook
-   )which define commands to uncompress and compress a folder and to append
-   messages to an existing compressed folder respectively.
-
-   For example:
-
- open-hook \\.gz$ "gzip -cd %f > %t"
- 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
-   the mode. If you specify append-hook though you'll be able to append to
-   the folder.
-
-   Note that Mutt-ng will only try to use hooks if the file is not in one of
-   the accepted formats. In particular, if the file is empty, mutt supposes
-   it is not compressed. This is important because it allows the use of
-   programs that do not have well defined extensions. Just use "." as a
-   regexp. But this may be surprising if your compressing script produces
-   empty files. In this situation, unset $save_empty ,so that the compressed
-   file will be removed if you delete all of the messages.
-
-  19.1. Open a compressed mailbox for reading
-
-   Usage: open-hookregexp "command"
-
-   The command is the command that can be used for opening the folders whose
-   names match regexp.
-
-   The command string is the printf-like format string, and it should accept
-   two parameters: %f, which is replaced with the (compressed) folder name,
-   and %t which is replaced with the name of the temporary folder to which to
-   write.
-
-   %f and %t can be repeated any number of times in the command string, and
-   all of the entries are replaced with the appropriate folder name. In
-   addition, %% is replaced by %, as in printf, and any other %anything is
-   left as is.
-
-   The command should not remove the original compressed file. The command
-   should return non-zero exit status if it fails, so mutt knows something's
-   wrong.
-
-   Example:
-
- 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-hookregexp"command"
-
-   This is used to close the folder that was open with the open-hook command
-   after some changes were made to it.
-
-   The command string is the command that can be used for closing the folders
-   whose names match regexp. It has the same format as in the open-hook
-   command. Temporary folder in this case is the folder previously produced
-   by the open-hook command.
-
-   The command should not remove the decompressed file. The command should
-   return non-zero exit status if it fails, so mutt knows something's wrong.
-
-   Example:
-
- 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.
-
-   close-hook is not called when you exit from the folder if the folder was
-   not changed.
-
-  19.3. Append a message to a compressed mailbox
-
-   Usage: append-hookregexp"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
-   names match regexp. It has the same format as in the open-hook command.
-   The temporary folder in this case contains the messages that are
-   beingappended.
-
-   The command should not remove the decompressed file. The command should
-   return non-zero exit status if it fails, so mutt knows something's wrong.
-
-   Example:
-
- 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
-   for the temporary folder).
-
-   If the file does not exist when you save to it, close-hook is called, and
-   not append-hook. append-hook is only for appending to existing folders.
-
-   If the command is empty, this operation is disabled for this file type. In
-   this case, the folder will be open and closed again (using open-hook and
-   close-hook respectively) each time you will add to it.
-
-  19.4. Encrypted folders
-
-   The compressed folders support can also be used to handle encrypted
-   folders. If you want to encrypt a folder with PGP, you may want to usethe
-   following hooks:
-
- 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.
-
-   Note: the folder is temporary stored decrypted in the /tmp directory,
-   where it can be read by your system administrator. So thinkabout the
-   security aspects of this.
-
-Chapter 5. Mutt-ng's MIME Support
-
-   Table of Contents
-
-   1. Using MIME in Mutt
-
-                1.1. Viewing MIME messages in the pager
-
-                1.2. The Attachment Menu
-
-                1.3. The Compose Menu
-
-   2. MIME Type configuration with mime.types
-
-   3. MIME Viewer configuration with mailcap
-
-                3.1. The Basics of the mailcap file
-
-                3.2. Secure use of mailcap
-
-                3.3. Advanced mailcap Usage
-
-                3.4. Example mailcap files
-
-   4. MIME Autoview
-
-   5. MIME Multipart/Alternative
-
-   6. Attachment Searching and Counting
-
-   7. MIME Lookup
-
-   Quite a bit of effort has been made to make Mutt-ng the premier text-mode
-   MIME MUA. Every effort has been made to provide the functionality that the
-   discerning MIME user requires, and the conformance to the standards
-   wherever possible. When configuring Mutt-ng for MIME, there are two
-   extratypes of configuration files which Mutt-ng uses. One is the
-   mime.types file, which contains the mapping of file extensions to IANA
-   MIME types. The other is the mailcap file, which specifies the external
-   commands to use for handling specific MIME types.
-
-1. Using MIME in Mutt
-
-   There are three areas/menus in Mutt-ng which deal with MIME, they are the
-   pager (while viewing a message), the attachment menu and the compose menu.
-
-  1.1. Viewing MIME messages in the pager
-
-   When you select a message from the index and view it in the pager, Mutt
-   decodes the message to a text representation. Mutt-ng internally supports
-   a number of MIME types, including text/plain, text/enriched,
-   message/rfc822, and message/news .In addition, the export controlled
-   version of Mutt-ng recognizes a variety of PGP MIME types, including
-   PGP/MIME and application/pgp.
-
-   Mutt-ng will denote attachments with a couple lines describing them. These
-   lines are of the form:
-
- [-- 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.
-
-   If Mutt-ng cannot deal with a MIME type, it will display a message like:
-
- [-- 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
-   attachment menu for a message. The attachment menu displays a list ofthe
-   attachments in a message. From the attachment menu, you can save, print,
-   pipe, delete, and view attachments. You can apply these operations to a
-   group of attachments at once, by tagging the attachments and by using the
-   ``tag-prefix'' operator. You can also reply to the current message from
-   this menu, and only the current attachment (or the attachments tagged)
-   will be quoted in your reply. You can view attachments as text, or view
-   them using the mailcap viewer definition.
-
-   Finally, you can apply the usual message-related functions (like
-   <resend-message>, and the reply and forward functions) to attachments of
-   type message/rfc822.
-
-   See the help on the attachment menu for more information.
-
-  1.3. The Compose Menu
-
-   The compose menu is the menu you see before you send a message. It allows
-   you to edit the recipient list, the subject, and other aspects of your
-   message. It also contains a list of the attachments of your message,
-   including the main body. From this menu, you can print, copy, filter,
-   pipe, edit, compose, review, and rename an attachment or a list of tagged
-   attachments. You can also modifying the attachment information, notably
-   the type, encoding and description.
-
-   Attachments appear as follows:
-
- 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
-   content-type, and can be changed with the edit-type command (default: ^T).
-   The next field is the encoding for the attachment, which allows a binary
-   message to be encoded for transmission on 7bit links. It can be changed
-   with the edit-encoding command (default: ^E). The next field is the size
-   of the attachment, rounded to kilobytes or megabytes. The next field is
-   the filename, which can be changed with the rename-file command (default:
-   R). The final field is the description of the attachment, and can be
-   changed with the edit-description command (default: d).
-
-2.  MIME Type configuration with mime.types
-
-   When you add an attachment to your mail message, Mutt-ng searches your
-   personal mime.types file within $HOME and then the system mime.types file
-   at /usr/local/share/mutt/mime.types or /etc/mime.types
-
-   The mime.types file consist of lines containing a MIME type and a space
-   separated list of extensions. For example:
-
- application/postscript          ps eps
- 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.
-
-   If Mutt-ng can not determine the mime type by the extension of the file
-   you attach, it will look at the file. If the file is free of binary
-   information, Mutt-ng will assume that the file is plain text, and mark it
-   as text/plain. If the file contains binary information, then Mutt-ng will
-   mark it as application/octet-stream. You can change the MIME type that
-   Mutt-ng assigns to an attachment by using the edit-type command from the
-   compose menu (default: ^T). The MIME type is actually a major mime type
-   followed by the sub-type, separated by a '/'. 6 major types: application,
-   text, image, video, audio, and model have been approved after various
-   internet discussions. Mutt-ng recognises all of these if the appropriate
-   entry is found in the mime.types file. It also recognises other major mime
-   types, such as the chemical type that is widely used in the molecular
-   modelling community to pass molecular data in various forms to various
-   molecular viewers. Non-recognised mime types should only be used if the
-   recipient of the message is likely to be expecting such attachments.
-
-3.  MIME Viewer configuration with mailcap
-
-   Mutt-ng supports RfC 1524 MIME Configuration, in particular the Unix
-   specific format specified in Appendix A of the RfC. This file format is
-   commonly referred to as the mailcap format. Many MIME compliant programs
-   utilize the mailcap format, allowing you to specify handling for all MIME
-   types in one place for all programs. Programs known to use this format
-   include Netscape, XMosaic, lynx and metamail.
-
-   In order to handle various MIME types that Mutt-ng can not handle
-   internally, Mutt-ng parses a series of external configuration files to
-   find an external handler. The default search string for these files is a
-   colon delimited list set to
-
- ${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,
-   usually as /usr/local/etc/mailcap, which contains some baseline entries.
-
-  3.1. The Basics of the mailcap file
-
-   A mailcap file consists of a series of lines which are comments, blank, or
-   definitions.
-
-   A comment line consists of a # character followed by anything you want.
-
-   A blank line is blank.
-
-   A definition line consists of a content type, a view command, and any
-   number of optional fields. Each field of a definition line is dividedby a
-   semicolon ';' character.
-
-   The content type is specified in the MIME standard type/subtype method.
-   For example, text/plain, text/html, image/gif, etc. In addition, the
-   mailcap format includes two formats for wildcards, one using the special
-   '*' subtype, the other is the implicit wild, where you only include the
-   major type. For example, image/* ,or video, will match all image types and
-   video types, respectively.
-
-   The view command is a Unix command for viewing the type specified. There
-   are two different types of commands supported. The default is to send the
-   body of the MIME message to the command on stdin. You can change this
-   behavior by using %s as a parameter to your view command. This will cause
-   Mutt-ng to save the body of the MIME message to a temporary file, and then
-   call the view command with the %s replaced by the name of the temporary
-   file. In both cases, Mutt-ng will turn over the terminal to the view
-   program until the program quits, at which time Mutt will remove the
-   temporary file if it exists.
-
-   So, in the simplest form, you can send a text/plain message to the
-   external pager more on stdin:
-
- 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
-   find the line which calls lynx, and run it. This causes lynx to
-   continuously spawn itself to view the object.
-
-   On the other hand, maybe you don't want to use lynx interactively, youjust
-   want to have it convert the text/html to text/plain, then you can use:
-
- 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
-
-   The interpretation of shell meta-characters embedded in MIME parameters
-   can lead to security problems in general. Mutt-ng tries to quote
-   parameters in expansion of %s syntaxes properly, and avoids risky
-   characters by substituting them, see the $mailcap_sanitize variable.
-
-   Although mutt's procedures to invoke programs with mailcap seem to be
-   safe, there are other applications parsing mailcap, maybe taking less care
-   of it. Therefore you should pay attention to the following rules:
-
-   Keep the %-expandos away from shell quoting. Don't quote them with single
-   or double quotes. Mutt-ng does this for you, the right way, as should any
-   other program which interprets mailcap. Don't put them into backtick
-   expansions. Be highly careful with eval statements, and avoid them if
-   possible at all. Trying to fix broken behaviour with quotes introduces new
-   leaks - there is no alternative to correct quoting in the first place.
-
-   If you have to use the %-expandos' values in context where you need
-   quoting or backtick expansions, put that value into a shell variable and
-   reference the shell variable where necessary, as in the following example
-   (using $charset inside the backtick expansion is safe, since it is not
-   itself subject to any further expansion):
-
- 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
-
-   In addition to the required content-type and view command fields, you can
-   add semi-colon ';' separated fields to set flags and other options.
-   Mutt-ng recognizes the following optional fields:
-
-   copiousoutput
-
-           This flag tells Mutt-ng that the command passes possibly large
-           amounts of text on stdout. This causes Mutt-ng to invoke a pager
-           (either the internal pager or the external pager defined by the
-           pager variable) on the output of the view command. Without this
-           flag, Mutt-ng assumes that the command is interactive. One could
-           use this to replace the pipe to more in the lynx -dump example in
-           the Basic section:
-
- 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.
-
-   needsterminal
-
-           Mutt-ng uses this flag when viewing attachments with auto_view, in
-           order to decide whether it should honor the setting of the
-           $wait_key variable or not. When an attachment is viewed using an
-           interactive program, and the corresponding mailcap entry has a
-           needsterminal flag, Mutt-ng will use $wait_key and the exit
-           statusof the program to decide if it will ask you to press a key
-           after the external program has exited. In all other situations it
-           will not prompt you for a key.
-
-   compose=<command>
-
-           This flag specifies the command to use to create a new attachment
-           of a specific MIME type. Mutt-ng supports this from the compose
-           menu.
-
-   composetyped=<command>
-
-           This flag specifies the command to use to create a new attachment
-           of a specific MIME type. This command differs from the compose
-           command in that mutt will expect standard MIME headers on the
-           data. This can be used to specify parameters, filename,
-           description, etc. for a new attachment. Mutt-ng supports this from
-           the compose menu.
-
-   print=<command>
-
-           This flag specifies the command to use to print a specific MIME
-           type. Mutt-ng supports this from the attachment and compose menus.
-
-   edit=<command>
-
-           This flag specifies the command to use to edit a specific MIME
-           type. Mutt-ng supports this from the compose menu, and also uses
-           it to compose new attachments. Mutt-ng will default to the defined
-           editor for text attachments.
-
-   nametemplate=<template>
-
-           This field specifies the format for the file denoted by %s in the
-           command fields. Certain programs will require a certain file
-           extension, for instance, to correctly view a file. For instance,
-           lynx will only interpret a file as text/html if the file ends in
-           .html. So, you would specify lynx as a text/html viewer with a
-           line in the mailcap file like:
-
- text/html; lynx %s; nametemplate=%s.html
-
-   test=<command>
-
-           This field specifies a command to run to test whether this mailcap
-           entry should be used. The command is defined with the command
-           expansion rules defined in the next section. If the command
-           returns 0, then the test passed, and Mutt-ng uses this entry. If
-           the command returns non-zero, then the test failed, and Mutt-ng
-           continues searching for the right entry. Note:the content-type
-           must match before Mutt-ng performs the test. For example:
-
- 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
-           display the text/html object. If RunningX doesn't return 0, then
-           Mutt-ng will go on to the next entry and use lynx to display the
-           text/html object.
-
-    3.3.2. Search Order
-
-   When searching for an entry in the mailcap file, Mutt-ng will search for
-   the most useful entry for its purpose. For instance, if you are attempting
-   to print an image/gif, and you have the following entries in your mailcap
-   file, Mutt-ng will search for an entry with the print command:
-
- image/*;        xv %s
- 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.
-
-   In addition, you can use this with auto_view to denote two commands for
-   viewing an attachment, one to be viewed automatically, the other to be
-   viewed interactively from the attachment menu. In addition, you can then
-   use the test feature to determine which viewer to use interactively
-   depending on your environment.
-
- text/html;      netscape -remote 'openURL(%s)' ; test=RunningX
- 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
-   returns non-zero, Mutt-ng will use the second entry for interactive
-   viewing.
-
-    3.3.3. Command Expansion
-
-   The various commands defined in the mailcap files are passed to the
-   /bin/sh shell using the system() function. Before the command is passed to
-   /bin/sh -c, it is parsed to expand various special parameters with
-   information from Mutt-ng. The keywords Mutt-ng expands are:
-
-   %s
-
-           As seen in the basic mailcap section, this variable is expanded to
-           a filename specified by the calling program. This file contains
-           the body of the message to view/print/edit or where the composing
-           program should place the results of composition. In addition, the
-           use of this keyword causes Mutt-ng to not pass the body of the
-           message to the view/print/edit program on stdin.
-
-   %t
-
-           Mutt-ng will expand %t to the text representation of the content
-           type of the message in the same form as the first parameter of the
-           mailcap definition line, ie text/html or image/gif.
-
-   %{<parameter>}
-
-           Mutt-ng will expand this to the value of the specified parameter
-           from the Content-Type: line of the mail message. For instance, if
-           Your mail message contains:
-
- 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.
-
-   \%
-
-           This will be replaced by a %
-
-   Mutt-ng does not currently support the %F and %n keywords specified in RfC
-   1524. The main purpose of these parameters is for multipart messages,
-   which is handled internally by Mutt-ng.
-
-  3.4. Example mailcap files
-
-   This mailcap file is fairly simple and standard:
-
- >
- # I'm always running X :)
- video/*;        xanim %s > /dev/null
- image/*;        xv %s > /dev/null
-
- # 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 that to /dev/null so I don't see it
- video/*;        xanim %s > /dev/null
-
- # Send html to a running netscape by remote
- text/html;      netscape -remote 'openURL(%s)'; test=RunningNetscape
- # If I'm not running netscape but I am running X, start netscape on the
- # object
- text/html;      netscape %s; test=RunningX
-
- # Else use lynx to view it as text
- text/html;      lynx %s
-
- # This version would convert the text/html to text/plain
- text/html;      lynx -dump %s; copiousoutput
-
- # I use enscript to print text in two columns to a page
- text/*;         more %s; print=enscript -2Gr %s
-
- # Netscape adds a flag to tell itself to view jpegs internally
- image/jpeg;xv %s; x-mozilla-flags=internal
-
- # Use xv to view images if I'm running X
- # In addition, this uses the \ to extend the line and set my editor
- # for images
- image/*;xv %s; test=RunningX; edit=xpaint %s
-
- # Convert images to text using the netpbm tools
- image/*;  (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | \
- pgmtopbm | pbmtoascii -1x2 ) 2>&1 ; copiousoutput
-
- # Send excel spreadsheets to my NT box
- application/ms-excel; open.pl %s
-
-4. MIME Autoview
-
-   Usage: auto_viewmime-type [mime-type ...]
-
-   Usage: unauto_viewmime-type [mime-type ...]
-
-   In addition to explicitly telling Mutt-ng to view an attachment with
-   theMIME viewer defined in the mailcap file, Mutt-ng has support for
-   automatically viewing MIME attachments while in the pager.
-
-   To work, you must define a viewer in the mailcap file which uses the
-   copiousoutput option to denote that it is non-interactive. Usually, you
-   also use the entry to convert the attachment to a text representation
-   which you can view in the pager.
-
-   You then use the auto_view muttrc command to list the content-types that
-   you wish to view automatically.
-
-   For instance, if you set auto_view to:
-
- 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.
-
- text/html;      lynx -dump %s; copiousoutput; nametemplate=%s.html
- image/*;        anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | pgmtopbm | pbmtoascii ; copiousoutput
- application/x-gunzip;   gzcat; copiousoutput
- 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.
-
-5. MIME Multipart/Alternative
-
-   Usage: alternative_ordermime-type [mime-type ...]
-
-   Usage: unalternative_ordermime-type [mime-type ...]
-
-   Mutt-ng has some heuristics for determining which attachment of a
-   multipart/alternative type to display. First, mutt will check the
-   alternative_order list to determine if one of the available typesis
-   preferred. The alternative_order list consists of a number of MIME types
-   in order, including support for implicit and explicit wildcards, for
-   example:
-
- 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.
-
-   To remove a MIME type from the alternative_order list, use the
-   unalternative_order command.
-
-6. Attachment Searching and Counting
-
-   If you ever lose track of attachments in your mailboxes, Mutt's
-   attachment-counting and -searching support might be for you. You can make
-   your message index display the number of qualifying attachments in each
-   message, or search for messages by attachment count. You also can
-   configure what kinds of attachments qualify for this feature with the
-   attachments and unattachments commands.
-
-   The syntax is:
-
-   Usage: attachments( {+|-}disposition mime-type | ? )
-
-   Usage: unattachments{+|-}disposition mime-type
-
-   Disposition is the attachment's Content-disposition type -- either
-   "inline" or "attachment". You can abbreviate this to I or A.
-
-   Disposition is prefixed by either a + symbolor a - symbol. If it's a +,
-   you're saying that you want to allow this disposition and MIME type to
-   qualify. If it's a -, you're saying that this disposition and MIME type is
-   an exception to previous + rules. There are examples below of how this is
-   useful.
-
-   Mime-type is, unsurprisingly, the MIME type of the attachment you want to
-   affect. A MIME type is always of the format "major/minor", where "major"
-   describes the broad category of document you're looking at, and "minor"
-   describes the specific type within that category. The major part of
-   mim-type must be literal text (or the special token "*"), but the minor
-   part may be a regular expression. (Therefore, "*/.*" matches any MIME
-   type.)
-
-   The MIME types you give to the attachments directive are a kind of
-   pattern. When you use the attachments directive, the patterns you specify
-   are added to a list. When you use unattachments, the pattern is removed
-   from the list. The patterns are not expanded and matched to specific MIME
-   types at this time -- they're just text in a list. They're only matched
-   when actually evaluating a message.
-
-   Some examples might help to illustrate. The examples that are not
-   commented out define the default configuration of the lists.
-
- ## Removing a pattern from a list removes that pattern literally. It
- ## does not remove any type matching the pattern.
- ##
- ## attachments +A */.*
- ## attachments +A image/jpeg
- ## unattachments +A */.*
- ##
- ## This leaves "attached" image/jpeg files on the allowed attachments
- ## list. It does not remove all items, as you might expect, because the
- ## second */.* is not a matching expression at this time.
- ##
- ## Remember: "unattachments" only undoes what "attachments" has done!
- ## It does not trigger any matching on actual messages.
-
-
- ## Qualify any MIME part with an "attachment" disposition, EXCEPT for
- ## text/x-vcard and application/pgp parts. (PGP parts are already known
- ## to mutt, and can be searched for with ~g, ~G, and ~k.)
- ##
- ## I've added x-pkcs7 to this, since it functions (for S/MIME)
- ## analogously to PGP signature attachments. S/MIME isn't supported
- ## in a stock mutt build, but we can still treat it specially here.
- ##
- attachments +A */.*
- attachments -A text/x-vcard application/pgp.*
- attachments -A application/x-pkcs7-.*
-
- ## Discount all MIME parts with an "inline" disposition, unless they're
- ## text/plain. (Why inline a text/plain part unless it's external to the
- ## message flow?)
- ##
- attachments +I text/plain
-
- ## These two lines make Mutt qualify MIME containers. (So, for example,
- ## a message/rfc822 forward will count as an attachment.) The first
- ## line is unnecessary if you already have "attach-allow */.*", of
- ## course. These are off by default! The MIME elements contained
- ## within a message/* or multipart/* are still examined, even if the
- ## containers themseves don't qualify.
- ##
- #attachments +A message/.* multipart/.*
- #attachments +I message/.* multipart/.*
-
- ## You probably don't really care to know about deleted attachments.
- attachments -A message/external-body
- attachments -I message/external-body
-
-   "attachments ?" will list your current settings in Muttrc format, so that
-   it can be pasted elsewhere.
-
-7. MIME Lookup
-
-   Usage: mime_lookupmime-type [mime-type ...]
-
-   Usage: unmime_lookupmime-type [mime-type ...]
-
-   Mutt-ng's mime_lookup list specifies a list of mime-types that should not
-   be treated according to their mailcap entry. This option is designed
-   todeal with binary types such as application/octet-stream. When an
-   attachment's mime-type is listed in mime_lookup, then the extension of the
-   filename will be compared to the list of extensions in the mime.types
-   file. The mime-type associated with this extension will then be used to
-   process the attachment according to the rules in the mailcap file and
-   according to any other configuration options (such as auto_view)
-   specified. Common usage would be:
-
- 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.
-
-Chapter 6. Security Considerations
-
-   Table of Contents
-
-   1. Passwords
-
-   2. Temporary Files
-
-   3. Information Leaks
-
-                3.1. Message-ID: headers
-
-                3.2. mailto:-style links
-
-   4. External applications
-
-                4.1. mailcap
-
-                4.2. Other
-
-   First of all, mutt-ng contains no security holes included by intention but
-   may contain unknown security holes. As a consequence, please run mutt-ng
-   only with as few permissions as possible.
-
-   Please do not run mutt-ng as the super user.
-
-   When configuring mutt-ng, there're some points to note about secure
-   setups.
-
-   In practice, mutt-ng can be easily made as vulnerable as even the most
-   insecure mail user agents (in their default configuration) just by
-   changing mutt-ng's configuration files: it then can execute arbitrary
-   programs and scripts attached to messages, send out private data on its
-   own, etc. Although this is not believed to the common type of setup,
-   please read this chapter carefully.
-
-1. Passwords
-
-   Although mutt-ng can be told the various passwords for accounts, please
-   never store passwords in configuration files. Besides the fact that the
-   system's operator can always read them, you could forget to replace the
-   actual password with asterisks when reporting a bug or asking for help
-   via, for example, a mailing list so that your mail including your password
-   could be archived by internet search engines, etc. Please never store
-   passwords on disk.
-
-2. Temporary Files
-
-   Mutt-ng uses many temporary files for viewing messages, verifying digital
-   signatures, etc. The $umask variable can be used to change the default
-   permissions of these files. Please only change it if you really know what
-   you are doing. Also, a different location for these files may be desired
-   which can be changed via the $tmpdir variable.
-
-3. Information Leaks
-
-  3.1. Message-ID: headers
-
-   In the default configuration, mutt-ng will leak some information to the
-   outside world when sending messages: the generation of Message-ID: headers
-   includes a step counter which is increased (and rotated) with every
-   message sent. If you'd like to hide this information probably telling
-   others how many mail you sent in which time, you at least need to remove
-   the %P expando from the default setting of the $msgid_format variable.
-   Please make sure that you really know how local parts of these Message-ID:
-   headers are composed.
-
-  3.2. mailto:-style links
-
-   As mutt-ng be can be set up to be the mail client to handle mailto: style
-   links in websites, there're security considerations, too. To keep the old
-   behavior by default, mutt-ng will be strict in interpreting them which
-   means that arbitrary header fields can be embedded in these links which
-   could override existing header fields or attach arbitrary files. This may
-   be problematic if the $edit_headers variable is unset, i.e. the user
-   doesn't want to see header fields while editing the message.
-
-   For example, following a link like
-
- 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.
-
-   When unsetting the $strict_mailto variable, mutt-ng will
-
-     o be less strict when interpreting these links by prepending a X-Mailto-
-       string to all header fields embedded in such a link and
-
-     o turn on the $edit_headers variable by force to let the user see all
-       the headers (because they still may leak information.)
-
-4. External applications
-
-   Mutt-ng in many places has to rely on external applications or for
-   convenience supports mechanisms involving external applications.
-
-  4.1. mailcap
-
-   One of these is the mailcap mechanism as defined by RfC 1524. Mutt-ng can
-   be set up to automatically execute any given utility as listed in one of
-   the mailcap files (see the $mailcap_path variable for details.)
-
-   These utilities may have a variety of security vulnerabilities, including
-   overwriting of arbitrary files, information leaks or other exploitable
-   bugs. These vulnerabilities may go unnoticed by the user, especially when
-   they are called automatically (and without interactive prompting) from the
-   mailcap file(s). When using mutt-ng's autoview mechanism in combination
-   with mailcap files, please be sure to...
-
-     o manually select trustworth applications with a reasonable calling
-       sequence
-
-     o periodically check the contents of mailcap files, especially after
-       software installations or upgrades
-
-     o keep the software packages referenced in the mailcap file up to date
-
-     o leave the $mailcap_sanitize variable in its default state to restrict
-       mailcap expandos to a safe set of characters
-
-  4.2. Other
-
-   Besides the mailcap mechanism, mutt-ng uses a number of other external
-   utilities for operation.
-
-   The same security considerations apply for these as for tools involved via
-   mailcap (for example, mutt-ng is vulnerable to Denial of Service Attacks
-   with compressed folders support if the uncompressed mailbox is too large
-   for the disk it is saved to.)
-
-   As already noted, most of these problems are not built in but caused by
-   wrong configuration, so please check your configuration.
-
-Chapter 7. Reference
-
-   Table of Contents
-
-   1. Command line options
-
-   2. Patterns
-
-   3. Configuration Commands
-
-   4. Configuration variables
-
-   5. Functions
-
-                5.1. generic
-
-                5.2. index
-
-                5.3. pager
-
-                5.4. alias
-
-                5.5. query
-
-                5.6. attach
-
-                5.7. compose
-
-                5.8. postpone
-
-                5.9. browser
-
-                5.10. pgp
-
-                5.11. editor
-
-                5.12. sidebar
-
-1. Command line options
-
-   Running mutt with no arguments will make Mutt-ng attempt to read your
-   spool mailbox. However, it is possible to read other mailboxes and to send
-   messages from the command line as well.
-
-   Table 7.1. Reference: Command Line Options
-
-   Option Description
-   -A     expand an alias
-   -a     attach a file to a message
-   -b     specify a blind carbon-copy (BCC) address
-   -c     specify a carbon-copy (Cc) address
-   -e     specify a config command to be run after initialization files are
-          read
-   -f     specify a mailbox to load
-   -F     specify an alternate file to read initialization commands
-   -h     print help on command line options
-   -H     specify a draft file from which to read a header and body
-   -i     specify a file to include in a message composition
-   -m     specify a default mailbox type
-   -n     do not read the system Muttngrc
-   -p     recall a postponed message
-   -Q     query a configuration variable
-   -R     open mailbox in read-only mode
-   -s     specify a subject (enclose in quotes if it contains spaces)
-   -t     dump the value of all variables to stdout
-   -T     dump the value of all changed variables to stdout
-   -v     show version number and compile-time definitions
-   -x     simulate the mailx(1) compose mode
-   -y     show a menu containing the files specified by the mailboxes command
-   -z     exit immediately if there are no messages in the mailbox
-   -Z     open the first folder with new message,exit immediately if none
-
-   To read messages in a mailbox
-
-   mutt ] -nz ] ] -F muttrc ] ] -m type ] ] -f mailbox ]
-
-   To compose a new message
-
-   mutt ] -n ] ] -F muttrc ] ] -a file ] ] -c address ] ] -i filename ] ] -s
-   subject ] address ] address ... ]
-
-   Mutt-ng also supports a ``batch'' mode to send prepared messages. Simply
-   redirect input from the file you wish to send. For example,
-
-   mutt -s "data set for run #2" professor@bigschool.edu < ~/run2.dat
-
-   This command will send a message to ``professor@bigschool.edu'' with a
-   subject of ``data set for run #2''. In the body of the message will be the
-   contents of the file ``~/run2.dat''.
-
-2. Patterns
-
-   Table 7.2. Reference: Patterns
-
-   Pattern Modifier Argument    Description
-   ~A/=A                        all messages
-   ~b/=b            EXPR        messages which contain EXPR in the message
-                                body
-   ~B/=B            EXPR        messages which contain EXPR in the whole
-                                message
-   ~c/=c            EXPR        messages carbon-copied to EXPR
-   ~C/=C            EXPR        message is either to: or cc: EXPR
-   ~D/=D                        deleted messages
-   ~d/=d            [MIN]-[MAX] messages with ``date-sent'' in a Date range
-   ~E/=E                        expired messages
-   ~e/=e            EXPR        message which contains EXPR in the ``Sender''
-                                field
-   ~F/=F                        flagged messages
-   ~f/=f            EXPR        messages originating from EXPR
-   ~g/=g                        cryptographically signed messages
-   ~G/=G                        cryptographically encrypted messages
-   ~H/=H            EXPR        messages with a spam attribute matching EXPR
-   ~h/=h            EXPR        messages which contain EXPR in the message
-                                header
-   ~k/=k                        message contains PGP key material
-   ~i/=i            EXPR        message which match ID in the ``Message-ID''
-                                field
-   ~L/=L            EXPR        message is either originated or received by
-                                EXPR
-   ~l/=l                        message is addressed to a known mailing list
-   ~m/=m            [MIN]-[MAX] message in the range MIN to MAX *)
-   ~M/=M                        multipart messages
-   ~n/=n            [MIN]-[MAX] messages with a score in the range MIN to MAX
-                                *)
-   ~N/=N                        new messages
-   ~O/=O                        old messages
-   ~p/=p                        message is addressed to you (consults
-                                alternates)
-   ~P/=P                        message is from you (consults alternates)
-   ~Q/=Q                        messages which have been replied to
-   ~R/=R                        read messages
-   ~r/=r            [MIN]-[MAX] messages with ``date-received'' in a Date
-                                range
-   ~S/=S                        superseded messages
-   ~s/=s            EXPR        messages having EXPR in the ``Subject''
-                                field.
-   ~T/=T                        tagged messages
-   ~t/=t            EXPR        messages addressed to EXPR
-   ~U/=U                        unread messages
-   ~u/=u                        message is addressed to a subscribed mailing
-                                list
-   ~v/=v                        message is part of a collapsed thread.
-   ~V/=V                        cryptographically verified messages
-                                messages which contain EXPR in the
-   ~w/=w            EXPR        `Newsgroups' field (if compiled with NNTP
-                                support)
-   ~x/=x            EXPR        messages which contain EXPR in the
-                                `References' field
-   ~X/=X            [MIN]-[MAX] messages with MIN to MAX attachments *)
-   ~y/=y            EXPR        messages which contain EXPR in the `X-Label'
-                                field
-   ~z/=z            [MIN]-[MAX] messages with a size in the range MIN to MAX
-                                *)
-   ~=/==                        duplicated messages (see $duplicate_threads)
-   ~$/=$                        unreferenced messages (requires threaded
-                                view)
-                                ``From'' contains realname and
-   ~*/=*                        (syntactically) valid address (excluded are
-                                addresses matching against alternates or any
-                                alias)
-
-   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.
-
-3. Configuration Commands
-
-   The following are the commands understood by mutt.
-
-     o account-hook pattern command
-
-     o aliaskeyaddress [, address, ... ]
-
-     o unalias [ * | key ... ]
-
-     o alternatesregexp [ regexp ... ]
-
-     o unalternates [ * | regexp ... ]
-
-     o alternative_ordermimetype [ mimetype ... ]
-
-     o unalternative_ordermimetype [ mimetype ... ]
-
-     o append-hook regexp command
-
-     o auto_viewmimetype [ mimetype ... ]
-
-     o unauto_viewmimetype [ mimetype ... ]
-
-     o bind map key function
-
-     o charset-hook alias charset
-
-     o close-hook regexp command
-
-     o colorobjectforegroundbackground [ regexp ]
-
-     o uncolorindexpattern [ pattern ... ]
-
-     o execfunction [ function ... ]
-
-     o fcc-hook pattern mailbox
-
-     o fcc-save-hook pattern mailbox
-
-     o folder-hook pattern command
-
-     o hdr_orderheader [ header ... ]
-
-     o unhdr_orderheader [ header ... ]
-
-     o charset-hook charset local-charset
-
-     o ignorepattern [ pattern ... ]
-
-     o unignorepattern [ pattern ... ]
-
-     o listsregexp [ regexp ... ]
-
-     o unlistsregexp [ regexp ... ]
-
-     o macromenukeysequence [ description ]
-
-     o mailboxesfilename [ filename ... ]
-
-     o mbox-hook pattern mailbox
-
-     o message-hook pattern command
-
-     o mime_lookupmimetype [ mimetype ... ]
-
-     o unmime_lookupmimetype [ mimetype ... ]
-
-     o monoobject attribute [ regexp ]
-
-     o unmonoindexpattern [ pattern ... ]
-
-     o my_hdr string
-
-     o unmy_hdrfield [ field ... ]
-
-     o open-hook regexp command
-
-     o crypt-hook pattern key-id
-
-     o push string
-
-     o resetvariable [ variable ... ]
-
-     o save-hook regexp filename
-
-     o score pattern value
-
-     o unscorepattern [ pattern ... ]
-
-     o send-hook regexp command
-
-     o reply-hook regexp command
-
-     o set [no|inv]variable[ =value ] [ variable ... ]
-
-     o unsetvariable [ variable ... ]
-
-     o source filename
-
-     o spam pattern format
-
-     o nospam pattern
-
-     o subscriberegexp [ regexp ... ]
-
-     o unsubscriberegexp [ regexp ... ]
-
-     o togglevariable [ variable ... ]
-
-     o unhook hook-type
-
-4. Configuration variables
-
-   The following list contains all variables which, in the process of
-   providing more consistency, have been renamed and are partially even
-   removed already. The left column contains the old synonym variables, the
-   right column the full/new name:
-
-   Table 7.3. Reference: Obsolete Variables
-
-   Old Name               New Name
-   edit_hdrs              $edit_headers
-   forw_decode            $forward_decode
-   forw_format            $forward_format
-   forw_quote             $forward_quote
-   hdr_format             $index_format
-   indent_str             $indent_string
-   mime_fwd               $mime_forward
-   msg_format             $message_format
-   pgp_autosign           $crypt_autosign
-   pgp_autoencrypt        $crypt_autoencrypt
-   pgp_replyencrypt       $crypt_replyencrypt
-   pgp_replysign          $crypt_replysign
-   pgp_replysignencrypted $crypt_replysignencrypted
-   pgp_verify_sig         $crypt_verify_sig
-   pgp_create_traditional $pgp_autoinline
-   pgp_auto_traditional   $pgp_replyinline
-   forw_decrypt           $forward_decrypt
-   smime_sign_as          $smime_default_key
-   post_indent_str        $post_indent_string
-   print_cmd              $print_command
-   shorten_hierarchy      $sidebar_shorten_hierarchy
-   ask_followup_to        $nntp_ask_followup_to
-   ask_x_comment_to       $nntp_ask_x_comment_to
-   catchup_newsgroup      $nntp_catchup
-   followup_to_poster     $nntp_followup_to_poster
-   group_index_format     $nntp_group_index_format
-   inews                  $nntp_inews
-   mime_subject           $nntp_mime_subject
-   news_cache_dir         $nntp_cache_dir
-   news_server            $nntp_host
-   newsrc                 $nntp_newsrc
-   nntp_poll              $nntp_mail_check
-   pop_checkinterval      $pop_mail_check
-   post_moderated         $nntp_post_moderated
-   save_unsubscribed      $nntp_save_unsubscribed
-   show_new_news          $nntp_show_new_news
-   show_only_unread       $nntp_show_only_unread
-   x_comment_to           $nntp_x_comment_to
-   smtp_auth_username     $smtp_user
-   smtp_auth_password     $smtp_pass
-   user_agent             $agent_string
-
-   The contrib subdirectory contains a script named update-config.pl which
-   eases migration.
-
-   A complete list of current variables follows.
-
-1. $abort_noattach
-
-   Type: quadoption
-
-   Default: no
-
-   This variable specifies whether to abort sending if no attachment was made
-   but the content references them, i.e. the content matches the regular
-   expression given in $attach_remind_regexp. If a match was found and this
-   variable is set to yes, message sending will be aborted but the mail will
-   be send nevertheless if set to no.
-
-   This variable and $attach_remind_regexp are intended to remind the user to
-   attach files if the message's text references them.
-
-   See also the $attach_remind_regexp variable.
-
-2. $abort_nosubject
-
-   Type: quadoption
-
-   Default: ask-yes
-
-   If set to yes, when composing messages and no subject is given at the
-   subject prompt, composition will be aborted. If set to no, composing
-   messages with no subject given at the subject prompt will never be
-   aborted.
-
-3. $abort_unmodified
-
-   Type: quadoption
-
-   Default: yes
-
-   If set to yes, composition will automatically abort after editing the
-   message body if no changes are made to the file (this check only happens
-   after the first edit of the file). When set to no, composition will never
-   be aborted.
-
-4. $agent_string
-
-   Type: boolean
-
-   Default: yes
-
-   When set, Mutt-ng will add a ``User-Agent:'' header to outgoing messages,
-   indicating which version of Mutt-ng was used for composing them.
-
-5. $alias_file
-
-   Type: path
-
-   Default: "~/.muttngrc"
-
-   The default file in which to save aliases created by the ``create-alias''
-   function.
-
-   Note: Mutt-ng will not automatically source this file; you must explicitly
-   use the ``source'' command for it to be executed.
-
-6. $alias_format
-
-   Type: string
-
-   Default: "%4n %2f %t %-10a %r"
-
-   Specifies the format of the data displayed for the ``alias'' menu. The
-   following printf(3)-style sequences are available:
-
-   %a
-
-           alias name
-
-   %f
-
-           flags - currently, a "d" for an alias marked for deletion
-
-   %n
-
-           index number
-
-   %r
-
-           address which alias expands to
-
-   %t
-
-           character which indicates if the alias is tagged for inclusion
-
-7. $allow_8bit
-
-   Type: boolean
-
-   Default: yes
-
-   Controls whether 8-bit data is converted to 7-bit using either
-   quoted-printable or base64 encoding when sending mail.
-
-8. $allow_ansi
-
-   Type: boolean
-
-   Default: no
-
-   Controls whether ANSI color codes in messages (and color tags in rich text
-   messages) are to be interpreted. Messages containing these codes are rare,
-   but if this option is set, their text will be colored accordingly. Note
-   that this may override your color choices, and even present a security
-   problem, since a message could include a line like ``[-- PGP output
-   follows ..." and give it the same color as your attachment color.
-
-9. $arrow_cursor
-
-   Type: boolean
-
-   Default: no
-
-   When set, an arrow (``->'') will be used to indicate the current entry in
-   menus instead of highlighting the whole line. On slow network or modem
-   links this will make response faster because there is less that has to be
-   redrawn on the screen when moving to the next or previous entries in the
-   menu.
-
-10. $ascii_chars
-
-   Type: boolean
-
-   Default: no
-
-   If set, Mutt-ng will use plain ASCII characters when displaying thread and
-   attachment trees, instead of the default ACS characters.
-
-11. $askbcc
-
-   Type: boolean
-
-   Default: no
-
-   If set, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients
-   before editing an outgoing message.
-
-12. $askcc
-
-   Type: boolean
-
-   Default: no
-
-   If set, Mutt-ng will prompt you for carbon-copy (Cc) recipients before
-   editing the body of an outgoing message.
-
-13. $assumed_charset
-
-   Type: string
-
-   Default: "us-ascii"
-
-   This variable is a colon-separated list of character encoding schemes for
-   messages without character encoding indication. Header field values and
-   message body content without character encoding indication would be
-   assumed that they are written in one of this list. By default, all the
-   header fields and message body without any charset indication are assumed
-   to be in us-ascii.
-
-   For example, Japanese users might prefer this:
-
-   set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-
-   However, only the first content is valid for the message body. This
-   variable is valid only if $strict_mime is unset.
-
-14. $attach_format
-
-   Type: string
-
-   Default: "%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] "
-
-   This variable describes the format of the ``attachment'' menu. The
-   following printf(3)-style sequences are understood:
-
-   %C
-
-           charset
-
-   %c
-
-           requires charset conversion (n or c)
-
-   %D
-
-           deleted flag
-
-   %d
-
-           description
-
-   %e
-
-           MIME Content-Transfer-Encoding: header field
-
-   %f
-
-           filename
-
-   %I
-
-           MIME Content-Disposition: header field (I=inline, A=attachment)
-
-   %m
-
-           major MIME type
-
-   %M
-
-           MIME subtype
-
-   %n
-
-           attachment number
-
-   %Q
-
-           "Q", if MIME part qualifies for attachment counting
-
-   %s
-
-           size
-
-   %t
-
-           tagged flag
-
-   %T
-
-           graphic tree characters
-
-   %u
-
-           unlink (=to delete) flag
-
-   %X
-
-           number of qualifying MIME parts in this part and its children
-
-   %>X
-
-           right justify the rest of the string and pad with character "X"
-
-   %|X
-
-           pad to the end of the line with character "X"
-
-15. $attach_remind_regexp
-
-   Type: regular expression
+set record=+sent_on_$HOSTNAME
 
-   Default: "attach"
-
-   If this variable is non-empty, muttng will scan a message's contents
-   before sending for this regular expression. If it is found, it will ask
-   for what to do depending on the setting of $abort_noattach.
-
-   This variable and $abort_noattach are intended to remind the user to
-   attach files if the message's text references them.
-
-16. $attach_sep
-
-   Type: string
-
-   Default: "\n"
-
-   The separator to add between attachments when operating (saving, printing,
-   piping, etc) on a list of tagged attachments.
-
-17. $attach_split
-
-   Type: boolean
-
-   Default: yes
-
-   If this variable is unset, when operating (saving, printing, piping, etc)
-   on a list of tagged attachments, Mutt-ng will concatenate the attachments
-   and will operate on them as a single attachment. The ``$attach_sep''
-   separator is added after each attachment. When set, Mutt-ng will operate
-   on the attachments one by one.
-
-18. $attribution
-
-   Type: string
-
-   Default: "On %d, %n wrote:"
-
-   This is the string that will precede a message which has been included in
-   a reply. For a full listing of defined printf(3)-like sequences see the
-   section on ``$index_format''.
-
-19. $auto_tag
-
-   Type: boolean
-
-   Default: no
-
-   When set, functions in the index menu which affect a message will be
-   applied to all tagged messages (if there are any). When unset, you must
-   first use the ``tag-prefix'' function (default: ";") to make the next
-   function apply to all tagged messages.
-
-20. $autoedit
-
-   Type: boolean
-
-   Default: no
-
-   When set along with ``$edit_headers'', Mutt-ng will skip the initial
-   send-menu and allow you to immediately begin editing the body of your
-   message. The send-menu may still be accessed once you have finished
-   editing the body of your message.
-
-   Also see ``$fast_reply''.
-
-21. $beep
-
-   Type: boolean
-
-   Default: yes
-
-   When this variable is set, Mutt-ng will beep when an error occurs.
-
-22. $beep_new
-
-   Type: boolean
-
-   Default: no
-
-   When this variable is set, Mutt-ng will beep whenever it prints a message
-   notifying you of new mail. This is independent of the setting of the
-   ``$beep'' variable.
-
-23. $bounce
-
-   Type: quadoption
-
-   Default: ask-yes
-
-   Controls whether you will be asked to confirm bouncing messages. If set to
-   yes you don't get asked if you want to bounce a message. Setting this
-   variable to no is not generally useful, and thus not recommended, because
-   you are unable to bounce messages.
-
-24. $bounce_delivered
-
-   Type: boolean
-
-   Default: yes
-
-   When this variable is set, Mutt-ng will include Delivered-To: header
-   fields when bouncing messages. Postfix users may wish to unset this
-   variable.
-
-25. $braille_friendly
-
-   Type: boolean
-
-   Default: no
-
-   When this variable is set, mutt will place the cursor at the beginning of
-   the current line in menus, even when the arrow_cursor variable is unset,
-   making it easier for blind persons using Braille displays to follow these
-   menus. The option is disabled by default because many visual terminals
-   don't permit making the cursor invisible.
-
-26. $certificate_file
-
-   Type: path
-
-   Default: "~/.mutt_certificates"
-
-   Availability: SSL or GNUTLS
-
-   This variable specifies the file where the certificates you trust are
-   saved. When an unknown certificate is encountered, you are asked if you
-   accept it or not. If you accept it, the certificate can also be saved in
-   this file and further connections are automatically accepted.
-
-   You can also manually add CA certificates in this file. Any server
-   certificate that is signed with one of these CA certificates are also
-   automatically accepted.
-
-   Example: set certificate_file=~/.muttng/certificates
-
-27. $charset
-
-   Type: string
-
-   Default: ""
-
-   Character set your terminal uses to display and enter textual data.
-
-28. $check_new
-
-   Type: boolean
-
-   Default: yes
-
-   Note: this option only affects maildir and MH style mailboxes.
-
-   When set, Mutt-ng will check for new mail delivered while the mailbox is
-   open. Especially with MH mailboxes, this operation can take quite some
-   time since it involves scanning the directory and checking each file to
-   see if it has already been looked at. If it's unset, no check for new mail
-   is performed while the mailbox is open.
-
-29. $collapse_unread
-
-   Type: boolean
-
-   Default: yes
-
-   When unset, Mutt-ng will not collapse a thread if it contains any unread
-   messages.
-
-30. $compose_format
-
-   Type: string
-
-   Default: "-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-"
-
-   Controls the format of the status line displayed in the ``compose'' menu.
-   This string is similar to ``$status_format'', but has its own set of
-   printf(3)-like sequences:
+   sets the $$rreeccoorrdd variable to the string _+_s_e_n_t___o_n__ and appends the
+   value of the evironment variable $HOSTNAME.
 
-   %a
-
-           total number of attachments
-
-   %h
-
-           local hostname
-
-   %l
-
-           approximate size (in bytes) of the current message
-
-   %v
-
-           Mutt-ng version string
-
-   See the text describing the ``$status_format'' option for more information
-   on how to set ``$compose_format''.
-
-31. $config_charset
-
-   Type: string
-
-   Default: ""
-
-   When defined, Mutt-ng will recode commands in rc files from this encoding.
-
-32. $confirmappend
-
-   Type: boolean
-
-   Default: yes
-
-   When set, Mutt-ng will prompt for confirmation when appending messages to
-   an existing mailbox.
-
-33. $confirmcreate
-
-   Type: boolean
-
-   Default: yes
+   _N_o_t_e_: There will be no warning if an environment variable is not
+   defined. The result will of the expansion will then be empty.
 
-   When set, Mutt-ng will prompt for confirmation when saving messages to a
-   mailbox which does not yet exist before creating it.
+3.3. Configuration Variables
 
-34. $connect_timeout
-
-   Type: number
-
-   Default: 30
-
-   Causes Mutt-ng to timeout a network connection (for IMAP or POP) after
-   this many seconds if the connection is not able to be established. A
-   negative value causes Mutt-ng to wait indefinitely for the connection to
-   succeed.
+   As for environment variables, the values of all configuration
+   variables as string can be used in the same way, too. For example,
 
-35. $content_type
-
-   Type: string
+set imap_home_namespace = $folder
 
-   Default: "text/plain"
+   would set the value of $$iimmaapp__hhoommee__nnaammeessppaaccee to the value to which
+   $$ffoollddeerr is _c_u_r_r_e_n_t_l_y set to.
 
-   Sets the default Content-Type: header field for the body of newly composed
-   messages.
+   _N_o_t_e_: There're no logical links established in such cases so that the
+   the value for $$iimmaapp__hhoommee__nnaammeessppaaccee won't change even if $$ffoollddeerr gets
+   changed.
 
-36. $copy
+   _N_o_t_e_: There will be no warning if a configuration variable is not
+   defined or is empty. The result will of the expansion will then be
+   empty.
 
-   Type: quadoption
+3.4. Self-Defined Variables
 
-   Default: yes
+   Mutt-ng flexibly allows users to define their own variables. To avoid
+   conflicts with the standard set and to prevent misleading error
+   messages, there's a reserved namespace for them: all user-defined
+   variables must be prefixed with user_ and can be used just like any
+   ordinary configuration or environment variable.
 
-   This variable controls whether or not copies of your outgoing messages
-   will be saved for later references. Also see ``$record'', ``$save_name'',
-   ``$force_name'' and ``fcc-hook''.
+   For example, to view the manual, users can either define two macros
+   like the following
 
-37. $crypt_autoencrypt
+macro generic <F1> "!less -r /path/to/manual" "Show manual"
+macro pager <F1> "!less -r /path/to/manual" "Show manual"
 
-   Type: boolean
+   for generic, pager and index .The alternative is to define a custom
+   variable like so:
 
-   Default: no
+set user_manualcmd = "!less -r /path/to_manual"
+macro generic <F1> "$user_manualcmd<enter>" "Show manual"
+macro pager <F1> "$user_manualcmd<enter>" "Show manual"
+macro index <F1> "$user_manualcmd<enter>" "Show manual"
 
-   Setting this variable will cause Mutt-ng to always attempt to PGP encrypt
-   outgoing messages. This is probably only useful in connection to the
-   send-hook command. It can be overridden by use of the pgp-menu, when
-   encryption is not required or signing is requested as well. If
-   ``$smime_is_default'' is set, then OpenSSL is used instead to create
-   S/MIME messages and settings can be overridden by use of the smime-menu.
-   (Crypto only)
+   to re-use the command sequence as in:
 
-38. $crypt_autopgp
+macro index <F2> "$user_manualcmd | grep '\^[ ]\\+~. '" "Show Patterns"
 
-   Type: boolean
+   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 end.
 
-   Default: yes
+   When the variable is first defined, the first value it gets assigned
+   is also the initial value to which it can be reset using the reset
+   command.
 
-   This variable controls whether or not Mutt-ng may automatically enable PGP
-   encryption/signing for messages. See also ``$crypt_autoencrypt'',
-   ``$crypt_replyencrypt'', ``$crypt_autosign'', ``$crypt_replysign'' and
-   ``$smime_is_default''.
+   The complete removal is done via the unset keyword.
 
-39. $crypt_autosign
+   After the following sequence:
 
-   Type: boolean
+set user_foo = 42
+set user_foo = 666
 
-   Default: no
+   the variable $user_foo has a current value of 666 and an initial of
+   42. The query
 
-   Setting this variable will cause Mutt-ng to always attempt to
-   cryptographically sign outgoing messages. This can be overridden by use of
-   the pgp-menu, when signing is not required or encryption is requested as
-   well. If ``$smime_is_default'' is set, then OpenSSL is used instead to
-   create S/MIME messages and settings can be overridden by use of the
-   smime-menu. (Crypto only)
+set ?user_foo
 
-40. $crypt_autosmime
+   will show 666. After doing the reset via
 
-   Type: boolean
+reset user_foo
 
-   Default: yes
+   a following query will give 42 as the result. After unsetting it via
 
-   This variable controls whether or not Mutt-ng may automatically enable
-   S/MIME encryption/signing for messages. See also ``$crypt_autoencrypt'',
-   ``$crypt_replyencrypt'', ``$crypt_autosign'', ``$crypt_replysign'' and
-   ``$smime_is_default''.
+unset user_foo
 
-41. $crypt_replyencrypt
+   any query or operation (except the noted expansion within other
+   statements) will lead to an error message.
 
-   Type: boolean
+3.5. Pre-Defined Variables
 
-   Default: yes
+   In order to allow users to share one setup over a number of different
+   machines without having to change its contents, there's a number of
+   pre-defined variables. These are prefixed with muttng_ and are
+   read-only, i.e. they cannot be set, unset or reset. The reference
+   chapter lists all available variables.
 
-   If set, automatically PGP or OpenSSL encrypt replies to messages which are
-   encrypted. (Crypto only)
+   _P_l_e_a_s_e_ _c_o_n_s_u_l_t_ _t_h_e_ _l_o_c_a_l_ _c_o_p_y_ _o_f_ _y_o_u_r_ _m_a_n_u_a_l_ _f_o_r_ _t_h_e_i_r_ _v_a_l_u_e_s_ _a_s_ _t_h_e_y
+   _m_a_y_ _d_i_f_f_e_r_ _f_r_o_m_ _d_i_f_f_e_r_e_n_t_ _m_a_n_u_a_l_ _s_o_u_r_c_e_s_. Where the manual is
+   installed in can be queried (already using such a variable) by
+   running:
 
-42. $crypt_replysign
+$ muttng -Q muttng_docdir
 
-   Type: boolean
+   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:
 
-   Default: no
+set user_manualcmd = '!less -r /path/to_manual'
 
-   If set, automatically PGP or OpenSSL sign replies to messages which are
-   signed.
+   to:
 
-   Note: this does not work on messages that are encrypted and signed!
-   (Crypto only)
+set user_manualcmd = "!less -r $muttng_docdir/manual.txt"
 
-43. $crypt_replysignencrypted
+   which works everywhere if a manual is installed.
 
-   Type: boolean
+   Please note that by the type of quoting, muttng determines when to
+   expand these values: when it finds double quotes, the value will be
+   expanded during reading the setup files but when it finds single
+   quotes, it'll expand it at runtime as needed.
 
-   Default: no
+   For example, the statement
 
-   If set, automatically PGP or OpenSSL sign replies to messages which are
-   encrypted. This makes sense in combination with ``$crypt_replyencrypt'',
-   because it allows you to sign all messages which are automatically
-   encrypted. This works around the problem noted in ``$crypt_replysign'',
-   that Mutt-ng is not able to find out whether an encrypted message is also
-   signed. (Crypto only)
+folder-hook . "set user_current_folder = $muttng_folder_name"
 
-44. $crypt_timestamp
+   will be already be translated to the following when reading the
+   startup files:
 
-   Type: boolean
+folder-hook . "set user_current_folder = some_folder"
 
-   Default: yes
+   with some_folder being the name of the first folder muttng opens. On
+   the contrary,
 
-   If set, Mutt-ng will include a time stamp in the lines surrounding PGP or
-   S/MIME output, so spoofing such lines is more difficult. If you are using
-   colors to mark these lines, and rely on these, you may unset this setting.
-   (Crypto only)
+folder-hook . 'set user_current_folder = $muttng_folder_name'
 
-45. $crypt_use_gpgme
+   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.
 
-   Type: boolean
+   A more practical example is:
 
-   Default: no
+folder-hook . 'source ~/.mutt/score-$muttng_folder_name'
 
-   This variable controls the use the GPGME enabled crypto backends. If it is
-   set and Mutt-ng was build with gpgme support, the gpgme code for S/MIME
-   and PGP will be used instead of the classic code.
+   which can be used to source files containing score commands depending
+   on the folder the user enters.
 
-   Note: You need to use this option in your .muttngrc configuration file as
-   it won't have any effect when used interactively.
+3.6. Type Conversions
 
-46. $crypt_verify_sig
+   A note about variable's types during conversion: internally values are
+   stored in internal types but for any dump/query or set operation
+   they're converted to and from string. That means that there's no need
+   to worry about types when referencing any variable. As an example, the
+   following can be used without harm (besides makeing muttng very likely
+   behave strange):
+
+set read_inc = 100
+set folder = $read_inc
+set read_inc = $folder
+set user_magic_number = 42
+set folder = $user_magic_number
 
-   Type: quadoption
+4. Defining/Using aliases
 
-   Default: yes
+   Usage: alias_k_e_y_ _a_d_d_r_e_s_s_ _[_,_ _a_d_d_r_e_s_s_,_._._._]
 
-   If ``yes'', always attempt to verify PGP or S/MIME signatures. If ``ask'',
-   ask whether or not to verify the signature. If ``no'', never attempt to
-   verify cryptographic signatures. (Crypto only)
+   It's usually very cumbersome to remember or type out the address of
+   someone you are communicating with. Mutt-ng allows you to create
+   ``aliases'' which map a short string to a full address.
 
-47. $date_format
+   _N_o_t_e_: if you want to create an alias for a group (by specifying more
+   than one address), you _m_u_s_t separate the addresses with a comma
+   (``,'').
 
-   Type: string
+   To remove an alias or aliases (``*'' means all aliases):
 
-   Default: "!%a, %b %d, %Y at %I:%M:%S%p %Z"
+   Usage: unalias_[_*_ _|_ _k_e_y_ _._._._ _]
 
-   This variable controls the format of the date printed by the ``%d''
-   sequence in ``$index_format''. This is passed to strftime(3) to process
-   the date.
+alias muttdude me@cs.hmc.edu (Michael Elkins)
+alias theguys manny, moe, jack
 
-   Unless the first character in the string is a bang (``!''), the month and
-   week day names are expanded according to the locale specified in the
-   variable ``$locale''. If the first character in the string is a bang, the
-   bang is discarded, and the month and week day names in the rest of the
-   string are expanded in the C locale (that is in US English).
+   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 ssoouurrccee. Consequently, you
+   can have multiple alias files, or you can have all aliases defined in
+   your muttrc.
 
-48. $debug_level
+   On the other hand, the <create-alias> function can use only one file,
+   the one pointed to by the $$aalliiaass__ffiillee variable (which is ~/.muttrc by
+   default). This file is not special either, in the sense that Mutt-ng
+   will happily append aliases to any file, but in order for the new
+   aliases to take effect you need to explicitly ssoouurrccee this file too.
 
-   Type: number
+   For example:
 
-   Default: 1
+source /usr/local/share/Mutt-ng.aliases
+source ~/.mail_aliases
+set alias_file=~/.mail_aliases
 
-   Availability: debug
+   To use aliases, you merely use the alias at any place in mutt where
+   muttprompts for addresses, such as the _T_o_: or _C_c_: prompt. You can also
+   enter aliases in your editor at the appropriate headers if you have
+   the $$eeddiittoorr__hheeaaddeerrss variable set.
 
-   This variable specifies the current debug level and may be used to
-   increase or decrease the verbosity level during runtime. It overrides the
-   level given with the -d command line option.
+   In addition, at the various address prompts, you can use the tab
+   character to expand a partial alias to the full alias. If there are
+   multiple matches, mutt will bring up a menu with the matching aliases.
+   In order to be presented with the full list of aliases, you must hit
+   tab with out a partial alias, such as at the beginning of the prompt
+   or after a comma denoting multiple addresses.
 
-   Currently, this number must be >= 0 and <= 5 and muttng must be started
-   with -d to enable debugging at all; enabling at runtime is not possible.
+   In the alias menu, you can select as many aliases as you want with the
+   _s_e_l_e_c_t_-_e_n_t_r_y key (default: RET), and use the _e_x_i_t key (default: q) to
+   return to the address prompt.
 
-49. $default_hook
+5. Changing the default key bindings
 
-   Type: string
+   Usage: bind_m_a_p_ _k_e_y_ _f_u_n_c_t_i_o_n
 
-   Default: "~f %s !~P | (~P ~C %s)"
+   This command allows you to change the default key bindings (operation
+   invoked when pressing a key).
 
-   This variable controls how send-hooks, message-hooks, save-hooks, and
-   fcc-hooks will be interpreted if they are specified with only a simple
-   regexp, instead of a matching pattern. The hooks are expanded when they
-   are declared, so a hook will be interpreted according to the value of this
-   variable at the time the hook is declared. The default value matches if
-   the message is either from a user matching the regular expression given,
-   or if it is from you (if the from address matches ``alternates'') and is
-   to or cc'ed to a user matching the given regular expression.
+   _m_a_p specifies in which menu the binding belongs. Multiple maps may be
+   specified by separating them with commas (no additional whitespace
+   isallowed). The currently defined maps are:
 
-50. $delete
+   generic
+          This is not a real menu, but is used as a fallback for all of
+          the other menus except for the pager and editor modes. If a key
+          is not defined in another menu, Mutt-ng will look for a binding
+          to use in this menu. This allows you to bind a key to a certain
+          function in multiple menus instead of having multiple bind
+          statements to accomplish the same task.
 
-   Type: quadoption
+   alias
+          The alias menu is the list of your personal aliases as defined
+          in your muttrc. It is the mapping from a short alias name to
+          the full email address(es) of the recipient(s).
 
-   Default: ask-yes
+   attach
+          The attachment menu is used to access the attachments on
+          received messages.
 
-   Controls whether or not messages are really deleted when closing or
-   synchronizing a mailbox. If set to yes, messages marked for deleting will
-   automatically be purged without prompting. If set to no, messages marked
-   for deletion will be kept in the mailbox.
+   browser
+          The browser is used for both browsing the local directory
+          structure, and for listing all of your incoming mailboxes.
 
-51. $delete_space
+   editor
+          The editor is the line-based editor the user enters text data.
 
-   Type: boolean
+   index
+          The index is the list of messages contained in a mailbox.
 
-   Default: no
+   compose
+          The compose menu is the screen used when sending a new message.
 
-   When sending messages with format=flowed by setting the $text_flowed
-   variable, this variable specifies whether to also set the DelSp parameter
-   to yes. If this is unset, no additional parameter will be send as a value
-   of no already is the default behavior.
+   pager
+          The pager is the mode used to display message/attachment data,
+          and help listings.
 
-   Note: this variable only has an effect on outgoing messages (if
-   $text_flowed is set) but not on incomming.
+   pgp
+          The pgp menu is used to select the OpenPGP keys used for
+          encrypting outgoing messages.
 
-52. $delete_untag
+   postpone
+          The postpone menu is similar to the index menu, except is used
+          when recalling a message the user was composing, but saved
+          until later.
 
-   Type: boolean
+   _k_e_y is the key (or key sequence) you wish to bind. To specify a
+   control character, use the sequence _\_C_x, where _x is the letter of the
+   control character (for example, to specify control-A use ``\Ca'').
+   Note that the case of _x as well as _\_C is ignored, so that _\_C_A, _\_C_a,
+   _\_c_A and _\_c_a are all equivalent. An alternative form is to specify the
+   key as a three digit octal number prefixed with a ``\'' (for example
+   _\_1_7_7 is equivalent to _\_c_?).
 
-   Default: yes
+   In addition, _k_e_y may consist of:
 
-   If this option is set, Mutt-ng will untag messages when marking them for
-   deletion. This applies when you either explicitly delete a message, or
-   when you save it to another folder.
+   _T_a_b_l_e_ _3_._1_._ _A_l_t_e_r_n_a_t_i_v_e_ _K_e_y_ _N_a_m_e_s
+   Sequence    Description
+   \t          tab
+   <tab>       tab
+   <backtab>   backtab / shift-tab
+   \r          carriage return
+   \n          newline
+   \e          escape
+   <esc>       escape
+   <up>        up arrow
+   <down>      down arrow
+   <left>      left arrow
+   <right>     right arrow
+   <pageup>    Page Up
+   <pagedown>  Page Down
+   <backspace> Backspace
+   <delete>    Delete
+   <insert>    Insert
+   <enter>     Enter
+   <return>    Return
+   <home>      Home
+   <end>       End
+   <space>     Space bar
+   <f1>        function key 1
+   <f10>       function key 10
 
-53. $digest_collapse
+   _k_e_y does not need to be enclosed in quotes unless it contains a space
+   (`` '').
 
-   Type: boolean
+   _f_u_n_c_t_i_o_n specifies which action to take when _k_e_y is pressed. For a
+   complete list of functions, see the ffuunnccttiioonnss. The special function
+   noop unbinds the specified key sequence.
 
-   Default: yes
+6. Defining aliases for character sets
 
-   If this option is set, Mutt-ng's received-attachments menu will not show
-   the subparts of individual messages in a multipart/digest. To see these
-   subparts, press 'v' on that menu.
+   Usage: cchhaarrsseett--hhooookk_a_l_i_a_s_c_h_a_r_s_e_t
 
-54. $display_filter
+   Usage: iiccoonnvv--hhooookk_c_h_a_r_s_e_t_l_o_c_a_l_-_c_h_a_r_s_e_t
 
-   Type: path
+   The cchhaarrsseett--hhooookk command defines an alias for a character set. This is
+   useful to properly display messages which are tagged with a character
+   set name not known to mutt.
 
-   Default: ""
+   The iiccoonnvv--hhooookk command defines a system-specific name for a character
+   set. This is helpful when your systems character conversion library
+   insists on using strange, system-specific names for character sets.
 
-   When set, specifies a command used to filter messages. When a message is
-   viewed it is passed as standard input to $display_filter, and the filtered
-   message is read from the standard output.
+7. Setting variables based upon mailbox
 
-55. $dotlock_program
+   Usage: ffoollddeerr--hhooookk [!]_r_e_g_e_x_p_c_o_m_m_a_n_d
 
-   Type: path
+   It is often desirable to change settings based on which mailbox you
+   are reading. The ffoollddeerr--hhooookk command provides a method by which you
+   can execute any configuration command. _r_e_g_e_x_p is a regular expression
+   specifying in which mailboxes to execute _c_o_m_m_a_n_d before loading. If a
+   mailbox matches multiple ffoollddeerr--hhooookk's, they are executed in the order
+   given in the muttrc.
 
-   Default: "$muttng_bindir/muttng_dotlock"
+   _N_o_t_e_: if you use the ``!'' shortcut for $$ssppoooollffiillee at the beginning of
+   the pattern, you must place it inside of double or single quotes in
+   order to distinguish it from the logical _n_o_t operator for the
+   expression.
 
-   Availability: Standalone and Dotlock
+   Note that the settings are _n_o_t restored when you leave the mailbox.
+   For example, a command action to perform is to change the sorting
+   methodbased upon the mailbox being read:
 
-   Contains the path of the muttng_dotlock(1) binary to be used by Mutt-ng.
+folder-hook mutt set sort=threads
 
-56. $dsn_notify
+   However, the sorting method is not restored to its previous value when
+   reading a different mailbox. To specify a _d_e_f_a_u_l_t command, use the
+   pattern ``.'':
 
-   Type: string
+folder-hook . set sort=date-sent
 
-   Default: ""
+8. Keyboard macros
 
-   Note: you should not enable this unless you are using Sendmail 8.8.x or
-   greater or in connection with the SMTP support via libESMTP.
+   Usage: macro_m_e_n_u_ _k_e_y_ _s_e_q_u_e_n_c_e_ _[_d_e_s_c_r_i_p_t_i_o_n_]
 
-   This variable sets the request for when notification is returned. The
-   string consists of a comma separated list (no spaces!) of one or more of
-   the following: never, to never request notification, failure, to request
-   notification on transmission failure, delay, to be notified of message
-   delays, success, to be notified of successful transmission.
+   Macros are useful when you would like a single key to perform a series
+   of actions. When you press _k_e_y in menu _m_e_n_u ,Mutt-ng will behave as if
+   you had typed _s_e_q_u_e_n_c_e. So if you have a common sequence of commands
+   you type, you can create a macro to execute those commands with a
+   singlekey.
 
-   Example: set dsn_notify="failure,delay"
+   _m_e_n_u is the mmaappss which the macro will be bound. Multiple maps may be
+   specified by separating multiple menu arguments by commas. Whitespace
+   may not be used in between the menu arguments and thecommas separating
+   them.
 
-57. $dsn_return
+   _k_e_y and _s_e_q_u_e_n_c_e are expanded by the same rules as the bbiinndd. There are
+   some additions however. The first is that control characters in
+   _s_e_q_u_e_n_c_e can also be specified as ^x. In order to get a caret (`^'')
+   you need to specify it twice. Secondly, to specify a certain key such
+   as _u_p or to invoke a function directly, you can use the format _<_k_e_y
+   _n_a_m_e_> and _<_f_u_n_c_t_i_o_n_ _n_a_m_e_> .For a listing of key names see the section
+   on bbiinndd. Functions are listed in the ffuunnccttiioonnss.
 
-   Type: string
+   The advantage with using function names directly is that the macros
+   willwork regardless of the current key bindings, so they are not
+   dependent on the user having particular key definitions. This makes
+   them more robustand portable, and also facilitates defining of macros
+   in files used by more than one user (eg. the system Muttngrc).
 
-   Default: ""
+   Optionally you can specify a descriptive text after _s_e_q_u_e_n_c_e, which is
+   shown in the help screens.
 
-   Note: you should not enable this unless you are using Sendmail 8.8.x or
-   greater or in connection with the SMTP support via libESMTP.
+   _N_o_t_e_: Macro definitions (if any) listed in the help screen(s), are
+   silently truncated at the screen width, and are not wrapped.
 
-   This variable controls how much of your message is returned in DSN
-   messages. It may be set to either hdrs to return just the message header,
-   or full to return the full message.
+9. Using color and mono video attributes
 
-   Example: set dsn_return=hdrs
+   Usage: color_o_b_j_e_c_t_ _f_o_r_e_g_r_o_u_n_d_ _b_a_c_k_g_r_o_u_n_d_ _[_r_e_g_e_x_p_]
+
+   Usage: color_i_n_d_e_x_ _f_o_r_e_g_r_o_u_n_d_ _p_a_t_t_e_r_n
+
+   Usage: uncolor_i_n_d_e_x_ _p_a_t_t_e_r_n_ _[_p_a_t_t_e_r_n_ _._._._]
+
+   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), you must specify both a foreground color _a_n_d a
+   background color (it is not possible to only specify one or the
+   other).
+
+   _o_b_j_e_c_t can be one of:
+
+     * attachment
+     * body (match _r_e_g_e_x_p in the body of messages)
+     * bold (highlighting bold patterns in the body of messages)
+     * error (error messages printed by Mutt-ng)
+     * header (match _r_e_g_e_x_p in the message header)
+     * hdrdefault (default color of the message header in the pager)
+     * index (match _p_a_t_t_e_r_n in the message index)
+     * indicator (arrow or bar used to indicate the current item in a
+       menu)
+     * markers (the ``+'' markers at the beginning of wrapped lines in
+       the pager)
+     * message (informational messages)
+     * normal
+     * quoted (text matching $$qquuoottee__rreeggeexxpp in the body of a message)
+     * quoted1, quoted2, ..., quoted_N (higher levels of quoting)
+     * search (highlighting of words in the pager)
+     * signature
+     * status (mode lines used to display info about the mailbox or
+       message)
+     * tilde (the ``~'' used to pad blank lines in the pager)
+     * tree (thread tree drawn in the message index and attachment menu)
+     * underline (highlighting underlined patterns in the body of
+       messages)
+
+   _f_o_r_e_g_r_o_u_n_d and _b_a_c_k_g_r_o_u_n_d can be one of the following:
+
+     * white
+     * black
+     * green
+     * magenta
+     * blue
+     * cyan
+     * yellow
+     * red
+     * default
+     * color_x
+
+   _f_o_r_e_g_r_o_u_n_d can optionally be prefixed with the keyword bright to make
+   the foreground color boldfaced (e.g., brightred).
+
+   If your terminal supports it, the special keyword _d_e_f_a_u_l_t can be used
+   as a transparent color. The value _b_r_i_g_h_t_d_e_f_a_u_l_t is also valid. If
+   Mutt-ng is linked against the _S_-_L_a_n_g library, you also need to set the
+   $COLORFGBG environment variable to the default colors of your terminal
+   for this to work; for example (for Bourne-like shells):
+
+set COLORFGBG="green;black"
+export COLORFGBG
+
+   _N_o_t_e_: The _S_-_L_a_n_g library requires you to use the _l_i_g_h_t_g_r_a_y and _b_r_o_w_n
+   keywords instead of _w_h_i_t_e and _y_e_l_l_o_w when setting this variable.
+
+   _N_o_t_e_: The uncolor command can be applied to the index object only. It
+   removes entries from the list. You _m_u_s_t specify the same pattern
+   specified in the color command for it to be removed. The pattern ``*''
+   is a special token which means to clear the color index list of all
+   entries.
+
+   Mutt-ng also recognizes the keywords _c_o_l_o_r_0, _c_o_l_o_r_1 ,..., _c_o_l_o_r_N_-_1 (_N
+   being the number of colors supported by your terminal). This is useful
+   when you remap the colors for your display (for example by changing
+   the color associated with _c_o_l_o_r_2 for your xterm), since color names
+   may then lose their normal meaning.
 
-58. $duplicate_threads
+   If your terminal does not support color, it is still possible change
+   the video attributes through the use of the ``mono'' command:
 
-   Type: boolean
+   Usage: mono_o_b_j_e_c_t_ _a_t_t_r_i_b_u_t_e_ _[_r_e_g_e_x_p_]
 
-   Default: yes
+   Usage: mono_i_n_d_e_x_ _a_t_t_r_i_b_u_t_e_ _p_a_t_t_e_r_n
 
-   This variable controls whether Mutt-ng, when sorting by threads, threads
-   messages with the same Message-ID: header field together. If it is set, it
-   will indicate that it thinks they are duplicates of each other with an
-   equals sign in the thread diagram.
+   Usage: unmono_i_n_d_e_x_ _p_a_t_t_e_r_n_ _[_p_a_t_t_e_r_n_ _._._._]
 
-59. $edit_headers
+   where _a_t_t_r_i_b_u_t_e is one of the following:
 
-   Type: boolean
+     * none
+     * bold
+     * underline
+     * reverse
+     * standout
 
-   Default: no
+10. Ignoring (weeding) unwanted message headers
 
-   This option allows you to edit the header of your outgoing messages along
-   with the body of your message.
+   Usage: ignore_p_a_t_t_e_r_n_ _[_p_a_t_t_e_r_n_ _._._._]
 
-   Which empty header fields to show is controlled by the $editor_headers
-   option.
+   Usage: unignore_p_a_t_t_e_r_n_ _[_p_a_t_t_e_r_n_ _._._._]
 
-60. $editor
+   Messages often have many header fields added by automatic processing
+   systems, or which may not seem useful to display on the screen. This
+   command allows you to specify header fields which you don't normally
+   want to see.
 
-   Type: path
+   You do not need to specify the full header field name. For example,
+   ``ignore content-'' will ignore all header fields that begin with the
+   pattern ``content-''. ``ignore *'' will ignore all headers.
 
-   Default: ""
+   To remove a previously added token from the list, use the ``unignore''
+   command. The ``unignore'' command will make Mutt-ng display headers
+   with the given pattern. For example, if you do ``ignore x-'' it is
+   possible to ``unignore x-mailer''.
 
-   This variable specifies which editor is used by Mutt-ng. It defaults to
-   the value of the $VISUAL, or $EDITOR, environment variable, or to the
-   string "vi" if neither of those are set.
+   ``unignore *'' will remove all tokens from the ignore list.
 
-61. $editor_headers
+   For example:
+# Sven's draconian header weeding
+ignore *
+unignore from date subject to cc
+unignore organization organisation x-mailer: x-newsreader: x-mailing-list:
+unignore posted-to:
 
-   Type: string
+11. Alternative addresses
 
-   Default: "From: To: Cc: Bcc: Subject: Reply-To: Newsgroups: Followup-To:
-   X-Comment-To:"
+   Usage: alternates_r_e_g_e_x_p_ _[_r_e_g_e_x_p_ _._._._]
 
-   If $edit_headers is set, this space-separated list specifies which
-   non-empty header fields to edit in addition to user-defined headers.
+   Usage: unalternates_r_e_g_e_x_p_ _[_r_e_g_e_x_p_ _._._._]
 
-   Note: if $edit_headers had to be turned on by force because $strict_mailto
-   is unset, this option has no effect.
+   With various functions, mutt will treat messages differently,
+   depending on 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 $$rreeppllyy__ttoo.)
 
-62. $encode_from
+   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 e-mail addresses you receive mail under. That's the purpose of
+   the alternates command: It takes a list of regular expressions, each
+   of which can identify an address under which you receive e-mail.
 
-   Type: boolean
+   The unalternates command can be used to write exceptions to alternates
+   patterns. If an address matches something in an alternates command,
+   but you nonetheless do not think it is from you, you can list a more
+   precise pattern under an unalternates command.
 
-   Default: no
+   To remove a regular expression from the alternates list, use the
+   unalternates command with exactly the same _r_e_g_e_x_p . Likewise, if the
+   _r_e_g_e_x_p for a alternates command matches an entry on the unalternates
+   list, that unalternates entry will be removed. If the _r_e_g_e_x_p for
+   unalternates is ``*'', _a_l_l_ _e_n_t_r_i_e_s on alternates will be removed.
 
-   When set, Mutt-ng will quoted-printable encode messages when they contain
-   the string ``From '' (note the trailing space) in the beginning of a line.
-   Useful to avoid the tampering certain mail delivery and transport agents
-   tend to do with messages.
+12. Format = Flowed
 
-   Note: as Mutt-ng currently violates RfC3676 defining format=flowed, it's
-   <em/strongly/ advised to set this option although discouraged by the
-   standard. Alternatively, you must take care of space-stuffing <tt/From /
-   lines (with a trailing space) yourself.
+12.1. Introduction
 
-63. $entropy_file
+   Mutt-ng contains support for so-called format=flowed messages. In the
+   beginning of email, each message had a fixed line width, and it was
+   enough for displaying them on fixed-size terminals. But times changed,
+   and nowadays hardly anybody still uses fixed-size terminals: more
+   people nowaydays use graphical user interfaces, with dynamically
+   resizable windows. This led to the demand of a new email format that
+   makes it possible for the email client to make the email look nice in
+   a resizable window without breaking quoting levels and creating an
+   incompatible email format that can also be displayed nicely on old
+   fixed-size terminals.
 
-   Type: path
+   For introductory information on format=flowed messages, see
+   <<hhttttpp::////wwwwww..jjooeeccllaarrkk..oorrgg//ffffaaqq..hhttmmll>>.
 
-   Default: ""
+12.2. Receiving: Display Setup
 
-   Availability: SSL
+   When you receive emails that are marked as format=flowed messages, and
+   is formatted correctly, mutt-ng will try to reformat the message to
+   optimally fit on your terminal. If you want a fixed margin on the
+   right side of your terminal, you can set the following:
 
-   The file which includes random data that is used to initialize SSL library
-   functions.
+set wrapmargin = 10
 
-64. $envelope_from_address
+   The code above makes the line break 10 columns before the right side
+   of the terminal.
 
-   Type: e-mail address
+   If your terminal is so wide that the lines are embarrassingly long,
+   you can also set a maximum line length:
 
-   Default: ""
+set max_line_length = 120
 
-   Manually sets the envelope sender for outgoing messages. This value is
-   ignored if ``$use_envelope_from'' is unset.
+   The example above will give you lines not longer than 120 characters.
 
-65. $escape
+   When you view at format=flowed messages, you will often see the
+   quoting hierarchy like in the following example:
 
-   Type: string
+>Bill, can you please send last month's progress report to Mr.
+>Morgan? We also urgently need the cost estimation for the new
+>production server that we want to set up before our customer's
+>project will go live.
 
-   Default: "~"
+   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:
 
-   Escape character to use for functions in the builtin editor.
+set stuff_quoted
 
-66. $fast_reply
+   This will lead to a nicer result that is easier to read:
 
-   Type: boolean
+> Bill, can you please send last month's progress report to Mr.
+> Morgan? We also urgently need the cost estimation for the new
+> production server that we want to set up before our customer's
+> project will go live.
 
-   Default: no
+12.3. Sending
 
-   When set, the initial prompt for recipients and subject are skipped when
-   replying to messages, and the initial prompt for subject is skipped when
-   forwarding messages.
+   If you want mutt-ng to send emails with format=flowed set, you need to
+   explicitly set it:
 
-   Note: this variable has no effect when the ``$autoedit'' variable is set.
+set text_flowed
 
-67. $fcc_attach
+   Additionally, you have to use an editor which supports writing
+   format=flowed-conforming emails. For vim(1), this is done by adding w
+   to the formatoptions (see :h formatoptions and :h fo-table) when
+   writing emails.
+
+   Also note that _f_o_r_m_a_t_=_f_l_o_w_e_d knows about ``space-stuffing'', that is,
+   when sending messages, some kinds of lines have to be indented with a
+   single space on the sending side. On the receiving side, the first
+   space (if any) is removed. As a consequence and in addition to the
+   above simple setting, please keep this in mind when making manual
+   formattings within the editor. Also note that mutt-ng currently
+   violates the standard (RRffCC  33667766) as it does not space-stuff lines
+   starting with:
+
+     * > This is _n_o_t the quote character but a right angle used for other
+       reasons
 
-   Type: boolean
+   Please make sure that you manually prepend a space to each of them.
 
-   Default: yes
+12.4. Additional Notes
 
-   This variable controls whether or not attachments on outgoing messages are
-   saved along with the main body of your message.
+   For completeness, the $$ddeelleettee__ssppaaccee variable provides the mechanism to
+   generate a DelSp=yes parameter on _o_u_t_g_o_i_n_g messages. According to the
+   standard, clients receiving a format=flowed messages should delete the
+   last space of a flowed line but still interpret the line as flowed.
+   Because flowed lines usually contain only one space at the end, this
+   parameter would make the receiving client concatenate the last word of
+   the previous with the first of the current line _w_i_t_h_o_u_t a space. This
+   makes ordinary text unreadable and is intended for languages rarely
+   using spaces. So please use this setting only if you're sure what
+   you're doing.
 
-68. $fcc_clear
+13. Mailing lists
 
-   Type: boolean
+   Usage: lists_r_e_g_e_x_p_ _[_r_e_g_e_x_p_ _._._._]
 
-   Default: no
+   Usage: unlists_r_e_g_e_x_p_ _[_r_e_g_e_x_p_ _._._._]
 
-   When this variable is set, FCCs will be stored unencrypted and unsigned,
-   even when the actual message is encrypted and/or signed. (PGP only)
+   Usage: subscribe_r_e_g_e_x_p_ _[_r_e_g_e_x_p_ _._._._]
 
-69. $file_charset
+   Usage: unsubscribe_r_e_g_e_x_p_ _[_r_e_g_e_x_p_ _._._._]
 
-   Type: string
+   Mutt-ng has a few nice features for uussiinngg--lliissttss. In order to take
+   advantage of them, you must specify which addresses belong to mailing
+   lists, and which mailing lists you are subscribed to. Once you have
+   done this, the lliisstt--rreeppllyy function will work for all known lists.
+   Additionally, when you send a message to a subscribed list, mutt will
+   add a Mail-Followup-To header to tell other users' mail user agents
+   not to send copies of replies to your personal address. Note that the
+   Mail-Followup-To header is a non-standard extension which is not
+   supported by all mail user agents. Adding it is not bullet-proof
+   against receiving personal CCs of list messages. Also note that the
+   generation of the Mail-Followup-To header is controlled by the
+   $$ffoolllloowwuupp__ttoo configuration variable.
+
+   More precisely, Mutt-ng maintains lists of patterns for the addresses
+   of known and subscribed mailing lists. Every subscribed mailing list
+   is known. To mark a mailing list as known, use the ``lists'' command.
+   To mark it as subscribed, use ``subscribe''.
+
+   You can use regular expressions with both commands. To mark all
+   messages sent to a specific bug report's address on mutt's bug
+   tracking system as list mail, for instance, you could say ``subscribe
+   [0-9]*@bugs.guug.de''. Often, it's sufficient to just give a portion
+   of the list's e-mail address.
 
-   Default: ""
+   Specify as much of the address as you need to to remove ambiguity. For
+   example, if you've subscribed to the Mutt-ng mailing list, you will
+   receive mail addressed to _m_u_t_t_-_u_s_e_r_s_@_m_u_t_t_._o_r_g. So, to tell Mutt-ng
+   that this is a mailing list, you could add ``lists mutt-users'' to
+   your initialization file. To tell mutt that you are subscribed to it,
+   add ``subscribe mutt-users'' to your initialization file instead. If
+   you also happen to get mail from someone whose address is
+   _m_u_t_t_-_u_s_e_r_s_@_e_x_a_m_p_l_e_._c_o_m, you could use ``lists mutt-users@mutt\\.org''
+   or ``subscribe mutt-users@mutt\\.org'' to match only mail from the
+   actual list.
+
+   The ``unlists'' command is used to remove a token from the list of
+   known and subscribed mailing-lists. Use ``unlists *'' to remove all
+   tokens.
+
+   To remove a mailing list from the list of subscribed mailing lists,
+   but keep it on the list of known mailing lists, use ``unsubscribe''.
 
-   This variable is a colon-separated list of character encoding schemes for
-   text file attatchments. If unset, $charset value will be used instead. For
-   example, the following configuration would work for Japanese text
-   handling:
+14. Using Multiple spool mailboxes
 
-   set file_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
+   Usage: mmbbooxx--hhooookk [!]_p_a_t_t_e_r_n_m_a_i_l_b_o_x
 
-   Note: ``iso-2022-*'' must be put at the head of the value as shown above
-   if included.
+   This command is used to move read messages from a specified mailbox to
+   adifferent mailbox automatically when you quit or change folders.
+   _p_a_t_t_e_r_n is a regular expression specifying the mailbox to treat as a
+   ``spool'' mailbox and _m_a_i_l_b_o_x specifies where mail should be saved
+   when read.
 
-70. $folder
+   Unlike some of the other _h_o_o_k commands, only the _f_i_r_s_t matching
+   pattern is used (it is not possible to save read mail in more than a
+   single mailbox).
 
-   Type: path
+15. Defining mailboxes which receive mail
 
-   Default: "~/Mail"
+   Usage: mailboxes_[_!_]_f_i_l_e_n_a_m_e_ _[_f_i_l_e_n_a_m_e_ _._._._ _]
 
-   Specifies the default location of your mailboxes. A ``+'' or ``='' at the
-   beginning of a pathname will be expanded to the value of this variable.
-   Note that if you change this variable from the default value you need to
-   make sure that the assignment occurs before you use ``+'' or ``='' for any
-   other variables since expansion takes place during the ``set'' command.
+   Usage: unmailboxes_[_!_]_f_i_l_e_n_a_m_e_ _[_f_i_l_e_n_a_m_e_ _._._._ _]
 
-71. $folder_format
+   This command specifies folders which can receive mail and which will
+   be checked for new messages. By default, the main menu status bar
+   displays how many of these folders have new messages.
 
-   Type: string
+   When changing folders, pressing _s_p_a_c_e will cycle through folders with
+   new mail.
 
-   Default: "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"
+   Pressing TAB in the directory browser will bring up a menu showing the
+   files specified by the mailboxes command, and indicate which contain
+   new messages. Mutt-ng will automatically enter this mode when invoked
+   from the command line with the -y option.
 
-   This variable allows you to customize the file browser display to your
-   personal taste. This string is similar to ``$index_format'', but has its
-   own set of printf(3)-like sequences:
+   The ``unmailboxes'' command is used to remove a token from the list of
+   folders which receive mail. Use ``unmailboxes *'' to remove all
+   tokens.
+
+   _N_o_t_e_: new mail is detected by comparing the last modification time to
+   the last access time. Utilities like biff or frm or any other program
+   which accesses the mailbox might cause Mutt-ng to never detect new
+   mail for that mailbox if they do not properly reset the access time.
+   Backup tools are another common reason for updated access times.
+
+   _N_o_t_e_: the filenames in the mailboxes command are resolved when the
+   command is executed, so if these names contain sshhoorrttccuuttss (such as
+   ``='' and ``!''), any variable definition that affect these characters
+   (like $$ffoollddeerr and $$ssppoooollffiillee) should be executed before the mailboxes
+   command.
 
-   %C
+16. User defined headers
 
-           current file number
+   Usage: my_hdr_s_t_r_i_n_g
 
-   %d
+   Usage: unmy_hdr_f_i_e_l_d_ _[_f_i_e_l_d_ _._._._]
 
-           date/time folder was last modified
+   The ``my_hdr'' command allows you to create your own header fields
+   which will be added to every message you send.
 
-   %f
+   For example, if you would like to add an ``Organization:'' header
+   field to all of your outgoing messages, you can put the command
 
-           filename
+my_hdr Organization: A Really Big Company, Anytown, USA
 
-   %F
+   in your .muttrc.
 
-           file permissions
+   _N_o_t_e_: space characters are _n_o_t allowed between the keyword and the
+   colon (``:''). The standard for electronic mail (RRffCC  882222) says that
+   space is illegal there, so Mutt-ng enforces the rule.
 
-   %g
+   If you would like to add a header field to a single message, you
+   should either set the $$eeddiitt__hheeaaddeerrss variable, or use the _e_d_i_t_-_h_e_a_d_e_r_s
+   function (default: ``E'') in the send-menu so that you can edit the
+   header of your message along with the body.
 
-           group name (or numeric gid, if missing)
+   To remove user defined header fields, use the ``unmy_hdr'' command.
+   You may specify an asterisk (``*'') to remove all header fields, or
+   the fields to remove. For example, to remove all ``To'' and ``Cc''
+   header fields, you could use:
 
-   %l
+unmy_hdr to cc
 
-           number of hard links
+17. Defining the order of headers when viewing messages
 
-   %N
+   Usage: hdr_order_h_e_a_d_e_r_ _h_e_a_d_e_r_ _[_h_e_a_d_e_r_ _._._._]
 
-           N if folder has new mail, blank otherwise
+   Usage: unhdr_order_[_ _*_ _|_ _h_e_a_d_e_r_ _h_e_a_d_e_r_ _._._._]
 
-   %s
+   With this command, you can specify an order in which mutt will attempt
+   to present headers to you when viewing messages.
 
-           size in bytes
+   ``unhdr_order *'' will clear all previous headers from the order list,
+   thus removing the header order effects set by the system-wide startup
+   file.
 
-   %t
+hdr_order From Date: From: To: Cc: Subject:
 
-           * if the file is tagged, blank otherwise
+18. Specify default save filename
 
-   %u
+   Usage: ssaavvee--hhooookk [!]_p_a_t_t_e_r_n_f_i_l_e_n_a_m_e
 
-           owner name (or numeric uid, if missing)
+   This command is used to override the default filename used when saving
+   messages. _f_i_l_e_n_a_m_e will be used as the default filename if the message
+   is _F_r_o_m_: an address matching _r_e_g_e_x_p or if you are the author and the
+   message is addressed _t_o_: something matching _r_e_g_e_x_p .
 
-   %>X
+   See ppaatttteerrnn--hhooookk for information on the exact format of _p_a_t_t_e_r_n.
 
-           right justify the rest of the string and pad with character "X"
+   Examples:
 
-   %|X
+save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
+save-hook aol\\.com$ +spam
 
-           pad to the end of the line with character "X"
+   Also see the ffcccc--ssaavvee--hhooookk command.
 
-72. $followup_to
+19. Specify default Fcc: mailbox when composing
 
-   Type: boolean
+   Usage: ffcccc--hhooookk [!]_p_a_t_t_e_r_n_m_a_i_l_b_o_x
 
-   Default: yes
+   This command is used to save outgoing mail in a mailbox other than
+   $$rreeccoorrdd. Mutt-ng searches the initial list of message recipients for
+   the first matching _r_e_g_e_x_p and uses _m_a_i_l_b_o_x as the default Fcc:
+   mailbox. If no match is found the message will be saved to $$rreeccoorrdd
+   mailbox.
 
-   Controls whether or not the Mail-Followup-To: header field is generated
-   when sending mail. When set, Mutt-ng will generate this field when you are
-   replying to a known mailing list, specified with the ``subscribe'' or
-   ``lists'' commands or detected by common mailing list headers.
+   See ppaatttteerrnn--hhooookk for information on the exact format of _p_a_t_t_e_r_n.
 
-   This field has two purposes. First, preventing you from receiving
-   duplicate copies of replies to messages which you send to mailing lists.
-   Second, ensuring that you do get a reply separately for any messages sent
-   to known lists to which you are not subscribed. The header will contain
-   only the list's address for subscribed lists, and both the list address
-   and your own email address for unsubscribed lists. Without this header, a
-   group reply to your message sent to a subscribed list will be sent to both
-   the list and your address, resulting in two copies of the same email for
-   you.
+   Example:
 
-73. $force_buffy_check
+fcc-hook [@.]aol\\.com$ +spammers
 
-   Type: boolean
+   The above will save a copy of all messages going to the aol.com domain
+   to the `+spammers' mailbox by default. Also see the ffcccc--ssaavvee--hhooookk
+   command.
 
-   Default: no
+20. Specify default save filename and default Fcc: mailbox at once
 
-   When set, it causes Mutt-ng to check for new mail when the buffy-list
-   command is invoked. When unset, buffy_list will just list all mailboxes
-   which are already known to have new mail.
+   Usage: ffcccc--ssaavvee--hhooookk [!]_p_a_t_t_e_r_n_m_a_i_l_b_o_x
 
-   Also see the following variables: ``$timeout'', ``$mail_check'' and
-   ``$imap_mail_check''.
+   This command is a shortcut, equivalent to doing both a ffcccc--hhooookk and a
+   ssaavvee--hhooookk with its arguments.
 
-74. $force_name
+21. Change settings based upon message recipients
 
-   Type: boolean
+   Usage: rreeppllyy--hhooookk [!]_p_a_t_t_e_r_n_c_o_m_m_a_n_d
 
-   Default: no
+   Usage: sseenndd--hhooookk [!]_p_a_t_t_e_r_n_c_o_m_m_a_n_d
 
-   This variable is similar to ``$save_name'', except that Mutt-ng will store
-   a copy of your outgoing message by the username of the address you are
-   sending to even if that mailbox does not exist.
+   Usage: sseenndd22--hhooookk [!]_p_a_t_t_e_r_n_c_o_m_m_a_n_d
 
-   Also see the ``$record'' variable.
+   These commands can be used to execute arbitrary configuration commands
+   based upon recipients of the message. _p_a_t_t_e_r_n is a regular expression
+   matching the desired address. _c_o_m_m_a_n_d is executed when _r_e_g_e_x_p matches
+   recipients of the message.
 
-75. $forward_decode
+   rreeppllyy--hhooookk is matched against the message you are _r_e_p_l_y_i_n_g _t_o, instead
+   of the message you are _s_e_n_d_i_n_g .  sseenndd--hhooookk is matched against all
+   messages, both _n_e_w and _r_e_p_l_i_e_s ._N_o_t_e_:rreeppllyy--hhooookks are matched _b_e_f_o_r_e
+   the sseenndd--hhooookk, _r_e_g_a_r_d_l_e_s_s of the order specified in the users's
+   configuration file.
 
-   Type: boolean
+   sseenndd22--hhooookk is matched every time a message is changed, either by
+   editing it, or by using the compose menu to change its recipients or
+   subject. sseenndd22--hhooookk is executed after sseenndd--hhooookk ,and can, e.g., be
+   used to set parameters such as the $$sseennddmmaaiill variable depending on the
+   message's sender address.
 
-   Default: yes
+   For each type of sseenndd--hhooookk or rreeppllyy--hhooookk, when multiple matches occur,
+   commands are executed in the order they are specified in the muttrc
+   (for that type of hook).
 
-   Controls the decoding of complex MIME messages into text/plain when
-   forwarding a message. The message header is also RFC2047 decoded. This
-   variable is only used, if ``$mime_forward'' is unset, otherwise
-   ``$mime_forward_decode'' is used instead.
+   See ppaatttteerrnn--hhooookk for information on the exact format of _p_a_t_t_e_r_n.
 
-76. $forward_decrypt
+   Example: send-hook mutt "set mime_forward signature=''"
 
-   Type: boolean
+   Another typical use for this command is to change the values of the
+   $$aattttrriibbuuttiioonn, $$ssiiggnnaattuurree and $$llooccaallee variables in order to change the
+   language of the attributions and signatures based upon the recipients.
 
-   Default: yes
+   _N_o_t_e_: the sseenndd--hhooookk's are only executed ONCE after getting the initial
+   list of recipients. Adding a recipient after replying or editing the
+   message will NOT cause any sseenndd--hhooookk to be executed. Also note that
+   my_hdr commands which modify recipient headers, or the message's
+   subject, don't have any effect on the current message when executed
+   from a sseenndd--hhooookk.
 
-   Controls the handling of encrypted messages when forwarding a message.
-   When set, the outer layer of encryption is stripped off. This variable is
-   only used if ``$mime_forward'' is set and ``$mime_forward_decode'' is
-   unset. (PGP only)
+22. Change settings before formatting a message
 
-77. $forward_edit
+   Usage: mmeessssaaggee--hhooookk [!]_p_a_t_t_e_r_n_c_o_m_m_a_n_d
 
-   Type: quadoption
+   This command can be used to execute arbitrary configuration commands
+   before viewing or formatting a message based upon information about
+   the message. _c_o_m_m_a_n_d is executed if the _p_a_t_t_e_r_n matches the message to
+   be displayed. When multiple matches occur, commands are executed in
+   the order they are specified in the muttrc.
 
-   Default: yes
+   See ppaatttteerrnn--hhooookk for information on the exact format of _p_a_t_t_e_r_n.
 
-   This quadoption controls whether or not the user is automatically placed
-   in the editor when forwarding messages. For those who always want to
-   forward with no modification, use a setting of no.
+   Example:
+message-hook ~A 'set pager=builtin'
+message-hook '~f freshmeat-news' 'set pager="less \"+/^  subject:.*\""'
 
-78. $forward_format
+23. Choosing the cryptographic key of the recipient
 
-   Type: string
+   Usage: ccrryypptt--hhooookk_p_a_t_t_e_r_n_k_e_y_i_d
 
-   Default: "[%a: %s]"
+   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 because, for some reasons, you need to
+   override the key Mutt-ng wouldnormally use. The ccrryypptt--hhooookk command
+   provides a method by which you can specify the ID of the public key to
+   be used when encrypting messages to a certain recipient.
 
-   This variable controls the default subject when forwarding a message. It
-   uses the same format sequences as the ``$index_format'' variable.
+   The meaning of "key id" is to be taken broadly in this context: You
+   can either put a numerical key ID here, an e-mail address, or even
+   just a real name.
 
-79. $forward_quote
+24. Adding key sequences to the keyboard buffer
 
-   Type: boolean
+   Usage: push_s_t_r_i_n_g
 
-   Default: no
+   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 mmaaccrroo command. You may use it to automatically
+   run a 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>'
 
-   When set forwarded messages included in the main body of the message (when
-   ``$mime_forward'' is unset) will be quoted using ``$indent_string''.
+25. Executing functions
 
-80. $from
+   Usage: exec_f_u_n_c_t_i_o_n_ _[_f_u_n_c_t_i_o_n_ _._._._ _]
 
-   Type: e-mail address
+   This command can be used to execute any function. Functions are listed
+   in the ffuunnccttiioonnss. ``exec function'' is equivalent to ``push
+   <function>''.
 
-   Default: ""
+26. Message Scoring
 
-   This variable contains a default from address. It can be overridden using
-   my_hdr (including from send-hooks) and ``$reverse_name''. This variable is
-   ignored if ``$use_from'' is unset.
+   Usage: score_p_a_t_t_e_r_n_ _v_a_l_u_e
 
-   E.g. you can use send-hook Mutt-ng-devel@lists.berlios.de 'my_hdr From:
-   Foo Bar <foo@bar.fb>' when replying to the Mutt-ng developer's mailing
-   list and Mutt-ng takes this email address.
+   Usage: unscore_p_a_t_t_e_r_n_ _[_p_a_t_t_e_r_n_ _._._._ _]
 
-   Defaults to the contents of the environment variable $EMAIL.
+   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 always useful to have the important messages marked and the
+   annoying messages or the ones that you aren't interested in deleted.
+   For this purpose, mutt-ng features a mechanism called ``scoring''.
 
-81. $gecos_mask
+   When you use scoring, every message has a base score of 0. You can
+   then use the score command to define patterns and a positive or
+   negative value associated with it. When a pattern matches a message,
+   the message's score will be raised or lowered by the amount of the
+   value associated with the pattern.
 
-   Type: regular expression
+score "~f nion@muttng\.org" 50
+score "~f @sco\.com" -100
 
-   Default: "^[^,]*"
+   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:
 
-   A regular expression used by Mutt-ng to parse the GECOS field of a
-   password entry when expanding the alias. By default the regular expression
-   is set to ``^[^,]*'' which will return the string up to the first ``,''
-   encountered. If the GECOS field contains a string like "lastname,
-   firstname" then you should do: set gecos_mask=".*".
+score "~f santaclaus@northpole\.int" =666
 
-   This can be useful if you see the following behavior: you address a e-mail
-   to user ID stevef whose full name is Steve Franklin. If Mutt-ng expands
-   stevef to ``Franklin'' stevef@foo.bar then you should set the gecos_mask
-   to a regular expression that will match the whole name so Mutt-ng will
-   expand ``Franklin'' to ``Franklin, Steve''.
+   What is important to note is that negative score values will be
+   rounded up to 0.
 
-82. $hdrs
+   To make scoring actually useful, the score must be applied in some
+   way. That's what the _s_c_o_r_e_ _t_h_r_e_s_h_o_l_d_s are for. Currently, there are
+   three score thresholds:
 
-   Type: boolean
+     * flag threshold: when a message has a score value equal or higher
+       than the flag threshold, it will be flagged.
+     * read threshold: when a message has a score value equal or lower
+       than the read threshold, it will be marked as read.
+     * delete threshold: when a message has a score value equal or lower
+       than the delete threshold, it will be marked as deleted.
 
-   Default: yes
+   These three thresholds can be set via the variables
+   $$ssccoorree__tthhrreesshhoolldd__rreeaadd, $$ssccoorree__tthhrreesshhoolldd__ffllaagg and
+   $$ssccoorree__tthhrreesshhoolldd__ddeelleettee.
 
-   When unset, the header fields normally added by the ``my_hdr'' command are
-   not created. This variable must be unset before composing a new message or
-   replying in order to take effect. If set, the user defined header fields
-   are added to every new message.
+   By default, $$ssccoorree__tthhrreesshhoolldd__rreeaadd and $$ssccoorree__tthhrreesshhoolldd__ddeelleettee are set
+   to -1, which means that in the default threshold configuration no
+   message will ever get marked as read or deleted.
 
-83. $header
+   Scoring gets especially interesting when combined with the color
+   command and the ~n pattern:
 
-   Type: boolean
+color index  black   yellow  "~n 10-"
+color index  red     yellow  "~n 100-"
 
-   Default: no
+   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 scoring mechanism, but it is more flexible, as it visually
+   marks different scores.
 
-   When set, this variable causes Mutt-ng to include the header of the
-   message you are replying to into the edit buffer. The ``$weed'' setting
-   applies.
+27. Spam detection
 
-84. $header_cache
+   Usage: spam_p_a_t_t_e_r_n_ _f_o_r_m_a_t
 
-   Type: path
+   Usage: nospam_p_a_t_t_e_r_n
 
-   Default: ""
+   Mutt-ng has generalized support for external spam-scoring filters. By
+   defining your spam patterns with the spam and nospam commands, you can
+   _l_i_m_i_t, _s_e_a_r_c_h, and _s_o_r_t your mail based on its spam attributes, as
+   determined by the external filter. You also can display the spam
+   attributes in your index display using the %H selector in the
+   $$iinnddeexx__ffoorrmmaatt variable. (Tip: try %?H?[%H] ? to display spam tags only
+   when they are defined for a given message.)
 
-   Availability: Header Cache
+   Your first step is to define your external filter's spam patterns
+   using the spam command. _p_a_t_t_e_r_n should be a regular expression that
+   matches a header in a mail message. If any message in the mailbox
+   matches this regular expression, it will receive a ``spam tag'' or
+   ``spam attribute'' (unless it also matches a nospam pattern -- see
+   below.) The appearance of this attribute is entirely up to you, and is
+   governed by the _f_o_r_m_a_t parameter. _f_o_r_m_a_t can be any static text, but
+   it also can include back-references from the _p_a_t_t_e_r_n expression. (A
+   regular expression ``back-reference'' refers to a sub-expression
+   contained within parentheses.) %1 is replaced with the first
+   back-reference in the regex, %2 with the second, etc.
+
+   If you're using multiple spam filters, a message can have more than
+   one spam-related header. You can define spam patterns for each filter
+   you use. If a message matches two or more of these patterns, and the
+   $spam_separator variable is set to a string, then the message's spam
+   tag will consist of all the _f_o_r_m_a_t strings joined together, with the
+   value of $spam_separator separating them.
 
-   The $header_cache variable points to the header cache database.
+   For example, suppose I use DCC, SpamAssassin, and PureMessage. I might
+   define these spam settings:
+spam "X-DCC-.*-Metrics:.*(....)=many"         "90+/DCC-%1"
+spam "X-Spam-Status: Yes"                     "90+/SA"
+spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM"
+set spam_separator=", "
 
-   If $header_cache points to a directory it will contain a header cache
-   database per folder. If $header_cache points to a file that file will be a
-   single global header cache. By default it is unset so no header caching
-   will be used.
+   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, 97/PM. (The four characters before ``=many'' in a
+   DCC report indicate the checksum used -- in this case, ``Fuz2''.)
 
-85. $header_cache_compress
+   If the $spam_separator variable is unset, then each spam pattern match
+   supersedes the previous one. Instead of getting joined _f_o_r_m_a_t strings,
+   you'll get only the last one to match.
 
-   Type: boolean
+   The spam tag is what will be displayed in the index when you use %H in
+   the $index_format variable. It's also the string that the ~H
+   pattern-matching expression matches against for _s_e_a_r_c_h and _l_i_m_i_t
+   functions. And it's what sorting by spam attribute will use as a sort
+   key.
+
+   That's a pretty complicated example, and most people's actual
+   environments will have only one spam filter. The simpler your
+   configuration, the more effective mutt can be, especially when it
+   comes to sorting.
+
+   Generally, when you sort by spam tag, mutt will sort _l_e_x_i_c_a_l_l_y -- that
+   is, by ordering strings alphnumerically. However, if a spam tag begins
+   with a number, mutt will sort numerically first, and lexically only
+   when two numbers are equal in value. (This is like UNIX's sort -n.) A
+   message with no spam attributes at all -- that is, one that didn't
+   match _a_n_y of your spam patterns -- is sorted at lowest priority.
+   Numbers are sorted next, beginning with 0 and ranging upward. Finally,
+   non-numeric strings are sorted, with ``a'' taking lowerpriority than
+   ``z''. Clearly, in general, sorting by spam tags is most effective
+   when you can coerce your filter to give you a raw number. But in case
+   you can't, mutt can still do something useful.
+
+   The nospam command can be used to write exceptions to spam patterns.
+   If a header pattern matches something in a spam command, but you
+   nonetheless do not want it to receive a spam tag, you can list amore
+   precise pattern under a nospam command.
+
+   If the _p_a_t_t_e_r_n given to nospam is exactly the same as the _p_a_t_t_e_r_n on
+   an existing spam list entry, the effect will be to remove the entry
+   from the spam list, instead of adding an exception. Likewise, if the
+   _p_a_t_t_e_r_n for a spam command matches an entry on the nospam list, that
+   nospam entry will be removed. If the _p_a_t_t_e_r_n for nospam is ``*'', _a_l_l
+   _e_n_t_r_i_e_s_ _o_n_ _b_o_t_h_ _l_i_s_t_s will be removed. This might be the default
+   action if you use spam and nospam in conjunction with a ffoollddeerr--hhooookk.
+
+   You can have as many spam or nospam commands as you like. You can even
+   do your own primitive spam detection within mutt -- for example, if
+   you consider all mail from MAILER-DAEMON to be spam, you can use a
+   spam command like this:
+
+spam "^From: .*MAILER-DAEMON"       "999"
 
-   Default: no
+28. Setting variables
 
-   If enabled the header cache will be compressed. So only one fifth of the
-   usual diskspace is used, but the uncompression can result in a slower open
-   of the cached folder.
+   Usage: set_[_n_o_|_i_n_v_]_v_a_r_i_a_b_l_e_ _[_=_v_a_l_u_e_]_ _[_v_a_r_i_a_b_l_e_._._._]
 
-86. $help
+   Usage: toggle_v_a_r_i_a_b_l_e_ _[_v_a_r_i_a_b_l_e_ _._._._]
 
-   Type: boolean
+   Usage: unset_v_a_r_i_a_b_l_e_ _[_v_a_r_i_a_b_l_e_ _._._._]
 
-   Default: yes
+   Usage: reset_v_a_r_i_a_b_l_e_ _[_v_a_r_i_a_b_l_e_ _._._._]
 
-   When set, help lines describing the bindings for the major functions
-   provided by each menu are displayed on the first line of the screen.
+   This command is used to set (and unset) vvaarriiaabblleess. There are four
+   basic types of variables: boolean, number, string and quadoption.
+   _b_o_o_l_e_a_n variables can be _s_e_t (true) or _u_n_s_e_t (false). _n_u_m_b_e_r variables
+   can be assigned a positive integer value.
 
-   Note: The binding will not be displayed correctly if the function is bound
-   to a sequence rather than a single keystroke. Also, the help line may not
-   be updated if a binding is changed while Mutt-ng is running. Since this
-   variable is primarily aimed at new users, neither of these should present
-   a major problem.
+   _s_t_r_i_n_g variables consist of any number of printable characters.
+   _s_t_r_i_n_g_s must be enclosed in quotes if they contain spaces or tabs. You
+   may also use the ``C'' escape sequences _\_n and _\_t for newline and tab,
+   respectively.
 
-87. $hidden_host
+   _q_u_a_d_o_p_t_i_o_n variables are used to control whether or not to be prompted
+   for certain actions, or to specify a default action. A value of _y_e_s
+   will cause the action to be carried out automatically as if you had
+   answered yes to the question. Similarly, a value of _n_o will cause the
+   the action to be carried out as if you had answered ``no.'' A value of
+   _a_s_k_-_y_e_s will cause a prompt with a default answer of ``yes'' and
+   _a_s_k_-_n_o will provide a default answer of ``no.''
 
-   Type: boolean
+   Prefixing a variable with ``no'' will unset it. Example: set noaskbcc
+   .
 
-   Default: no
+   For _b_o_o_l_e_a_n variables, you may optionally prefix the variable name
+   with inv to toggle the value (on or off). This is useful when writing
+   macros. Example: set invsmart_wrap.
 
-   When set, Mutt-ng will skip the host name part of ``$hostname'' variable
-   when adding the domain part to addresses. This variable does not affect
-   the generation of Message-ID: header fields, and it will not lead to the
-   cut-off of first-level domains.
+   The toggle command automatically prepends the inv prefix to all
+   specified variables.
 
-88. $hide_limited
+   The unset command automatically prepends the no prefix to all
+   specified variables.
 
-   Type: boolean
+   Using the enter-command function in the _i_n_d_e_x menu, you can query the
+   value of a variable by prefixing the name of the variable with a
+   question mark:
 
-   Default: no
+set ?allow_8bit
 
-   When set, Mutt-ng will not show the presence of messages that are hidden
-   by limiting, in the thread tree.
+   The question mark is actually only required for boolean and quadoption
+   variables.
 
-89. $hide_missing
+   The reset command resets all given variables to the compile time
+   defaults (hopefully mentioned in this manual). If you use the command
+   set and prefix the variable with ``&'' this has the same behavior as
+   the reset command.
 
-   Type: boolean
+   With the reset command there exists the special variable ``all'',
+   which allows you to reset all variables to their system defaults.
 
-   Default: yes
+29. Reading initialization commands from another file
 
-   When set, Mutt-ng will not show the presence of missing messages in the
-   thread tree.
+   Usage: source_f_i_l_e_n_a_m_e_ _[_f_i_l_e_n_a_m_e_ _._._._]
 
-90. $hide_thread_subject
+   This command allows the inclusion of initialization commands from
+   other files. For example, I place all of my aliases in ~/.mail_aliases
+   so that I can make my ~/.muttrc readable and keep my aliases private.
 
-   Type: boolean
+   If the filename begins with a tilde (``~''), it will be expanded to
+   the path of your home directory.
 
-   Default: yes
+   If the filename ends with a vertical bar (|), then _f_i_l_e_n_a_m_e is
+   considered to be an executable program from which to read input (eg.
+   source ~/bin/myscript|).
 
-   When set, Mutt-ng will not show the subject of messages in the thread tree
-   that have the same subject as their parent or closest previously displayed
-   sibling.
+30. Removing hooks
 
-91. $hide_top_limited
+   Usage: unhook_[_*_ _|_ _h_o_o_k_-_t_y_p_e_]
 
-   Type: boolean
+   This command permits you to flush hooks you have previously defined.
+   You can either remove all hooks by giving the ``*'' character as an
+   argument, or you can remove all hooks of a specific type by saying
+   something like unhook send.
 
-   Default: no
+31. Sharing Setups
 
-   When set, Mutt-ng will not show the presence of messages that are hidden
-   by limiting, at the top of threads in the thread tree. Note that when
-   $hide_missing is set, this option will have no effect.
+31.1. Character Sets
 
-92. $hide_top_missing
+   As users may run mutt-ng on different systems, the configuration must
+   be maintained because it's likely that people want to use the setup
+   everywhere they use mutt-ng. And mutt-ng tries to help where it can.
 
-   Type: boolean
+   To not produce conflicts with different character sets, mutt-ng allows
+   users to specify in which character set their configuration files are
+   encoded. Please note that while reading the configuration files, this
+   is only respected after the corresponding declaration appears. It's
+   advised to put the following at the very beginning of a users
+   muttngrc:
 
-   Default: yes
+set config_charset = "..."
 
-   When set, Mutt-ng will not show the presence of missing messages at the
-   top of threads in the thread tree. Note that when $hide_limited is set,
-   this option will have no effect.
+   and replacing the dots with the actual character set. To avoid
+   problems while maintaining the setup, vim(1) user's may want to use
+   modelines as show in:
 
-93. $history
+# vim:fileencoding=...:
 
-   Type: number
+   while, again, replacing the dots with the appropriate name. This tells
+   vim(1) as which character set to read and save the file.
 
-   Default: 10
+31.2. Modularization
 
-   This variable controls the size (in number of strings remembered) of the
-   string history buffer. The buffer is cleared each time the variable is
-   changed.
+   ``Modularization'' means to divide the setup into several files while
+   sorting the options or commands by topic. Especially for longer setups
+   (e.g. with many hooks), this helps maintaining it and solving trouble.
 
-94. $honor_followup_to
+   When using separation, setups may be, as a whole or in fractions,
+   shared over different systems.
 
-   Type: quadoption
+31.3. Conditional parts
 
-   Default: yes
+   When using a configuration on different systems, the user may not
+   always have influence on how mutt-ng is installed and which features
+   it includes.
 
-   This variable controls whether or not a Mail-Followup-To: header field is
-   honored when group-replying to a message.
+   To solve this, mutt-ng contain a feature based on the ``ifdef'' patch
+   written for mutt. Its basic syntax is:
 
-95. $hostname
+ifdef <item> <command>
+ifndef <item> <command>
 
-   Type: string
+   ...whereby <item> can be one of:
 
-   Default: ""
+     * a function name
+     * a variable name
+     * a menu name
+     * a feature name
 
-   Specifies the hostname to use after the ``@'' in local e-mail addresses
-   and during generation of Message-ID: headers.
+   All available functions, variables and menus are documented elsewhere
+   in this manual but ``features'' is specific to these two commands. To
+   test for one, prefix one of the following keywords with feature_:
+   ncurses, slang, iconv, idn, dotlock, standalone, pop, nntp, imap, ssl,
+   gnutls, sasl, sasl2, libesmtp, compressed, color, classic_pgp,
+   classic_smime, gpgme, header_cache
 
-   Please be sure to really know what you are doing when changing this
-   variable to configure a custom domain part of Message-IDs.
+   As an example, one can use the following in ~/.muttngrc:
 
-96. $ignore_list_reply_to
+ifdef feature_imap 'source ~/.mutt-ng/setup-imap'
+ifdef feature_pop  'source ~/.mutt-ng/setup-pop'
+ifdef feature_nntp 'source ~/.mutt-ng/setup-nntp'
 
-   Type: boolean
+   ...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.
 
-   Default: no
+   An example for testing for variable names can be used if users use
+   different revisions of mutt-ng whereby the older one may not have a
+   certain variable. To test for the availability of $$iimmaapp__mmaaiill__cchheecckk
+   use:
 
-   Affects the behaviour of the reply function when replying to messages from
-   mailing lists. When set, if the ``Reply-To:'' header field is set to the
-   same value as the ``To:'' header field, Mutt-ng assumes that the
-   ``Reply-To:'' header field was set by the mailing list to automate
-   responses to the list, and will ignore this field. To direct a response to
-   the mailing list when this option is set, use the list-reply function;
-   group-reply will reply to both the sender and the list. Remember: This
-   option works only for mailing lists which are explicitly set in your
-   muttngrc configuration file.
+ifdef imap_mail_check 'set imap_mail_check = 300'
 
-97. $imap_authenticators
+   Provided for completeness is the test for menu names. To set
+   $$ppaaggeerr__iinnddeexx__lliinneess only if the pager menu is available, use:
 
-   Type: string
+ifdef pager 'set pager_index_lines = 10'
 
-   Default: ""
+   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:
 
-   Availability: IMAP
+ifdef feature_ncurses 'source ~/.mutt-ng/setup-ncurses'
+ifndef feature_ncurses 'source ~/.mutt-ng/setup-slang'
 
-   This is a colon-delimited list of authentication methods Mutt-ng may
-   attempt to use to log in to an IMAP server, in the order Mutt-ng should
-   try them. Authentication methods are either ``login'' or the right side of
-   an IMAP ``AUTH='' capability string, e.g. ``digest-md5'', ``gssapi'' or
-   ``cram-md5''. This parameter is case-insensitive.
+   ...and...
 
-   If this parameter is unset (the default) Mutt-ng will try all available
-   methods, in order from most-secure to least-secure.
+ifdef feature_slang 'source ~/.mutt-ng/setup-slang'
+ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses'
 
-   Example: set imap_authenticators="gssapi:cram-md5:login"
+32. Obsolete Variables
 
-   Note: Mutt-ng will only fall back to other authentication methods if the
-   previous methods are unavailable. If a method is available but
-   authentication fails, Mutt-ng will not connect to the IMAP server.
+   In the process of ensuring and creating more consistency, many
+   variables have been renamed and some of the old names were already
+   removed. Please see sseecctt--oobbssoolleettee for a complete list.
 
-98. $imap_check_subscribed
+Chapter 4. Advanced Usage
 
-   Type: boolean
+   _T_a_b_l_e_ _o_f_ _C_o_n_t_e_n_t_s
 
-   Default: no
+   11..  RReegguullaarr  EExxpprreessssiioonnss
+   22..  PPaatttteerrnnss
 
-   When set, mutt will fetch the set of subscribed folders from your server
-   on connection, and add them to the set of mailboxes it polls for new mail.
-   See also the ``mailboxes'' command.
+        22..11..  CCoommpplleexx  PPaatttteerrnnss
+        22..22..  PPaatttteerrnnss  aanndd  DDaatteess
 
-99. $imap_delim_chars
+   33..  FFoorrmmaatt  SSttrriinnggss
 
-   Type: string
+        33..11..  IInnttrroodduuccttiioonn
+        33..22..  CCoonnddiittiioonnaall  EExxppaannssiioonn
+        33..33..  MMooddiiffiiccaattiioonnss  aanndd  PPaaddddiinngg
 
-   Default: "/."
+   44..  UUssiinngg  TTaaggss
+   55..  UUssiinngg  HHooookkss
 
-   Availability: IMAP
+        55..11..  MMeessssaaggee  MMaattcchhiinngg  iinn  HHooookkss
 
-   This contains the list of characters which you would like to treat as
-   folder separators for displaying IMAP paths. In particular it helps in
-   using the '=' shortcut for your $folder variable.
+   66..  UUssiinngg  tthhee  ssiiddeebbaarr
+   77..  EExxtteerrnnaall  AAddddrreessss  QQuueerriieess
+   88..  MMaaiillbbooxx  FFoorrmmaattss
+   99..  MMaaiillbbooxx  SShhoorrttccuuttss
+   1100..  HHaannddlliinngg  MMaaiilliinngg  LLiissttss
+   1111..  EEddiittiinngg  tthhrreeaaddss
 
-100. $imap_headers
+        1111..11..  LLiinnkkiinngg  tthhrreeaaddss
+        1111..22..  BBrreeaakkiinngg  tthhrreeaaddss
 
-   Type: string
+   1122..  DDeelliivveerryy  SSttaattuuss  NNoottiiffiiccaattiioonn  ((DDSSNN))  SSuuppppoorrtt
+   1133..  PPOOPP33  SSuuppppoorrtt  ((OOPPTTIIOONNAALL))
+   1144..  IIMMAAPP  SSuuppppoorrtt  ((OOPPTTIIOONNAALL))
 
-   Default: ""
+        1144..11..  TThhee  FFoollddeerr  BBrroowwsseerr
+        1144..22..  AAuutthheennttiiccaattiioonn
 
-   Availability: IMAP
+   1155..  NNNNTTPP  SSuuppppoorrtt  ((OOPPTTIIOONNAALL))
 
-   Mutt-ng requests these header fields in addition to the default headers
-   (``DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE
-   CONTENT-DESCRIPTION IN-REPLY-TO REPLY-TO LINES X-LABEL'') from IMAP
-   servers before displaying the ``index'' menu. You may want to add more
-   headers for spam detection.
+        1155..11..  AAggaaiinn::  SSccoorriinngg
 
-   Note: This is a space separated list.
+   1166..  SSMMTTPP  SSuuppppoorrtt  ((OOPPTTIIOONNAALL))
+   1177..  MMaannaaggiinngg  mmuullttiippllee  IIMMAAPP//PPOOPP//NNNNTTPP  aaccccoouunnttss  ((OOPPTTIIOONNAALL))
+   1188..  SSttaarrtt  aa  WWWWWW  BBrroowwsseerr  oonn  UURRLLss  ((EEXXTTEERRNNAALL))
+   1199..  CCoommpprreesssseedd  ffoollddeerrss  SSuuppppoorrtt  ((OOPPTTIIOONNAALL))
 
-101. $imap_home_namespace
+        1199..11..  OOppeenn  aa  ccoommpprreesssseedd  mmaaiillbbooxx  ffoorr  rreeaaddiinngg
+        1199..22..  WWrriittee  aa  ccoommpprreesssseedd  mmaaiillbbooxx
+        1199..33..  AAppppeenndd  aa  mmeessssaaggee  ttoo  aa  ccoommpprreesssseedd  mmaaiillbbooxx
+        1199..44..  EEnnccrryypptteedd  ffoollddeerrss
 
-   Type: string
+1. Regular Expressions
 
-   Default: ""
+   All string patterns in Mutt-ng including those in more complex
+   ppaatttteerrnnss must be specified using regular expressions (regexp) in the
+   ``POSIX extended'' syntax (which is more or less the syntax used by
+   egrep and GNU awk). For your convenience, we have included below a
+   brief description of this syntax.
+
+   The search is case sensitive if the pattern contains at least one
+   upper case letter, and case insensitive otherwise. Note that ``\''
+   must be quoted if used for a regular expression in an initialization
+   command: ``\\''.
+
+   A regular expression is a pattern that describes a set of strings.
+   Regular expressions are constructed analogously to arithmetic
+   expressions, by using various operators to combine smaller
+   expressions.
+
+   Note that the regular expression can be enclosed/delimited by either "
+   or ' which is useful if the regular expression includes a white-space
+   character. See mmuuttttrrcc--ssyynnttaaxx for more information on " and ' delimiter
+   processing. To match a literal " or ' you must preface it with \
+   (backslash).
 
-   Availability: IMAP
+   The fundamental building blocks are the regular expressions that match
+   a single character. Most characters, including all letters and digits,
+   are regular expressions that match themselves. Any metacharacter with
+   special meaning may be quoted by preceding it with a backslash.
 
-   You normally want to see your personal folders alongside your INBOX in the
-   IMAP browser. If you see something else, you may set this variable to the
-   IMAP path to your folders.
+   The period ``.'' matches any single character. The caret ``^'' andthe
+   dollar sign ``$'' are metacharacters that respectively match the empty
+   string at the beginning and end of a line.
 
-102. $imap_keepalive
+   A list of characters enclosed by ``]'' and ``]'' matches any single
+   character in that list; if the first character of the list is a caret
+   ``^'' then it matches any character _n_o_t in the list. For example, the
+   regular expression _]_0_1_2_3_4_5_6_7_8_9_] matches any single digit. A range of
+   ASCII characters may be specified by giving the first and last
+   characters, separated by a hyphen ``-''. Most metacharacters lose
+   their special meaning inside lists. To include a literal ``]'' place
+   it first in the list. Similarly, to include a literal ``^'' place it
+   anywhere but first. Finally, to include a literal hyphen ``-'' place
+   it last.
 
-   Type: number
+   Certain named classes of characters are predefined. Character classes
+   consist of ``[:'', a keyword denoting the class, and ``:]''. The
+   following classes are defined by the POSIX standard:
 
-   Default: 900
+   [:alnum:]
+          Alphanumeric characters.
 
-   Availability: IMAP
+   [:alpha:]
+          Alphabetic characters.
 
-   This variable specifies the maximum amount of time in seconds that Mutt-ng
-   will wait before polling open IMAP connections, to prevent the server from
-   closing them before Mutt-ng has finished with them.
+   [:blank:]
+          Space or tab characters.
 
-   The default is well within the RFC-specified minimum amount of time (30
-   minutes) before a server is allowed to do this, but in practice the RFC
-   does get violated every now and then.
+   [:cntrl:]
+          Control characters.
 
-   Reduce this number if you find yourself getting disconnected from your
-   IMAP server due to inactivity.
+   [:digit:]
+          Numeric characters.
 
-103. $imap_list_subscribed
+   [:graph:]
+          Characters that are both printable and visible. (A space is
+          printable, but not visible, while an ``a'' is both.)
 
-   Type: boolean
+   [:lower:]
+          Lower-case alphabetic characters.
 
-   Default: no
+   [:print:]
+          Printable characters (characters that are not control
+          characters.)
 
-   Availability: IMAP
+   [:punct:]
+          Punctuation characters (characters that are not letter, digits,
+          control characters, or space characters).
 
-   This variable configures whether IMAP folder browsing will look for only
-   subscribed folders or all folders. This can be toggled in the IMAP browser
-   with the toggle-subscribed function.
+   [:space:]
+          Space characters (such as space, tab and formfeed, to name a
+          few).
 
-104. $imap_login
+   [:upper:]
+          Upper-case alphabetic characters.
 
-   Type: string
+   [:xdigit:]
+          Characters that are hexadecimal digits.
 
-   Default: ""
+   A character class is only valid in a regular expression inside the
+   brackets of a character list. Note that the brackets in these class
+   names are part of the symbolic names, and must be included in addition
+   to the brackets delimiting the bracket list. For example, _[_[_:_d_i_g_i_t_:_]_]
+   is equivalent to _[_0_-_9_].
 
-   Availability: IMAP
+   Two additional special sequences can appear in character lists. These
+   apply to non-ASCII character sets, which can have single symbols
+   (calledcollating elements) that are represented with more than one
+   character, as well as several characters that are equivalent for
+   collating or sorting purposes:
 
-   Your login name on the IMAP server.
+   Collating Symbols
+          A collating symbol is a multi-character collating element
+          enclosed in ``[.'' and ``.]''. For example, if ``ch'' is a
+          collating element, then _[_[_._c_h_._]_] is a regexp that matches this
+          collating element, while _[_c_h_] is a regexp that matches either
+          ``c'' or ``h''.
 
-   This variable defaults to the value of ``$imap_user.''
+   Equivalence Classes
+          An equivalence class is a locale-specific name for a list of
+          characters that are equivalent. The name is enclosed in ``[=''
+          and ``=]''. For example, the name ``e'' might be used to
+          represent all of ``è'' ``é'' and ``e''. In this case, _[_[_=_e_=_]_]
+          is a regexp that matches any of ``è'', ``é'' and ``e''.
 
-105. $imap_mail_check
+   A regular expression matching a single character may be followed by
+   one of several repetition operators:
 
-   Type: number
+   ?
+          The preceding item is optional and matched at most once.
 
-   Default: 300
+   *
+          The preceding item will be matched zero or more times.
 
-   This variable configures how often (in seconds) Mutt-ng should look for
-   new mail in IMAP folders. This is split from the ``mail_check'' variable
-   to generate less traffic and get more accurate information for local
-   folders.
+   +
+          The preceding item will be matched one or more times.
 
-106. $imap_pass
+   {n}
+          The preceding item is matched exactly _n times.
 
-   Type: string
+   {n,}
+          The preceding item is matched _n or more times.
 
-   Default: ""
+   {,m}
+          The preceding item is matched at most _m times.
 
-   Availability: IMAP
+   {n,m}
+          The preceding item is matched at least _n times, but no more
+          than _m times.
 
-   Specifies the password for your IMAP account. If unset, Mutt-ng will
-   prompt you for your password when you invoke the fetch-mail function.
+   Two regular expressions may be concatenated; the resulting regular
+   expression matches any string formed by concatenating two substrings
+   that respectively match the concatenated subexpressions.
 
-   Warning: you should only use this option when you are on a fairly secure
-   machine, because the superuser can read your configuration even if you are
-   the only one who can read the file.
+   Two regular expressions may be joined by the infix operator ``|''; the
+   resulting regular expression matches any string matching either
+   subexpression.
 
-107. $imap_passive
+   Repetition takes precedence over concatenation, which in turn takes
+   precedence over alternation. A whole subexpression may be enclosed in
+   parentheses to override these precedence rules.
 
-   Type: boolean
+   _N_o_t_e_: If you compile Mutt-ng with the GNU _r_x package, the following
+   operators may also be used in regular expressions:
 
-   Default: yes
+   \\y
+          Matches the empty string at either the beginning or the end of
+          a word.
 
-   Availability: IMAP
+   \\B
+          Matches the empty string within a word.
 
-   When set, Mutt-ng will not open new IMAP connections to check for new
-   mail. Mutt-ng will only check for new mail over existing IMAP connections.
-   This is useful if you don't want to be prompted to user/password pairs on
-   Mutt-ng invocation, or if opening the connection is slow.
+   \\<
+          Matches the empty string at the beginning of a word.
 
-108. $imap_peek
+   \\>
+          Matches the empty string at the end of a word.
 
-   Type: boolean
+   \\w
+          Matches any word-constituent character (letter, digit, or
+          underscore).
 
-   Default: yes
+   \\W
+          Matches any character that is not word-constituent.
 
-   Availability: IMAP
+   \\`
+          Matches the empty string at the beginning of a buffer (string).
 
-   If set, Mutt-ng will avoid implicitly marking your mail as read whenever
-   you fetch a message from the server. This is generally a good thing, but
-   can make closing an IMAP folder somewhat slower. This option exists to
-   appease speed freaks.
+   \\'
+          Matches the empty string at the end of a buffer.
 
-109. $imap_reconnect
+   Please note however that these operators are not defined by POSIX, so
+   they may or may not be available in stock libraries on various
+   systems.
 
-   Type: quadoption
+2. Patterns
 
-   Default: ask-yes
+   Mutt-ng's pattern language provides a simple yet effective way to set
+   up rules to match messages, e.g. for operations like tagging and
+   scoring. A pattern consists of one or more sub-pattern, which can be
+   logically grouped, ORed, and negated. For a complete listing of these
+   patterns, please refer to table ppaatttteerrnnss in the Reference chapter.
 
-   Availability: IMAP
+   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.
 
-   Controls whether or not Mutt-ng will try to reconnect to IMAP server when
-   the connection is lost.
+2.1. Complex Patterns
 
-110. $imap_servernoise
+   It is possible to combine several sub-patterns to a more complex
+   pattern. The most simple possibility is to logically AND several
+   patterns by stringing them together:
 
-   Type: boolean
+~s 'SPAM' ~U
 
-   Default: yes
+   The pattern above matches all messages that contain ``SPAM'' in the
+   subject and are unread.
 
-   Availability: IMAP
+   To logical OR patterns, simply use the | operator. This one especially
+   useful when using local groups:
 
-   When set, Mutt-ng will display warning messages from the IMAP server as
-   error messages. Since these messages are often harmless, or generated due
-   to configuration problems on the server which are out of the users' hands,
-   you may wish to suppress them at some point.
+~f ("nion@muttng\.org"|"ak@muttng\.org"|"pdmef@muttng\.org")
+(~b mutt-ng|~s Mutt-ng)
+!~x '@synflood\.at'
 
-111. $imap_user
+   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 third pattern matches all messages that do not contain
+   ``@synflood\.at'' in the References: header, i.e. messages that are
+   not an (indirect) reply to one of my messages. A pattern can be
+   logicall negated using the ! operator.
 
-   Type: string
+2.2. Patterns and Dates
 
-   Default: ""
+   When using dates in patterns, the dates must be specified in a special
+   format, i.e. DD/MM/YYYY. If you don't specify month or year, they
+   default to the current month or year. When using date ranges, and you
+   specify only the minimum or the maximum, the specified date will be
+   excluded, e.g. 01/06/2005- matches against all messages _a_f_t_e_r Juni
+   1st, 2005.
 
-   Availability: IMAP
+   It is also possible to use so-called ``error margins'' when specifying
+   date ranges. You simply specify a date, and then the error margin.
+   This margin needs to contain the information whether it goes ``forth''
+   or ``back'' in time, by using + and -. Then follows a number and a
+   unit, i.e. y for years, m for months, w for weeks and d for days. If
+   you use the special * sign, it means that the error margin goes to
+   both``directions'' in time.
+
+~d 01/01/2005+1y
+~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 matches all dates 1 day around December 28th, 2004 (i.e.
+   Dec 27th, 28th and 29th).
 
-   The name of the user whose mail you intend to access on the IMAP server.
+   Relative dates are also very important, as they make it possible to
+   specify date ranges between a fixed number of units and the current
+   date. How this works can be seen in the following example:
 
-   This variable defaults to your user name on the local machine.
+~d >2w # messages older than two weeks
+~d <3d # messages newer than 3 days
+~d =1m # messages that are exactly one month old
 
-112. $implicit_autoview
+3. Format Strings
 
-   Type: boolean
+3.1. Introduction
 
-   Default: no
+   The so called _F_o_r_m_a_t_ _S_t_r_i_n_g_s offer great flexibility when configuring
+   mutt-ng. In short, they describe what items to print out how in menus
+   and status messages.
 
-   If set, Mutt-ng will look for a mailcap entry with the ``copiousoutput''
-   flag set for every MIME attachment it doesn't have an internal viewer
-   defined for. If such an entry is found, Mutt-ng will use the viewer
-   defined in that entry to convert the body part to text form.
+   Basically, they work as this: for different menus and bars, there's a
+   variable specifying the layout. For every item available, there is a
+   so called _e_x_p_a_n_d_o.
 
-113. $include
+   For example, when running mutt-ng on different machines or different
+   versions for testing purposes, it may be interesting to have the
+   following information always printed on screen when one is in the
+   index:
 
-   Type: quadoption
+     * the current hostname
+     * the current mutt-ng version number
 
-   Default: ask-yes
+   The setting for the status bar of the index is controlled via the
+   $$ssttaattuuss__ffoorrmmaatt variable. For the hostname and version string, there's
+   an expando for $status_format: %h expands to the hostname and %v to
+   the version string. When just configuring:
 
-   Controls whether or not a copy of the message(s) you are replying to is
-   included in your reply.
+set status_format = "%v on %h: ..."
 
-114. $include_onlyfirst
+   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:
 
-   Type: boolean
+Mutt-ng 1.5.9i on mailhost: ...
 
-   Default: no
+   In the index, there're more useful information one could want to see:
 
-   Controls whether or not Mutt-ng includes only the first attachment of the
-   message you are replying.
+     * which mailbox is open
+     * how man new, flagged or postponed messages
+     * ...
 
-115. $indent_string
+   To include the mailbox' name is as easy as:
 
-   Type: string
+set status_format = "%v on %h: %B: ...
 
-   Default: "> "
+   When the currently opened mailbox is Inbox, this will be expanded to:
 
-   Specifies the string to prepend to each line of text quoted in a message
-   to which you are replying. You are strongly encouraged not to change this
-   value, as it tends to agitate the more fanatical netizens.
+Mutt-ng 1.5.9i on mailhost: Inbox: ...
 
-116. $index_format
+   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 instead only print something if there are any.
 
-   Type: string
+3.2. Conditional Expansion
 
-   Default: "%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s"
+   To only print the number of messages if there are new messages in the
+   current mailbox, further extend $status_format to:
 
-   This variable allows you to customize the message index display to your
-   personal taste.
+set status_format = "%v on %h: %B %?n?%n new? ...
 
-   ``Format strings'' are similar to the strings used in the ``C'' function
-   printf(3) to format output (see the man page for more detail). The
-   following sequences are defined in Mutt-ng:
+   This feature is called _n_o_n_z_e_r_o_-_p_r_i_n_t_i_n_g 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 basic syntax is:
 
-   %a
+%?<item>?<string if nonzero>?
 
-           address of the author
+   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.
 
-   %A
+   But this is not all: this feature only offers one alternative: ``print
+   something if not zero.'' Mutt-ng does, as you might guess, also
+   provide a logically complete version: ``if zero, print something and
+   else print something else.'' This is achieved by the following syntax
+   for those expandos which may be printed nonzero:
 
-           reply-to address (if present; otherwise: address of author)
+%?<item>?<string if nonzero>&<string if zero>?
 
-   %b
+   Using this we can make mutt-ng to do the following:
 
-           filename of the original message folder (think mailBox)
+     * make it print ``_n new messages'' whereby _n is the count but only
+       if there new ones
+     * and make it print ``no new messages'' if there aren't any
 
-   %B
+   The corresponding configuration is:
 
-           the list to which the letter was sent, or else the folder name
-           (%b).
+set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ...
 
-   %c
+   This doubles the use of the ``new messages'' string because it'll get
+   always printed. Thus, it can be shortened to:
 
-           number of characters (bytes) in the message
+set status_format = "%v on %h: %B: %?n?%n&no? new messages ...
 
-   %C
+   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.
 
-           current message number
+3.3. Modifications and Padding
 
-   %d
+   Besides the information given so far, there're even more features of
+   format strings:
 
-           date and time of the message in the format specified by
-           ``date_format'' converted to sender's time zone
+     * When specifying %_<item> instead of just %<item>, mutt-ng will
+       convert all characters in the expansion of <item> to lowercase.
+     * When specifying %:<item> instead of just %<item>, mutt-ng will
+       convert all dots in the expansion of <item> to underscores (_).
 
-   %D
+   Also, there's a feature called _P_a_d_d_i_n_g supplied by the following two
+   expandos: %|X and %>X .
 
-           date and time of the message in the format specified by
-           ``date_format'' converted to the local time zone
+   %|X
+          When this occurs, mutt-ng will fill the rest of the line with
+          the character X. In our example, filling the rest of the line
+          with dashes is done by setting:
 
-   %e
+set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-"
 
-           current message number in thread
+   %>X
+          Since the previous expando stops at the end of line, there must
+          be a way to fill the gap between two items via the %>X expando:
+          it puts as many characters X in between two items so that the
+          rest of the line will be right-justified. For example, to not
+          put the version string and hostname of our example on the left
+          but on the right and fill the gap with spaces, one might use
+          (note the space after %>):
 
-   %E
+set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)"
 
-           number of messages in current thread
+4. Using Tags
 
-   %f
+   Sometimes it is desirable to perform an operation on a group of
+   messages all at once rather than one at a time. An example might be to
+   save messages to a mailing list to a separate folder, or to delete all
+   messages with a given subject. To tag all messages matching a pattern,
+   use the tag-pattern function, which is bound to ``shift-T'' by
+   default. Or you can select individual messages by hand using the
+   ``tag-message'' function, which is bound to ``t'' by default. See
+   ppaatttteerrnnss for Mutt-ng's pattern matching syntax.
+
+   Once you have tagged the desired messages, you can use the
+   ``tag-prefix'' operator, which is the ``;'' (semicolon) key by
+   default. When the ``tag-prefix'' operator is used, the _n_e_x_t operation
+   will be applied to all tagged messages if that operation can be used
+   in that manner. If the $$aauuttoo__ttaagg variable is set, the next operation
+   applies to the tagged messages automatically, without requiring the
+   ``tag-prefix''.
+
+   In mmaaccrroo or ppuusshh commands, you can use the ``tag-prefix-cond''
+   operator. If there are no tagged messages, mutt will "eat" the rest of
+   the macro to abort it's execution.Mutt-ng will stop "eating" the macro
+   when it encounters the ``end-cond'' operator; after this operator the
+   rest of the macro will be executed asnormal.
 
-           entire From: line (address + real name)
+5. Using Hooks
 
-   %F
+   A _h_o_o_k is a concept borrowed from the EMACS editor which allows you to
+   execute arbitrary commands before performing some operation. For
+   example, you may wish to tailor your configuration based upon which
+   mailbox you are reading, or to whom you are sending mail. In the
+   Mutt-ng world, a _h_o_o_k consists of a rreeggeexxpp or ppaatttteerrnnss along with a
+   configuration option/command. See
+     * ffoollddeerr--hhooookk
+     * sseenndd--hhooookk
+     * mmeessssaaggee--hhooookk
+     * ssaavvee--hhooookk
+     * mmbbooxx--hhooookk
+     * ffcccc--hhooookk
+     * ffcccc--ssaavvee--hhooookk
+
+   for specific details on each type of _h_o_o_k available.
+
+   _N_o_t_e_: if a hook changes configuration settings, these changes remain
+   effective until the end of the current mutt session. As this is
+   generally not desired, a default hook needs to be added before all
+   other hooks to restore configuration defaults. Here is an example with
+   sseenndd--hhooookk and the my_hdr directive:
+
+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 (  sseenndd--hhooookk, ssaavvee--hhooookk, ffcccc--hhooookk,
+   mmeessssaaggee--hhooookk )are evaluated in a slightly different manner. For the
+   other types of hooks, a rreeggeexxpp is sufficient. But in dealing with
+   messages a finer grain of control is needed for matching since for
+   different purposes you want to match different criteria.
+
+   Mutt-ng allows the use of the ppaatttteerrnnss language for matching messages
+   in hook commands. This works in exactly the same way as it would when
+   _l_i_m_i_t_i_n_g or_s_e_a_r_c_h_i_n_g the mailbox, except that you are restricted to
+   those operators which match information mutt extracts from the header
+   of the message (i.e. from, to, cc, date, subject, etc.).
+
+   For example, if you wanted to set your return address based upon
+   sending mail to a specific address, you could do something like:
+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
+   _m_e_@_c_s_._h_m_c_._e_d_u.
+
+   However, it is not required that you write the pattern to match using
+   the full searching language. You can still specify a simple _r_e_g_u_l_a_r
+   _e_x_p_r_e_s_s_i_o_n like the other hooks, in which case Mutt-ng will translate
+   your pattern into the full language, using the translation specified
+   by the ddeeffaauulltt--hhooookk variable. The pattern is translated at the time
+   the hook is declared, so the value of ddeeffaauulltt--hhooookk that is in effect
+   at that time will be used.
 
-           author name, or recipient name if the message is from you
+6. Using the sidebar
 
-   %H
+   The sidebar, a feature specific to Mutt-ng, allows you to use a
+   mailbox listing which looks very similar to the ones you probably know
+   from GUI mail clients. The sidebar lists all specified mailboxes,
+   shows the number in each and highlights the ones with new email Use
+   the following configuration commands:
+set sidebar_visible="yes"
+set sidebar_width=25
 
-           spam attribute(s) of this message
+   If you want to specify the mailboxes you can do so with:
+set mbox='=INBOX'
+mailboxes INBOX \
+MBOX1 \
+MBOX2 \
+...
 
-   %g
+   You can also specify the colors for mailboxes with new mails by using:
+color sidebar_new red black
+color sidebar white black
 
-           newsgroup name (if compiled with nntp support)
+   Reasonable key bindings look e.g. like this:
+bind index \Cp sidebar-prev
+bind index \Cn sidebar-next
+bind index \Cb sidebar-open
+bind pager \Cp sidebar-prev
+bind pager \Cn sidebar-next
+bind pager \Cb sidebar-open
 
-   %i
+macro index B ':toggle sidebar_visible^M'
+macro pager B ':toggle sidebar_visible^M'
 
-           message-id of the current message
+   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'.
 
-   %l
+7. External Address Queries
 
-           number of lines in the message (does not work with maildir, mh,
-           and possibly IMAP folders)
+   Mutt-ng supports connecting to external directory databases such as
+   LDAP, ph/qi, bbdb, or NIS through a wrapper script which connects to
+   mutt using a simple interface. Using the $$qquueerryy__ccoommmmaanndd variable, you
+   specify the wrapper command to use. For example:
 
-   %L
+set query_command = "mutt_ldap_query.pl '%s'"
 
-           If an address in the To or CC header field matches an address
-           defined by the users ``subscribe'' command, this displays "To
-           <list-name>", otherwise the same as %F.
+   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 optional information. On error, or if there are no
+   matching addresses, return a non-zero exit code and a one line error
+   message.
 
-   %m
+   An example multiple response output:
+Searching database ... 20 entries ... 3 matching:
+me@cs.hmc.edu           Michael Elkins  mutt dude
+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 the matching responses. From the query menu, you
+   can select addresses to create aliases, or to mail. You can tag
+   multiple addressesto mail, start a new query, or have a new query
+   appended to the current responses.
 
-           total number of message in the mailbox
+   The other mechanism for accessing the query function is for address
+   completion, similar to the alias completion. In any prompt for address
+   entry, you can use the complete-query function (default: ^T) to run a
+   query based on the current address you have typed. Like aliases, mutt
+   will look for what you have typed back to the last space or comma. If
+   there is a single response for that query, mutt will expand the
+   address in place. If there are multiple responses, mutt will activate
+   the querymenu. At the query menu, you can select one or more addresses
+   to be added to the prompt.
 
-   %M
+8. Mailbox Formats
 
-           number of hidden messages if the thread is collapsed.
+   Mutt-ng supports reading and writing of four different mailbox
+   formats: mbox, MMDF, MH and Maildir. The mailbox type is autodetected,
+   so there is no need to use a flag for different mailbox types. When
+   creating newmailboxes, Mutt-ng uses the default specified with the
+   $$mmbbooxx__ttyyppee variable.
 
-   %N
+   _m_b_o_x. This is the most widely used mailbox format for UNIX. All
+   messages are stored in a single file. Each message has a line of the
+   form:
 
-           message score
+From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
 
-   %n
+   to denote the start of a new message (this is often referred to as the
+   ``From_'' line).
 
-           author's real name (or address if missing)
+   _M_M_D_F. This is a variant of the _m_b_o_x format. Each message is surrounded
+   by lines containing ``^A^A^A^A'' (four control-A's).
 
-   %O
+   _M_H. A radical departure from _m_b_o_x and _M_M_D_F, a mailbox consists of a
+   directory and each message is stored in a separate file. The filename
+   indicates the message number (however, this is may not correspond to
+   the message number Mutt-ng displays). Deleted messages arerenamed with
+   a comma (,) prepended to the filename. _N_o_t_e_: Mutt detects this type of
+   mailbox by looking for either .mh_sequences or .xmhcache (needed to
+   distinguish normal directories from MH mailboxes).
+
+   _M_a_i_l_d_i_r. The newest of the mailbox formats, used by the Qmail MTA (a
+   replacement for sendmail). Similar to _M_H, except that it adds three
+   subdirectories of the mailbox: _t_m_p, _n_e_w and _c_u_r .Filenames for the
+   messages are chosen in such a way they are unique, even when
+   twoprograms are writing the mailbox over NFS, which means that no file
+   locking is needed.
 
-           (_O_riginal save folder) Where Mutt-ng would formerly have stashed
-           the message: list name or recipient name if no list
+9. Mailbox Shortcuts
 
-   %s
+   There are a number of built in shortcuts which refer to specific
+   mailboxes. These shortcuts can be used anywhere you are prompted for a
+   file or mailbox path.
 
-           subject of the message
+     * ! -- refers to your $$ssppoooollffiillee (incoming) mailbox
+     * > -- refers to your $$mmbbooxx file
+     * < -- refers to your $$rreeccoorrdd file
+     * ^ -- refers to the current mailbox
+     * - or !! -- refers to the file you've last visited
+     * ~ -- refers to your home directory
+     * = or + -- refers to your $$ffoollddeerr directory
+     * @_a_l_i_a_s -- refers to the ssaavvee--hhooookk as determined by the address of
+       the alias
 
-   %S
+10. Handling Mailing Lists
 
-           status of the message (N/D/d/!/r/*)
+   Mutt-ng has a few configuration options that make dealing with large
+   amounts of mail easier. The first thing you must do is to let Mutt
+   know what addresses you consider to be mailing lists (technically this
+   does not have to be a mailing list, but that is what it is most often
+   used for), and what lists you are subscribed to. This is accomplished
+   through the use of the lliissttss commands in your muttrc.
 
-   %t
+   Now that Mutt-ng knows what your mailing lists are, it can do several
+   things, the first of which is the ability to show the name of a list
+   through which you received a message (i.e., of a subscribed list) in
+   the _i_n_d_e_x menu display. This is useful to distinguish between personal
+   and list mail in the same mailbox. In the $$iinnddeexx__ffoorrmmaatt variable, the
+   escape ``%L'' will return the string ``To <list>'' when ``list''
+   appears in the ``To'' field, and ``Cc <list>'' when it appears in the
+   ``Cc'' field (otherwise it returns the name of the author).
+
+   Often times the ``To'' and ``Cc'' fields in mailing list messages tend
+   to get quite large. Most people do not bother to remove the author of
+   the message they are reply to from the list, resulting in two or more
+   copies being sent to that person. The ``list-reply'' function, which
+   by default is bound to ``L'' in the _i_n_d_e_x menu and _p_a_g_e_r, helps reduce
+   the clutter by only replying to the known mailing list addresses
+   instead of all recipients (except as specified by Mail-Followup-To,
+   see below).
+
+   Mutt-ng also supports the Mail-Followup-To header. When you send a
+   message to a list of recipients which includes one or several
+   subscribed mailing lists, and if the $$ffoolllloowwuupp__ttoo option is set, mutt
+   will generate a Mail-Followup-To header which contains all the
+   recipients to whom you send this message, but not your address. This
+   indicates that group-replies or list-replies (also known as
+   ``followups'') to this message should only be sent to the original
+   recipients of the message, and not separately to you - you'll receive
+   your copy through one of the mailing lists you are subscribed to.
+
+   Conversely, when group-replying or list-replying to a message which
+   has a Mail-Followup-To header, mutt will respect this header if the
+   $$hhoonnoorr__ffoolllloowwuupp__ttoo configuration variable is set. Using list-reply
+   will in this case also make sure that the reply goes to the mailing
+   list, even if it's not specified in the list of recipients in the
+   Mail-Followup-To.
 
-           `to:' field (recipients)
+   Note that, when header editing is enabled, you can create a
+   Mail-Followup-To header manually. Mutt-ng will only auto-generate this
+   header if it doesn't exist when you send the message.
 
-   %T
+   The other method some mailing list admins use is to generate a
+   ``Reply-To'' field which points back to the mailing list address
+   rather than the author of the message. This can create problems when
+   trying to reply directly to the author in private, since most mail
+   clients will automatically reply to the address given in the
+   ``Reply-To'' field. Mutt-ng uses the $$rreeppllyy__ttoo variable to help decide
+   which address to use. If set to _a_s_k_-_y_e_s or _a_s_k_-_n_o, you will be
+   prompted as to whether or not you would like to use the address given
+   inthe ``Reply-To'' field, or reply directly to the address given in
+   the ``From'' field. When set to _y_e_s, the ``Reply-To'' field will be
+   used when present.
 
-           the appropriate character from the $to_chars string
+   The ``X-Label:'' header field can be used to further identify mailing
+   lists or list subject matter (or just to annotate messages
+   individually). The $$iinnddeexx__ffoorrmmaatt variable's ``%y'' and ``%Y'' escapes
+   can be used to expand ``X-Label:'' fields in the index, and Mutt-ng's
+   pattern-matcher can match regular expressions to ``X-Label:'' fields
+   with the ``~y'' selector. ``X-Label:'' is not a standard message
+   header field, but it can easily be inserted by procmailand other mail
+   filtering agents.
+
+   Lastly, Mutt-ng has the ability to ssoorrtt the mailbox into tthhrreeaaddss. A
+   thread is a group of messages which all relate to the same subject.
+   This is usually organized into a tree-like structure where a message
+   and all of its replies are represented graphically. If you've ever
+   used a threaded news client, this is the same concept. It makes
+   dealingwith large volume mailing lists easier because you can easily
+   delete uninteresting threads and quickly find topics of value.
 
-   %u
+11. Editing threads
 
-           user (login) name of the author
+   Mutt-ng has the ability to dynamically restructure threads that are
+   broken either by misconfigured software or bad behavior from some
+   correspondents. This allows to clean your mailboxes formats) from
+   these annoyances which make it hard to follow a discussion.
 
-   %v
+11.1. Linking threads
 
-           first name of the author, or the recipient if the message is from
-           you
+   Some mailers tend to "forget" to correctly set the "In-Reply-To:" and
+   "References:" headers when replying to a message. This results in
+   broken discussions because Mutt-ng has not enough information to guess
+   the correct threading. You can fix this by tagging the reply, then
+   moving to the parent message and using the ``link-threads'' function
+   (bound to & by default). The reply will then be connected to this
+   "parent" message.
 
-   %W
+   You can also connect multiple children at once, tagging them and using
+   the tag-prefix command (';') or the auto_tag option.
 
-           name of organization of author (`organization:' field)
+11.2. Breaking threads
 
-   %X
+   On mailing lists, some people are in the bad habit of starting a new
+   discussion by hitting "reply" to any message from the list and
+   changing the subject to a totally unrelated one. You can fix such
+   threads by using the ``break-thread'' function (boundby default to #),
+   which will turn the subthread starting from the current message into a
+   whole different thread.
 
-           number of attachments
+12. Delivery Status Notification (DSN) Support
 
-   %y
+   RRffCC  11889944 defines a set of MIME content types for relaying information
+   about the status of electronic mail messages. These can be thought of
+   as ``return receipts.''
 
-           `x-label:' field, if present
+   Users can make use of it in one of the following two ways:
 
-   %Y
+     * Berkeley sendmail 8.8.x currently has some command line options in
+       which the mail client can make requests as to what type of status
+       messages should be returned.
+     * The SMTP support via libESMTP supports it, too.
 
-           `x-label' field, if present, and (1) not at part of a thread tree,
-           (2) at the top of a thread, or (3) `x-label' is different from
-           preceding message's `x-label'.
+   To support this, there are two variables:
 
-   %Z
+     * $$ddssnn__nnoottiiffyy is used to request receipts for different results
+       (such as failed message,message delivered, etc.).
+     * $$ddssnn__rreettuurrnn requests how much of your message should be returned
+       with the receipt (headers or full message).
 
-           message status flags
+   Please see the reference chapter for possible values.
 
-   %{fmt}
+13. POP3 Support (OPTIONAL)
 
-           the date and time of the message is converted to sender's time
-           zone, and ``fmt'' is expanded by the library function
-           ``strftime''; a leading bang disables locales
+   If Mutt-ng was compiled with POP3 support (by running the _c_o_n_f_i_g_u_r_e
+   script with the _-_-_e_n_a_b_l_e_-_p_o_p flag), it has the ability to work with
+   mailboxes located on a remote POP3 server and fetch mail for local
+   browsing.
 
-   %[fmt]
+   You can access the remote POP3 mailbox by selecting the folder
+   pop://popserver/.
 
-           the date and time of the message is converted to the local time
-           zone, and ``fmt'' is expanded by the library function
-           ``strftime''; a leading bang disables locales
+   You can select an alternative port by specifying it with the server,
+   i.e.: pop://popserver:port/.
 
-   %(fmt)
+   You can also specify different username for each folder, i.e.:
+   pop://username@popserver[:port]/.
 
-           the local date and time when the message was received. ``fmt'' is
-           expanded by the library function ``strftime''; a leading bang
-           disables locales
+   Polling for new mail is more expensive over POP3 than locally. For
+   this reason the frequency at which Mutt-ng will check for mail
+   remotely can be controlled by the $$ppoopp__mmaaiill__cchheecckk variable, which
+   defaults to every 60 seconds.
 
-   %<fmt>
+   If Mutt-ng was compiled with SSL support (by running the _c_o_n_f_i_g_u_r_e
+   script with the _-_-_w_i_t_h_-_s_s_l flag), connections to POP3 servers can be
+   encrypted. This naturally requires that the server supports SSL
+   encrypted connections. To access a folder with POP3/SSL, you should
+   use pops: prefix, ie: pops://[username@]popserver[:port]/.
 
-           the current local time. ``fmt'' is expanded by the library
-           function ``strftime''; a leading bang disables locales.
+   Another way to access your POP3 mail is the _f_e_t_c_h_-_m_a_i_l function
+   (default: G). It allows to connect to ppoopp--hhoosstt ,fetch all your new
+   mail and place it in the local $$ssppoooollffiillee. After this point, Mutt-ng
+   runs exactly as if the mail had always been local.
 
-   %>X
+   _N_o_t_e_: If you only need to fetch all messages to local mailbox you
+   should consider using a specialized program, such as fetchmail(1).
 
-           right justify the rest of the string and pad with character "X"
+14. IMAP Support (OPTIONAL)
 
-   %|X
+   If Mutt-ng was compiled with IMAP support (by running the _c_o_n_f_i_g_u_r_e
+   script with the _-_-_e_n_a_b_l_e_-_i_m_a_p flag), it has the ability to work with
+   folders located on a remote IMAP server.
 
-           pad to the end of the line with character "X"
+   You can access the remote inbox by selecting the folder via its URL:
 
-   See also: ``$to_chars''.
+imap://imapserver/INBOX
 
-117. $ispell
+   where imapserver is the name of the IMAP server and INBOX is the
+   special name for your spool mailbox on the IMAP server. If you want to
+   access another mail folder at the IMAP server, you should use
 
-   Type: path
+imap://imapserver/path/to/folder
 
-   Default: "ispell"
+   where path/to/folder is the path of the folder you want to access. You
+   can select an alternative port by specifying it with the server, i.e.:
 
-   How to invoke ispell (GNU's spell-checking software).
+imap://imapserver:port/INBOX
 
-118. $keep_flagged
+   You can also specify different username for each folder by prenpending
+   your username and an @ symbol to the server's name.
 
-   Type: boolean
+   If Mutt-ng was compiled with SSL support (by running the _c_o_n_f_i_g_u_r_e
+   script with the _-_-_w_i_t_h_-_s_s_l flag), connections to IMAP servers can be
+   encrypted. This naturally requires that the server supports SSL
+   encrypted connections. To access a folder with IMAP/SSL, you only need
+   to substitute the initial imap:// by imaps:// in the above examples.
 
-   Default: no
+   Note that not all servers use / as the hierarchy separator. Mutt-ng
+   should correctly notice which separator is being used by the server
+   and convertpaths accordingly.
 
-   If set, read messages marked as flagged will not be moved from your spool
-   mailbox to your ``$mbox'' mailbox, or as a result of a ``mbox-hook''
-   command.
+   When browsing folders on an IMAP server, you can toggle whether to
+   look at only the folders you are subscribed to, or all folders with
+   the _t_o_g_g_l_e_-_s_u_b_s_c_r_i_b_e_d command. See also the $$iimmaapp__lliisstt__ssuubbssccrriibbeedd
+   variable.
 
-119. $list_reply
+   Polling for new mail on an IMAP server can cause noticeable delays.
+   So, you'll want to carefully tune the $$iimmaapp__mmaaiill__cchheecckk and $$ttiimmeeoouutt
+   variables.
 
-   Type: quadoption
+   Note that if you are using mbox as the mail store on UW servers prior
+   tov12.250, the server has been reported to disconnect a client if
+   another client selects the same folder.
 
-   Default: no
+14.1. The Folder Browser
 
-   When set, address replies to the mailing list the original message came
-   from (instead to the author only). Setting this option to ``ask-yes'' or
-   ``ask-no'' will ask if you really intended to reply to the author only.
+   As of version 1.2, mutt supports browsing mailboxes on an IMAP server.
+   This is mostly the same as the local file browser, with the following
+   differences:
+     * Instead of file permissions, mutt displays the string "IMAP",
+       possibly followed by the symbol "+", indicating that the entry
+       contains both messages and subfolders. On Cyrus-like servers
+       folders will often contain both messages and subfolders.
+     * For the case where an entry can contain both messages and
+       subfolders, the selection key (bound to enter by default) will
+       choose to descend into the subfolder view. If you wish to view the
+       messages in that folder, you must use view-file instead (bound to
+       space by default).
+     * You can create, delete and rename mailboxes with the
+       create-mailbox, delete-mailbox, and rename-mailbox commands
+       (default bindings: C , d and r, respectively). You may also
+       subscribe and unsubscribe to mailboxes (normally these are bound
+       to s and u, respectively).
+
+14.2. Authentication
 
-120. $locale
+   Mutt-ng supports four authentication methods with IMAP servers: SASL,
+   GSSAPI, CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add
+   NTLM authentication for you poor exchange users out there, but it has
+   yet to be integrated into the main tree). There is also support for
+   the pseudo-protocol ANONYMOUS, which allows you to log in to a public
+   IMAP server without having an account. To use ANONYMOUS, simply make
+   your username blank or "anonymous".
 
-   Type: string
+   SASL is a special super-authenticator, which selects among several
+   protocols (including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the
+   most secure method available on your host and the server. Using some
+   of these methods (including DIGEST-MD5 and possibly GSSAPI), your
+   entire session will be encrypted and invisible to those teeming
+   network snoops. It is the best option if you have it. To use it, you
+   must have the Cyrus SASL libraryinstalled on your system and compile
+   mutt with the _-_-_w_i_t_h_-_s_a_s_l flag.
+
+   Mutt-ng will try whichever methods are compiled in and available on
+   the server, in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5,
+   LOGIN.
 
-   Default: "C"
+   There are a few variables which control authentication:
+     * $$iimmaapp__uusseerr - controls the username under which you request
+       authentication on the IMAP server, for all authenticators. This is
+       overridden by an explicit username in the mailbox path (i.e. by
+       using a mailbox name of the form {user@host}).
+     * $$iimmaapp__ppaassss - a password which you may preset, used by all
+       authentication methods where a password is needed.
+     * $$iimmaapp__aauutthheennttiiccaattoorrss - a colon-delimited list of IMAP
+       authentication methods to try, in the order you wish to try them.
+       If specified, this overrides mutt's default (attempt everything,
+       in the order listed above).
 
-   The locale used by strftime(3) to format dates. Legal values are the
-   strings your system accepts for the locale variable LC_TIME.
+15. NNTP Support (OPTIONAL)
 
-121. $mail_check
+   If compiled with ``--enable-nntp'' option, Mutt-ng can read news from
+   a newsserver via NNTP. You can open a newsgroup with the
+   ``change-newsgroup'' function from the index/pager which is by default
+   bound to i.
 
-   Type: number
+   The Default newsserver can be obtained from the $NNTPSERVER
+   environment variable. Like other news readers, info about subscribed
+   newsgroups is saved in a file as specified by the $$nnnnttpp__nneewwssrrcc
+   variable. Article headers are cached and can be loaded from a file
+   when a newsgroup is entered instead loading from newsserver;
+   currently, this caching mechanism still is different from the header
+   caching for maildir/IMAP.
 
-   Default: 5
+15.1. Again: Scoring
 
-   This variable configures how often (in seconds) Mutt-ng should look for
-   new mail.
+   Especially for Usenet, people often ask for advanced filtering and
+   scoring functionality. Of course, mutt-ng has scoring and allows a
+   killfile, too. How to use a killfile has been discussed in MMeessssaaggee
+   SSccoorriinngg.
 
-   Note: This does not apply to IMAP mailboxes, see $imap_mail_check.
+   What has not been discusses in detail is mutt-ng's built-in realname
+   filter. For may newsreaders including those for ``advanced users''
+   like _s_l_r_n or _t_i_n, there are frequent request for such functionality.
+   The solutions offered often are complicated regular expressions.
 
-122. $mailcap_path
+   In mutt-ng this is as easy as
 
-   Type: string
+score ~* =42
 
-   Default: ""
+   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
 
-   This variable specifies which files to consult when attempting to display
-   MIME bodies not directly supported by Mutt-ng.
+score !~* =42
 
-123. $mailcap_sanitize
+   on the contrary applies a score of 42 to all messages _n_o_t matching
+   those criteria which are very strict:
 
-   Type: boolean
+     * Email addresses must be valid according to RRffCC  22882222
+     * the name must consist of at least 2 fields whereby a field must
+       not end in a dot. This means that ``Joe User'' and ``Joe A.User''
+       are valid while ``J. User'' and ``J. A. User'' aren't.
+     * it's assumed that users are interested in reading their own mail
+       and mail from people who they have defined an alias forso that
+       those 2 groups of messages are excluded from the strict rules.
 
-   Default: yes
+16. SMTP Support (OPTIONAL)
 
-   If set, Mutt-ng will restrict possible characters in mailcap % expandos to
-   a well-defined set of safe characters. This is the safe setting, but we
-   are not sure it doesn't break some more advanced MIME stuff.
+   Mutt-ng can be built using a library called ``libESMTP'' which
+   provides SMTP functionality. When configure was called with
+   --with-libesmtp or the output muttng -v contains +USE_LIBESMTP, this
+   will be or is the case already. The SMTP support includes support for
+   Delivery Status Notification (see ddssnn section) as well as handling the
+   8BITMIME flag controlled via $$uussee__88bbiittmmiimmee.
+
+   To enable sending mail directly via SMTP without an MTA such as
+   Postfix or SSMTP and the like, simply set the $$ssmmttpp__hhoosstt variable
+   pointing to your SMTP server.
+
+   Authentication mechanisms are available via the $$ssmmttpp__uusseerr and
+   $$ssmmttpp__ppaassss variables.
+
+   Transport Encryption via the StartTLS command is also available. For
+   this to work, first of all Mutt-ng must be built with SSL or GNUTLS.
+   Secondly, the $$ssmmttpp__uussee__ttllss variable must be either set to ``enabled''
+   or ``required.'' In both cases, StartTLS will be used if the server
+   supports it: for the second case, the connection will fail ifit
+   doesn't while switching back to unencrypted communication for the
+   first one.
+
+   Some mail providers require user's to set a particular envelope
+   sender, i.e. they allow for only one value which may not be what the
+   user wants to send as the From: header. In this case, the variable
+   $$ssmmttpp__eennvveellooppee may be used to set the envelope different from the
+   From: header.
 
-   DON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE DOING!
+17. Managing multiple IMAP/POP/NNTP accounts (OPTIONAL)
 
-124. $maildir_header_cache_verify
+   If you happen to have accounts on multiple IMAP and/or POP servers,
+   you may find managing all the authentication settings inconvenient and
+   error-prone. The aaccccoouunntt--hhooookk command may help. This hook works like
+   ffoollddeerr--hhooookk but is invoked whenever you access a remote mailbox
+   (including inside the folder browser), not just when you open the
+   mailbox.
 
-   Type: boolean
+   Some examples:
 
-   Default: yes
+account-hook . 'unset imap_user; unset imap_pass; unset tunnel'
+account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'
+account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
 
-   Availability: Header Cache
+18. Start a WWW Browser on URLs (EXTERNAL)
 
-   Check for Maildir unaware programs other than Mutt-ng having modified
-   maildir files when the header cache is in use. This incurs one stat(2) per
-   message every time the folder is opened.
+   If a message contains URLs (_u_n_i_f_i_e_d_ _r_e_s_o_u_r_c_e_ _l_o_c_a_t_o_r = address in the
+   WWW space like _h_t_t_p_:_/_/_w_w_w_._m_u_t_t_._o_r_g_/), it is efficient to get a menu
+   with all the URLs and start a WWW browser on one of them. This
+   functionality is provided by the external urlview program which can be
+   retrieved at <<ffttpp::////ffttpp..mmuutttt..oorrgg//mmuutttt//ccoonnttrriibb//>> and the configuration
+   commands:
+macro index \cb |urlview\n
+macro pager \cb |urlview\n
 
-125. $maildir_trash
+19. Compressed folders Support (OPTIONAL)
 
-   Type: boolean
+   If Mutt-ng was compiled with compressed folders support (by running
+   the _c_o_n_f_i_g_u_r_e script with the _-_-_e_n_a_b_l_e_-_c_o_m_p_r_e_s_s_e_d flag), Mutt can open
+   folders stored in an arbitrary format, provided that the user has a
+   script to convert from/to this format to one of the accepted.
 
-   Default: no
+   The most common use is to open compressed archived folders e.g. with
+   gzip.
 
-   If set, messages marked as deleted will be saved with the maildir
-   (T)rashed flag instead of physically deleted.
+   In addition, the user can provide a script that gets a folder in an
+   accepted format and appends its context to the folder in the
+   user-defined format, which may be faster than converting the entire
+   folder to the accepted format, appending to it and converting back to
+   the user-defined format.
 
-   NOTE: this only applies to maildir-style mailboxes. Setting it will have
-   no effect on other mailbox types.
+   There are three hooks defined (ooppeenn--hhooookk, cclloossee--hhooookk and aappppeenndd--hhooookk
+   )which define commands to uncompress and compress a folder and to
+   append messages to an existing compressed folder respectively.
 
-   It is similiar to the trash option.
+   For example:
 
-126. $mark_old
+open-hook \\.gz$ "gzip -cd %f > %t"
+close-hook \\.gz$ "gzip -c %t > %f"
+append-hook \\.gz$ "gzip -c %t >> %f"
 
-   Type: boolean
+   You do not have to specify all of the commands. If you omit
+   aappppeenndd--hhooookk ,the folder will be open and closed again each time you
+   will add to it. If you omit cclloossee--hhooookk (or give empty command) , the
+   folder will be open in the mode. If you specify aappppeenndd--hhooookk though
+   you'll be able to append to the folder.
 
-   Default: yes
+   Note that Mutt-ng will only try to use hooks if the file is not in one
+   of the accepted formats. In particular, if the file is empty, mutt
+   supposes it is not compressed. This is important because it allows the
+   use of programs that do not have well defined extensions. Just use "."
+   as a regexp. But this may be surprising if your compressing script
+   produces empty files. In this situation, unset $$ssaavvee__eemmppttyy ,so that
+   the compressed file will be removed if you delete all of the messages.
 
-   Controls whether or not Mutt-ng marks newunread messages as old if you
-   exit a mailbox without reading them.
+19.1. Open a compressed mailbox for reading
 
-   With this option set, the next time you start Mutt-ng, the messages will
-   show up with an "O" next to them in the ``index'' menu, indicating that
-   they are old.
+   Usage: ooppeenn--hhooookk_r_e_g_e_x_p "_c_o_m_m_a_n_d"
 
-127. $markers
+   The _c_o_m_m_a_n_d is the command that can be used for opening the folders
+   whose names match _r_e_g_e_x_p.
 
-   Type: boolean
+   The _c_o_m_m_a_n_d string is the printf-like format string, and it should
+   accept two parameters: %f, which is replaced with the (compressed)
+   folder name, and %t which is replaced with the name of the temporary
+   folder to which to write.
 
-   Default: yes
+   %f and %t can be repeated any number of times in the command string,
+   and all of the entries are replaced with the appropriate folder name.
+   In addition, %% is replaced by %, as in printf, and any other
+   %anything is left as is.
 
-   Controls the display of wrapped lines in the internal pager. If set, a
-   ``+'' marker is displayed at the beginning of wrapped lines. Also see the
-   ``$smart_wrap'' variable.
+   The _c_o_m_m_a_n_d should _n_o_t remove the original compressed file. The
+   _c_o_m_m_a_n_d should return non-zero exit status if it fails, so mutt knows
+   something's wrong.
 
-128. $mask
+   Example:
 
-   Type: regular expression
+open-hook \\.gz$ "gzip -cd %f > %t"
 
-   Default: "!^\.[^.]"
+   If the _c_o_m_m_a_n_d is empty, this operation is disabled for this file
+   type.
 
-   A regular expression used in the file browser, optionally preceded by the
-   not operator ``!''. Only files whose names match this mask will be shown.
-   The match is always case-sensitive.
+19.2. Write a compressed mailbox
 
-129. $max_display_recips
+   Usage: cclloossee--hhooookk_r_e_g_e_x_p"_c_o_m_m_a_n_d"
 
-   Type: number
+   This is used to close the folder that was open with the ooppeenn--hhooookk
+   command after some changes were made to it.
 
-   Default: 0
+   The _c_o_m_m_a_n_d string is the command that can be used for closing the
+   folders whose names match _r_e_g_e_x_p. It has the same format as in the
+   ooppeenn--hhooookk command. Temporary folder in this case is the folder
+   previously produced by the ooppeenn--hhooookk command.
 
-   When set non-zero, this specifies the maximum number of recipient header
-   lines (To:, Cc: and Bcc:) to display in the pager if header weeding is
-   turned on. In case the number of lines exeeds its value, the last line
-   will have 3 dots appended.
+   The _c_o_m_m_a_n_d should _n_o_t remove the decompressed file. The _c_o_m_m_a_n_d
+   should return non-zero exit status if it fails, so mutt knows
+   something's wrong.
 
-130. $max_line_length
+   Example:
 
-   Type: number
+close-hook \\.gz$ "gzip -c %t > %f"
 
-   Default: 0
+   If the _c_o_m_m_a_n_d is empty, this operation is disabled for this file
+   type, and the file can only be open in the readonly mode.
 
-   When set, the maximum line length for displaying ``format = flowed''
-   messages is limited to this length. A value of 0 (which is also the
-   default) means that the maximum line length is determined by the terminal
-   width and $wrapmargin.
+   cclloossee--hhooookk is not called when you exit from the folder if the folder
+   was not changed.
 
-131. $mbox
+19.3. Append a message to a compressed mailbox
 
-   Type: path
+   Usage: aappppeenndd--hhooookk_r_e_g_e_x_p"_c_o_m_m_a_n_d"
 
-   Default: "~/mbox"
+   This command is used for saving to an existing compressed folder. The
+   _c_o_m_m_a_n_d is the command that can be used for appending to the folders
+   whose names match _r_e_g_e_x_p. It has the same format as in the ooppeenn--hhooookk
+   command. The temporary folder in this case contains the messages that
+   are beingappended.
 
-   This specifies the folder into which read mail in your ``$spoolfile''
-   folder will be appended.
+   The _c_o_m_m_a_n_d should _n_o_t remove the decompressed file. The _c_o_m_m_a_n_d
+   should return non-zero exit status if it fails, so mutt knows
+   something's wrong.
 
-132. $mbox_type
+   Example:
 
-   Type: folder magic
+append-hook \\.gz$ "gzip -c %t >> %f"
 
-   Default: mbox
+   When aappppeenndd--hhooookk 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 ($$mmbbooxx__ttyyppee )type is always supposed (i.e. this is the
+   format used for the temporary folder).
 
-   The default mailbox type used when creating new folders. May be any of
-   mbox, MMDF, MH and Maildir.
+   If the file does not exist when you save to it, cclloossee--hhooookk is called,
+   and not aappppeenndd--hhooookk. aappppeenndd--hhooookk is only for appending to existing
+   folders.
 
-133. $menu_context
+   If the _c_o_m_m_a_n_d is empty, this operation is disabled for this file
+   type. In this case, the folder will be open and closed again (using
+   ooppeenn--hhooookk and cclloossee--hhooookk respectively) each time you will add to it.
 
-   Type: number
+19.4. Encrypted folders
 
-   Default: 0
+   The compressed folders support can also be used to handle encrypted
+   folders. If you want to encrypt a folder with PGP, you may want to
+   usethe following hooks:
 
-   This variable controls the number of lines of context that are given when
-   scrolling through menus. (Similar to ``$pager_context''.)
+open-hook  \\.pgp$ "pgp -f < %f > %t"
+close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
 
-134. $menu_move_off
+   Please note, that PGP does not support appending to an encrypted
+   folder, so there is no aappppeenndd--hhooookk defined.
 
-   Type: boolean
+   _N_o_t_e_: the folder is temporary stored decrypted in the /tmp directory,
+   where it can be read by your system administrator. So thinkabout the
+   security aspects of this.
 
-   Default: yes
+Chapter 5. Mutt-ng's MIME Support
 
-   When unset, the bottom entry of menus will never scroll up past the bottom
-   of the screen, unless there are less entries than lines. When set, the
-   bottom entry may move off the bottom.
+   _T_a_b_l_e_ _o_f_ _C_o_n_t_e_n_t_s
 
-135. $menu_scroll
+   11..  UUssiinngg  MMIIMMEE  iinn  MMuutttt
 
-   Type: boolean
+        11..11..  VViieewwiinngg  MMIIMMEE  mmeessssaaggeess  iinn  tthhee  ppaaggeerr
+        11..22..  TThhee  AAttttaacchhmmeenntt  MMeennuu
+        11..33..  TThhee  CCoommppoossee  MMeennuu
 
-   Default: no
+   22..  MMIIMMEE  TTyyppee  ccoonnffiigguurraattiioonn  wwiitthh  mmiimmee..ttyyppeess
+   33..  MMIIMMEE  VViieewweerr  ccoonnffiigguurraattiioonn  wwiitthh  mmaaiillccaapp
 
-   When set, menus will be scrolled up or down one line when you attempt to
-   move across a screen boundary. If unset, the screen is cleared and the
-   next or previous page of the menu is displayed (useful for slow links to
-   avoid many redraws).
+        33..11..  TThhee  BBaassiiccss  ooff  tthhee  mmaaiillccaapp  ffiillee
+        33..22..  SSeeccuurree  uussee  ooff  mmaaiillccaapp
+        33..33..  AAddvvaanncceedd  mmaaiillccaapp  UUssaaggee
+        33..44..  EExxaammppllee  mmaaiillccaapp  ffiilleess
 
-136. $message_format
+   44..  MMIIMMEE  AAuuttoovviieeww
+   55..  MMIIMMEE  MMuullttiippaarrtt//AAlltteerrnnaattiivvee
+   66..  AAttttaacchhmmeenntt  SSeeaarrcchhiinngg  aanndd  CCoouunnttiinngg
+   77..  MMIIMMEE  LLooookkuupp
 
-   Type: string
+   Quite a bit of effort has been made to make Mutt-ng the premier
+   text-mode MIME MUA. Every effort has been made to provide the
+   functionality that the discerning MIME user requires, and the
+   conformance to the standards wherever possible. When configuring
+   Mutt-ng for MIME, there are two extratypes of configuration files
+   which Mutt-ng uses. One is the mime.types file, which contains the
+   mapping of file extensions to IANA MIME types. The other is the
+   mailcap file, which specifies the external commands to use for
+   handling specific MIME types.
 
-   Default: "%s"
+1. Using MIME in Mutt
 
-   This is the string displayed in the ``attachment'' menu for attachments of
-   type message/rfc822. For a full listing of defined printf(3)-like
-   sequences see the section on ``$index_format''.
+   There are three areas/menus in Mutt-ng which deal with MIME, they are
+   the pager (while viewing a message), the attachment menu and the
+   compose menu.
 
-137. $meta_key
+1.1. Viewing MIME messages in the pager
 
-   Type: boolean
+   When you select a message from the index and view it in the pager,
+   Mutt decodes the message to a text representation. Mutt-ng internally
+   supports a number of MIME types, including text/plain, text/enriched,
+   message/rfc822, and message/news .In addition, the export controlled
+   version of Mutt-ng recognizes a variety of PGP MIME types, including
+   PGP/MIME and application/pgp.
 
-   Default: no
+   Mutt-ng will denote attachments with a couple lines describing them.
+   These lines are of the form:
+[-- Attachment #1: Description --]
+[-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
 
-   If set, forces Mutt-ng to interpret keystrokes with the high bit (bit 8)
-   set as if the user had pressed the ESC key and whatever key remains after
-   having the high bit removed. For example, if the key pressed has an ASCII
-   value of 0xf8, then this is treated as if the user had pressed ESC then
-   ``x''. This is because the result of removing the high bit from ``0xf8''
-   is ``0x78'', which is the ASCII character ``x''.
+   Where the Description is the description or filename given for the
+   attachment, and the Encoding is one of
+   7bit/8bit/quoted-printable/base64/binary.
 
-138. $metoo
+   If Mutt-ng cannot deal with a MIME type, it will display a message
+   like:
+[-- image/gif is unsupported (use 'v' to view this part) --]
 
-   Type: boolean
+1.2. The Attachment Menu
 
-   Default: no
+   The default binding for view-attachments is `v', which displays the
+   attachment menu for a message. The attachment menu displays a list
+   ofthe attachments in a message. From the attachment menu, you can
+   save, print, pipe, delete, and view attachments. You can apply these
+   operations to a group of attachments at once, by tagging the
+   attachments and by using the ``tag-prefix'' operator. You can also
+   reply to the current message from this menu, and only the current
+   attachment (or the attachments tagged) will be quoted in your reply.
+   You can view attachments as text, or view them using the mailcap
+   viewer definition.
 
-   If unset, Mutt-ng will remove your address (see the ``alternates''
-   command) from the list of recipients when replying to a message.
+   Finally, you can apply the usual message-related functions (like
+   <resend-message>, and the reply and forward functions) to attachments
+   of type message/rfc822.
 
-139. $mh_purge
+   See the help on the attachment menu for more information.
 
-   Type: boolean
+1.3. The Compose Menu
 
-   Default: no
+   The compose menu is the menu you see before you send a message. It
+   allows you to edit the recipient list, the subject, and other aspects
+   of your message. It also contains a list of the attachments of your
+   message, including the main body. From this menu, you can print, copy,
+   filter, pipe, edit, compose, review, and rename an attachment or a
+   list of tagged attachments. You can also modifying the attachment
+   information, notably the type, encoding and description.
 
-   When unset, Mutt-ng will mimic mh's behaviour and rename deleted messages
-   to ,<old file name> in mh folders instead of really deleting them. If the
-   variable is set, the message files will simply be deleted.
+   Attachments appear as follows:
+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>
 
-140. $mh_seq_flagged
+   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
+   content-type, and can be changed with the edit-type command (default:
+   ^T). The next field is the encoding for the attachment, which allows a
+   binary message to be encoded for transmission on 7bit links. It can be
+   changed with the edit-encoding command (default: ^E). The next field
+   is the size of the attachment, rounded to kilobytes or megabytes. The
+   next field is the filename, which can be changed with the rename-file
+   command (default: R). The final field is the description of the
+   attachment, and can be changed with the edit-description command
+   (default: d).
 
-   Type: string
+2.  MIME Type configuration with mime.types
 
-   Default: "flagged"
+   When you add an attachment to your mail message, Mutt-ng searches your
+   personal mime.types file within $HOME and then the system mime.types
+   file at /usr/local/share/mutt/mime.types or /etc/mime.types
+
+   The mime.types file consist of lines containing a MIME type and a
+   space separated list of extensions. For example:
+application/postscript          ps eps
+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.
+
+   If Mutt-ng can not determine the mime type by the extension of the
+   file you attach, it will look at the file. If the file is free of
+   binary information, Mutt-ng will assume that the file is plain text,
+   and mark it as text/plain. If the file contains binary information,
+   then Mutt-ng will mark it as application/octet-stream. You can change
+   the MIME type that Mutt-ng assigns to an attachment by using the
+   edit-type command from the compose menu (default: ^T). The MIME type
+   is actually a major mime type followed by the sub-type, separated by a
+   '/'. 6 major types: application, text, image, video, audio, and model
+   have been approved after various internet discussions. Mutt-ng
+   recognises all of these if the appropriate entry is found in the
+   mime.types file. It also recognises other major mime types, such as
+   the chemical type that is widely used in the molecular modelling
+   community to pass molecular data in various forms to various molecular
+   viewers. Non-recognised mime types should only be used if the
+   recipient of the message is likely to be expecting such attachments.
 
-   The name of the MH sequence used for flagged messages.
+3.  MIME Viewer configuration with mailcap
 
-141. $mh_seq_replied
+   Mutt-ng supports RRffCC  11552244 MIME Configuration, in particular the Unix
+   specific format specified in Appendix A of the RfC. This file format
+   is commonly referred to as the mailcap format. Many MIME compliant
+   programs utilize the mailcap format, allowing you to specify handling
+   for all MIME types in one place for all programs. Programs known to
+   use this format include Netscape, XMosaic, lynx and metamail.
 
-   Type: string
+   In order to handle various MIME types that Mutt-ng can not handle
+   internally, Mutt-ng parses a series of external configuration files to
+   find an external handler. The default search string for these files is
+   a colon delimited list set to
+${HOME}/.mailcap:/usr/local/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/e
+tc/mailcap:/usr/local/etc/mailcap
 
-   Default: "replied"
+   where $HOME is your home directory.
 
-   The name of the MH sequence used to tag replied messages.
+   In particular, the metamail distribution will install a mailcap file,
+   usually as /usr/local/etc/mailcap, which contains some baseline
+   entries.
 
-142. $mh_seq_unseen
+3.1. The Basics of the mailcap file
 
-   Type: string
+   A mailcap file consists of a series of lines which are comments,
+   blank, or definitions.
 
-   Default: "unseen"
+   A comment line consists of a # character followed by anything you
+   want.
 
-   The name of the MH sequence used for unseen messages.
+   A blank line is blank.
 
-143. $mime_forward
+   A definition line consists of a content type, a view command, and any
+   number of optional fields. Each field of a definition line is
+   dividedby a semicolon ';' character.
+
+   The content type is specified in the MIME standard type/subtype
+   method. For example, text/plain, text/html, image/gif, etc. In
+   addition, the mailcap format includes two formats for wildcards, one
+   using the special '*' subtype, the other is the implicit wild, where
+   you only include the major type. For example, image/* ,or video, will
+   match all image types and video types, respectively.
+
+   The view command is a Unix command for viewing the type specified.
+   There are two different types of commands supported. The default is to
+   send the body of the MIME message to the command on stdin. You can
+   change this behavior by using %s as a parameter to your view command.
+   This will cause Mutt-ng to save the body of the MIME message to a
+   temporary file, and then call the view command with the %s replaced by
+   the name of the temporary file. In both cases, Mutt-ng will turn over
+   the terminal to the view program until the program quits, at which
+   time Mutt will remove the temporary file if it exists.
 
-   Type: quadoption
+   So, in the simplest form, you can send a text/plain message to the
+   external pager more on stdin:
+text/plain; more
 
-   Default: no
+   Or, you could send the message as a file:
+text/plain; more %s
 
-   When set, the message you are forwarding will be attached as a separate
-   MIME part instead of included in the main body of the message.
+   Perhaps you would like to use lynx to interactively view a text/html
+   message:
+text/html; lynx %s
 
-   This is useful for forwarding MIME messages so the receiver can properly
-   view the message as it was delivered to you. If you like to switch between
-   MIME and not MIME from mail to mail, set this variable to ask-no or
-   ask-yes.
+   In this case, lynx does not support viewing a file from stdin, so you
+   must use the %s syntax. _N_o_t_e_:_S_o_m_e_ _o_l_d_e_r_ _v_e_r_s_i_o_n_s_ _o_f_ _l_y_n_x_ _c_o_n_t_a_i_n_ _a_ _b_u_g
+   _w_h_e_r_e_ _t_h_e_y_ _w_i_l_l_ _c_h_e_c_k_ _t_h_e_ _m_a_i_l_c_a_p_ _f_i_l_e_ _f_o_r_ _a_ _v_i_e_w_e_r_ _f_o_r_ _t_e_x_t_/_h_t_m_l_.
+   _T_h_e_y_ _w_i_l_l_ _f_i_n_d_ _t_h_e_ _l_i_n_e_ _w_h_i_c_h_ _c_a_l_l_s_ _l_y_n_x_,_ _a_n_d_ _r_u_n_ _i_t_._ _T_h_i_s_ _c_a_u_s_e_s_ _l_y_n_x
+   _t_o_ _c_o_n_t_i_n_u_o_u_s_l_y_ _s_p_a_w_n_ _i_t_s_e_l_f_ _t_o_ _v_i_e_w_ _t_h_e_ _o_b_j_e_c_t_.
 
-   Also see ``$forward_decode'' and ``$mime_forward_decode''.
+   On the other hand, maybe you don't want to use lynx interactively,
+   youjust want to have it convert the text/html to text/plain, then you
+   can use:
+text/html; lynx -dump %s | more
 
-144. $mime_forward_decode
+   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
 
-   Type: boolean
+   This is the simplest form of a mailcap file.
 
-   Default: no
+3.2. Secure use of mailcap
 
-   Controls the decoding of complex MIME messages into text/plain when
-   forwarding a message while ``$mime_forward'' is set. Otherwise
-   ``$forward_decode'' is used instead.
+   The interpretation of shell meta-characters embedded in MIME
+   parameters can lead to security problems in general. Mutt-ng tries to
+   quote parameters in expansion of %s syntaxes properly, and avoids
+   risky characters by substituting them, see the $$mmaaiillccaapp__ssaanniittiizzee
+   variable.
 
-145. $mime_forward_rest
+   Although mutt's procedures to invoke programs with mailcap seem to be
+   safe, there are other applications parsing mailcap, maybe taking less
+   care of it. Therefore you should pay attention to the following rules:
 
-   Type: quadoption
+   _K_e_e_p_ _t_h_e_ _%_-_e_x_p_a_n_d_o_s_ _a_w_a_y_ _f_r_o_m_ _s_h_e_l_l_ _q_u_o_t_i_n_g_. Don't quote them with
+   single or double quotes. Mutt-ng does this for you, the right way, as
+   should any other program which interprets mailcap. Don't put them into
+   backtick expansions. Be highly careful with eval statements, and avoid
+   them if possible at all. Trying to fix broken behaviour with quotes
+   introduces new leaks - there is no alternative to correct quoting in
+   the first place.
 
-   Default: yes
+   If you have to use the %-expandos' values in context where you need
+   quoting or backtick expansions, put that value into a shell variable
+   and reference the shell variable where necessary, as in the following
+   example (using $charset inside the backtick expansion is safe, since
+   it is not itself subject to any further expansion):
 
-   When forwarding multiple attachments of a MIME message from the recvattach
-   menu, attachments which cannot be decoded in a reasonable manner will be
-   attached to the newly composed message if this option is set.
+text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
+&& test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
 
-146. $mix_entry_format
+3.3. Advanced mailcap Usage
 
-   Type: string
+3.3.1. Optional Fields
 
-   Default: "%4n %c %-16s %a"
+   In addition to the required content-type and view command fields, you
+   can add semi-colon ';' separated fields to set flags and other
+   options. Mutt-ng recognizes the following optional fields:
 
-   Availability: Mixmaster
+   copiousoutput
+          This flag tells Mutt-ng that the command passes possibly large
+          amounts of text on stdout. This causes Mutt-ng to invoke a
+          pager (either the internal pager or the external pager defined
+          by the pager variable) on the output of the view command.
+          Without this flag, Mutt-ng assumes that the command is
+          interactive. One could use this to replace the pipe to more in
+          the lynx -dump example in the Basic section:
 
-   This variable describes the format of a remailer line on the mixmaster
-   chain selection screen. The following printf(3)-like sequences are
-   supported:
+text/html; lynx -dump %s ; copiousoutput
 
-   %n
+          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.
 
-           The running number on the menu.
+   needsterminal
+          Mutt-ng uses this flag when viewing attachments with aauuttoo__vviieeww,
+          in order to decide whether it should honor the setting of the
+          $$wwaaiitt__kkeeyy variable or not. When an attachment is viewed using
+          an interactive program, and the corresponding mailcap entry has
+          a _n_e_e_d_s_t_e_r_m_i_n_a_l flag, Mutt-ng will use $$wwaaiitt__kkeeyy and the exit
+          statusof the program to decide if it will ask you to press a
+          key after the external program has exited. In all other
+          situations it will not prompt you for a key.
 
-   %c
+   compose=<command>
+          This flag specifies the command to use to create a new
+          attachment of a specific MIME type. Mutt-ng supports this from
+          the compose menu.
 
-           Remailer capabilities.
+   composetyped=<command>
+          This flag specifies the command to use to create a new
+          attachment of a specific MIME type. This command differs from
+          the compose command in that mutt will expect standard MIME
+          headers on the data. This can be used to specify parameters,
+          filename, description, etc. for a new attachment. Mutt-ng
+          supports this from the compose menu.
 
-   %s
+   print=<command>
+          This flag specifies the command to use to print a specific MIME
+          type. Mutt-ng supports this from the attachment and compose
+          menus.
 
-           The remailer's short name.
+   edit=<command>
+          This flag specifies the command to use to edit a specific MIME
+          type. Mutt-ng supports this from the compose menu, and also
+          uses it to compose new attachments. Mutt-ng will default to the
+          defined editor for text attachments.
 
-   %a
+   nametemplate=<template>
+          This field specifies the format for the file denoted by %s in
+          the command fields. Certain programs will require a certain
+          file extension, for instance, to correctly view a file. For
+          instance, lynx will only interpret a file as text/html if the
+          file ends in .html. So, you would specify lynx as a text/html
+          viewer with a line in the mailcap file like:
 
-           The remailer's e-mail address.
+text/html; lynx %s; nametemplate=%s.html
 
-147. $mixmaster
+   test=<command>
+          This field specifies a command to run to test whether this
+          mailcap entry should be used. The command is defined with the
+          command expansion rules defined in the next section. If the
+          command returns 0, then the test passed, and Mutt-ng uses this
+          entry. If the command returns non-zero, then the test failed,
+          and Mutt-ng continues searching for the right entry. _N_o_t_e_:_t_h_e
+          _c_o_n_t_e_n_t_-_t_y_p_e_ _m_u_s_t_ _m_a_t_c_h_ _b_e_f_o_r_e_ _M_u_t_t_-_n_g_ _p_e_r_f_o_r_m_s_ _t_h_e_ _t_e_s_t_. For
+          example:
+
+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 display the text/html object. If RunningX doesn't
+          return 0, then Mutt-ng will go on to the next entry and use
+          lynx to display the text/html object.
+
+3.3.2. Search Order
+
+   When searching for an entry in the mailcap file, Mutt-ng will search
+   for the most useful entry for its purpose. For instance, if you are
+   attempting to print an image/gif, and you have the following entries
+   in your mailcap file, Mutt-ng will search for an entry with the print
+   command:
+image/*;        xv %s
+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.
+
+   In addition, you can use this with aauuttoo__vviieeww to denote two commands
+   for viewing an attachment, one to be viewed automatically, the other
+   to be viewed interactively from the attachment menu. In addition, you
+   can then use the test feature to determine which viewer to use
+   interactively depending on your environment.
+text/html;      netscape -remote 'openURL(%s)' ; test=RunningX
+text/html;      lynx %s; nametemplate=%s.html
+text/html;      lynx -dump %s; nametemplate=%s.html; copiousoutput
+
+   For aauuttoo__vviieeww, 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
+   returns non-zero, Mutt-ng will use the second entry for interactive
+   viewing.
 
-   Type: path
+3.3.3. Command Expansion
 
-   Default: "mixmaster"
+   The various commands defined in the mailcap files are passed to the
+   /bin/sh shell using the system() function. Before the command is
+   passed to /bin/sh -c, it is parsed to expand various special
+   parameters with information from Mutt-ng. The keywords Mutt-ng expands
+   are:
 
-   Availability: Mixmaster
+   %s
+          As seen in the basic mailcap section, this variable is expanded
+          to a filename specified by the calling program. This file
+          contains the body of the message to view/print/edit or where
+          the composing program should place the results of composition.
+          In addition, the use of this keyword causes Mutt-ng to not pass
+          the body of the message to the view/print/edit program on
+          stdin.
 
-   This variable contains the path to the Mixmaster binary on your system. It
-   is used with various sets of parameters to gather the list of known
-   remailers, and to finally send a message through the mixmaster chain.
+   %t
+          Mutt-ng will expand %t to the text representation of the
+          content type of the message in the same form as the first
+          parameter of the mailcap definition line, ie text/html or
+          image/gif.
 
-148. $move
+   %{<parameter>}
+          Mutt-ng will expand this to the value of the specified
+          parameter from the Content-Type: line of the mail message. For
+          instance, if Your mail message contains:
 
-   Type: quadoption
+Content-Type: text/plain; charset=iso-8859-1
 
-   Default: ask-no
+          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.
 
-   Controls whether or not Mutt-ng will move read messages from your spool
-   mailbox to your ``$mbox'' mailbox, or as a result of a ``mbox-hook''
-   command.
+   \%
+          This will be replaced by a %
 
-149. $msgid_format
+   Mutt-ng does not currently support the %F and %n keywords specified in
+   RRffCC  11552244. The main purpose of these parameters is for multipart
+   messages, which is handled internally by Mutt-ng.
 
-   Type: string
+3.4. Example mailcap files
 
-   Default: "%Y%m%d%h%M%s.G%P%p"
+   This mailcap file is fairly simple and standard:
+>
+# I'm always running X :)
+video/*;        xanim %s > /dev/null
+image/*;        xv %s > /dev/null
 
-   This is the format for the ``local part'' of the Message-ID: header field
-   generated by Mutt-ng. If this variable is empty, no Message-ID: headers
-   will be generated. The '%' character marks that certain data will be added
-   to the string, similar to printf(3). The following characters are allowed:
+# I'm always running netscape (if my computer had more memory, maybe)
+text/html;      netscape -remote 'openURL(%s)'
 
-   %d
+   This mailcap file shows quite a number of examples:
 
-           the current day of month
+# Use xanim to view all videos   Xanim produces a header on startup,
+# send that to /dev/null so I don't see it
+video/*;        xanim %s > /dev/null
 
-   %h
+# Send html to a running netscape by remote
+text/html;      netscape -remote 'openURL(%s)'; test=RunningNetscape
+# If I'm not running netscape but I am running X, start netscape on the
+# object
+text/html;      netscape %s; test=RunningX
 
-           the current hour
+# Else use lynx to view it as text
+text/html;      lynx %s
 
-   %m
+# This version would convert the text/html to text/plain
+text/html;      lynx -dump %s; copiousoutput
 
-           the current month
+# I use enscript to print text in two columns to a page
+text/*;         more %s; print=enscript -2Gr %s
 
-   %M
+# Netscape adds a flag to tell itself to view jpegs internally
+image/jpeg;xv %s; x-mozilla-flags=internal
 
-           the current minute
+# Use xv to view images if I'm running X
+# In addition, this uses the \ to extend the line and set my editor
+# for images
+image/*;xv %s; test=RunningX; edit=xpaint %s
 
-   %O
+# Convert images to text using the netpbm tools
+image/*;  (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | \
+pgmtopbm | pbmtoascii -1x2 ) 2>&1 ; copiousoutput
 
-           the current UNIX timestamp (octal)
+# Send excel spreadsheets to my NT box
+application/ms-excel; open.pl %s
 
-   %p
+4. MIME Autoview
 
-           the process ID
+   Usage: auto_view_m_i_m_e_-_t_y_p_e_ _[_m_i_m_e_-_t_y_p_e_ _._._._]
 
-   %P
+   Usage: unauto_view_m_i_m_e_-_t_y_p_e_ _[_m_i_m_e_-_t_y_p_e_ _._._._]
 
-           the current Message-ID prefix (a character rotating with every
-           Message-ID being generated)
+   In addition to explicitly telling Mutt-ng to view an attachment with
+   theMIME viewer defined in the mailcap file, Mutt-ng has support for
+   automatically viewing MIME attachments while in the pager.
 
-   %r
+   To work, you must define a viewer in the mailcap file which uses the
+   copiousoutput option to denote that it is non-interactive. Usually,
+   you also use the entry to convert the attachment to a text
+   representation which you can view in the pager.
 
-           a random integer value (decimal)
+   You then use the auto_view muttrc command to list the content-types
+   that you wish to view automatically.
 
-   %R
+   For instance, if you set auto_view to:
+auto_view text/html application/x-gunzip application/postscript
+image/gif application/x-tar-gz
 
-           a random integer value (hexadecimal)
+   Mutt-ng could use the following mailcap entries to automatically view
+   attachments of these types.
+text/html;      lynx -dump %s; copiousoutput; nametemplate=%s.html
+image/*;        anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | pgmtopb
+m | pbmtoascii ; copiousoutput
+application/x-gunzip;   gzcat; copiousoutput
+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 mmeessssaaggee--hhooookk to autoview messages
+   based on size, etc. ``unauto_view *'' will remove all previous
+   entries.
 
-   %s
+5. MIME Multipart/Alternative
 
-           the current second
+   Usage: alternative_order_m_i_m_e_-_t_y_p_e_ _[_m_i_m_e_-_t_y_p_e_ _._._._]
 
-   %T
+   Usage: unalternative_order_m_i_m_e_-_t_y_p_e_ _[_m_i_m_e_-_t_y_p_e_ _._._._]
 
-           the current UNIX timestamp (decimal)
+   Mutt-ng has some heuristics for determining which attachment of a
+   multipart/alternative type to display. First, mutt will check the
+   alternative_order list to determine if one of the available typesis
+   preferred. The alternative_order list consists of a number of MIME
+   types in order, including support for implicit and explicit wildcards,
+   for example:
+alternative_order text/enriched text/plain text
+application/postscript image/*
 
-   %X
+   Next, mutt will check if any of the types have a defined aauuttoo__vviieeww,
+   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.
 
-           the current UNIX timestamp (hexadecimal)
+   To remove a MIME type from the alternative_order list, use the
+   unalternative_order command.
 
-   %Y
+6. Attachment Searching and Counting
 
-           the current year (Y2K compliant)
+   If you ever lose track of attachments in your mailboxes, Mutt's
+   attachment-counting and -searching support might be for you. You can
+   make your message index display the number of qualifying attachments
+   in each message, or search for messages by attachment count. You also
+   can configure what kinds of attachments qualify for this feature with
+   the attachments and unattachments commands.
 
-   %%
+   The syntax is:
 
-           the '%' character
+   Usage: attachments_(_ _{_+_|_-_}_d_i_s_p_o_s_i_t_i_o_n_ _m_i_m_e_-_t_y_p_e_ _|_ _?_ _)
 
-   Note: Please only change this setting if you know what you are doing. Also
-   make sure to consult RFC2822 to produce technically valid strings.
+   Usage: unattachments_{_+_|_-_}_d_i_s_p_o_s_i_t_i_o_n_ _m_i_m_e_-_t_y_p_e
 
-150. $muttng_bindir
+   Disposition is the attachment's Content-disposition type -- either
+   "inline" or "attachment". You can abbreviate this to I or A.
 
-   Type: system property
+   Disposition is prefixed by either a + symbolor a - symbol. If it's a
+   +, you're saying that you want to allow this disposition and MIME type
+   to qualify. If it's a -, you're saying that this disposition and MIME
+   type is an exception to previous + rules. There are examples below of
+   how this is useful.
 
-   Value: /opt/freebsd4/mutt-ng/bin
+   Mime-type is, unsurprisingly, the MIME type of the attachment you want
+   to affect. A MIME type is always of the format "major/minor", where
+   "major" describes the broad category of document you're looking at,
+   and "minor" describes the specific type within that category. The
+   major part of mim-type must be literal text (or the special token
+   "*"), but the minor part may be a regular expression. (Therefore,
+   "*/.*" matches any MIME type.)
 
-   This is a read-only system property and specifies the directory containing
-   the muttng binary.
+   The MIME types you give to the attachments directive are a kind of
+   pattern. When you use the attachments directive, the patterns you
+   specify are added to a list. When you use unattachments, the pattern
+   is removed from the list. The patterns are not expanded and matched to
+   specific MIME types at this time -- they're just text in a list.
+   They're only matched when actually evaluating a message.
 
-151. $muttng_docdir
+   Some examples might help to illustrate. The examples that are not
+   commented out define the default configuration of the lists.
+## Removing a pattern from a list removes that pattern literally. It
+## does not remove any type matching the pattern.
+##
+## attachments +A */.*
+## attachments +A image/jpeg
+## unattachments +A */.*
+##
+## This leaves "attached" image/jpeg files on the allowed attachments
+## list. It does not remove all items, as you might expect, because the
+## second */.* is not a matching expression at this time.
+##
+## Remember: "unattachments" only undoes what "attachments" has done!
+## It does not trigger any matching on actual messages.
+
+
+## Qualify any MIME part with an "attachment" disposition, EXCEPT for
+## text/x-vcard and application/pgp parts. (PGP parts are already known
+## to mutt, and can be searched for with ~g, ~G, and ~k.)
+##
+## I've added x-pkcs7 to this, since it functions (for S/MIME)
+## analogously to PGP signature attachments. S/MIME isn't supported
+## in a stock mutt build, but we can still treat it specially here.
+##
+attachments +A */.*
+attachments -A text/x-vcard application/pgp.*
+attachments -A application/x-pkcs7-.*
+
+## Discount all MIME parts with an "inline" disposition, unless they're
+## text/plain. (Why inline a text/plain part unless it's external to the
+## message flow?)
+##
+attachments +I text/plain
+
+## These two lines make Mutt qualify MIME containers. (So, for example,
+## a message/rfc822 forward will count as an attachment.) The first
+## line is unnecessary if you already have "attach-allow */.*", of
+## course. These are off by default! The MIME elements contained
+## within a message/* or multipart/* are still examined, even if the
+## containers themseves don't qualify.
+##
+#attachments +A message/.* multipart/.*
+#attachments +I message/.* multipart/.*
+
+## You probably don't really care to know about deleted attachments.
+attachments -A message/external-body
+attachments -I message/external-body
+
+   "attachments ?" will list your current settings in Muttrc format, so
+   that it can be pasted elsewhere.
+
+   Please note that counting attachments may require lots of data be
+   loaded. This may cause noticeable slowdowns over network links
+   depending on the connection speed and message sizes. To fine-tune the
+   behavior on a per-folder or other basis, the $$ccoouunntt__aattttaacchhmmeennttss
+   variable may be used.
 
-   Type: system property
+7. MIME Lookup
 
-   Value: /opt/freebsd4/mutt-ng/doc/muttng
+   Usage: mime_lookup_m_i_m_e_-_t_y_p_e_ _[_m_i_m_e_-_t_y_p_e_ _._._._]
 
-   This is a read-only system property and specifies the directory containing
-   the muttng documentation.
+   Usage: unmime_lookup_m_i_m_e_-_t_y_p_e_ _[_m_i_m_e_-_t_y_p_e_ _._._._]
 
-152. $muttng_folder_name
+   Mutt-ng's mime_lookup list specifies a list of mime-types that should
+   not be treated according to their mailcap entry. This option is
+   designed todeal with binary types such as application/octet-stream.
+   When an attachment's mime-type is listed in mime_lookup, then the
+   extension of the filename will be compared to the list of extensions
+   in the mime.types file. The mime-type associated with this extension
+   will then be used to process the attachment according to the rules in
+   the mailcap file and according to any other configuration options
+   (such as auto_view) specified. Common usage would be:
+mime_lookup application/octet-stream application/X-Lotus-Manuscript
 
-   Type: system property
+   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.
 
-   Value:
+Chapter 6. Security Considerations
 
-   This is a read-only system property and, at runtime, specifies the last
-   part of the full path or URI of the folder currently open (if any), i.e.
-   everything after the last ``/''.
+   _T_a_b_l_e_ _o_f_ _C_o_n_t_e_n_t_s
 
-153. $muttng_folder_path
+   11..  PPaasssswwoorrddss
+   22..  TTeemmppoorraarryy  FFiilleess
+   33..  IInnffoorrmmaattiioonn  LLeeaakkss
 
-   Type: system property
+        33..11..  MMeessssaaggee--IIDD::  hheeaaddeerrss
+        33..22..  mmaaiillttoo::--ssttyyllee  lliinnkkss
 
-   Value:
+   44..  EExxtteerrnnaall  aapppplliiccaattiioonnss
 
-   This is a read-only system property and, at runtime, specifies the full
-   path or URI of the folder currently open (if any).
+        44..11..  mmaaiillccaapp
+        44..22..  OOtthheerr
 
-154. $muttng_hcache_backend
+   First of all, mutt-ng contains no security holes included by intention
+   but may contain unknown security holes. As a consequence, please run
+   mutt-ng only with as few permissions as possible.
 
-   Type: system property
+   Please do not run mutt-ng as the super user.
 
-   Value: qdbm
+   When configuring mutt-ng, there're some points to note about secure
+   setups.
 
-   This is a read-only system property and specifies the header chaching's
-   database backend.
+   In practice, mutt-ng can be easily made as vulnerable as even the most
+   insecure mail user agents (in their default configuration) just by
+   changing mutt-ng's configuration files: it then can execute arbitrary
+   programs and scripts attached to messages, send out private data on
+   its own, etc. Although this is not believed to the common type of
+   setup, please read this chapter carefully.
 
-155. $muttng_pwd
+1. Passwords
 
-   Type: system property
+   Although mutt-ng can be told the various passwords for accounts,
+   please never store passwords in configuration files. Besides the fact
+   that the system's operator can always read them, you could forget to
+   replace the actual password with asterisks when reporting a bug or
+   asking for help via, for example, a mailing list so that your mail
+   including your password could be archived by internet search engines,
+   etc. Please never store passwords on disk.
 
-   Value:
+2. Temporary Files
 
-   This is a read-only system property and, at runtime, specifies the current
-   working directory of the muttng binary.
+   Mutt-ng uses many temporary files for viewing messages, verifying
+   digital signatures, etc. The $$uummaasskk variable can be used to change the
+   default permissions of these files. Please only change it if you
+   really know what you are doing. Also, a different location for these
+   files may be desired which can be changed via the $$ttmmppddiirr variable.
 
-156. $muttng_revision
+3. Information Leaks
 
-   Type: system property
+3.1. Message-ID: headers
 
-   Value: 541
+   In the default configuration, mutt-ng will leak some information to
+   the outside world when sending messages: the generation of Message-ID:
+   headers includes a step counter which is increased (and rotated) with
+   every message sent. If you'd like to hide this information probably
+   telling others how many mail you sent in which time, you at least need
+   to remove the %P expando from the default setting of the $$mmssggiidd__ffoorrmmaatt
+   variable. Please make sure that you really know how local parts of
+   these Message-ID: headers are composed.
 
-   This is a read-only system property and specifies muttng's subversion
-   revision string.
+3.2. mailto:-style links
 
-157. $muttng_sysconfdir
+   As mutt-ng be can be set up to be the mail client to handle mailto:
+   style links in websites, there're security considerations, too. To
+   keep the old behavior by default, mutt-ng will be strict in
+   interpreting them which means that arbitrary header fields can be
+   embedded in these links which could override existing header fields or
+   attach arbitrary files. This may be problematic if the $$eeddiitt__hheeaaddeerrss
+   variable is _u_n_s_e_t, i.e. the user doesn't want to see header fields
+   while editing the message.
 
-   Type: system property
+   For example, following a link like
 
-   Value: /opt/freebsd4/mutt-ng/etc
+mailto:joe@host?Attach=~/.gnupg/secring.gpg
 
-   This is a read-only system property and specifies the directory containing
-   the muttng system-wide configuration.
+   will send out the user's private gnupg keyring to joe@host if the user
+   doesn't follow the information on screen carefully enough.
 
-158. $muttng_version
+   When _u_n_s_e_t_t_i_n_g the $$ssttrriicctt__mmaaiillttoo variable, mutt-ng will
 
-   Type: system property
+     * be less strict when interpreting these links by prepending a
+       X-Mailto- string to all header fields embedded in such a link _a_n_d
+     * turn on the $$eeddiitt__hheeaaddeerrss variable by force to let the user see
+       all the headers (because they still may leak information.)
 
-   Value: devel
+4. External applications
 
-   This is a read-only system property and specifies muttng's version string.
+   Mutt-ng in many places has to rely on external applications or for
+   convenience supports mechanisms involving external applications.
 
-159. $narrow_tree
+4.1. mailcap
 
-   Type: boolean
+   One of these is the mailcap mechanism as defined by RRffCC  11552244. Mutt-ng
+   can be set up to _a_u_t_o_m_a_t_i_c_a_l_l_y execute any given utility as listed in
+   one of the mailcap files (see the $$mmaaiillccaapp__ppaatthh variable for details.)
 
-   Default: no
+   These utilities may have a variety of security vulnerabilities,
+   including overwriting of arbitrary files, information leaks or other
+   exploitable bugs. These vulnerabilities may go unnoticed by the user,
+   especially when they are called automatically (and without interactive
+   prompting) from the mailcap file(s). When using mutt-ng's autoview
+   mechanism in combination with mailcap files, please be sure to...
 
-   This variable, when set, makes the thread tree narrower, allowing deeper
-   threads to fit on the screen.
+     * manually select trustworth applications with a reasonable calling
+       sequence
+     * periodically check the contents of mailcap files, especially after
+       software installations or upgrades
+     * keep the software packages referenced in the mailcap file up to
+       date
+     * leave the $$mmaaiillccaapp__ssaanniittiizzee variable in its default state to
+       restrict mailcap expandos to a safe set of characters
 
-160. $net_inc
+4.2. Other
 
-   Type: number
+   Besides the mailcap mechanism, mutt-ng uses a number of other external
+   utilities for operation.
 
-   Default: 10
+   The same security considerations apply for these as for tools involved
+   via mailcap (for example, mutt-ng is vulnerable to Denial of Service
+   Attacks with compressed folders support if the uncompressed mailbox is
+   too large for the disk it is saved to.)
 
-   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.
+   As already noted, most of these problems are not built in but caused
+   by wrong configuration, so please check your configuration.
 
-   See also ``$read_inc'' and ``$write_inc''.
+Chapter 7. Reference
 
-161. $nntp_ask_followup_to
+   _T_a_b_l_e_ _o_f_ _C_o_n_t_e_n_t_s
+
+   11..  CCoommmmaanndd  lliinnee  ooppttiioonnss
+   22..  PPaatttteerrnnss
+   33..  CCoonnffiigguurraattiioonn  CCoommmmaannddss
+   44..  CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   55..  FFuunnccttiioonnss
+
+        55..11..  ggeenneerriicc
+        55..22..  iinnddeexx
+        55..33..  ppaaggeerr
+        55..44..  aalliiaass
+        55..55..  qquueerryy
+        55..66..  aattttaacchh
+        55..77..  ccoommppoossee
+        55..88..  ppoossttppoonnee
+        55..99..  bbrroowwsseerr
+        55..1100..  ppggpp
+        55..1111..  eeddiittoorr
+        55..1122..  ssiiddeebbaarr
 
-   Type: boolean
+1. Command line options
 
-   Default: no
+   Running mutt with no arguments will make Mutt-ng attempt to read your
+   spool mailbox. However, it is possible to read other mailboxes and to
+   send messages from the command line as well.
 
-   Availability: NNTP
+   _T_a_b_l_e_ _7_._1_._ _R_e_f_e_r_e_n_c_e_:_ _C_o_m_m_a_n_d_ _L_i_n_e_ _O_p_t_i_o_n_s
+   Option Description
+   -A expand an alias
+   -a attach a file to a message
+   -b specify a blind carbon-copy (BCC) address
+   -c specify a carbon-copy (Cc) address
+   -e specify a config command to be run after initialization files are
+   read
+   -f specify a mailbox to load
+   -F specify an alternate file to read initialization commands
+   -h print help on command line options
+   -H specify a draft file from which to read a header and body
+   -i specify a file to include in a message composition
+   -m specify a default mailbox type
+   -n do not read the system Muttngrc
+   -p recall a postponed message
+   -Q query a configuration variable
+   -R open mailbox in read-only mode
+   -s specify a subject (enclose in quotes if it contains spaces)
+   -t dump the value of all variables to stdout
+   -T dump the value of all changed variables to stdout
+   -v show version number and compile-time definitions
+   -x simulate the mailx(1) compose mode
+   -y show a menu containing the files specified by the mailboxes command
+   -z exit immediately if there are no messages in the mailbox
+   -Z open the first folder with new message,exit immediately if none
 
-   If set, Mutt-ng will prompt you for the Followup-To: header field before
-   editing the body of an outgoing news article.
+   To read messages in a mailbox
 
-162. $nntp_ask_x_comment_to
+   mutt ] -nz ] ] -F _m_u_t_t_r_c ] ] -m _t_y_p_e ] ] -f _m_a_i_l_b_o_x ]
 
-   Type: boolean
+   To compose a new message
 
-   Default: no
+   mutt ] -n ] ] -F _m_u_t_t_r_c ] ] -a _f_i_l_e ] ] -c _a_d_d_r_e_s_s ] ] -i _f_i_l_e_n_a_m_e ] ]
+   -s _s_u_b_j_e_c_t ] _a_d_d_r_e_s_s ] _a_d_d_r_e_s_s ... ]
 
-   Availability: NNTP
+   Mutt-ng also supports a ``batch'' mode to send prepared messages.
+   Simply redirect input from the file you wish to send. For example,
 
-   If set, Mutt-ng will prompt you for the X-Comment-To: header field before
-   editing the body of an outgoing news article.
+   mutt -s "data set for run #2" professor@bigschool.edu < ~/run2.dat
 
-163. $nntp_cache_dir
+   This command will send a message to ``professor@bigschool.edu'' with a
+   subject of ``data set for run #2''. In the body of the message will be
+   the contents of the file ``~/run2.dat''.
 
-   Type: path
+2. Patterns
 
-   Default: "~/.muttng"
+   _T_a_b_l_e_ _7_._2_._ _R_e_f_e_r_e_n_c_e_:_ _P_a_t_t_e_r_n_s
+   Pattern Modifier Argument Description
+   ~A/=A all messages
+   ~b/=b EXPR messages which contain EXPR in the message body
+   ~B/=B EXPR messages which contain EXPR in the whole message
+   ~c/=c EXPR messages carbon-copied to EXPR
+   ~C/=C EXPR message is either to: or cc: EXPR
+   ~D/=D deleted messages
+   ~d/=d [MIN]-[MAX] messages with ``date-sent'' in a Date range
+   ~E/=E expired messages
+   ~e/=e EXPR message which contains EXPR in the ``Sender'' field
+   ~F/=F flagged messages
+   ~f/=f EXPR messages originating from EXPR
+   ~g/=g cryptographically signed messages
+   ~G/=G cryptographically encrypted messages
+   ~H/=H EXPR messages with a spam attribute matching EXPR
+   ~h/=h EXPR messages which contain EXPR in the message header
+   ~k/=k message contains PGP key material
+   ~i/=i EXPR message which match ID in the ``Message-ID'' field
+   ~L/=L EXPR message is either originated or received by EXPR
+   ~l/=l message is addressed to a known mailing list
+   ~m/=m [MIN]-[MAX] message in the range MIN to MAX *)
+   ~M/=M multipart messages
+   ~n/=n [MIN]-[MAX] messages with a score in the range MIN to MAX *)
+   ~N/=N new messages
+   ~O/=O old messages
+   ~p/=p message is addressed to you (consults alternates)
+   ~P/=P message is from you (consults alternates)
+   ~Q/=Q messages which have been replied to
+   ~R/=R read messages
+   ~r/=r [MIN]-[MAX] messages with ``date-received'' in a Date range
+   ~S/=S superseded messages
+   ~s/=s EXPR messages having EXPR in the ``Subject'' field.
+   ~T/=T tagged messages
+   ~t/=t EXPR messages addressed to EXPR
+   ~U/=U unread messages
+   ~u/=u message is addressed to a subscribed mailing list
+   ~v/=v message is part of a collapsed thread.
+   ~V/=V cryptographically verified messages
+   ~w/=w EXPR messages which contain EXPR in the `Newsgroups' field (if
+   compiled with NNTP support)
+   ~x/=x EXPR messages which contain EXPR in the `References' field
+   ~X/=X [MIN]-[MAX] messages with MIN to MAX attachments *)
+   ~y/=y EXPR messages which contain EXPR in the `X-Label' field
+   ~z/=z [MIN]-[MAX] messages with a size in the range MIN to MAX *)
+   ~=/== duplicated messages (see $duplicate_threads)
+   ~$/=$ unreferenced messages (requires threaded view)
+   ~*/=* ``From'' contains realname and (syntactically) valid address
+   (excluded are addresses matching against alternates or any alias)
+
+   Where EXPR are rreeggeexxpp. 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 (\\).
 
-   Availability: NNTP
+   *) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too.
 
-   This variable points to directory where Mutt-ng will cache news article
-   headers. If unset, headers will not be saved at all and will be reloaded
-   each time when you enter a newsgroup.
+3. Configuration Commands
 
-   As for the header caching in connection with IMAP and/or Maildir, this
-   drastically increases speed and lowers traffic.
+   The following are the commands understood by mutt.
 
-164. $nntp_catchup
+     * aaccccoouunntt--hhooookk _p_a_t_t_e_r_n _c_o_m_m_a_n_d
+     * aalliiaass_k_e_y_a_d_d_r_e_s_s [, _a_d_d_r_e_s_s, ... ]
+     * uunnaalliiaass [ * | _k_e_y ... ]
+     * aalltteerrnnaatteess_r_e_g_e_x_p [ _r_e_g_e_x_p ... ]
+     * uunnaalltteerrnnaatteess [ * | _r_e_g_e_x_p ... ]
+     * aalltteerrnnaattiivvee__oorrddeerr_m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ]
+     * uunnaalltteerrnnaattiivvee__oorrddeerr_m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ]
+     * aappppeenndd--hhooookk _r_e_g_e_x_p _c_o_m_m_a_n_d
+     * aauuttoo__vviieeww_m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ]
+     * uunnaauuttoo__vviieeww_m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ]
+     * bbiinndd _m_a_p _k_e_y _f_u_n_c_t_i_o_n
+     * cchhaarrsseett--hhooookk _a_l_i_a_s _c_h_a_r_s_e_t
+     * cclloossee--hhooookk _r_e_g_e_x_p _c_o_m_m_a_n_d
+     * ccoolloorr_o_b_j_e_c_t_f_o_r_e_g_r_o_u_n_d_b_a_c_k_g_r_o_u_n_d [ _r_e_g_e_x_p ]
+     * uunnccoolloorr_i_n_d_e_x_p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ]
+     * eexxeecc_f_u_n_c_t_i_o_n [ _f_u_n_c_t_i_o_n ... ]
+     * ffcccc--hhooookk _p_a_t_t_e_r_n _m_a_i_l_b_o_x
+     * ffcccc--ssaavvee--hhooookk _p_a_t_t_e_r_n _m_a_i_l_b_o_x
+     * ffoollddeerr--hhooookk _p_a_t_t_e_r_n _c_o_m_m_a_n_d
+     * hhddrr__oorrddeerr_h_e_a_d_e_r [ _h_e_a_d_e_r ... ]
+     * uunnhhddrr__oorrddeerr_h_e_a_d_e_r [ _h_e_a_d_e_r ... ]
+     * cchhaarrsseett--hhooookk _c_h_a_r_s_e_t _l_o_c_a_l_-_c_h_a_r_s_e_t
+     * iiggnnoorree_p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ]
+     * uunniiggnnoorree_p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ]
+     * lliissttss_r_e_g_e_x_p [ _r_e_g_e_x_p ... ]
+     * uunnlliissttss_r_e_g_e_x_p [ _r_e_g_e_x_p ... ]
+     * mmaaccrroo_m_e_n_u_k_e_y_s_e_q_u_e_n_c_e [ _d_e_s_c_r_i_p_t_i_o_n ]
+     * mmaaiillbbooxxeess_f_i_l_e_n_a_m_e [ _f_i_l_e_n_a_m_e ... ]
+     * mmbbooxx--hhooookk _p_a_t_t_e_r_n _m_a_i_l_b_o_x
+     * mmeessssaaggee--hhooookk _p_a_t_t_e_r_n _c_o_m_m_a_n_d
+     * mmiimmee__llooookkuupp_m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ]
+     * uunnmmiimmee__llooookkuupp_m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ]
+     * mmoonnoo_o_b_j_e_c_t_ _a_t_t_r_i_b_u_t_e [ _r_e_g_e_x_p ]
+     * uunnmmoonnoo_i_n_d_e_x_p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ]
+     * mmyy__hhddrr _s_t_r_i_n_g
+     * uunnmmyy__hhddrr_f_i_e_l_d [ _f_i_e_l_d ... ]
+     * ooppeenn--hhooookk _r_e_g_e_x_p _c_o_m_m_a_n_d
+     * ccrryypptt--hhooookk _p_a_t_t_e_r_n _k_e_y_-_i_d
+     * ppuusshh _s_t_r_i_n_g
+     * rreesseett_v_a_r_i_a_b_l_e [ _v_a_r_i_a_b_l_e ... ]
+     * ssaavvee--hhooookk _r_e_g_e_x_p _f_i_l_e_n_a_m_e
+     * ssccoorree _p_a_t_t_e_r_n _v_a_l_u_e
+     * uunnssccoorree_p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ]
+     * sseenndd--hhooookk _r_e_g_e_x_p _c_o_m_m_a_n_d
+     * rreeppllyy--hhooookk _r_e_g_e_x_p _c_o_m_m_a_n_d
+     * sseett [no|inv]_v_a_r_i_a_b_l_e[ =_v_a_l_u_e ] [ _v_a_r_i_a_b_l_e ... ]
+     * uunnsseett_v_a_r_i_a_b_l_e [ _v_a_r_i_a_b_l_e ... ]
+     * ssoouurrccee _f_i_l_e_n_a_m_e
+     * ssppaamm _p_a_t_t_e_r_n _f_o_r_m_a_t
+     * nnoossppaamm _p_a_t_t_e_r_n
+     * ssuubbssccrriibbee_r_e_g_e_x_p [ _r_e_g_e_x_p ... ]
+     * uunnssuubbssccrriibbee_r_e_g_e_x_p [ _r_e_g_e_x_p ... ]
+     * ttooggggllee_v_a_r_i_a_b_l_e [ _v_a_r_i_a_b_l_e ... ]
+     * uunnhhooookk _h_o_o_k_-_t_y_p_e
 
-   Type: quadoption
+4. Configuration variables
 
-   Default: ask-yes
+   The following list contains all variables which, in the process of
+   providing more consistency, have been renamed and are partially even
+   removed already. The left column contains the old synonym variables,
+   the right column the full/new name:
 
-   Availability: NNTP
+   _T_a_b_l_e_ _7_._3_._ _R_e_f_e_r_e_n_c_e_:_ _O_b_s_o_l_e_t_e_ _V_a_r_i_a_b_l_e_s
+   Old Name               New Name
+   edit_hdrs              $$eeddiitt__hheeaaddeerrss
+   forw_decode            $$ffoorrwwaarrdd__ddeeccooddee
+   forw_format            $$ffoorrwwaarrdd__ffoorrmmaatt
+   forw_quote             $$ffoorrwwaarrdd__qquuoottee
+   hdr_format             $$iinnddeexx__ffoorrmmaatt
+   indent_str             $$iinnddeenntt__ssttrriinngg
+   mime_fwd               $$mmiimmee__ffoorrwwaarrdd
+   msg_format             $$mmeessssaaggee__ffoorrmmaatt
+   pgp_autosign           $$ccrryypptt__aauuttoossiiggnn
+   pgp_autoencrypt        $$ccrryypptt__aauuttooeennccrryypptt
+   pgp_replyencrypt       $$ccrryypptt__rreeppllyyeennccrryypptt
+   pgp_replysign          $$ccrryypptt__rreeppllyyssiiggnn
+   pgp_replysignencrypted $$ccrryypptt__rreeppllyyssiiggnneennccrryypptteedd
+   pgp_verify_sig         $$ccrryypptt__vveerriiffyy__ssiigg
+   pgp_create_traditional $$ppggpp__aauuttooiinnlliinnee
+   pgp_auto_traditional   $$ppggpp__rreeppllyyiinnlliinnee
+   forw_decrypt           $$ffoorrwwaarrdd__ddeeccrryypptt
+   smime_sign_as          $$ssmmiimmee__ddeeffaauulltt__kkeeyy
+   post_indent_str        $$ppoosstt__iinnddeenntt__ssttrriinngg
+   print_cmd              $$pprriinntt__ccoommmmaanndd
+   shorten_hierarchy      $$ssiiddeebbaarr__sshhoorrtteenn__hhiieerraarrcchhyy
+   ask_followup_to        $$nnnnttpp__aasskk__ffoolllloowwuupp__ttoo
+   ask_x_comment_to       $$nnnnttpp__aasskk__xx__ccoommmmeenntt__ttoo
+   catchup_newsgroup      $$nnnnttpp__ccaattcchhuupp
+   followup_to_poster     $$nnnnttpp__ffoolllloowwuupp__ttoo__ppoosstteerr
+   group_index_format     $$nnnnttpp__ggrroouupp__iinnddeexx__ffoorrmmaatt
+   inews                  $$nnnnttpp__iinneewwss
+   mime_subject           $$nnnnttpp__mmiimmee__ssuubbjjeecctt
+   news_cache_dir         $$nnnnttpp__ccaacchhee__ddiirr
+   news_server            $$nnnnttpp__hhoosstt
+   newsrc                 $$nnnnttpp__nneewwssrrcc
+   nntp_poll              $$nnnnttpp__mmaaiill__cchheecckk
+   pop_checkinterval      $$ppoopp__mmaaiill__cchheecckk
+   post_moderated         $$nnnnttpp__ppoosstt__mmooddeerraatteedd
+   save_unsubscribed      $$nnnnttpp__ssaavvee__uunnssuubbssccrriibbeedd
+   show_new_news          $$nnnnttpp__sshhooww__nneeww__nneewwss
+   show_only_unread       $$nnnnttpp__sshhooww__oonnllyy__uunnrreeaadd
+   x_comment_to           $$nnnnttpp__xx__ccoommmmeenntt__ttoo
+   smtp_auth_username     $$ssmmttpp__uusseerr
+   smtp_auth_password     $$ssmmttpp__ppaassss
+   user_agent             $$aaggeenntt__ssttrriinngg
+
+   The contrib subdirectory contains a script named update-config.pl
+   which eases migration.
 
-   If this variable is set, Mutt-ng will mark all articles in a newsgroup as
-   read when you leaving it.
+   A complete list of current variables follows.
 
-165. $nntp_context
+1. $abort_noattach
 
-   Type: number
+   Type: quadoption
 
-   Default: 1000
+   Default: no
 
-   Availability: NNTP
+   This variable specifies whether to abort sending if no attachment was
+   made but the content references them, i.e. the content matches the
+   regular expression given in $$aattttaacchh__rreemmiinndd__rreeggeexxpp. If a match was
+   found and this variable is set to _y_e_s, message sending will be aborted
+   but the mail will be send nevertheless if set to _n_o.
 
-   This variable controls how many news articles to cache per newsgroup (if
-   caching is enabled, see $nntp_cache_dir) and how many news articles to
-   show in the ``index'' menu.
+   This variable and $$aattttaacchh__rreemmiinndd__rreeggeexxpp are intended to remind the
+   user to attach files if the message's text references them.
 
-   If there're more articles than defined with $nntp_context, all older ones
-   will be removed/not shown in the index.
+   See also the $$aattttaacchh__rreemmiinndd__rreeggeexxpp variable.
 
-166. $nntp_followup_to_poster
+2. $abort_nosubject
 
    Type: quadoption
 
    Default: ask-yes
 
-   Availability: NNTP
-
-   If this variable is set and the keyword "poster" is present in the
-   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.
-
-167. $nntp_group_index_format
-
-   Type: string
+   If set to _y_e_s, when composing messages and no subject is given at the
+   subject prompt, composition will be aborted. If set to _n_o, composing
+   messages with no subject given at the subject prompt will never be
+   aborted.
 
-   Default: "%4C %M%N %5s %-45.45f %d"
+3. $abort_unmodified
 
-   Availability: NNTP
+   Type: quadoption
 
-   This variable allows you to customize the newsgroup browser display to
-   your personal taste. This string is similar to ``index_format'', but has
-   its own set of printf(3)-like sequences:
+   Default: yes
 
- %C      current newsgroup number
- %d      description of newsgroup (retrieved from server)
- %f      newsgroup name
- %M      ``-'' if newsgroup not allowed for direct post (moderated for example)
- %N      ``N'' if newsgroup is new, ``u'' if unsubscribed, blank otherwise
- %n      number of new articles in newsgroup
- %s      number of unread articles in newsgroup
- %>X     right justify the rest of the string and pad with character "X"
- %|X     pad to the end of the line with character "X"
+   If set to _y_e_s, composition will automatically abort after editing the
+   message body if no changes are made to the file (this check only
+   happens after the _f_i_r_s_t edit of the file). When set to _n_o, composition
+   will never be aborted.
 
+4. $agent_string
 
-168. $nntp_host
+   Type: boolean
 
-   Type: string
+   Default: yes
 
-   Default: ""
+   When _s_e_t, Mutt-ng will add a ``User-Agent:'' header to outgoing
+   messages, indicating which version of Mutt-ng was used for composing
+   them.
 
-   Availability: NNTP
+5. $alias_file
 
-   This variable specifies the name (or address) of the NNTP server to be
-   used.
+   Type: path
 
-   It defaults to the value specified via the environment variable
-   $NNTPSERVER or contained in the file /etc/nntpserver.
+   Default: "~/.muttngrc"
 
-   You can also specify a username and an alternative port for each
-   newsserver, e.g.
+   The default file in which to save aliases created by the
+   ``ccrreeaattee--aalliiaass'' function.
 
-   [nntp[s]://][username[:password]@]newsserver[:port]
+   _N_o_t_e_: Mutt-ng will not automatically source this file; you must
+   explicitly use the ``ssoouurrccee'' command for it to be executed.
 
-   Note: Using a password as shown and stored in a configuration file
-   presents a security risk since the superuser of your machine may read it
-   regardless of the file's permissions.
+6. $alias_format
 
-169. $nntp_inews
+   Type: string
 
-   Type: path
+   Default: "%4n %2f %t %-10a %r"
 
-   Default: ""
+   Specifies the format of the data displayed for the ``alias'' menu. The
+   following printf(3)-style sequences are available:
 
-   Availability: NNTP
+   %a
+          alias name
 
-   If set, specifies the program and arguments used to deliver news posted by
-   Mutt-ng. Otherwise, Mutt-ng posts article using current connection. The
-   following printf(3)-style sequence is understood:
+   %f
+          flags - currently, a "d" for an alias marked for deletion
 
- %s      newsserver name
+   %n
+          index number
 
+   %r
+          address which alias expands to
 
-   Example: set inews="/usr/local/bin/inews -hS"
+   %t
+          character which indicates if the alias is tagged for inclusion
 
-170. $nntp_load_description
+7. $allow_8bit
 
    Type: boolean
 
    Default: yes
 
-   Availability: NNTP
+   Controls whether 8-bit data is converted to 7-bit using either
+   quoted-printable or base64 encoding when sending mail.
 
-   This variable controls whether or not descriptions for newsgroups are to
-   be loaded when subscribing to a newsgroup.
+8. $allow_ansi
 
-171. $nntp_mail_check
+   Type: boolean
 
-   Type: number
+   Default: no
 
-   Default: 60
+   Controls whether ANSI color codes in messages (and color tags in rich
+   text messages) are to be interpreted. Messages containing these codes
+   are rare, but if this option is set, their text will be colored
+   accordingly. Note that this may override your color choices, and even
+   present a security problem, since a message could include a line like
+   ``[-- PGP output follows ..." and give it the same color as your
+   attachment color.
 
-   Availability: NNTP
+9. $arrow_cursor
 
-   The time in seconds until any operations on a newsgroup except posting a
-   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.).
+   Type: boolean
 
-172. $nntp_mime_subject
+   Default: no
 
-   Type: boolean
+   When _s_e_t, an arrow (``->'') will be used to indicate the current entry
+   in menus instead of highlighting the whole line. On slow network or
+   modem links this will make response faster because there is less that
+   has to be redrawn on the screen when moving to the next or previous
+   entries in the menu.
 
-   Default: yes
+10. $ascii_chars
 
-   Availability: NNTP
+   Type: boolean
 
-   If unset, an 8-bit ``Subject:'' header field in a news article will not be
-   encoded according to RFC2047.
+   Default: no
 
-   Note: Only change this setting if you know what you are doing.
+   If _s_e_t, Mutt-ng will use plain ASCII characters when displaying thread
+   and attachment trees, instead of the default ACS characters.
 
-173. $nntp_newsrc
+11. $askbcc
 
-   Type: path
+   Type: boolean
 
-   Default: "~/.newsrc"
+   Default: no
 
-   Availability: NNTP
+   If _s_e_t, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients
+   before editing an outgoing message.
 
-   This file contains information about subscribed newsgroup and articles
-   read so far.
+12. $askcc
 
-   To ease the use of multiple news servers, the following printf(3)-style
-   sequence is understood:
+   Type: boolean
 
- %s      newsserver name
+   Default: no
 
+   If _s_e_t, Mutt-ng will prompt you for carbon-copy (Cc) recipients before
+   editing the body of an outgoing message.
 
-174. $nntp_pass
+13. $assumed_charset
 
    Type: string
 
-   Default: ""
+   Default: "us-ascii"
 
-   Availability: NNTP
+   This variable is a colon-separated list of character encoding schemes
+   for messages without character encoding indication. Header field
+   values and message body content without character encoding indication
+   would be assumed that they are written in one of this list. By
+   default, all the header fields and message body without any charset
+   indication are assumed to be in us-ascii.
 
-   Your password for NNTP account.
+   For example, Japanese users might prefer this:
 
-   Note: Storing passwords in a configuration file presents a security risk
-   since the superuser of your machine may read it regardless of the file's
-   permissions.
+   set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
 
-175. $nntp_post_moderated
+   However, only the first content is valid for the message body. This
+   variable is valid only if $$ssttrriicctt__mmiimmee is unset.
 
-   Type: quadoption
+14. $attach_format
 
-   Default: ask-yes
+   Type: string
 
-   Availability: NNTP
+   Default: "%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] "
 
-   If set to yes, Mutt-ng will post articles to newsgroup that have not
-   permissions to post (e.g. moderated).
+   This variable describes the format of the ``attachment'' menu. The
+   following printf(3)-style sequences are understood:
 
-   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.
+   %C
+          charset
 
-176. $nntp_reconnect
+   %c
+          requires charset conversion (n or c)
 
-   Type: quadoption
+   %D
+          deleted flag
 
-   Default: ask-yes
+   %d
+          description
 
-   Availability: NNTP
+   %e
+          MIME Content-Transfer-Encoding: header field
 
-   Controls whether or not Mutt-ng will try to reconnect to a newsserver when
-   the was connection lost.
+   %f
+          filename
 
-177. $nntp_save_unsubscribed
+   %I
+          MIME Content-Disposition: header field (I=inline, A=attachment)
 
-   Type: boolean
+   %m
+          major MIME type
 
-   Default: no
+   %M
+          MIME subtype
 
-   Availability: NNTP
+   %n
+          attachment number
 
-   When set, info about unsubscribed newsgroups will be saved into the
-   ``newsrc'' file and into the news cache.
+   %Q
+          "Q", if MIME part qualifies for attachment counting
 
-178. $nntp_show_new_news
+   %s
+          size
 
-   Type: boolean
+   %t
+          tagged flag
 
-   Default: yes
+   %T
+          graphic tree characters
 
-   Availability: NNTP
+   %u
+          unlink (=to delete) flag
 
-   If set, the newsserver will be asked for new newsgroups on entering the
-   browser. Otherwise, it will be done only once for a newsserver. Also
-   controls whether or not the number of new articles of subscribed
-   newsgroups will be checked.
+   %X
+          number of qualifying MIME parts in this part and its children
+
+   %>X
+          right justify the rest of the string and pad with character "X"
 
-179. $nntp_show_only_unread
+   %|X
+          pad to the end of the line with character "X"
 
-   Type: boolean
+15. $attach_remind_regexp
 
-   Default: no
+   Type: regular expression
 
-   Availability: NNTP
+   Default: "attach"
 
-   If set, only subscribed newsgroups that contain unread articles will be
-   displayed in the newsgroup browser.
+   If this variable is non-empty, muttng will scan a message's contents
+   before sending for this regular expression. If it is found, it will
+   ask for what to do depending on the setting of $$aabboorrtt__nnooaattttaacchh.
 
-180. $nntp_user
+   This variable and $$aabboorrtt__nnooaattttaacchh are intended to remind the user to
+   attach files if the message's text references them.
 
-   Type: string
+16. $attach_sep
 
-   Default: ""
+   Type: string
 
-   Availability: NNTP
+   Default: "\n"
 
-   Your login name on the NNTP server. If unset and the server requires
-   authentification, Mutt-ng will prompt you for your account name.
+   The separator to add between attachments when operating (saving,
+   printing, piping, etc) on a list of tagged attachments.
 
-181. $nntp_x_comment_to
+17. $attach_split
 
    Type: boolean
 
-   Default: no
-
-   Availability: NNTP
+   Default: yes
 
-   If set, Mutt-ng will add a ``X-Comment-To:'' header field (that contains
-   full name of the original article author) to articles that you followup
-   to.
+   If this variable is _u_n_s_e_t, when operating (saving, printing, piping,
+   etc) on a list of tagged attachments, Mutt-ng will concatenate the
+   attachments and will operate on them as a single attachment. The
+   ``$$aattttaacchh__sseepp'' separator is added after each attachment. When _s_e_t,
+   Mutt-ng will operate on the attachments one by one.
 
-182. $operating_system
+18. $attribution
 
    Type: string
 
-   Default: ""
-
-   This specifies the operating system name for the User-Agent: header field.
-   If this is unset, it will be set to the operating system name that
-   uname(2) returns. If uname(2) fails, ``UNIX'' will be used.
-
-   It may, for example, look as: ``mutt-ng 1.5.9i (Linux)''.
-
-183. $pager
-
-   Type: path
-
-   Default: "builtin"
+   Default: "On %d, %n wrote:"
 
-   This variable specifies which pager you would like to use to view
-   messages. ``builtin'' means to use the builtin pager, otherwise this
-   variable should specify the pathname of the external pager you would like
-   to use.
+   This is the string that will precede a message which has been included
+   in a reply. For a full listing of defined printf(3)-like sequences see
+   the section on ``$$iinnddeexx__ffoorrmmaatt''.
 
-   Using an external pager may have some disadvantages: Additional keystrokes
-   are necessary because you can't call Mutt-ng functions directly from the
-   pager, and screen resizes cause lines longer than the screen width to be
-   badly formatted in the help menu.
+19. $auto_tag
 
-184. $pager_context
+   Type: boolean
 
-   Type: number
+   Default: no
 
-   Default: 0
+   When _s_e_t, functions in the _i_n_d_e_x menu which affect a message will be
+   applied to all tagged messages (if there are any). When unset, you
+   must first use the ``tag-prefix'' function (default: ";") to make the
+   next function apply to all tagged messages.
 
-   This variable controls the number of lines of context that are given when
-   displaying the next or previous page in the internal pager. By default,
-   Mutt-ng will display the line after the last one on the screen at the top
-   of the next page (0 lines of context).
+20. $autoedit
 
-185. $pager_format
+   Type: boolean
 
-   Type: string
+   Default: no
 
-   Default: "-%Z- %C/%m: %-20.20n %s"
+   When _s_e_t along with ``$$eeddiitt__hheeaaddeerrss'', Mutt-ng will skip the initial
+   send-menu and allow you to immediately begin editing the body of your
+   message. The send-menu may still be accessed once you have finished
+   editing the body of your message.
 
-   This variable controls the format of the one-line message ``status''
-   displayed before each message in either the internal or an external pager.
-   The valid sequences are listed in the ``$index_format'' section.
+   Also see ``$$ffaasstt__rreeppllyy''.
 
-186. $pager_index_lines
+21. $beep
 
-   Type: number
+   Type: boolean
 
-   Default: 0
+   Default: yes
 
-   Determines the number of lines of a mini-index which is shown when in the
-   pager. The current message, unless near the top or bottom of the folder,
-   will be roughly one third of the way down this mini-index, giving the
-   reader the context of a few messages before and after the message. This is
-   useful, for example, to determine how many messages remain to be read in
-   the current thread. One of the lines is reserved for the status bar from
-   the index, so a pager_index_lines of 6 will only show 5 lines of the
-   actual index. A value of 0 results in no index being shown. If the 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.
+   When this variable is _s_e_t, Mutt-ng will beep when an error occurs.
 
-187. $pager_stop
+22. $beep_new
 
    Type: boolean
 
    Default: no
 
-   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.
+   When this variable is _s_e_t, Mutt-ng will beep whenever it prints a
+   message notifying you of new mail. This is independent of the setting
+   of the ``$$bbeeeepp'' variable.
 
-188. $pgp_auto_decode
+23. $bounce
 
-   Type: boolean
+   Type: quadoption
 
-   Default: no
+   Default: ask-yes
 
-   If set, Mutt-ng will automatically attempt to decrypt traditional PGP
-   messages whenever the user performs an operation which ordinarily would
-   result in the contents of the message being operated on. For example, if
-   the user displays a pgp-traditional message which has not been manually
-   checked with the check-traditional-pgp function, Mutt-ng will
-   automatically check the message for traditional pgp.
+   Controls whether you will be asked to confirm bouncing messages. If
+   set to _y_e_s you don't get asked if you want to bounce a message.
+   Setting this variable to _n_o is not generally useful, and thus not
+   recommended, because you are unable to bounce messages.
 
-189. $pgp_autoinline
+24. $bounce_delivered
 
    Type: boolean
 
-   Default: no
+   Default: yes
 
-   This option controls whether Mutt-ng generates old-style inline
-   (traditional) PGP encrypted or signed messages under certain
-   circumstances. This can be overridden by use of the pgp-menu, when inline
-   is not required.
+   When this variable is _s_e_t, Mutt-ng will include Delivered-To: header
+   fields when bouncing messages. Postfix users may wish to _u_n_s_e_t this
+   variable.
 
-   Note that Mutt-ng might automatically use PGP/MIME for messages which
-   consist of more than a single MIME part. Mutt-ng can be configured to ask
-   before sending PGP/MIME messages when inline (traditional) would not work.
-   See also: ``$pgp_mime_auto''.
+25. $braille_friendly
 
-   Also note that using the old-style PGP message format is
-   stronglydeprecated. (PGP only)
+   Type: boolean
 
-190. $pgp_check_exit
+   Default: no
 
-   Type: boolean
+   When this variable is set, mutt will place the cursor at the beginning
+   of the current line in menus, even when the arrow_cursor variable is
+   unset, making it easier for blind persons using Braille displays to
+   follow these menus. The option is disabled by default because many
+   visual terminals don't permit making the cursor invisible.
 
-   Default: yes
+26. $certificate_file
 
-   If set, Mutt-ng will check the exit code of the PGP subprocess when
-   signing or encrypting. A non-zero exit code means that the subprocess
-   failed. (PGP only)
+   Type: path
 
-191. $pgp_clearsign_command
+   Default: "~/.mutt_certificates"
 
-   Type: string
+   Availability: SSL or GNUTLS
 
-   Default: ""
+   This variable specifies the file where the certificates you trust are
+   saved. When an unknown certificate is encountered, you are asked if
+   you accept it or not. If you accept it, the certificate can also be
+   saved in this file and further connections are automatically accepted.
 
-   This format is used to create a old-style ``clearsigned'' PGP message.
+   You can also manually add CA certificates in this file. Any server
+   certificate that is signed with one of these CA certificates are also
+   automatically accepted.
 
-   Note that the use of this format is stronglydeprecated. (PGP only)
+   Example: set certificate_file=~/.muttng/certificates
 
-192. $pgp_decode_command
+27. $charset
 
    Type: string
 
    Default: ""
 
-   This format strings specifies a command which is used to decode
-   application/pgp attachments.
-
-   The PGP command formats have their own set of printf(3)-like sequences:
-
-   %p
-
-           Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
-           string otherwise. Note: This may be used with a %? construct.
+   Character set your terminal uses to display and enter textual data.
 
-   %f
+28. $check_new
 
-           Expands to the name of a file containing a message.
+   Type: boolean
 
-   %s
+   Default: yes
 
-           Expands to the name of a file containing the signature part of a
-           multipart/signed attachment when verifying it.
+   _N_o_t_e_: this option only affects _m_a_i_l_d_i_r and _M_H style mailboxes.
 
-   %a
+   When _s_e_t, Mutt-ng will check for new mail delivered while the mailbox
+   is open. Especially with MH mailboxes, this operation can take quite
+   some time since it involves scanning the directory and checking each
+   file to see if it has already been looked at. If it's _u_n_s_e_t, no check
+   for new mail is performed while the mailbox is open.
 
-           The value of $pgp_sign_as.
+29. $collapse_unread
 
-   %r
+   Type: boolean
 
-           One or more key IDs.
+   Default: yes
 
-   For examples on how to configure these formats for the various versions of
-   PGP which are floating around, see the pgp*.rc and gpg.rc files in the
-   samples/ subdirectory which has been installed on your system alongside
-   the documentation. (PGP only)
+   When _u_n_s_e_t, Mutt-ng will not collapse a thread if it contains any
+   unread messages.
 
-193. $pgp_decrypt_command
+30. $compose_format
 
    Type: string
 
-   Default: ""
+   Default: "-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-"
 
-   This command is used to decrypt a PGP encrypted message. (PGP only)
+   Controls the format of the status line displayed in the ``compose''
+   menu. This string is similar to ``$$ssttaattuuss__ffoorrmmaatt'', but has its own
+   set of printf(3)-like sequences:
 
-194. $pgp_encrypt_only_command
+   %a
+          total number of attachments
 
-   Type: string
+   %h
+          local hostname
 
-   Default: ""
+   %l
+          approximate size (in bytes) of the current message
+
+   %v
+          Mutt-ng version string
 
-   This command is used to encrypt a body part without signing it. (PGP only)
+   See the text describing the ``$$ssttaattuuss__ffoorrmmaatt'' option for more
+   information on how to set ``$$ccoommppoossee__ffoorrmmaatt''.
 
-195. $pgp_encrypt_sign_command
+31. $config_charset
 
    Type: string
 
    Default: ""
 
-   This command is used to both sign and encrypt a body part. (PGP only)
-
-196. $pgp_entry_format
-
-   Type: string
+   When defined, Mutt-ng will recode commands in rc files from this
+   encoding.
 
-   Default: "%4n %t%f %4l/0x%k %-4a %2c %u"
+32. $confirmappend
 
-   This variable allows you to customize the PGP key selection menu to your
-   personal taste. This string is similar to ``$index_format'', but has its
-   own set of printf(3)-like sequences:
+   Type: boolean
 
-   %n
+   Default: yes
 
-           number
+   When _s_e_t, Mutt-ng will prompt for confirmation when appending messages
+   to an existing mailbox.
 
-   %k
+33. $confirmcreate
 
-           key id
+   Type: boolean
 
-   %u
+   Default: yes
 
-           user id
+   When _s_e_t, Mutt-ng will prompt for confirmation when saving messages to
+   a mailbox which does not yet exist before creating it.
 
-   %a
+34. $connect_timeout
 
-           algorithm
+   Type: number
 
-   %l
+   Default: 30
 
-           key length
+   Causes Mutt-ng to timeout a network connection (for IMAP or POP) after
+   this many seconds if the connection is not able to be established. A
+   negative value causes Mutt-ng to wait indefinitely for the connection
+   to succeed.
 
-   %f
+35. $content_type
 
-           flags
+   Type: string
 
-   %c
+   Default: "text/plain"
 
-           capabilities
+   Sets the default Content-Type: header field for the body of newly
+   composed messages.
 
-   %t
+36. $copy
 
-           trust/validity of the key-uid association
+   Type: quadoption
 
-   %[<s>]
+   Default: yes
 
-           date of the key where <s> is an strftime(3) expression
+   This variable controls whether or not copies of your outgoing messages
+   will be saved for later references. Also see ``$$rreeccoorrdd'',
+   ``$$ssaavvee__nnaammee'', ``$$ffoorrccee__nnaammee'' and ``  ffcccc--hhooookk''.
 
-   (PGP only)
+37. $count_attachments
 
-197. $pgp_export_command
+   Type: boolean
 
-   Type: string
+   Default: yes
 
-   Default: ""
+   This variable controls whether attachments should be counted for
+   $index_format and its %X expando or not. As for scoring, this variable
+   can be used to selectively turn counting on or off instead of removing
+   and re-adding rules as prefered because counting requires full loading
+   of messages.
 
-   This command is used to export a public key from the user's key ring. (PGP
-   only)
+   If it is _s_e_t and rules were defined via the attachments and/or
+   unattachments commands, counting will be done. If it is _u_n_s_e_t no
+   counting will be done regardless whether rules were defined or not.
 
-198. $pgp_getkeys_command
+38. $crypt_autoencrypt
 
-   Type: string
+   Type: boolean
 
-   Default: ""
+   Default: no
 
-   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)
+   Setting this variable will cause Mutt-ng to always attempt to PGP
+   encrypt outgoing messages. This is probably only useful in connection
+   to the _s_e_n_d_-_h_o_o_k command. It can be overridden by use of the _p_g_p_-_m_e_n_u,
+   when encryption is not required or signing is requested as well. If
+   ``$$ssmmiimmee__iiss__ddeeffaauulltt'' is _s_e_t, then OpenSSL is used instead to create
+   S/MIME messages and settings can be overridden by use of the
+   _s_m_i_m_e_-_m_e_n_u. (Crypto only)
 
-199. $pgp_good_sign
+39. $crypt_autopgp
 
-   Type: regular expression
+   Type: boolean
 
-   Default: ""
+   Default: yes
 
-   If you assign a text to this variable, then a PGP signature is only
-   considered verified if the output from $pgp_verify_command contains the
-   text. Use this variable if the exit code from the command is 0 even for
-   bad signatures. (PGP only)
+   This variable controls whether or not Mutt-ng may automatically enable
+   PGP encryption/signing for messages. See also ``$$ccrryypptt__aauuttooeennccrryypptt'',
+   ``$$ccrryypptt__rreeppllyyeennccrryypptt'', ``$$ccrryypptt__aauuttoossiiggnn'', ``$$ccrryypptt__rreeppllyyssiiggnn'' and
+   ``$$ssmmiimmee__iiss__ddeeffaauulltt''.
 
-200. $pgp_ignore_subkeys
+40. $crypt_autosign
 
    Type: boolean
 
-   Default: yes
-
-   Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys.
-   Instead, the principal key will inherit the subkeys' capabilities. Unset
-   this if you want to play interesting key selection games. (PGP only)
+   Default: no
 
-201. $pgp_import_command
+   Setting this variable will cause Mutt-ng to always attempt to
+   cryptographically sign outgoing messages. This can be overridden by
+   use of the _p_g_p_-_m_e_n_u, when signing is not required or encryption is
+   requested as well. If ``$$ssmmiimmee__iiss__ddeeffaauulltt'' is _s_e_t, then OpenSSL is
+   used instead to create S/MIME messages and settings can be overridden
+   by use of the _s_m_i_m_e_-_m_e_n_u. (Crypto only)
 
-   Type: string
+41. $crypt_autosmime
 
-   Default: ""
+   Type: boolean
 
-   This command is used to import a key from a message into the user's public
-   key ring. (PGP only)
+   Default: yes
 
-202. $pgp_list_pubring_command
+   This variable controls whether or not Mutt-ng may automatically enable
+   S/MIME encryption/signing for messages. See also
+   ``$$ccrryypptt__aauuttooeennccrryypptt'', ``$$ccrryypptt__rreeppllyyeennccrryypptt'', ``$$ccrryypptt__aauuttoossiiggnn'',
+   ``$$ccrryypptt__rreeppllyyssiiggnn'' and ``$$ssmmiimmee__iiss__ddeeffaauulltt''.
 
-   Type: string
+42. $crypt_replyencrypt
 
-   Default: ""
+   Type: boolean
 
-   This command is used to list the public key ring's contents. The output
-   format must be analogous to the one used by gpg --list-keys --with-colons.
+   Default: yes
 
-   This format is also generated by the pgpring utility which comes with
-   Mutt-ng. (PGP only)
+   If _s_e_t, automatically PGP or OpenSSL encrypt replies to messages which
+   are encrypted. (Crypto only)
 
-203. $pgp_list_secring_command
+43. $crypt_replysign
 
-   Type: string
+   Type: boolean
 
-   Default: ""
+   Default: no
 
-   This command is used to list the secret key ring's contents. The output
-   format must be analogous to the one used by gpg --list-keys --with-colons.
+   If _s_e_t, automatically PGP or OpenSSL sign replies to messages which
+   are signed.
 
-   This format is also generated by the pgpring utility which comes with
-   Mutt-ng. (PGP only)
+   _N_o_t_e_: this does not work on messages that are encrypted _a_n_d signed!
+   (Crypto only)
 
-204. $pgp_long_ids
+44. $crypt_replysignencrypted
 
    Type: boolean
 
    Default: no
 
-   If set, use 64 bit PGP key IDs. Unset uses the normal 32 bit Key IDs. (PGP
-   only)
-
-205. $pgp_mime_auto
+   If _s_e_t, automatically PGP or OpenSSL sign replies to messages which
+   are encrypted. This makes sense in combination with
+   ``$$ccrryypptt__rreeppllyyeennccrryypptt'', because it allows you to sign all messages
+   which are automatically encrypted. This works around the problem noted
+   in ``$$ccrryypptt__rreeppllyyssiiggnn'', that Mutt-ng is not able to find out whether
+   an encrypted message is also signed. (Crypto only)
 
-   Type: quadoption
+45. $crypt_timestamp
 
-   Default: ask-yes
+   Type: boolean
 
-   This option controls whether Mutt-ng will prompt you for automatically
-   sending a (signed/encrypted) message using PGP/MIME when inline
-   (traditional) fails (for any reason).
+   Default: yes
 
-   Also note that using the old-style PGP message format is
-   stronglydeprecated. (PGP only)
+   If _s_e_t, Mutt-ng will include a time stamp in the lines surrounding PGP
+   or S/MIME output, so spoofing such lines is more difficult. If you are
+   using colors to mark these lines, and rely on these, you may _u_n_s_e_t
+   this setting. (Crypto only)
 
-206. $pgp_replyinline
+46. $crypt_use_gpgme
 
    Type: boolean
 
    Default: no
 
-   Setting this variable will cause Mutt-ng to always attempt to create an
-   inline (traditional) message when replying to a message which is PGP
-   encrypted/signed inline. This can be overridden by use of the pgp-menu,
-   when inline is not required. This option does not automatically detect if
-   the (replied-to) message is inline; instead it relies on Mutt-ng internals
-   for previously checked/flagged messages.
+   This variable controls the use the GPGME enabled crypto backends. If
+   it is _s_e_t and Mutt-ng was build with gpgme support, the gpgme code for
+   S/MIME and PGP will be used instead of the classic code.
 
-   Note that Mutt-ng might automatically use PGP/MIME for messages which
-   consist of more than a single MIME part. Mutt-ng can be configured to ask
-   before sending PGP/MIME messages when inline (traditional) would not work.
-   See also: ``$pgp_mime_auto''.
+   _N_o_t_e: You need to use this option in your .muttngrc configuration file
+   as it won't have any effect when used interactively.
 
-   Also note that using the old-style PGP message format is
-   stronglydeprecated. (PGP only)
+47. $crypt_verify_sig
 
-207. $pgp_retainable_sigs
+   Type: quadoption
 
-   Type: boolean
+   Default: yes
 
-   Default: no
+   If ``_y_e_s'', always attempt to verify PGP or S/MIME signatures. If
+   ``_a_s_k'', ask whether or not to verify the signature. If ``_n_o'', never
+   attempt to verify cryptographic signatures. (Crypto only)
 
-   If set, signed and encrypted messages will consist of nested
-   multipart/signed and multipart/encrypted body parts.
+48. $date_format
 
-   This is useful for applications like encrypted and signed mailing lists,
-   where the outer layer (multipart/encrypted) can be easily removed, while
-   the inner multipart/signed part is retained. (PGP only)
+   Type: string
 
-208. $pgp_show_unusable
+   Default: "!%a, %b %d, %Y at %I:%M:%S%p %Z"
 
-   Type: boolean
+   This variable controls the format of the date printed by the ``%d''
+   sequence in ``$$iinnddeexx__ffoorrmmaatt''. This is passed to strftime(3) to
+   process the date.
 
-   Default: yes
+   Unless the first character in the string is a bang (``!''), the month
+   and week day names are expanded according to the locale specified in
+   the variable ``$$llooccaallee''. If the first character in the string is a
+   bang, the bang is discarded, and the month and week day names in the
+   rest of the string are expanded in the _C locale (that is in US
+   English).
 
-   If set, Mutt-ng will display non-usable keys on the PGP key selection
-   menu. This includes keys which have been revoked, have expired, or have
-   been marked as ``disabled'' by the user. (PGP only)
+49. $debug_level
 
-209. $pgp_sign_as
+   Type: number
 
-   Type: string
+   Default: 1
 
-   Default: ""
+   Availability: debug
 
-   If you have more than one key pair, this option allows you to specify
-   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)
+   This variable specifies the current debug level and may be used to
+   increase or decrease the verbosity level during runtime. It overrides
+   the level given with the -d command line option.
+
+   Currently, this number must be >= 0 and <= 5 and muttng must be
+   started with -d to enable debugging at all; enabling at runtime is not
+   possible.
 
-210. $pgp_sign_command
+50. $default_hook
 
    Type: string
 
-   Default: ""
+   Default: "~f %s !~P | (~P ~C %s)"
 
-   This command is used to create the detached PGP signature for a
-   multipart/signed PGP/MIME body part. (PGP only)
+   This variable controls how send-hooks, message-hooks, save-hooks, and
+   fcc-hooks will be interpreted if they are specified with only a simple
+   regexp, instead of a matching pattern. The hooks are expanded when
+   they are declared, so a hook will be interpreted according to the
+   value of this variable at the time the hook is declared. The default
+   value matches if the message is either from a user matching the
+   regular expression given, or if it is from you (if the from address
+   matches ``alternates'') and is to or cc'ed to a user matching the
+   given regular expression.
 
-211. $pgp_sort_keys
+51. $delete
 
-   Type: sort order
+   Type: quadoption
 
-   Default: address
+   Default: ask-yes
 
-   Specifies how the entries in the ``pgp keys'' menu are sorted. The
-   following are legal values:
+   Controls whether or not messages are really deleted when closing or
+   synchronizing a mailbox. If set to _y_e_s, messages marked for deleting
+   will automatically be purged without prompting. If set to _n_o, messages
+   marked for deletion will be kept in the mailbox.
 
-   address
+52. $delete_space
 
-           sort alphabetically by user id
+   Type: boolean
 
-   keyid
+   Default: no
 
-           sort alphabetically by key id
+   When sending messages with format=flowed by _s_e_t_t_i_n_g the $$tteexxtt__fflloowweedd
+   variable, this variable specifies whether to also set the DelSp
+   parameter to yes. If this is _u_n_s_e_t, no additional parameter will be
+   send as a value of no already is the default behavior.
 
-   date
+   _N_o_t_e_: this variable only has an effect on _o_u_t_g_o_i_n_g messages (if
+   $$tteexxtt__fflloowweedd is _s_e_t) but not on incomming.
 
-           sort by key creation date
+53. $delete_untag
 
-   trust
+   Type: boolean
 
-           sort by the trust of the key
+   Default: yes
 
-   If you prefer reverse order of the above values, prefix it with
-   ``reverse-''. (PGP only)
+   If this option is _s_e_t, Mutt-ng will untag messages when marking them
+   for deletion. This applies when you either explicitly delete a
+   message, or when you save it to another folder.
 
-212. $pgp_strict_enc
+54. $digest_collapse
 
    Type: boolean
 
    Default: yes
 
-   If set, Mutt-ng will automatically encode PGP/MIME signed messages as
-   quoted-printable. Please note that unsetting this variable may lead to
-   problems with non-verifyable PGP signatures, so only change this if you
-   know what you are doing. (PGP only)
+   If this option is _s_e_t, Mutt-ng's received-attachments menu will not
+   show the subparts of individual messages in a multipart/digest. To see
+   these subparts, press 'v' on that menu.
 
-213. $pgp_timeout
+55. $display_filter
 
-   Type: number
+   Type: path
 
-   Default: 300
+   Default: ""
 
-   The number of seconds after which a cached passphrase will expire if not
-   used. Default: 300. (PGP only)
+   When _s_e_t, specifies a command used to filter messages. When a message
+   is viewed it is passed as standard input to $$ddiissppllaayy__ffiilltteerr, and the
+   filtered message is read from the standard output.
 
-214. $pgp_use_gpg_agent
+56. $dotlock_program
 
-   Type: boolean
+   Type: path
 
-   Default: no
+   Default: "$muttng_bindir/muttng_dotlock"
 
-   If set, Mutt-ng will use a possibly-running gpg-agent process. (PGP only)
+   Availability: Standalone and Dotlock
+
+   Contains the path of the muttng_dotlock(1) binary to be used by
+   Mutt-ng.
 
-215. $pgp_verify_command
+57. $dsn_notify
 
    Type: string
 
    Default: ""
 
-   This command is used to verify PGP signatures. (PGP only)
+   _N_o_t_e_: you should not enable this unless you are using Sendmail 8.8.x
+   or greater or in connection with the SMTP support via libESMTP.
+
+   This variable sets the request for when notification is returned. The
+   string consists of a comma separated list (no spaces!) of one or more
+   of the following: _n_e_v_e_r, to never request notification, _f_a_i_l_u_r_e, to
+   request notification on transmission failure, _d_e_l_a_y, to be notified of
+   message delays, _s_u_c_c_e_s_s, to be notified of successful transmission.
+
+   Example: set dsn_notify="failure,delay"
 
-216. $pgp_verify_key_command
+58. $dsn_return
 
    Type: string
 
    Default: ""
 
-   This command is used to verify key information from the key selection
-   menu. (PGP only)
-
-217. $pipe_decode
-
-   Type: boolean
+   _N_o_t_e_: you should not enable this unless you are using Sendmail 8.8.x
+   or greater or in connection with the SMTP support via libESMTP.
 
-   Default: no
+   This variable controls how much of your message is returned in DSN
+   messages. It may be set to either _h_d_r_s to return just the message
+   header, or _f_u_l_l to return the full message.
 
-   Used in connection with the pipe-message command. When unset, Mutt-ng will
-   pipe the messages without any preprocessing. When set, Mutt-ng will weed
-   headers and will attempt to PGP/MIME decode the messages first.
+   Example: set dsn_return=hdrs
 
-218. $pipe_sep
+59. $duplicate_threads
 
-   Type: string
+   Type: boolean
 
-   Default: "\n"
+   Default: yes
 
-   The separator to add between messages when piping a list of tagged
-   messages to an external Unix command.
+   This variable controls whether Mutt-ng, when sorting by threads,
+   threads messages with the same Message-ID: header field together. If
+   it is _s_e_t, it will indicate that it thinks they are duplicates of each
+   other with an equals sign in the thread diagram.
 
-219. $pipe_split
+60. $edit_headers
 
    Type: boolean
 
    Default: no
 
-   Used in connection with the pipe-message command and the ``tag- prefix''
-   or ``tag-prefix-cond'' operators. If this variable is unset, when piping a
-   list of tagged messages Mutt-ng will concatenate the messages and will
-   pipe them as a single folder. When set, Mutt-ng will pipe the messages one
-   by one. In both cases the messages are piped in the current sorted order,
-   and the ``$pipe_sep'' separator is added after each message.
+   This option allows you to edit the header of your outgoing messages
+   along with the body of your message.
 
-220. $pop_auth_try_all
+   Which empty header fields to show is controlled by the $$eeddiittoorr__hheeaaddeerrss
+   option.
 
-   Type: boolean
+61. $editor
 
-   Default: yes
+   Type: path
 
-   Availability: POP
+   Default: ""
 
-   If set, Mutt-ng will try all available methods. When unset, Mutt-ng will
-   only fall back to other authentication methods if the previous methods are
-   unavailable. If a method is available but authentication fails, Mutt-ng
-   will not connect to the POP server.
+   This variable specifies which editor is used by Mutt-ng. It defaults
+   to the value of the $VISUAL, or $EDITOR, environment variable, or to
+   the string "vi" if neither of those are set.
 
-221. $pop_authenticators
+62. $editor_headers
 
    Type: string
 
-   Default: ""
+   Default: "From: To: Cc: Bcc: Subject: Reply-To: Newsgroups:
+   Followup-To: X-Comment-To:"
 
-   Availability: POP
+   If $$eeddiitt__hheeaaddeerrss is _s_e_t, this space-separated list specifies which
+   _n_o_n_-_e_m_p_t_y header fields to edit in addition to user-defined headers.
 
-   This is a colon-delimited list of authentication methods Mutt-ng may
-   attempt to use to log in to an POP server, in the order Mutt-ng should try
-   them. Authentication methods are either ``user'', ``apop'' or any SASL
-   mechanism, eg ``digest-md5'', ``gssapi'' or ``cram-md5''.
+   Note: if $$eeddiitt__hheeaaddeerrss had to be turned on by force because
+   $$ssttrriicctt__mmaaiillttoo is _u_n_s_e_t, this option has no effect.
 
-   This parameter is case-insensitive. If this parameter is unset (the
-   default) Mutt-ng will try all available methods, in order from most-secure
-   to least-secure.
+63. $encode_from
 
-   Example: set pop_authenticators="digest-md5:apop:user"
+   Type: boolean
 
-222. $pop_delete
+   Default: no
 
-   Type: quadoption
+   When _s_e_t, Mutt-ng will quoted-printable encode messages when they
+   contain the string ``From '' (note the trailing space) in the
+   beginning of a line. Useful to avoid the tampering certain mail
+   delivery and transport agents tend to do with messages.
 
-   Default: ask-no
+   _N_o_t_e_: as Mutt-ng currently violates RfC3676 defining format=flowed,
+   it's <em/strongly/ advised to _s_e_t this option although discouraged by
+   the standard. Alternatively, you must take care of space-stuffing
+   <tt/From / lines (with a trailing space) yourself.
 
-   Availability: POP
+64. $entropy_file
 
-   If set, Mutt-ng will delete successfully downloaded messages from the POP
-   server when using the ``fetch-mail'' function. When unset, Mutt-ng will
-   download messages but also leave them on the POP server.
+   Type: path
 
-223. $pop_host
+   Default: ""
 
-   Type: string
+   Availability: SSL
 
-   Default: ""
+   The file which includes random data that is used to initialize SSL
+   library functions.
 
-   Availability: POP
+65. $envelope_from_address
 
-   The name of your POP server for the ``fetch-mail'' function. You can also
-   specify an alternative port, username and password, i.e.:
+   Type: e-mail address
 
-   [pop[s]://][username[:password]@]popserver[:port]
+   Default: ""
 
-   Note: Storing passwords in a configuration file presents a security risk
-   since the superuser of your machine may read it regardless of the file's
-   permissions.
+   Manually sets the _e_n_v_e_l_o_p_e sender for outgoing messages. This value is
+   ignored if ``$$uussee__eennvveellooppee__ffrroomm'' is unset.
 
-224. $pop_last
+66. $escape
 
-   Type: boolean
+   Type: string
 
-   Default: no
+   Default: "~"
 
-   Availability: POP
+   Escape character to use for functions in the builtin editor.
 
-   If this variable is set, Mutt-ng will try to use the ``LAST'' POP command
-   for retrieving only unread messages from the POP server when using the
-   ``fetch-mail'' function.
+67. $fast_reply
 
-225. $pop_mail_check
+   Type: boolean
 
-   Type: number
+   Default: no
 
-   Default: 60
+   When _s_e_t, the initial prompt for recipients and subject are skipped
+   when replying to messages, and the initial prompt for subject is
+   skipped when forwarding messages.
 
-   Availability: POP
+   _N_o_t_e_: this variable has no effect when the ``$$aauuttooeeddiitt'' variable is
+   _s_e_t.
 
-   This variable configures how often (in seconds) Mutt-ng should look for
-   new mail.
+68. $fcc_attach
 
-226. $pop_pass
+   Type: boolean
 
-   Type: string
+   Default: yes
 
-   Default: ""
+   This variable controls whether or not attachments on outgoing messages
+   are saved along with the main body of your message.
 
-   Availability: POP
+69. $fcc_clear
 
-   Specifies the password for your POP account. If unset, Mutt-ng will prompt
-   you for your password when you open POP mailbox.
+   Type: boolean
 
-   Note: Storing passwords in a configuration file presents a security risk
-   since the superuser of your machine may read it regardless of the file's
-   permissions.
+   Default: no
 
-227. $pop_reconnect
+   When this variable is _s_e_t, FCCs will be stored unencrypted and
+   unsigned, even when the actual message is encrypted and/or signed.
+   (PGP only)
 
-   Type: quadoption
+70. $file_charset
 
-   Default: ask-yes
+   Type: string
 
-   Availability: POP
+   Default: ""
 
-   Controls whether or not Mutt-ng will try to reconnect to a POP server if
-   the connection is lost.
+   This variable is a colon-separated list of character encoding schemes
+   for text file attatchments. If _u_n_s_e_t, $$cchhaarrsseett value will be used
+   instead. For example, the following configuration would work for
+   Japanese text handling:
 
-228. $pop_user
+   set file_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
 
-   Type: string
+   Note: ``iso-2022-*'' must be put at the head of the value as shown
+   above if included.
 
-   Default: ""
+71. $folder
 
-   Availability: POP
+   Type: path
 
-   Your login name on the POP server.
+   Default: "~/Mail"
 
-   This variable defaults to your user name on the local machine.
+   Specifies the default location of your mailboxes. A ``+'' or ``='' at
+   the beginning of a pathname will be expanded to the value of this
+   variable. Note that if you change this variable from the default value
+   you need to make sure that the assignment occurs _b_e_f_o_r_e you use ``+''
+   or ``='' for any other variables since expansion takes place during
+   the ``set'' command.
 
-229. $post_indent_string
+72. $folder_format
 
    Type: string
 
-   Default: ""
-
-   Similar to the ``$attribution'' variable, Mutt-ng will append this string
-   after the inclusion of a message which is being replied to.
+   Default: "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"
 
-230. $postpone
+   This variable allows you to customize the file browser display to your
+   personal taste. This string is similar to ``$$iinnddeexx__ffoorrmmaatt'', but has
+   its own set of printf(3)-like sequences:
 
-   Type: quadoption
+   %C
+          current file number
 
-   Default: ask-yes
+   %d
+          date/time folder was last modified
 
-   Controls whether or not messages are saved in the ``$postponed'' mailbox
-   when you elect not to send immediately.
+   %f
+          filename
 
-231. $postponed
+   %F
+          file permissions
 
-   Type: path
+   %g
+          group name (or numeric gid, if missing)
 
-   Default: "~/postponed"
+   %l
+          number of hard links
 
-   Mutt-ng allows you to indefinitely ``postpone sending a message'' which
-   you are editing. When you choose to postpone a message, Mutt-ng saves it
-   in the mailbox specified by this variable. Also see the ``$postpone''
-   variable.
+   %N
+          N if folder has new mail, blank otherwise
 
-232. $preconnect
+   %s
+          size in bytes
 
-   Type: string
+   %t
+          * if the file is tagged, blank otherwise
 
-   Default: ""
+   %u
+          owner name (or numeric uid, if missing)
 
-   If set, a shell command to be executed if Mutt-ng fails to establish a
-   connection to the server. This is useful for setting up secure
-   connections, e.g. with ssh(1). If the command returns a nonzero status,
-   Mutt-ng gives up opening the server. Example:
+   %>X
+          right justify the rest of the string and pad with character "X"
 
-   preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net sleep 20 <
-   /dev/null > /dev/null"
+   %|X
+          pad to the end of the line with character "X"
 
-   Mailbox ``foo'' on mailhost.net can now be reached as
-   ``{localhost:1234}foo''.
+73. $followup_to
 
-   Note: For this example to work, you must be able to log in to the remote
-   machine without having to enter a password.
+   Type: boolean
 
-233. $print
+   Default: yes
 
-   Type: quadoption
+   Controls whether or not the Mail-Followup-To: header field is
+   generated when sending mail. When _s_e_t, Mutt-ng will generate this
+   field when you are replying to a known mailing list, specified with
+   the ``subscribe'' or ``lliissttss'' commands or detected by common mailing
+   list headers.
 
-   Default: ask-no
+   This field has two purposes. First, preventing you from receiving
+   duplicate copies of replies to messages which you send to mailing
+   lists. Second, ensuring that you do get a reply separately for any
+   messages sent to known lists to which you are not subscribed. The
+   header will contain only the list's address for subscribed lists, and
+   both the list address and your own email address for unsubscribed
+   lists. Without this header, a group reply to your message sent to a
+   subscribed list will be sent to both the list and your address,
+   resulting in two copies of the same email for you.
 
-   Controls whether or not Mutt-ng really prints messages. This is set to
-   ask-no by default, because some people accidentally hit ``p'' often.
+74. $force_buffy_check
 
-234. $print_command
+   Type: boolean
 
-   Type: path
+   Default: no
 
-   Default: "lpr"
+   When _s_e_t, it causes Mutt-ng to check for new mail when the _b_u_f_f_y_-_l_i_s_t
+   command is invoked. When _u_n_s_e_t, _b_u_f_f_y___l_i_s_t will just list all
+   mailboxes which are already known to have new mail.
 
-   This specifies the command pipe that should be used to print messages.
+   Also see the following variables: ``$$ttiimmeeoouutt'', ``$$mmaaiill__cchheecckk'' and
+   ``$$iimmaapp__mmaaiill__cchheecckk''.
 
-235. $print_decode
+75. $force_list_reply
 
-   Type: boolean
+   Type: quadoption
 
-   Default: yes
+   Default: ask-no
 
-   Used in connection with the print-message command. If this option is set,
-   the message is decoded before it is passed to the external command
-   specified by $print_command. If this option is unset, no processing will
-   be applied to the message when printing it. The latter setting may be
-   useful if you are using some advanced printer filter which is able to
-   properly format e-mail messages for printing.
+   This variable controls what effect ordinary replies have on mailing
+   list messages: if _s_e_t, a normal reply will be interpreted as
+   list-reply while if it's _u_n_s_e_t the reply functions work as usual.
 
-236. $print_split
+76. $force_name
 
    Type: boolean
 
    Default: no
 
-   Used in connection with the print-message command. If this option is set,
-   the command specified by $print_command is executed once for each message
-   which is to be printed. If this option is unset, the command specified by
-   $print_command is executed only once, and all the messages are
-   concatenated, with a form feed as the message separator.
+   This variable is similar to ``$$ssaavvee__nnaammee'', except that Mutt-ng will
+   store a copy of your outgoing message by the username of the address
+   you are sending to even if that mailbox does not exist.
 
-   Those who use the enscript(1) program's mail-printing mode will most
-   likely want to set this option.
+   Also see the ``$$rreeccoorrdd'' variable.
 
-237. $prompt_after
+77. $forward_decode
 
    Type: boolean
 
    Default: yes
 
-   If you use an external ``$pager'', setting this variable will cause
-   Mutt-ng to prompt you for a command when the pager exits rather than
-   returning to the index menu. If unset, Mutt-ng will return to the index
-   menu when the external pager exits.
+   Controls the decoding of complex MIME messages into text/plain when
+   forwarding a message. The message header is also RFC2047 decoded. This
+   variable is only used, if ``$$mmiimmee__ffoorrwwaarrdd'' is _u_n_s_e_t, otherwise
+   ``$$mmiimmee__ffoorrwwaarrdd__ddeeccooddee'' is used instead.
 
-238. $query_command
+78. $forward_decrypt
 
-   Type: path
+   Type: boolean
 
-   Default: ""
+   Default: yes
 
-   This specifies the command that Mutt-ng will use to make external address
-   queries. The string should contain a %s, which will be substituted with
-   the query string the user types. See ``query'' for more information.
+   Controls the handling of encrypted messages when forwarding a message.
+   When _s_e_t, the outer layer of encryption is stripped off. This variable
+   is only used if ``$$mmiimmee__ffoorrwwaarrdd'' is _s_e_t and ``$$mmiimmee__ffoorrwwaarrdd__ddeeccooddee''
+   is _u_n_s_e_t. (PGP only)
 
-239. $quit
+79. $forward_edit
 
    Type: quadoption
 
    Default: yes
 
-   This variable controls whether ``quit'' and ``exit'' actually quit from
-   Mutt-ng. If it set to yes, they do quit, if it is set to no, they have no
-   effect, and if it is set to ask-yes or ask-no, you are prompted for
-   confirmation when you try to quit.
+   This quadoption controls whether or not the user is automatically
+   placed in the editor when forwarding messages. For those who always
+   want to forward with no modification, use a setting of _n_o.
 
-240. $quote_empty
+80. $forward_format
 
-   Type: boolean
+   Type: string
 
-   Default: yes
+   Default: "[%a: %s]"
 
-   Controls whether or not empty lines will be quoted using
-   ``indent_string''.
+   This variable controls the default subject when forwarding a message.
+   It uses the same format sequences as the ``$$iinnddeexx__ffoorrmmaatt'' variable.
 
-241. $quote_quoted
+81. $forward_quote
 
    Type: boolean
 
    Default: no
 
-   Controls how quoted lines will be quoted. If set, one quote character will
-   be added to the end of existing prefix. Otherwise, quoted lines will be
-   prepended by ``indent_string''.
+   When _s_e_t forwarded messages included in the main body of the message
+   (when ``$$mmiimmee__ffoorrwwaarrdd'' is _u_n_s_e_t) will be quoted using
+   ``$$iinnddeenntt__ssttrriinngg''.
 
-242. $quote_regexp
+82. $from
 
-   Type: regular expression
+   Type: e-mail address
 
-   Default: "^([ \t]*[|>:}#])+"
+   Default: ""
 
-   A regular expression used in the internal-pager to determine quoted
-   sections of text in the body of a message.
+   This variable contains a default from address. It can be overridden
+   using my_hdr (including from send-hooks) and ``$$rreevveerrssee__nnaammee''. This
+   variable is ignored if ``$$uussee__ffrroomm'' is unset.
+
+   E.g. you can use send-hook Mutt-ng-devel@lists.berlios.de 'my_hdr
+   From: Foo Bar <foo@bar.fb>' when replying to the Mutt-ng developer's
+   mailing list and Mutt-ng takes this email address.
 
-   Note: In order to use the quotedx patterns in the internal pager, you need
-   to set this to a regular expression that matches exactly the quote
-   characters at the beginning of quoted lines.
+   Defaults to the contents of the environment variable $EMAIL.
 
-243. $read_inc
+83. $gecos_mask
 
-   Type: number
+   Type: regular expression
 
-   Default: 10
+   Default: "^[^,]*"
+
+   A regular expression used by Mutt-ng to parse the GECOS field of a
+   password entry when expanding the alias. By default the regular
+   expression is set to ``^[^,]*'' which will return the string up to the
+   first ``,'' encountered. If the GECOS field contains a string like
+   "lastname, firstname" then you should do: set gecos_mask=".*".
+
+   This can be useful if you see the following behavior: you address a
+   e-mail to user ID stevef whose full name is Steve Franklin. If Mutt-ng
+   expands stevef to ``Franklin'' stevef@foo.bar then you should set the
+   gecos_mask to a regular expression that will match the whole name so
+   Mutt-ng will expand ``Franklin'' to ``Franklin, Steve''.
 
-   If set to a value greater than 0, Mutt-ng will display which message it is
-   currently on when reading a mailbox. The message is printed after read_inc
-   messages have been read (e.g., if set to 25, Mutt-ng will print a message
-   when it reads message 25, and then again when it gets to message 50). This
-   variable is meant to indicate progress when reading large mailboxes which
-   may take some time. When set to 0, only a single message will appear
-   before the reading the mailbox.
+84. $hdrs
+
+   Type: boolean
+
+   Default: yes
 
-   Also see the ``$write_inc'' variable.
+   When _u_n_s_e_t, the header fields normally added by the ``mmyy__hhddrr'' command
+   are not created. This variable _m_u_s_t be _u_n_s_e_t before composing a new
+   message or replying in order to take effect. If _s_e_t, the user defined
+   header fields are added to every new message.
 
-244. $read_only
+85. $header
 
    Type: boolean
 
    Default: no
 
-   If set, all folders are opened in read-only mode.
+   When _s_e_t, this variable causes Mutt-ng to include the header of the
+   message you are replying to into the edit buffer. The ``$$wweeeedd''
+   setting applies.
 
-245. $realname
+86. $header_cache
 
-   Type: string
+   Type: path
 
    Default: ""
 
-   This variable specifies what ``real'' or ``personal'' name should be used
-   when sending messages.
-
-   By default, this is the GECOS field from /etc/passwd.
+   Availability: Header Cache
 
-   Note: This variable will not be used when the user has set a real name in
-   the $from variable.
+   The $$hheeaaddeerr__ccaacchhee variable points to the header cache database.
 
-246. $recall
+   If $$hheeaaddeerr__ccaacchhee points to a directory it will contain a header cache
+   database per folder. If $$hheeaaddeerr__ccaacchhee points to a file that file will
+   be a single global header cache. By default it is _u_n_s_e_t so no header
+   caching will be used.
 
-   Type: quadoption
+87. $header_cache_compress
 
-   Default: ask-yes
+   Type: boolean
 
-   Controls whether or not Mutt-ng recalls postponed messages when composing
-   a new message. Also see ``$postponed''.
+   Default: no
 
-   Setting this variable to yes is not generally useful, and thus not
-   recommended.
+   If enabled the header cache will be compressed. So only one fifth of
+   the usual diskspace is used, but the uncompression can result in a
+   slower open of the cached folder.
 
-247. $record
+88. $help
 
-   Type: path
+   Type: boolean
 
-   Default: ""
+   Default: yes
 
-   This specifies the file into which your outgoing messages should be
-   appended. (This is meant as the primary method for saving a copy of your
-   messages, but another way to do this is using the ``my_hdr'' command to
-   create a Bcc: header field with your email address in it.)
+   When _s_e_t, help lines describing the bindings for the major functions
+   provided by each menu are displayed on the first line of the screen.
 
-   The value of $record is overridden by the ``$force_name'' and
-   ``$save_name'' variables, and the ``fcc-hook'' command.
+   _N_o_t_e_: The binding will not be displayed correctly if the function is
+   bound to a sequence rather than a single keystroke. Also, the help
+   line may not be updated if a binding is changed while Mutt-ng is
+   running. Since this variable is primarily aimed at new users, neither
+   of these should present a major problem.
 
-248. $reply_regexp
+89. $hidden_host
 
-   Type: regular expression
+   Type: boolean
 
-   Default: "^(re([\[0-9\]+])*|aw):[ \t]*"
+   Default: no
 
-   A regular expression used to recognize reply messages when threading and
-   replying. The default value corresponds to the English ``Re:'' and the
-   German ``Aw:''.
+   When _s_e_t, Mutt-ng will skip the host name part of ``$$hhoossttnnaammee''
+   variable when adding the domain part to addresses. This variable does
+   not affect the generation of Message-ID: header fields, and it will
+   not lead to the cut-off of first-level domains.
 
-249. $reply_self
+90. $hide_limited
 
    Type: boolean
 
    Default: no
 
-   If unset and you are replying to a message sent by you, Mutt-ng will
-   assume that you want to reply to the recipients of that message rather
-   than to yourself.
-
-250. $reply_to
+   When _s_e_t, Mutt-ng will not show the presence of messages that are
+   hidden by limiting, in the thread tree.
 
-   Type: quadoption
+91. $hide_missing
 
-   Default: ask-yes
+   Type: boolean
 
-   If set, when replying to a message, Mutt-ng will use the address listed in
-   the ``Reply-To:'' header field as the recipient of the reply. If unset, it
-   will use the address in the ``From:'' header field instead.
+   Default: yes
 
-   This option is useful for reading a mailing list that sets the
-   ``Reply-To:'' header field to the list address and you want to send a
-   private message to the author of a message.
+   When _s_e_t, Mutt-ng will not show the presence of missing messages in
+   the thread tree.
 
-251. $resolve
+92. $hide_thread_subject
 
    Type: boolean
 
    Default: yes
 
-   When set, the cursor will be automatically advanced to the next (possibly
-   undeleted) message whenever a command that modifies the current message is
-   executed.
+   When _s_e_t, Mutt-ng will not show the subject of messages in the thread
+   tree that have the same subject as their parent or closest previously
+   displayed sibling.
 
-252. $reverse_alias
+93. $hide_top_limited
 
    Type: boolean
 
    Default: no
 
-   This variable controls whether or not Mutt-ng will display the
-   ``personal'' name from your aliases in the index menu if it finds an alias
-   that matches the message's sender. For example, if you have the following
-   alias:
+   When _s_e_t, Mutt-ng will not show the presence of messages that are
+   hidden by limiting, at the top of threads in the thread tree. Note
+   that when $$hhiiddee__mmiissssiinngg is _s_e_t, this option will have no effect.
 
-   alias juser abd30425@somewhere.net (Joe User)
+94. $hide_top_missing
 
-   and then you receive mail which contains the following header:
+   Type: boolean
 
-   From: abd30425@somewhere.net
+   Default: yes
 
-   It would be displayed in the index menu as ``Joe User'' instead of
-   ``abd30425@somewhere.net.'' This is useful when the person's e-mail
-   address is not human friendly (like CompuServe addresses).
+   When _s_e_t, Mutt-ng will not show the presence of missing messages at
+   the top of threads in the thread tree. Note that when $$hhiiddee__lliimmiitteedd is
+   _s_e_t, this option will have no effect.
 
-253. $reverse_name
+95. $history
 
-   Type: boolean
+   Type: number
 
-   Default: no
+   Default: 10
 
-   It may sometimes arrive that you receive mail to a certain machine, move
-   the messages to another machine, and reply to some the messages from
-   there. If this variable is set, the default From: line of the reply
-   messages is built using the address where you received the messages you
-   are replying to if that address matches your alternates. If the variable
-   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.
+   This variable controls the size (in number of strings remembered) of
+   the string history buffer. The buffer is cleared each time the
+   variable is changed.
 
-254. $reverse_realname
+96. $honor_followup_to
 
-   Type: boolean
+   Type: quadoption
 
    Default: yes
 
-   This variable fine-tunes the behaviour of the reverse_name feature. When
-   it is set, Mutt-ng will use the address from incoming messages as-is,
-   possibly including eventual real names. When it is unset, Mutt-ng will
-   override any such real names with the setting of the realname variable.
+   This variable controls whether or not a Mail-Followup-To: header field
+   is honored when group-replying to a message.
 
-255. $rfc2047_parameters
+97. $hostname
 
-   Type: boolean
+   Type: string
 
-   Default: no
+   Default: ""
 
-   When this variable is set, Mutt-ng will decode RFC-2047-encoded MIME
-   parameters. You want to set this variable when Mutt-ng suggests you to
-   save attachments to files named like this:
+   Specifies the hostname to use after the ``@'' in local e-mail
+   addresses and during generation of Message-ID: headers.
 
-   =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
+   Please be sure to really know what you are doing when changing this
+   variable to configure a custom domain part of Message-IDs.
 
-   When this variable is set interactively, the change doesn't have the
-   desired effect before you have changed folders.
+98. $ignore_list_reply_to
 
-   Note that this use of RFC 2047's encoding is explicitly, prohibited by the
-   standard, but nevertheless encountered in the wild.
+   Type: boolean
 
-   Also note that setting this parameter will not have the effect that
-   Mutt-ng generates this kind of encoding. Instead, Mutt-ng will
-   unconditionally use the encoding specified in RFC 2231.
+   Default: no
 
-256. $save_address
+   Affects the behaviour of the _r_e_p_l_y function when replying to messages
+   from mailing lists. When _s_e_t, if the ``Reply-To:'' header field is set
+   to the same value as the ``To:'' header field, Mutt-ng assumes that
+   the ``Reply-To:'' header field was set by the mailing list to automate
+   responses to the list, and will ignore this field. To direct a
+   response to the mailing list when this option is set, use the
+   _l_i_s_t_-_r_e_p_l_y function; _g_r_o_u_p_-_r_e_p_l_y will reply to both the sender and the
+   list. Remember: This option works only for mailing lists which are
+   explicitly set in your muttngrc configuration file.
 
-   Type: boolean
+99. $imap_authenticators
 
-   Default: no
+   Type: string
 
-   If set, Mutt-ng will take the sender's full address when choosing a
-   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.
+   Default: ""
 
-257. $save_empty
+   Availability: IMAP
 
-   Type: boolean
+   This is a colon-delimited list of authentication methods Mutt-ng may
+   attempt to use to log in to an IMAP server, in the order Mutt-ng
+   should try them. Authentication methods are either ``login'' or the
+   right side of an IMAP ``AUTH='' capability string, e.g.
+   ``digest-md5'', ``gssapi'' or ``cram-md5''. This parameter is
+   case-insensitive.
 
-   Default: yes
+   If this parameter is _u_n_s_e_t (the default) Mutt-ng will try all
+   available methods, in order from most-secure to least-secure.
 
-   When unset, mailboxes which contain no saved messages will be removed when
-   closed (the exception is ``$spoolfile'' which is never removed). If set,
-   mailboxes are never removed.
+   Example: set imap_authenticators="gssapi:cram-md5:login"
 
-   Note: This only applies to mbox and MMDF folders, Mutt-ng does not delete
-   MH and Maildir directories.
+   _N_o_t_e_: Mutt-ng will only fall back to other authentication methods if
+   the previous methods are unavailable. If a method is available but
+   authentication fails, Mutt-ng will not connect to the IMAP server.
 
-258. $save_name
+100. $imap_check_subscribed
 
    Type: boolean
 
    Default: no
 
-   This variable controls how copies of outgoing messages are saved. When
-   set, a check is made to see if a mailbox specified by the recipient
-   address exists (this is done by searching for a mailbox in the ``$folder''
-   directory with the username part of the recipient address). If the mailbox
-   exists, the outgoing message will be saved to that mailbox, otherwise the
-   message is saved to the ``$record'' mailbox.
+   When _s_e_t, mutt will fetch the set of subscribed folders from your
+   server on connection, and add them to the set of mailboxes it polls
+   for new mail. See also the ``mmaaiillbbooxxeess'' command.
 
-   Also see the ``$force_name'' variable.
+101. $imap_delim_chars
 
-259. $score
+   Type: string
 
-   Type: boolean
+   Default: "/."
 
-   Default: yes
+   Availability: IMAP
 
-   When this variable is unset, scoring is turned off. This can be useful to
-   selectively disable scoring for certain folders when the
-   ``$score_threshold_delete'' variable and friends are used.
+   This contains the list of characters which you would like to treat as
+   folder separators for displaying IMAP paths. In particular it helps in
+   using the '=' shortcut for your $$ffoollddeerr variable.
 
-260. $score_threshold_delete
+102. $imap_headers
 
-   Type: number
+   Type: string
 
-   Default: -1
+   Default: ""
 
-   Messages which have been assigned a score equal to or lower than the value
-   of this variable are automatically marked for deletion by Mutt-ng. Since
-   Mutt-ng scores are always greater than or equal to zero, the default
-   setting of this variable will never mark a message for deletion.
+   Availability: IMAP
 
-261. $score_threshold_flag
+   Mutt-ng requests these header fields in addition to the default
+   headers (``DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE
+   CONTENT-DESCRIPTION IN-REPLY-TO REPLY-TO LINES X-LABEL'') from IMAP
+   servers before displaying the ``index'' menu. You may want to add more
+   headers for spam detection.
 
-   Type: number
+   _N_o_t_e_: This is a space separated list.
 
-   Default: 9999
+103. $imap_home_namespace
 
-   Messages which have been assigned a score greater than or equal to this
-   variable's value are automatically marked ``flagged''.
+   Type: string
 
-262. $score_threshold_read
+   Default: ""
 
-   Type: number
+   Availability: IMAP
 
-   Default: -1
+   You normally want to see your personal folders alongside your INBOX in
+   the IMAP browser. If you see something else, you may set this variable
+   to the IMAP path to your folders.
 
-   Messages which have been assigned a score equal to or lower than the value
-   of this variable are automatically marked as read by Mutt-ng. Since
-   Mutt-ng scores are always greater than or equal to zero, the default
-   setting of this variable will never mark a message read.
+104. $imap_keepalive
 
-263. $send_charset
+   Type: number
 
-   Type: string
+   Default: 900
 
-   Default: "us-ascii:iso-8859-1:utf-8"
+   Availability: IMAP
 
-   A list of character sets for outgoing messages. Mutt-ng will use the first
-   character set into which the text can be converted exactly. If your
-   ``$charset'' is not iso-8859-1 and recipients may not understand UTF-8, it
-   is advisable to include in the list an appropriate widely used standard
-   character set (such as iso-8859-2, koi8-r or iso-2022-jp) either instead
-   of or after iso-8859-1.
+   This variable specifies the maximum amount of time in seconds that
+   Mutt-ng will wait before polling open IMAP connections, to prevent the
+   server from closing them before Mutt-ng has finished with them.
 
-264. $sendmail
+   The default is well within the RFC-specified minimum amount of time
+   (30 minutes) before a server is allowed to do this, but in practice
+   the RFC does get violated every now and then.
 
-   Type: path
+   Reduce this number if you find yourself getting disconnected from your
+   IMAP server due to inactivity.
 
-   Default: "/usr/sbin/sendmail -oem -oi"
+105. $imap_list_subscribed
+
+   Type: boolean
 
-   Specifies the program and arguments used to deliver mail sent by Mutt-ng.
-   Mutt-ng expects that the specified program interprets additional arguments
-   as recipient addresses.
+   Default: no
 
-265. $sendmail_wait
+   Availability: IMAP
 
-   Type: number
+   This variable configures whether IMAP folder browsing will look for
+   only subscribed folders or all folders. This can be toggled in the
+   IMAP browser with the _t_o_g_g_l_e_-_s_u_b_s_c_r_i_b_e_d function.
 
-   Default: 0
+106. $imap_login
 
-   Specifies the number of seconds to wait for the ``$sendmail'' process to
-   finish before giving up and putting delivery in the background.
+   Type: string
 
-   Mutt-ng interprets the value of this variable as follows:
+   Default: ""
 
-   >0
+   Availability: IMAP
 
-           number of seconds to wait for sendmail to finish before continuing
+   Your login name on the IMAP server.
 
-   0
+   This variable defaults to the value of ``$$iimmaapp__uusseerr.''
 
-           wait forever for sendmail to finish
+107. $imap_mail_check
 
-   <0
+   Type: number
 
-           always put sendmail in the background without waiting
+   Default: 300
 
-   Note that if you specify a value other than 0, the output of the child
-   process will be put in a temporary file. If there is some error, you will
-   be informed as to where to find the output.
+   This variable configures how often (in seconds) Mutt-ng should look
+   for new mail in IMAP folders. This is split from the ``mmaaiill__cchheecckk''
+   variable to generate less traffic and get more accurate information
+   for local folders.
 
-266. $shell
+108. $imap_pass
 
-   Type: path
+   Type: string
 
    Default: ""
 
-   Command to use when spawning a subshell. By default, the user's login
-   shell from /etc/passwd is used.
-
-267. $sidebar_boundary
+   Availability: IMAP
 
-   Type: string
+   Specifies the password for your IMAP account. If _u_n_s_e_t, Mutt-ng will
+   prompt you for your password when you invoke the fetch-mail function.
 
-   Default: "."
+   _W_a_r_n_i_n_g: you should only use this option when you are on a fairly
+   secure machine, because the superuser can read your configuration even
+   if you are the only one who can read the file.
 
-   When the sidebar is displayed and $sidebar_shorten_hierarchy is set, this
-   variable specifies the characters at which to split a folder name into
-   ``hierarchy items.''
+109. $imap_passive
 
-268. $sidebar_delim
+   Type: boolean
 
-   Type: string
+   Default: yes
 
-   Default: "|"
+   Availability: IMAP
 
-   This specifies the delimiter between the sidebar (if visible) and other
-   screens.
+   When _s_e_t, Mutt-ng will not open new IMAP connections to check for new
+   mail. Mutt-ng will only check for new mail over existing IMAP
+   connections. This is useful if you don't want to be prompted to
+   user/password pairs on Mutt-ng invocation, or if opening the
+   connection is slow.
 
-269. $sidebar_newmail_only
+110. $imap_peek
 
    Type: boolean
 
-   Default: no
-
-   If set, only folders with new mail will be shown in the sidebar.
+   Default: yes
 
-270. $sidebar_number_format
+   Availability: IMAP
 
-   Type: string
+   If _s_e_t, Mutt-ng will avoid implicitly marking your mail as read
+   whenever you fetch a message from the server. This is generally a good
+   thing, but can make closing an IMAP folder somewhat slower. This
+   option exists to appease speed freaks.
 
-   Default: "%m%?n?(%n)?%?f?[%f]?"
+111. $imap_reconnect
 
-   This variable controls how message counts are printed when the sidebar is
-   enabled. If this variable is empty (and only if), no numbers will be
-   printed and Mutt-ng won't frequently count mail (which may be a great
-   speedup esp. with mbox-style mailboxes.)
+   Type: quadoption
 
-   The following printf(3)-like sequences are supported all of which may be
-   printed non-zero:
+   Default: ask-yes
 
-   %d
+   Availability: IMAP
 
-           Number of deleted messages. 1)
+   Controls whether or not Mutt-ng will try to reconnect to IMAP server
+   when the connection is lost.
 
-   %F
+112. $imap_servernoise
 
-           Number of flagged messages.
+   Type: boolean
 
-   %m
+   Default: yes
 
-           Total number of messages.
+   Availability: IMAP
 
-   %M
+   When _s_e_t, Mutt-ng will display warning messages from the IMAP server
+   as error messages. Since these messages are often harmless, or
+   generated due to configuration problems on the server which are out of
+   the users' hands, you may wish to suppress them at some point.
 
-           Total number of messages shown, i.e. not hidden by a limit. 1)
+113. $imap_user
 
-   %n
+   Type: string
 
-           Number of new messages.
+   Default: ""
 
-   %t
+   Availability: IMAP
 
-           Number of tagged messages. 1)
+   The name of the user whose mail you intend to access on the IMAP
+   server.
 
-   1) These expandos only have a non-zero value for the current mailbox and
-   will always be zero otherwise.
+   This variable defaults to your user name on the local machine.
 
-271. $sidebar_shorten_hierarchy
+114. $implicit_autoview
 
    Type: boolean
 
    Default: no
 
-   When set, the ``hierarchy'' of the sidebar entries will be shortened only
-   if they cannot be printed in full length (because ``$sidebar_width'' is
-   set to a too low value). For example, if the newsgroup name
-   ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get
-   shortened ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will
-   not get shortened.
+   If _s_e_t, Mutt-ng will look for a mailcap entry with the
+   ``copiousoutput'' flag set for _e_v_e_r_y MIME attachment it doesn't have
+   an internal viewer defined for. If such an entry is found, Mutt-ng
+   will use the viewer defined in that entry to convert the body part to
+   text form.
 
-   At which characters this compression is done is controled via the
-   $sidebar_boundary variable.
+115. $include
+
+   Type: quadoption
+
+   Default: ask-yes
 
-272. $sidebar_visible
+   Controls whether or not a copy of the message(s) you are replying to
+   is included in your reply.
+
+116. $include_onlyfirst
 
    Type: boolean
 
    Default: no
 
-   This specifies whether or not to show the sidebar (a list of folders
-   specified with the ``mailboxes'' command).
+   Controls whether or not Mutt-ng includes only the first attachment of
+   the message you are replying.
 
-273. $sidebar_width
+117. $indent_string
 
-   Type: number
+   Type: string
 
-   Default: 0
+   Default: "> "
 
-   The width of the sidebar.
+   Specifies the string to prepend to each line of text quoted in a
+   message to which you are replying. You are strongly encouraged not to
+   change this value, as it tends to agitate the more fanatical netizens.
 
-274. $sig_dashes
+118. $index_format
 
-   Type: boolean
+   Type: string
 
-   Default: yes
+   Default: "%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s"
 
-   If set, a line containing ``-- '' (dash, dash, space) will be inserted
-   before your ``$signature''. It is strongly recommended that you not unset
-   this variable unless your ``signature'' contains just your name. The
-   reason for this is because many software packages use ``-- \n'' to detect
-   your signature.
+   This variable allows you to customize the message index display to
+   your personal taste.
 
-   For example, Mutt-ng has the ability to highlight the signature in a
-   different color in the builtin pager.
+   ``Format strings'' are similar to the strings used in the ``C''
+   function printf(3) to format output (see the man page for more
+   detail). The following sequences are defined in Mutt-ng:
+
+   %a
+          address of the author
 
-275. $sig_on_top
+   %A
+          reply-to address (if present; otherwise: address of author)
 
-   Type: boolean
+   %b
+          filename of the original message folder (think mailBox)
 
-   Default: no
+   %B
+          the list to which the letter was sent, or else the folder name
+          (%b).
 
-   If set, the signature will be included before any quoted or forwarded
-   text. It is strongly recommended that you do not set this variable unless
-   you really know what you are doing, and are prepared to take some heat
-   from netiquette guardians.
+   %c
+          number of characters (bytes) in the message
 
-276. $signature
+   %C
+          current message number
 
-   Type: path
+   %d
+          date and time of the message in the format specified by
+          ``date_format'' converted to sender's time zone
 
-   Default: "~/.signature"
+   %D
+          date and time of the message in the format specified by
+          ``date_format'' converted to the local time zone
 
-   Specifies the filename of your signature, which is appended to all
-   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.
+   %e
+          current message number in thread
 
-277. $signoff_string
+   %E
+          number of messages in current thread
 
-   Type: string
+   %f
+          entire From: line (address + real name)
 
-   Default: ""
+   %F
+          author name, or recipient name if the message is from you
 
-   If set, this string will be inserted before the signature. This is useful
-   for people that want to sign off every message they send with their name.
+   %H
+          spam attribute(s) of this message
 
-   If you want to insert your website's URL, additional contact information
-   or witty quotes into your mails, better use a signature file instead of
-   the signoff string.
+   %g
+          newsgroup name (if compiled with nntp support)
 
-278. $simple_search
+   %i
+          message-id of the current message
 
-   Type: string
+   %l
+          number of lines in the message (does not work with maildir, mh,
+          and possibly IMAP folders)
+
+   %L
+          If an address in the To or CC header field matches an address
+          defined by the users ``subscribe'' command, this displays "To
+          <list-name>", otherwise the same as %F.
+
+   %m
+          total number of message in the mailbox
+
+   %M
+          number of hidden messages if the thread is collapsed.
+
+   %N
+          message score
 
-   Default: "~f %s | ~s %s"
+   %n
+          author's real name (or address if missing)
 
-   Specifies how Mutt-ng should expand a simple search into a real search
-   pattern. A simple search is one that does not contain any of the ~
-   operators. See ``patterns'' for more information on search patterns.
+   %O
+          (_O_riginal save folder) Where Mutt-ng would formerly have
+          stashed the message: list name or recipient name if no list
 
-   For example, if you simply type ``joe'' at a search or limit prompt,
-   Mutt-ng will automatically expand it to the value specified by this
-   variable. For the default value it would be:
+   %s
+          subject of the message
 
-   ~f joe | ~s joe
+   %S
+          status of the message (N/D/d/!/r/*)
 
-279. $sleep_time
+   %t
+          `to:' field (recipients)
 
-   Type: number
+   %T
+          the appropriate character from the $$ttoo__cchhaarrss string
 
-   Default: 1
+   %u
+          user (login) name of the author
 
-   Specifies time, in seconds, to pause while displaying certain
-   informational messages, while moving from folder to folder and after
-   expunging messages from the current folder. The default is to pause one
-   second, so a value of zero for this option suppresses the pause.
+   %v
+          first name of the author, or the recipient if the message is
+          from you
 
-280. $smart_wrap
+   %W
+          name of organization of author (`organization:' field)
 
-   Type: boolean
+   %X
+          number of attachments
 
-   Default: yes
+   %y
+          `x-label:' field, if present
 
-   Controls the display of lines longer than the screen width in the internal
-   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.
+   %Y
+          `x-label' field, if present, and (1) not at part of a thread
+          tree, (2) at the top of a thread, or (3) `x-label' is different
+          from preceding message's `x-label'.
 
-281. $smileys
+   %Z
+          message status flags
 
-   Type: regular expression
+   %{fmt}
+          the date and time of the message is converted to sender's time
+          zone, and ``fmt'' is expanded by the library function
+          ``strftime''; a leading bang disables locales
 
-   Default: "(>From )|(:[-^]?[][)(><}{|/DP])"
+   %[fmt]
+          the date and time of the message is converted to the local time
+          zone, and ``fmt'' is expanded by the library function
+          ``strftime''; a leading bang disables locales
 
-   The pager uses this variable to catch some common false positives of
-   ``$quote_regexp'', most notably smileys in the beginning of a line
+   %(fmt)
+          the local date and time when the message was received. ``fmt''
+          is expanded by the library function ``strftime''; a leading
+          bang disables locales
 
-282. $smime_ask_cert_label
+   %<fmt>
+          the current local time. ``fmt'' is expanded by the library
+          function ``strftime''; a leading bang disables locales.
 
-   Type: boolean
+   %>X
+          right justify the rest of the string and pad with character "X"
 
-   Default: yes
+   %|X
+          pad to the end of the line with character "X"
 
-   This flag controls whether you want to be asked to enter a label for a
-   certificate about to be added to the database or not. It is set by
-   default. (S/MIME only)
+   See also: ``$$ttoo__cchhaarrss''.
 
-283. $smime_ca_location
+119. $ispell
 
    Type: path
 
-   Default: ""
+   Default: "ispell"
 
-   This variable contains the name of either a directory, or a file which
-   contains trusted certificates for use with OpenSSL. (S/MIME only)
+   How to invoke ispell (GNU's spell-checking software).
 
-284. $smime_certificates
+120. $keep_flagged
 
-   Type: path
+   Type: boolean
 
-   Default: ""
+   Default: no
 
-   Since there is no pubring/secring as with PGP, Mutt-ng has to handle
-   storage and retrieval of keys by itself. This is very basic right now, and
-   keys and certificates are stored in two different directories, both named
-   as the hash-value retrieved from OpenSSL. There is an index file which
-   contains mailbox-address keyid pairs, and which can be manually edited.
-   This one points to the location of the certificates. (S/MIME only)
+   If _s_e_t, read messages marked as flagged will not be moved from your
+   spool mailbox to your ``$$mmbbooxx'' mailbox, or as a result of a
+   ``mmbbooxx--hhooookk'' command.
 
-285. $smime_decrypt_command
+121. $locale
 
    Type: string
 
-   Default: ""
+   Default: "C"
 
-   This format string specifies a command which is used to decrypt
-   application/x-pkcs7-mime attachments.
+   The locale used by strftime(3) to format dates. Legal values are the
+   strings your system accepts for the locale variable LC_TIME.
 
-   The OpenSSL command formats have their own set of printf(3)-like sequences
-   similar to PGP's:
+122. $mail_check
 
-   %f
+   Type: number
 
-           Expands to the name of a file containing a message.
+   Default: 5
 
-   %s
+   This variable configures how often (in seconds) Mutt-ng should look
+   for new mail.
 
-           Expands to the name of a file containing the signature part of a
-           multipart/signed attachment when verifying it.
+   _N_o_t_e_: This does not apply to IMAP mailboxes, see $$iimmaapp__mmaaiill__cchheecckk.
 
-   %k
+123. $mailcap_path
 
-           The key-pair specified with $smime_default_key
+   Type: string
 
-   %c
+   Default: ""
 
-           One or more certificate IDs.
+   This variable specifies which files to consult when attempting to
+   display MIME bodies not directly supported by Mutt-ng.
 
-   %a
+124. $mailcap_sanitize
 
-           The algorithm used for encryption.
+   Type: boolean
 
-   %C
+   Default: yes
 
-           CA location: Depending on whether $smime_ca_location points to a
-           directory or file, this expands to "-CApath $smime_ca_location" or
-           "-CAfile $smime_ca_location".
+   If _s_e_t, Mutt-ng will restrict possible characters in mailcap %
+   expandos to a well-defined set of safe characters. This is the safe
+   setting, but we are not sure it doesn't break some more advanced MIME
+   stuff.
 
-   For examples on how to configure these formats, see the smime.rc in the
-   samples/ subdirectory which has been installed on your system alongside
-   the documentation. (S/MIME only)
+   _D_O_N_'_T_ _C_H_A_N_G_E_ _T_H_I_S_ _S_E_T_T_I_N_G_ _U_N_L_E_S_S_ _Y_O_U_ _A_R_E_ _R_E_A_L_L_Y_ _S_U_R_E_ _W_H_A_T_ _Y_O_U_ _A_R_E
+   _D_O_I_N_G_!
 
-286. $smime_decrypt_use_default_key
+125. $maildir_header_cache_verify
 
    Type: boolean
 
    Default: yes
 
-   If set (default) this tells Mutt-ng to use the default key for decryption.
-   Otherwise, if manage multiple certificate-key-pairs, Mutt-ng will try to
-   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)
+   Availability: Header Cache
 
-287. $smime_default_key
+   Check for Maildir unaware programs other than Mutt-ng having modified
+   maildir files when the header cache is in use. This incurs one stat(2)
+   per message every time the folder is opened.
 
-   Type: string
+126. $maildir_trash
 
-   Default: ""
+   Type: boolean
 
-   This is the default key-pair to use for signing. This must be set to the
-   keyid (the hash-value that OpenSSL generates) to work properly (S/MIME
-   only)
+   Default: no
 
-288. $smime_encrypt_command
+   If _s_e_t, messages marked as deleted will be saved with the maildir
+   (T)rashed flag instead of physically deleted.
 
-   Type: string
+   _N_O_T_E_: this only applies to maildir-style mailboxes. Setting it will
+   have no effect on other mailbox types.
 
-   Default: ""
+   It is similiar to the trash option.
 
-   This command is used to create encrypted S/MIME messages. (S/MIME only)
+127. $mark_old
 
-289. $smime_encrypt_with
+   Type: boolean
 
-   Type: string
+   Default: yes
 
-   Default: ""
+   Controls whether or not Mutt-ng marks _n_e_w_u_n_r_e_a_d messages as _o_l_d if you
+   exit a mailbox without reading them.
 
-   This sets the algorithm that should be used for encryption. Valid choices
-   are ``des'', ``des3'', ``rc2-40'', ``rc2-64'', ``\frc2-128''.
+   With this option _s_e_t, the next time you start Mutt-ng, the messages
+   will show up with an "O" next to them in the ``index'' menu,
+   indicating that they are old.
 
-   If unset ``3des'' (TripleDES) is used. (S/MIME only)
+128. $markers
 
-290. $smime_get_cert_command
+   Type: boolean
 
-   Type: string
+   Default: yes
 
-   Default: ""
+   Controls the display of wrapped lines in the internal pager. If set, a
+   ``+'' marker is displayed at the beginning of wrapped lines. Also see
+   the ``$$ssmmaarrtt__wwrraapp'' variable.
 
-   This command is used to extract X509 certificates from a PKCS7 structure.
-   (S/MIME only)
+129. $mask
 
-291. $smime_get_cert_email_command
+   Type: regular expression
 
-   Type: string
+   Default: "!^\.[^.]"
 
-   Default: ""
+   A regular expression used in the file browser, optionally preceded by
+   the _n_o_t operator ``!''. Only files whose names match this mask will be
+   shown. The match is always case-sensitive.
 
-   This command is used to extract the mail address(es) used for storing X509
-   certificates, and for verification purposes (to check whether the
-   certificate was issued for the sender's mailbox). (S/MIME only)
+130. $max_display_recips
 
-292. $smime_get_signer_cert_command
+   Type: number
 
-   Type: string
+   Default: 0
 
-   Default: ""
+   When set non-zero, this specifies the maximum number of recipient
+   header lines (To:, Cc: and Bcc:) to display in the pager if header
+   weeding is turned on. In case the number of lines exeeds its value,
+   the last line will have 3 dots appended.
 
-   This command is used to extract only the signers X509 certificate from a
-   S/MIME signature, so that the certificate's owner may get compared to the
-   email's ``From:'' header field. (S/MIME only)
+131. $max_line_length
 
-293. $smime_import_cert_command
+   Type: number
 
-   Type: string
+   Default: 0
 
-   Default: ""
+   When _s_e_t, the maximum line length for displaying ``format = flowed''
+   messages is limited to this length. A value of 0 (which is also the
+   default) means that the maximum line length is determined by the
+   terminal width and $$wwrraappmmaarrggiinn.
 
-   This command is used to import a certificate via smime_keysng. (S/MIME
-   only)
+132. $mbox
 
-294. $smime_is_default
+   Type: path
 
-   Type: boolean
+   Default: "~/mbox"
 
-   Default: no
+   This specifies the folder into which read mail in your ``$$ssppoooollffiillee''
+   folder will be appended.
 
-   The default behaviour of Mutt-ng is to use PGP on all auto-sign/encryption
-   operations. To override and to use OpenSSL instead this must be set.
+133. $mbox_type
 
-   However, this has no effect while replying, since Mutt-ng will
-   automatically select the same application that was used to sign/encrypt
-   the original message.
+   Type: folder magic
 
-   (Note that this variable can be overridden by unsetting $crypt_autosmime.)
-   (S/MIME only)
+   Default: mbox
 
-295. $smime_keys
+   The default mailbox type used when creating new folders. May be any of
+   mbox, MMDF, MH and Maildir.
 
-   Type: path
+134. $menu_context
 
-   Default: ""
+   Type: number
 
-   Since there is no pubring/secring as with PGP, Mutt-ng has to handle
-   storage ad retrieval of keys/certs by itself. This is very basic right
-   now, and stores keys and certificates in two different directories, both
-   named as the hash-value retrieved from OpenSSL. There is an index file
-   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)
+   Default: 0
 
-296. $smime_pk7out_command
+   This variable controls the number of lines of context that are given
+   when scrolling through menus. (Similar to ``$$ppaaggeerr__ccoonntteexxtt''.)
 
-   Type: string
+135. $menu_move_off
 
-   Default: ""
+   Type: boolean
 
-   This command is used to extract PKCS7 structures of S/MIME signatures, in
-   order to extract the public X509 certificate(s). (S/MIME only)
+   Default: yes
 
-297. $smime_sign_command
+   When _u_n_s_e_t, the bottom entry of menus will never scroll up past the
+   bottom of the screen, unless there are less entries than lines. When
+   _s_e_t, the bottom entry may move off the bottom.
 
-   Type: string
+136. $menu_scroll
 
-   Default: ""
+   Type: boolean
 
-   This command is used to created S/MIME signatures of type
-   multipart/signed, which can be read by all mail clients. (S/MIME only)
+   Default: no
+
+   When _s_e_t, menus will be scrolled up or down one line when you attempt
+   to move across a screen boundary. If _u_n_s_e_t, the screen is cleared and
+   the next or previous page of the menu is displayed (useful for slow
+   links to avoid many redraws).
 
-298. $smime_sign_opaque_command
+137. $message_format
 
    Type: string
 
-   Default: ""
+   Default: "%s"
 
-   This command is used to created S/MIME signatures of type
-   application/x-pkcs7-signature, which can only be handled by mail clients
-   supporting the S/MIME extension. (S/MIME only)
+   This is the string displayed in the ``attachment'' menu for
+   attachments of type message/rfc822. For a full listing of defined
+   printf(3)-like sequences see the section on ``$$iinnddeexx__ffoorrmmaatt''.
 
-299. $smime_timeout
+138. $meta_key
 
-   Type: number
+   Type: boolean
 
-   Default: 300
+   Default: no
 
-   The number of seconds after which a cached passphrase will expire if not
-   used. (S/MIME only)
+   If _s_e_t, forces Mutt-ng to interpret keystrokes with the high bit (bit
+   8) set as if the user had pressed the ESC key and whatever key remains
+   after having the high bit removed. For example, if the key pressed has
+   an ASCII value of 0xf8, then this is treated as if the user had
+   pressed ESC then ``x''. This is because the result of removing the
+   high bit from ``0xf8'' is ``0x78'', which is the ASCII character
+   ``x''.
 
-300. $smime_verify_command
+139. $metoo
 
-   Type: string
+   Type: boolean
 
-   Default: ""
+   Default: no
 
-   This command is used to verify S/MIME signatures of type multipart/signed.
-   (S/MIME only)
+   If _u_n_s_e_t, Mutt-ng will remove your address (see the ``alternates''
+   command) from the list of recipients when replying to a message.
 
-301. $smime_verify_opaque_command
+140. $mh_purge
 
-   Type: string
+   Type: boolean
 
-   Default: ""
+   Default: no
 
-   This command is used to verify S/MIME signatures of type
-   application/x-pkcs7-mime. (S/MIME only)
+   When _u_n_s_e_t, Mutt-ng will mimic mh's behaviour and rename deleted
+   messages to _,_<_o_l_d_ _f_i_l_e_ _n_a_m_e_> in mh folders instead of really deleting
+   them. If the variable is set, the message files will simply be
+   deleted.
 
-302. $smtp_host
+141. $mh_seq_flagged
 
    Type: string
 
-   Default: ""
-
-   Availability: SMTP
+   Default: "flagged"
 
-   Defines the SMTP host which will be used to deliver mail, as opposed to
-   invoking the sendmail binary. Setting this variable overrides the value of
-   ``$sendmail'', and any associated variables.
+   The name of the MH sequence used for flagged messages.
 
-303. $smtp_pass
+142. $mh_seq_replied
 
    Type: string
 
-   Default: ""
-
-   Availability: SMTP
+   Default: "replied"
 
-   Defines the password to use with SMTP AUTH. If ``$smtp_user'' is set, but
-   this variable is not, you will be prompted for a password when sending.
+   The name of the MH sequence used to tag replied messages.
 
-   Note: Storing passwords in a configuration file presents a security risk
-   since the superuser of your machine may read it regardless of the file's
-   permissions.
+143. $mh_seq_unseen
 
-304. $smtp_port
+   Type: string
 
-   Type: number
+   Default: "unseen"
 
-   Default: 25
+   The name of the MH sequence used for unseen messages.
 
-   Availability: SMTP
+144. $mime_forward
 
-   Defines the port that the SMTP host is listening on for mail delivery.
-   Must be specified as a number.
+   Type: quadoption
 
-   Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP
-   servers will probably desire 587, the mail submission port.
+   Default: no
 
-305. $smtp_use_tls
+   When _s_e_t, the message you are forwarding will be attached as a
+   separate MIME part instead of included in the main body of the
+   message.
 
-   Type: string
+   This is useful for forwarding MIME messages so the receiver can
+   properly view the message as it was delivered to you. If you like to
+   switch between MIME and not MIME from mail to mail, set this variable
+   to ask-no or ask-yes.
 
-   Default: ""
+   Also see ``$$ffoorrwwaarrdd__ddeeccooddee'' and ``$$mmiimmee__ffoorrwwaarrdd__ddeeccooddee''.
 
-   Availability: SMTP (and SSL)
+145. $mime_forward_decode
 
-   Defines wether to use STARTTLS. If this option is set to ``required'' and
-   the server does not support STARTTLS or there is an error in the TLS
-   Handshake, the connection will fail. Setting this to ``enabled'' will try
-   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.
+   Type: boolean
 
-306. $smtp_user
+   Default: no
 
-   Type: string
+   Controls the decoding of complex MIME messages into text/plain when
+   forwarding a message while ``$$mmiimmee__ffoorrwwaarrdd'' is _s_e_t. Otherwise
+   ``$$ffoorrwwaarrdd__ddeeccooddee'' is used instead.
 
-   Default: ""
+146. $mime_forward_rest
 
-   Availability: SMTP
+   Type: quadoption
 
-   Defines the username to use with SMTP AUTH. Setting this variable will
-   cause Mutt-ng to attempt to use SMTP AUTH when sending.
+   Default: yes
 
-307. $sort
+   When forwarding multiple attachments of a MIME message from the
+   recvattach menu, attachments which cannot be decoded in a reasonable
+   manner will be attached to the newly composed message if this option
+   is set.
 
-   Type: sort order
+147. $mix_entry_format
 
-   Default: date
+   Type: string
 
-   Specifies how to sort messages in the index menu. Valid values are:
+   Default: "%4n %c %-16s %a"
 
-    date or date-sent
-    date-received
-    from
-    mailbox-order (unsorted)
-    score
-    size
-    spam
-    subject
-    threads
-    to
+   Availability: Mixmaster
 
+   This variable describes the format of a remailer line on the mixmaster
+   chain selection screen. The following printf(3)-like sequences are
+   supported:
 
-   You may optionally use the ``reverse-'' prefix to specify reverse sorting
-   order (example: set sort=reverse-date-sent).
+   %n
+          The running number on the menu.
 
-308. $sort_alias
+   %c
+          Remailer capabilities.
 
-   Type: sort order
+   %s
+          The remailer's short name.
 
-   Default: alias
+   %a
+          The remailer's e-mail address.
 
-   Specifies how the entries in the ``alias'' menu are sorted. The following
-   are legal values:
+148. $mixmaster
 
-    address (sort alphabetically by email address)
-    alias (sort alphabetically by alias name)
-    unsorted (leave in order specified in .muttrc)
+   Type: path
 
+   Default: "mixmaster"
 
-309. $sort_aux
+   Availability: Mixmaster
 
-   Type: sort order
+   This variable contains the path to the Mixmaster binary on your
+   system. It is used with various sets of parameters to gather the list
+   of known remailers, and to finally send a message through the
+   mixmaster chain.
 
-   Default: date
+149. $move
 
-   When sorting by threads, this variable controls how threads are sorted in
-   relation to other threads, and how the branches of the thread trees are
-   sorted. This can be set to any value that ``$sort'' can, except threads
-   (in that case, Mutt-ng will just use date-sent). You can also specify the
-   ``last-'' prefix in addition to ``reverse-'' prefix, but last- must come
-   after reverse-. The last- prefix causes messages to be sorted against its
-   siblings by which has the last descendant, using the rest of sort_aux as
-   an ordering.
+   Type: quadoption
 
-   For instance, set sort_aux=last-date-received would mean that if a new
-   message is received in a thread, that thread becomes the last one
-   displayed (or the first, if you have set sort=reverse-threads.)
+   Default: ask-no
 
-   Note: For reversed ``$sort'' order $sort_aux is reversed again (which is
-   not the right thing to do, but kept to not break any existing
-   configuration setting).
+   Controls whether or not Mutt-ng will move read messages from your
+   spool mailbox to your ``$$mmbbooxx'' mailbox, or as a result of a
+   ``mmbbooxx--hhooookk'' command.
 
-310. $sort_browser
+150. $msgid_format
 
-   Type: sort order
+   Type: string
 
-   Default: alpha
+   Default: "%Y%m%d%h%M%s.G%P%p"
 
-   Specifies how to sort entries in the file browser. By default, the entries
-   are sorted alphabetically. Valid values:
+   This is the format for the ``local part'' of the Message-ID: header
+   field generated by Mutt-ng. If this variable is empty, no Message-ID:
+   headers will be generated. The '%' character marks that certain data
+   will be added to the string, similar to printf(3). The following
+   characters are allowed:
 
-    alpha (alphabetically)
-    date
-    size
-    unsorted
+   %d
+          the current day of month
 
+   %h
+          the current hour
 
-   You may optionally use the ``reverse-'' prefix to specify reverse sorting
-   order (example: set sort_browser=reverse-date).
+   %m
+          the current month
 
-311. $sort_re
+   %M
+          the current minute
 
-   Type: boolean
+   %O
+          the current UNIX timestamp (octal)
 
-   Default: yes
+   %p
+          the process ID
 
-   This variable is only useful when sorting by threads with
-   ``$strict_threads'' unset. In that case, it changes the heuristic Mutt-ng
-   uses to thread messages by subject. With $sort_reset, Mutt-ng will only
-   attach a message as the child of another message by subject if the subject
-   of the child message starts with a substring matching the setting of
-   ``$reply_regexp''. With $sort_reunset, Mutt-ng will attach the message
-   whether or not this is the case, as long as the non-``$reply_regexp''
-   parts of both messages are identical.
+   %P
+          the current Message-ID prefix (a character rotating with every
+          Message-ID being generated)
 
-312. $spam_separator
+   %r
+          a random integer value (decimal)
 
-   Type: string
+   %R
+          a random integer value (hexadecimal)
 
-   Default: ","
+   %s
+          the current second
 
-   ``spam_separator'' controls what happens when multiple spam headers are
-   matched: if unset, each successive header will overwrite any previous
-   matches value for the spam label. If set, each successive match will
-   append to the previous, using ``spam_separator'' as a separator.
+   %T
+          the current UNIX timestamp (decimal)
 
-313. $spoolfile
+   %X
+          the current UNIX timestamp (hexadecimal)
 
-   Type: path
+   %Y
+          the current year (Y2K compliant)
 
-   Default: ""
+   %%
+          the '%' character
 
-   If your spool mailbox is in a non-default place where Mutt-ng cannot find
-   it, you can specify its location with this variable. Mutt-ng will
-   automatically set this variable to the value of the environment variable
-   $MAIL if it is not set.
+   _N_o_t_e_: Please only change this setting if you know what you are doing.
+   Also make sure to consult RFC2822 to produce technically _v_a_l_i_d
+   strings.
 
-314. $ssl_ca_certificates_file
+151. $muttng_bindir
 
-   Type: path
+   Type: system property
 
-   Default: ""
+   Value: /opt/freebsd4/mutt-ng/bin
 
-   This variable specifies a file containing trusted CA certificates. Any
-   server certificate that is signed with one of these CA certificates are
-   also automatically accepted.
+   _T_h_i_s_ _i_s_ _a_ _r_e_a_d_-_o_n_l_y_ _s_y_s_t_e_m_ _p_r_o_p_e_r_t_y_ _a_n_d_ _s_p_e_c_i_f_i_e_s_ _t_h_e_ _d_i_r_e_c_t_o_r_y
+   _c_o_n_t_a_i_n_i_n_g_ _t_h_e_ _m_u_t_t_n_g_ _b_i_n_a_r_y_.
 
-   Example: set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
+152. $muttng_docdir
 
-315. $ssl_client_cert
+   Type: system property
 
-   Type: path
+   Value: /opt/freebsd4/mutt-ng/doc/muttng
 
-   Default: ""
+   _T_h_i_s_ _i_s_ _a_ _r_e_a_d_-_o_n_l_y_ _s_y_s_t_e_m_ _p_r_o_p_e_r_t_y_ _a_n_d_ _s_p_e_c_i_f_i_e_s_ _t_h_e_ _d_i_r_e_c_t_o_r_y
+   _c_o_n_t_a_i_n_i_n_g_ _t_h_e_ _m_u_t_t_n_g_ _d_o_c_u_m_e_n_t_a_t_i_o_n_.
 
-   Availability: SSL
+153. $muttng_folder_name
 
-   The file containing a client certificate and its associated private key.
+   Type: system property
 
-316. $ssl_force_tls
+   Value:
 
-   Type: boolean
+   _T_h_i_s_ _i_s_ _a_ _r_e_a_d_-_o_n_l_y_ _s_y_s_t_e_m_ _p_r_o_p_e_r_t_y_ _a_n_d_,_ _a_t_ _r_u_n_t_i_m_e_,_ _s_p_e_c_i_f_i_e_s_ _t_h_e
+   _a_c_t_u_a_l_ _n_a_m_e_ _o_f_ _t_h_e_ _f_o_l_d_e_r_ _a_s_ _f_a_r_ _a_s_ _i_t_ _c_o_u_l_d_ _b_e_ _d_e_t_e_c_t_e_d_.
 
-   Default: no
+   For detection, $folder is first taken into account and simply stripped
+   to form the result when a match is found. For example, with $folder
+   being imap://host and the folder is imap://host/INBOX/foo,
+   $muttng_folder_name will be just INBOX/foo.)
 
-   If this variable is set, Mutt-ng will require that all connections to
-   remote servers be encrypted. Furthermore it will attempt to negotiate TLS
-   even if the server does not advertise the capability, since it would
-   otherwise have to abort the connection anyway. This option supersedes
-   ``$ssl_starttls''.
+   Second, if the initial portion of a name is not $folder, the result
+   will be everything after the last ``/''.
 
-317. $ssl_min_dh_prime_bits
+   Third and last, the result will be just the name if neither $folder
+   nor a ``/'' were found in the name.
 
-   Type: number
+154. $muttng_folder_path
 
-   Default: 0
+   Type: system property
 
-   Availability: GNUTLS
+   Value:
 
-   This variable specifies the minimum acceptable prime size (in bits) for
-   use in any Diffie-Hellman key exchange. A value of 0 will use the default
-   from the GNUTLS library.
+   _T_h_i_s_ _i_s_ _a_ _r_e_a_d_-_o_n_l_y_ _s_y_s_t_e_m_ _p_r_o_p_e_r_t_y_ _a_n_d_,_ _a_t_ _r_u_n_t_i_m_e_,_ _s_p_e_c_i_f_i_e_s_ _t_h_e
+   _f_u_l_l_ _p_a_t_h_ _o_r_ _U_R_I_ _o_f_ _t_h_e_ _f_o_l_d_e_r_ _c_u_r_r_e_n_t_l_y_ _o_p_e_n_ _(_i_f_ _a_n_y_)_.
 
-318. $ssl_starttls
+155. $muttng_hcache_backend
 
-   Type: quadoption
+   Type: system property
 
-   Default: yes
+   Value: qdbm
 
-   Availability: SSL or GNUTLS
+   _T_h_i_s_ _i_s_ _a_ _r_e_a_d_-_o_n_l_y_ _s_y_s_t_e_m_ _p_r_o_p_e_r_t_y_ _a_n_d_ _s_p_e_c_i_f_i_e_s_ _t_h_e_ _h_e_a_d_e_r
+   _c_h_a_c_h_i_n_g_'_s_ _d_a_t_a_b_a_s_e_ _b_a_c_k_e_n_d_.
 
-   If set (the default), Mutt-ng will attempt to use STARTTLS on servers
-   advertising the capability. When unset, Mutt-ng will not attempt to use
-   STARTTLS regardless of the server's capabilities.
+156. $muttng_pwd
 
-319. $ssl_use_sslv2
+   Type: system property
 
-   Type: boolean
+   Value:
 
-   Default: yes
+   _T_h_i_s_ _i_s_ _a_ _r_e_a_d_-_o_n_l_y_ _s_y_s_t_e_m_ _p_r_o_p_e_r_t_y_ _a_n_d_,_ _a_t_ _r_u_n_t_i_m_e_,_ _s_p_e_c_i_f_i_e_s_ _t_h_e
+   _c_u_r_r_e_n_t_ _w_o_r_k_i_n_g_ _d_i_r_e_c_t_o_r_y_ _o_f_ _t_h_e_ _m_u_t_t_n_g_ _b_i_n_a_r_y_.
 
-   Availability: SSL
+157. $muttng_revision
 
-   This variables specifies whether to attempt to use SSLv2 in the SSL
-   authentication process.
+   Type: system property
 
-320. $ssl_use_sslv3
+   Value: 790
 
-   Type: boolean
+   _T_h_i_s_ _i_s_ _a_ _r_e_a_d_-_o_n_l_y_ _s_y_s_t_e_m_ _p_r_o_p_e_r_t_y_ _a_n_d_ _s_p_e_c_i_f_i_e_s_ _m_u_t_t_n_g_'_s_ _s_u_b_v_e_r_s_i_o_n
+   _r_e_v_i_s_i_o_n_ _s_t_r_i_n_g_.
 
-   Default: yes
+158. $muttng_sysconfdir
 
-   Availability: SSL or GNUTLS
+   Type: system property
 
-   This variables specifies whether to attempt to use SSLv3 in the SSL
-   authentication process.
+   Value: /opt/freebsd4/mutt-ng/etc
 
-321. $ssl_use_tlsv1
+   _T_h_i_s_ _i_s_ _a_ _r_e_a_d_-_o_n_l_y_ _s_y_s_t_e_m_ _p_r_o_p_e_r_t_y_ _a_n_d_ _s_p_e_c_i_f_i_e_s_ _t_h_e_ _d_i_r_e_c_t_o_r_y
+   _c_o_n_t_a_i_n_i_n_g_ _t_h_e_ _m_u_t_t_n_g_ _s_y_s_t_e_m_-_w_i_d_e_ _c_o_n_f_i_g_u_r_a_t_i_o_n_.
 
-   Type: boolean
+159. $muttng_version
 
-   Default: yes
+   Type: system property
 
-   Availability: SSL or GNUTLS
+   Value: devel
 
-   This variables specifies whether to attempt to use TLSv1 in the SSL
-   authentication process.
+   _T_h_i_s_ _i_s_ _a_ _r_e_a_d_-_o_n_l_y_ _s_y_s_t_e_m_ _p_r_o_p_e_r_t_y_ _a_n_d_ _s_p_e_c_i_f_i_e_s_ _m_u_t_t_n_g_'_s_ _v_e_r_s_i_o_n
+   _s_t_r_i_n_g_.
 
-322. $ssl_usesystemcerts
+160. $narrow_tree
 
    Type: boolean
 
-   Default: yes
+   Default: no
 
-   Availability: SSL
+   This variable, when _s_e_t, makes the thread tree narrower, allowing
+   deeper threads to fit on the screen.
 
-   If set to yes, Mutt-ng will use CA certificates in the system-wide
-   certificate store when checking if server certificate is signed by a
-   trusted CA.
+161. $net_inc
 
-323. $status_chars
+   Type: number
 
-   Type: string
+   Default: 10
 
-   Default: "-*%A"
+   Operations that expect to transfer a large amount of data over the
+   network will update their progress every _n_e_t___i_n_c kilobytes. If set to
+   0, no progress messages will be displayed.
 
-   Controls the characters used by the ``%r'' indicator in
-   ``$status_format''. The first character is used when the mailbox is
-   unchanged. The second is used when the mailbox has been changed, and it
-   needs to be resynchronized. The third is used if the mailbox is in
-   read-only mode, or if the mailbox will not be written when exiting that
-   mailbox (You can toggle whether to write changes to a mailbox with the
-   toggle-write operation, bound by default to ``%''). The fourth is used to
-   indicate that the current folder has been opened in attach-message mode
-   (Certain operations like composing a new mail, replying, forwarding, etc.
-   are not permitted in this mode).
-
-324. $status_format
+   See also ``$$rreeaadd__iinncc'' and ``$$wwrriittee__iinncc''.
 
-   Type: string
+162. $nntp_ask_followup_to
 
-   Default: "-%r-Mutt-ng: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d?
-   Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l?
-   %l?]---(%s/%S)-%>-(%P)---"
+   Type: boolean
 
-   Controls the format of the status line displayed in the index menu. This
-   string is similar to ``$index_format'', but has its own set of
-   printf(3)-like sequences:
+   Default: no
 
-   %b
+   Availability: NNTP
 
-           number of mailboxes with new mail *
+   If _s_e_t, Mutt-ng will prompt you for the Followup-To: header field
+   before editing the body of an outgoing news article.
 
-   %B
+163. $nntp_ask_x_comment_to
 
-           the short pathname of the current mailbox
+   Type: boolean
 
-   %d
+   Default: no
 
-           number of deleted messages *
+   Availability: NNTP
 
-   %f
+   If _s_e_t, Mutt-ng will prompt you for the X-Comment-To: header field
+   before editing the body of an outgoing news article.
 
-           the full pathname of the current mailbox
+164. $nntp_cache_dir
 
-   %F
+   Type: path
 
-           number of flagged messages *
+   Default: "~/.muttng"
 
-   %h
+   Availability: NNTP
 
-           local hostname
+   This variable points to directory where Mutt-ng will cache news
+   article headers. If _u_n_s_e_t, headers will not be saved at all and will
+   be reloaded each time when you enter a newsgroup.
 
-   %l
+   As for the header caching in connection with IMAP and/or Maildir, this
+   drastically increases speed and lowers traffic.
 
-           size (in bytes) of the current mailbox *
+165. $nntp_catchup
 
-   %L
+   Type: quadoption
 
-           size (in bytes) of the messages shown (i.e., which match the
-           current limit) *
+   Default: ask-yes
 
-   %m
+   Availability: NNTP
 
-           the number of messages in the mailbox *
+   If this variable is _s_e_t, Mutt-ng will mark all articles in a newsgroup
+   as read when you leaving it.
 
-   %M
+166. $nntp_context
 
-           the number of messages shown (i.e., which match the current limit)
-           *
+   Type: number
 
-   %n
+   Default: 1000
 
-           number of new messages in the mailbox *
+   Availability: NNTP
 
-   %o
+   This variable controls how many news articles to cache per newsgroup
+   (if caching is enabled, see $$nnnnttpp__ccaacchhee__ddiirr) and how many news
+   articles to show in the ``index'' menu.
 
-           number of old unread messages *
+   If there're more articles than defined with $$nnnnttpp__ccoonntteexxtt, all older
+   ones will be removed/not shown in the index.
 
-   %p
+167. $nntp_followup_to_poster
 
-           number of postponed messages *
+   Type: quadoption
 
-   %P
+   Default: ask-yes
 
-           percentage of the way through the index
+   Availability: NNTP
 
-   %r
+   If this variable is _s_e_t and the keyword "poster" is present in the
+   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.
 
-           modified/read-only/won't-write/attach-message indicator, according
-           to $status_chars
+168. $nntp_group_index_format
 
-   %s
+   Type: string
 
-           current sorting mode ($sort)
+   Default: "%4C %M%N %5s %-45.45f %d"
 
-   %S
+   Availability: NNTP
 
-           current aux sorting method ($sort_aux)
+   This variable allows you to customize the newsgroup browser display to
+   your personal taste. This string is similar to ``iinnddeexx__ffoorrmmaatt'', but
+   has its own set of printf(3)-like sequences:
 
-   %t
+%C      current newsgroup number
+%d      description of newsgroup (retrieved from server)
+%f      newsgroup name
+%M      ``-'' if newsgroup not allowed for direct post (moderated for example)
+%N      ``N'' if newsgroup is new, ``u'' if unsubscribed, blank otherwise
+%n      number of new articles in newsgroup
+%s      number of unread articles in newsgroup
+%>X     right justify the rest of the string and pad with character "X"
+%|X     pad to the end of the line with character "X"
 
-           number of tagged messages *
+169. $nntp_host
 
-   %u
+   Type: string
 
-           number of unread messages *
+   Default: ""
 
-   %v
+   Availability: NNTP
 
-           Mutt-ng version string
+   This variable specifies the name (or address) of the NNTP server to be
+   used.
 
-   %V
+   It defaults to the value specified via the environment variable
+   $NNTPSERVER or contained in the file /etc/nntpserver.
 
-           currently active limit pattern, if any *
+   You can also specify a username and an alternative port for each
+   newsserver, e.g.
 
-   %>X
+   [nntp[s]://][username[:password]@]newsserver[:port]
 
-           right justify the rest of the string and pad with "X"
+   _N_o_t_e_: Using a password as shown and stored in a configuration file
+   presents a security risk since the superuser of your machine may read
+   it regardless of the file's permissions.
 
-   %|X
+170. $nntp_inews
 
-           pad to the end of the line with "X"
+   Type: path
 
-   * = can be optionally printed if nonzero
+   Default: ""
 
-   Some of the above sequences can be used to optionally print a string if
-   their value is nonzero. For example, you may only want to see the number
-   of flagged messages if such messages exist, since zero is not particularly
-   meaningful. To optionally print a string based upon one of the above
-   sequences, the following construct is used
+   Availability: NNTP
 
-   %?<sequence_char>?<optional_string>?
+   If _s_e_t, specifies the program and arguments used to deliver news
+   posted by Mutt-ng. Otherwise, Mutt-ng posts article using current
+   connection. The following printf(3)-style sequence is understood:
 
-   where sequence_char is a character from the table above, and
-   optional_string is the string you would like printed if sequence_char is
-   nonzero. optional_stringmay contain other sequences as well as normal
-   text, but you may not nest optional strings.
+%s      newsserver name
 
-   Here is an example illustrating how to optionally print the number of new
-   messages in a mailbox:
+   Example: set inews="/usr/local/bin/inews -hS"
 
-   %?n?%n new messages.?
+171. $nntp_load_description
 
-   Additionally you can switch between two strings, the first one, if a value
-   is zero, the second one, if the value is nonzero, by using the following
-   construct:
+   Type: boolean
 
-   %?<sequence_char>?<if_string>&<else_string>?
+   Default: yes
 
-   You can additionally force the result of any printf(3)-like sequence to be
-   lowercase by prefixing the sequence character with an underscore (_) sign.
-   For example, if you want to display the local hostname in lowercase, you
-   would use:
+   Availability: NNTP
 
-   %_h
+   This variable controls whether or not descriptions for newsgroups are
+   to be loaded when subscribing to a newsgroup.
 
-   If you prefix the sequence character with a colon (:) character, Mutt-ng
-   will replace any dots in the expansion by underscores. This might be
-   helpful with IMAP folders that don't like dots in folder names.
+172. $nntp_mail_check
 
-325. $status_on_top
+   Type: number
 
-   Type: boolean
+   Default: 60
 
-   Default: no
+   Availability: NNTP
 
-   Setting this variable causes the ``status bar'' to be displayed on the
-   first line of the screen rather than near the bottom.
+   The time in seconds until any operations on a newsgroup except posting
+   a 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.).
 
-326. $strict_mailto
+173. $nntp_mime_subject
 
    Type: boolean
 
    Default: yes
 
-   With mailto: style links, a body as well as arbitrary header information
-   may be embedded. This may lead to (user) headers being overwriten without
-   note if ``$edit_headers'' is unset.
+   Availability: NNTP
 
-   If this variable is set, Mutt-ng is strict and allows anything to be
-   changed. If it's unset, all headers given will be prefixed with
-   ``X-Mailto-'' and the message including headers will be shown in the
-   editor regardless of what ``$edit_headers'' is set to.
+   If _u_n_s_e_t, an 8-bit ``Subject:'' header field in a news article will
+   not be encoded according to RFC2047.
 
-327. $strict_mime
+   _N_o_t_e_: Only change this setting if you know what you are doing.
 
-   Type: boolean
+174. $nntp_newsrc
 
-   Default: yes
+   Type: path
 
-   When unset, non MIME-compliant messages that doesn't have any charset
-   indication in the ``Content-Type:'' header field can be displayed (non
-   MIME-compliant messages are often generated by old mailers or buggy
-   mailers like MS Outlook Express). See also $assumed_charset.
+   Default: "~/.newsrc"
 
-   This option also replaces linear-white-space between encoded-word and
-   *text to a single space to prevent the display of MIME-encoded
-   ``Subject:'' header field from being devided into multiple lines.
+   Availability: NNTP
 
-328. $strict_threads
+   This file contains information about subscribed newsgroup and articles
+   read so far.
 
-   Type: boolean
+   To ease the use of multiple news servers, the following
+   printf(3)-style sequence is understood:
 
-   Default: no
+%s      newsserver name
 
-   If set, threading will only make use of the ``In-Reply-To:'' and
-   ``References:'' header fields when you ``$sort'' by message threads. By
-   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. See also ``$sort_re'' for a less drastic
-   way of controlling this behaviour.
+175. $nntp_pass
 
-329. $strip_was
+   Type: string
 
-   Type: boolean
+   Default: ""
 
-   Default: no
+   Availability: NNTP
 
-   When set, Mutt-ng will remove the trailing part of the ``Subject:'' line
-   which matches $strip_was_regex when replying. This is useful to properly
-   react on subject changes and reduce ``subject noise.'' (esp. in Usenet)
+   Your password for NNTP account.
 
-330. $strip_was_regex
+   _N_o_t_e_: Storing passwords in a configuration file presents a security
+   risk since the superuser of your machine may read it regardless of the
+   file's permissions.
 
-   Type: regular expression
+176. $nntp_post_moderated
 
-   Default: "\([Ww][Aa][RrSs]: .*\)[ ]*$"
+   Type: quadoption
 
-   When non-empty and $strip_was is set, Mutt-ng will remove this trailing
-   part of the ``Subject'' line when replying if it won't be empty
-   afterwards.
+   Default: ask-yes
 
-331. $stuff_quoted
+   Availability: NNTP
 
-   Type: boolean
+   If set to _y_e_s, Mutt-ng will post articles to newsgroup that have not
+   permissions to post (e.g. moderated).
 
-   Default: no
+   _N_o_t_e_: if the newsserver does not support posting to that newsgroup or
+   a group is totally read-only, that posting will not have any effect.
 
-   If set, attachments with flowed format will have their quoting
-   ``stuffed'', i.e. a space will be inserted between the quote characters
-   and the actual text.
+177. $nntp_reconnect
 
-332. $suspend
+   Type: quadoption
 
-   Type: boolean
+   Default: ask-yes
 
-   Default: yes
+   Availability: NNTP
 
-   When unset, Mutt-ng won't stop when the user presses the terminal's susp
-   key, usually CTRL+Z. This is useful if you run Mutt-ng inside an xterm
-   using a command like ``xterm -e muttng.''
+   Controls whether or not Mutt-ng will try to reconnect to a newsserver
+   when the was connection lost.
 
-333. $text_flowed
+178. $nntp_save_unsubscribed
 
    Type: boolean
 
    Default: no
 
-   When set, Mutt-ng will generate text/plain; format=flowed attachments.
-   This format is easier to handle for some mailing software, and generally
-   just looks like ordinary text. To actually make use of this format's
-   features, you'll need support in your editor.
+   Availability: NNTP
 
-   Note that $indent_string is ignored when this option is set.
+   When _s_e_t, info about unsubscribed newsgroups will be saved into the
+   ``newsrc'' file and into the news cache.
 
-334. $thorough_search
+179. $nntp_show_new_news
 
    Type: boolean
 
-   Default: no
+   Default: yes
 
-   Affects the ~b and ~h search operations described in section ``patterns''
-   above. If set, the headers and attachments of messages to be searched are
-   decoded before searching. If unset, messages are searched as they appear
-   in the folder.
+   Availability: NNTP
+
+   If _s_e_t, the newsserver will be asked for new newsgroups on entering
+   the browser. Otherwise, it will be done only once for a newsserver.
+   Also controls whether or not the number of new articles of subscribed
+   newsgroups will be checked.
 
-335. $thread_received
+180. $nntp_show_only_unread
 
    Type: boolean
 
    Default: no
 
-   When set, Mutt-ng uses the date received rather than the date sent to
-   thread messages by subject.
-
-336. $tilde
+   Availability: NNTP
 
-   Type: boolean
+   If _s_e_t, only subscribed newsgroups that contain unread articles will
+   be displayed in the newsgroup browser.
 
-   Default: no
+181. $nntp_user
 
-   When set, the internal-pager will pad blank lines to the bottom of the
-   screen with a tilde (~).
+   Type: string
 
-337. $timeout
+   Default: ""
 
-   Type: number
+   Availability: NNTP
 
-   Default: 600
+   Your login name on the NNTP server. If _u_n_s_e_t and the server requires
+   authentification, Mutt-ng will prompt you for your account name.
 
-   This variable controls the number of seconds Mutt-ng will wait for a key
-   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.
+182. $nntp_x_comment_to
 
-338. $tmpdir
+   Type: boolean
 
-   Type: path
+   Default: no
 
-   Default: ""
+   Availability: NNTP
 
-   This variable allows you to specify where Mutt-ng will place its temporary
-   files needed for displaying and composing messages. If this variable is
-   not set, the environment variable $TMPDIR is used. If $TMPDIR is not set
-   then "/tmp" is used.
+   If _s_e_t, Mutt-ng will add a ``X-Comment-To:'' header field (that
+   contains full name of the original article author) to articles that
+   you followup to.
 
-339. $to_chars
+183. $operating_system
 
    Type: string
 
-   Default: " +TCFL"
-
-   Controls the character used to indicate mail addressed to you. The first
-   character is the one used when the mail is NOT addressed to your address
-   (default: space). The second is used when you are the only recipient of
-   the message (default: +). The third is when your address appears in the
-   ``To:'' header field, but you are not the only recipient of the message
-   (default: T). The fourth character is used when your address is specified
-   in the ``Cc:'' header field, but you are not the only recipient. The fifth
-   character is used to indicate mail that was sent by you. The sixth
-   character is used to indicate when a mail was sent to a mailing-list
-   you're subscribe to (default: L).
+   Default: ""
 
-340. $trash
+   This specifies the operating system name for the User-Agent: header
+   field. If this is _u_n_s_e_t, it will be set to the operating system name
+   that uname(2) returns. If uname(2) fails, ``UNIX'' will be used.
 
-   Type: path
+   It may, for example, look as: ``mutt-ng 1.5.9i (Linux)''.
 
-   Default: ""
+184. $pager
 
-   If set, this variable specifies the path of the trash folder where the
-   mails marked for deletion will be moved, instead of being irremediably
-   purged.
+   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.
+   Default: "builtin"
 
-341. $tunnel
+   This variable specifies which pager you would like to use to view
+   messages. ``builtin'' means to use the builtin pager, otherwise this
+   variable should specify the pathname of the external pager you would
+   like to use.
 
-   Type: string
+   Using an external pager may have some disadvantages: Additional
+   keystrokes are necessary because you can't call Mutt-ng functions
+   directly from the pager, and screen resizes cause lines longer than
+   the screen width to be badly formatted in the help menu.
 
-   Default: ""
+185. $pager_context
 
-   Setting this variable will cause Mutt-ng to open a pipe to a command
-   instead of a raw socket. You may be able to use this to set up
-   preauthenticated connections to your IMAP/POP3 server. Example:
+   Type: number
 
-   tunnel="ssh -q mailhost.net /usr/local/libexec/imapd"
+   Default: 0
 
-   Note: For this example to work you must be able to log in to the remote
-   machine without having to enter a password.
+   This variable controls the number of lines of context that are given
+   when displaying the next or previous page in the internal pager. By
+   default, Mutt-ng will display the line after the last one on the
+   screen at the top of the next page (0 lines of context).
 
-342. $umask
+186. $pager_format
 
-   Type: number
+   Type: string
 
-   Default: 0077
+   Default: "-%Z- %C/%m: %-20.20n %s"
 
-   This sets the umask that will be used by Mutt-ng when creating all kinds
-   of files. If unset, the default value is 077.
+   This variable controls the format of the one-line message ``status''
+   displayed before each message in either the internal or an external
+   pager. The valid sequences are listed in the ``$$iinnddeexx__ffoorrmmaatt''
+   section.
 
-343. $uncollapse_jump
+187. $pager_index_lines
 
-   Type: boolean
+   Type: number
 
-   Default: no
+   Default: 0
 
-   When set, Mutt-ng will jump to the next unread message, if any, when the
-   current thread is uncollapsed.
+   Determines the number of lines of a mini-index which is shown when in
+   the pager. The current message, unless near the top or bottom of the
+   folder, will be roughly one third of the way down this mini-index,
+   giving the reader the context of a few messages before and after the
+   message. This is useful, for example, to determine how many messages
+   remain to be read in the current thread. One of the lines is reserved
+   for the status bar from the index, so a _p_a_g_e_r___i_n_d_e_x___l_i_n_e_s of 6 will
+   only show 5 lines of the actual index. A value of 0 results in no
+   index being shown. If the number of messages in the current folder is
+   less than _p_a_g_e_r___i_n_d_e_x___l_i_n_e_s, then the index will only use as many
+   lines as it needs.
 
-344. $use_8bitmime
+188. $pager_stop
 
    Type: boolean
 
    Default: no
 
-   Warning: do not set this variable unless you are using a version of
-   sendmail which supports the -B8BITMIME flag (such as sendmail 8.8.x) or in
-   connection with the SMTP support via libESMTP. Otherwise you may not be
-   able to send mail.
-
-   When set, Mutt-ng will either invoke ``$sendmail'' with the -B8BITMIME
-   flag when sending 8-bit messages to enable ESMTP negotiation or tell
-   libESMTP to do so.
+   When _s_e_t, the internal-pager will _n_o_t move to the next message when
+   you are at the end of a message and invoke the _n_e_x_t_-_p_a_g_e function.
 
-345. $use_domain
+189. $pgp_auto_decode
 
    Type: boolean
 
-   Default: yes
+   Default: no
 
-   When set, Mutt-ng will qualify all local addresses (ones without the @host
-   portion) with the value of ``$hostname''. If unset, no addresses will be
-   qualified.
+   If _s_e_t, Mutt-ng will automatically attempt to decrypt traditional PGP
+   messages whenever the user performs an operation which ordinarily
+   would result in the contents of the message being operated on. For
+   example, if the user displays a pgp-traditional message which has not
+   been manually checked with the check-traditional-pgp function, Mutt-ng
+   will automatically check the message for traditional pgp.
 
-346. $use_envelope_from
+190. $pgp_autoinline
 
    Type: boolean
 
    Default: no
 
-   When set, Mutt-ng will use ``$envelope_from_address'' as the envelope
-   sender if that is set, otherwise it will attempt to derive it from the
-   "From:" header.
-
-   Note: This information is passed to sendmail command using the "-f"
-   command line switch and passed to the SMTP server for libESMTP (if support
-   is compiled in).
-
-347. $use_from
-
-   Type: boolean
+   This option controls whether Mutt-ng generates old-style inline
+   (traditional) PGP encrypted or signed messages under certain
+   circumstances. This can be overridden by use of the _p_g_p_-_m_e_n_u, when
+   inline is not required.
 
-   Default: yes
+   Note that Mutt-ng might automatically use PGP/MIME for messages which
+   consist of more than a single MIME part. Mutt-ng can be configured to
+   ask before sending PGP/MIME messages when inline (traditional) would
+   not work. See also: ``$$ppggpp__mmiimmee__aauuttoo''.
 
-   When set, Mutt-ng will generate the ``From:'' header field when sending
-   messages. If unset, no ``From:'' header field will be generated unless the
-   user explicitly sets one using the ``my_hdr'' command.
+   Also note that using the old-style PGP message format is
+   _s_t_r_o_n_g_l_y_d_e_p_r_e_c_a_t_e_d. (PGP only)
 
-348. $use_idn
+191. $pgp_check_exit
 
    Type: boolean
 
    Default: yes
 
-   Availability: IDN
-
-   When set, Mutt-ng will show you international domain names decoded.
+   If _s_e_t, Mutt-ng will check the exit code of the PGP subprocess when
+   signing or encrypting. A non-zero exit code means that the subprocess
+   failed. (PGP only)
 
-   Note: You can use IDNs for addresses even if this is unset. This variable
-   only affects decoding.
+192. $pgp_clearsign_command
 
-349. $use_ipv6
+   Type: string
 
-   Type: boolean
+   Default: ""
 
-   Default: yes
+   This format is used to create a old-style ``clearsigned'' PGP message.
 
-   When set, Mutt-ng will look for IPv6 addresses of hosts it tries to
-   contact. If this option is unset, Mutt-ng will restrict itself to IPv4
-   addresses. Normally, the default should work.
+   Note that the use of this format is _s_t_r_o_n_g_l_y_d_e_p_r_e_c_a_t_e_d. (PGP only)
 
-350. $visual
+193. $pgp_decode_command
 
-   Type: path
+   Type: string
 
    Default: ""
 
-   Specifies the visual editor to invoke when the ~v command is given in the
-   builtin editor.
+   This format strings specifies a command which is used to decode
+   application/pgp attachments.
 
-351. $wait_key
+   The PGP command formats have their own set of printf(3)-like
+   sequences:
 
-   Type: boolean
+   %p
+          Expands to PGPPASSFD=0 when a pass phrase is needed, to an
+          empty string otherwise. Note: This may be used with a %?
+          construct.
 
-   Default: yes
+   %f
+          Expands to the name of a file containing a message.
+
+   %s
+          Expands to the name of a file containing the signature part of
+          a multipart/signed attachment when verifying it.
 
-   Controls whether Mutt-ng will ask you to press a key after shell- escape,
-   pipe-message, pipe-entry, print-message, and print-entry commands.
+   %a
+          The value of $$ppggpp__ssiiggnn__aass.
 
-   It is also used when viewing attachments with ``auto_view'', provided that
-   the corresponding mailcap entry has a needsterminal flag, and the external
-   program is interactive.
+   %r
+          One or more key IDs.
 
-   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.
+   For examples on how to configure these formats for the various
+   versions of PGP which are floating around, see the pgp*.rc and gpg.rc
+   files in the samples/ subdirectory which has been installed on your
+   system alongside the documentation. (PGP only)
 
-352. $weed
+194. $pgp_decrypt_command
 
-   Type: boolean
+   Type: string
 
-   Default: yes
+   Default: ""
 
-   When set, Mutt-ng will weed headers when displaying, forwarding, printing,
-   or replying to messages.
+   This command is used to decrypt a PGP encrypted message. (PGP only)
 
-353. $wrap_search
+195. $pgp_encrypt_only_command
 
-   Type: boolean
+   Type: string
 
-   Default: yes
+   Default: ""
 
-   Controls whether searches wrap around the end of the mailbox.
+   This command is used to encrypt a body part without signing it. (PGP
+   only)
 
-   When set, searches will wrap around the first (or last) message. When
-   unset, searches will not wrap.
+196. $pgp_encrypt_sign_command
 
-354. $wrapmargin
+   Type: string
 
-   Type: number
+   Default: ""
 
-   Default: 0
+   This command is used to both sign and encrypt a body part. (PGP only)
 
-   Controls the size of the margin remaining at the right side of the
-   terminal when Mutt-ng's pager does smart wrapping.
+197. $pgp_entry_format
 
-355. $write_bcc
+   Type: string
 
-   Type: boolean
+   Default: "%4n %t%f %4l/0x%k %-4a %2c %u"
 
-   Default: yes
+   This variable allows you to customize the PGP key selection menu to
+   your personal taste. This string is similar to ``$$iinnddeexx__ffoorrmmaatt'', but
+   has its own set of printf(3)-like sequences:
 
-   Controls whether Mutt-ng writes out the Bcc header when preparing messages
-   to be sent. Exim users may wish to unset this.
+   %n
+          number
 
-356. $write_inc
+   %k
+          key id
 
-   Type: number
+   %u
+          user id
 
-   Default: 10
+   %a
+          algorithm
 
-   When writing a mailbox, a message will be printed every write_inc messages
-   to indicate progress. If set to 0, only a single message will be displayed
-   before writing a mailbox.
+   %l
+          key length
 
-   Also see the ``$read_inc'' variable.
+   %f
+          flags
 
-357. $xterm_icon
+   %c
+          capabilities
 
-   Type: string
+   %t
+          trust/validity of the key-uid association
 
-   Default: "M%?n?AIL&ail?"
+   %[<s>]
+          date of the key where <s> is an strftime(3) expression
 
-   Controls the format of the X11 icon title, as long as $xterm_set_titles is
-   set. This string is identical in formatting to the one used by
-   ``$status_format''.
+   (PGP only)
 
-358. $xterm_leave
+198. $pgp_export_command
 
    Type: string
 
    Default: ""
 
-   If $xterm_set_titles is set, this string will be used to set the title
-   when leaving Mutt-ng. For terminal-based programs, there's no easy and
-   portable way to read the current title so Mutt-ng cannot read it upon
-   startup and restore it when exiting.
-
-   Based on the xterm FAQ, the following might work:
-
-   set xterm_leave = "`test x$DISPLAY != x && xprop -id $WINDOWID | grep
-   WM_NAME | cut -d '"' -f 2`"
+   This command is used to export a public key from the user's key ring.
+   (PGP only)
 
-359. $xterm_set_titles
+199. $pgp_getkeys_command
 
-   Type: boolean
+   Type: string
 
-   Default: no
+   Default: ""
 
-   Controls whether Mutt-ng sets the xterm title bar and icon name (as long
-   as you're in an appropriate terminal). The default must be unset to force
-   in the validity checking.
+   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)
 
-360. $xterm_title
+200. $pgp_good_sign
 
-   Type: string
+   Type: regular expression
 
-   Default: "Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?"
+   Default: ""
 
-   Controls the format of the title bar of the xterm provided that
-   $xterm_set_titles has been set. This string is identical in formatting to
-   the one used by ``$status_format''.
+   If you assign a text to this variable, then a PGP signature is only
+   considered verified if the output from $$ppggpp__vveerriiffyy__ccoommmmaanndd contains
+   the text. Use this variable if the exit code from the command is 0
+   even for bad signatures. (PGP only)
 
-5. Functions
+201. $pgp_ignore_subkeys
 
-   The following is the list of available functions listed by the mapping in
-   which they are available. The default key setting is given, and an
-   explanation of what the function does. The key bindings of these functions
-   can be changed with the bind command.
+   Type: boolean
 
-  5.1. generic
+   Default: yes
 
-   The generic menu is not a real menu, but specifies common functions (such
-   as movement) available in all menus except for pager and editor. Changing
-   settings for this menu will affect the default bindings for all menus
-   (except as noted).
+   Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys.
+   Instead, the principal key will inherit the subkeys' capabilities.
+   _U_n_s_e_t this if you want to play interesting key selection games. (PGP
+   only)
 
-   Table 7.4. Reference: Default Generic Function Bindings
+202. $pgp_import_command
 
-   Function          Default Key Description
-   <bottom-page>     L           move to the bottom of the page
-   <current-bottom>              move current entry to bottom of page
-   <current-middle>              move current entry to middle of page
-   <current-top>                 move current entry to top of page
-   <enter-command>   :           enter a muttngrc command
-   <exit>            q           exit this menu
-   <first-entry>     =           move to the first entry
-   <half-down>       ]           scroll down 1/2 page
-   <half-up>         [           scroll up 1/2 page
-   <help>            ?           this screen
-   <jump>            number      jump to an index number
-   <last-entry>      *           move to the last entry
-   <middle-page>     M           move to the middle of the page
-   <next-entry>      j           move to the next entry
-   <next-line>       >           scroll down one line
-   <next-page>       z           move to the next page
-   <previous-entry>  k           move to the previous entry
-   <previous-line>   >           scroll up one line
-   <previous-page>   Z           move to the previous page
-   <refresh>         C-L         clear and redraw the screen
-   <search>          /           search for a regular expression
-   <search-next>     n           search for next match
-   <search-opposite>             search for next match in opposite direction
-   <search-reverse>  E-/         search backwards for a regular expression
-   <select-entry>    Return      select the current entry
-   <shell-escape>    !           run a program in a subshell
-   <tag-entry>       t           toggle the tag on the current entry
-   <tag-prefix>      ;           apply next command to tagged entries
-   <tag-prefix-cond>             apply next function ONLY to tagged messages
-   <top-page>        H           move to the top of the page
-   <what-key>                    display the keycode for a key press
-
-  5.2. index
-
-   Table 7.5. Reference: Default Index Function Bindings
-
-   Function                   Default Key Description
-   <bounce-message>           b           remail a message to another user
-   <change-folder>            c           open a different folder
-   <change-folder-readonly>   E-c         open a different folder in read
-                                          only mode
-   <check-traditional-pgp>    E-P         check for classic pgp
-   <clear-flag>               W           clear a status flag from a message
-   <copy-message>             C           copy a message to a file/mailbox
-   <create-alias>             a           create an alias from a message
-                                          sender
-   <decode-copy>              E-C         decode a message and copy it to a
-                                          file/mailbox
-   <decode-save>              E-s         decode a message and save it to a
-                                          file/mailbox
-   <delete-message>           d           delete the current entry
-   <delete-pattern>           D           delete messages matching a pattern
-   <delete-subthread>         E-d         delete all messages in subthread
-   <delete-thread>            C-D         delete all messages in thread
-   <display-address>          @           display full address of sender
-   <display-toggle-weed>      h           display message and toggle header
-                                          weeding
-   <display-message>          Return      display a message
-   <edit>                     e           edit the current message
-   <edit-type>                C-E         edit the current message's
-                                          Content-Type
-   <exit>                     x           exit without saving changes
-   <extract-keys>             C-K         extract PGP public keys
-   <fetch-mail>               G           retrieve mail from POP server
-   <flag-message>             F           toggle a message's 'important' flag
-   <forget-passphrase>        C-F         wipe PGP passphrase from memory
-   <forward-message>          f           forward a message with comments
-   <group-reply>              g           reply to all recipients
-   <limit>                    l           show only messages matching a
-                                          pattern
-   <list-reply>               L           reply to specified mailing list
-   <mail>                     m           compose a new mail message
-   <mail-key>                 E-k         mail a PGP public key
-   <next-new>                             jump to the next new message
-   <next-new-then-unread>     Tab         jump to the next new or unread
-                                          message
-   <next-subthread>           E-n         jump to the next subthread
-   <next-thread>              C-N         jump to the next thread
-   <next-undeleted>           j           move to the next undeleted message
-   <next-unread>                          jump to the next unread message
-   <parent-message>           P           jump to parent message in thread
-   <pipe-message>             |           pipe message/attachment to a shell
-                                          command
-   <previous-new>                         jump to the previous new message
-   <previous-new-then-unread> E-Tab       jump to the previous new or unread
-                                          message
-   <previous-page>            Z           move to the previous page
-   <previous-subthread>       E-p         jump to previous subthread
-   <previous-thread>          C-P         jump to previous thread
-   <previous-undeleted>       k           move to the last undelete message
-   <previous-unread>                      jump to the previous unread message
-   <print-message>            p           print the current entry
-   <query>                    Q           query external program for
-                                          addresses
-   <quit>                     q           save changes to mailbox and quit
-   <read-subthread>           E-r         mark the current subthread as read
-   <read-thread>              C-R         mark the current thread as read
-   <recall-message>           R           recall a postponed message
-   <reply>                    r           reply to a message
-   <resend-message>           E-e         resend message and preserve MIME
-                                          structure
-   <save-message>             s           save message/attachment to a file
-   <set-flag>                 w           set a status flag on a message
-   <show-version>             V           show the Mutt-ng version number and
-                                          date
-   <show-limit>               E-l         show currently active limit
-                                          pattern, if any
-   <sort-mailbox>             o           sort messages
-   <sort-reverse>             O           sort messages in reverse order
-   <sync-mailbox>             $           save changes to mailbox
-   <tag-pattern>              T           tag messages matching a pattern
-   <tag-thread>               E-t         tag/untag all messages in the
-                                          current thread
-   <toggle-new>               N           toggle a message's 'new' flag
-   <toggle-write>             %           toggle whether the mailbox will be
-                                          rewritten
-   <undelete-message>         u           undelete the current entry
-   <undelete-pattern>         U           undelete messages matching a
-                                          pattern
-   <undelete-subthread>       E-u         undelete all messages in subthread
-   <undelete-thread>          C-U         undelete all messages in thread
-   <untag-pattern>            C-T         untag messages matching a pattern
-   <view-attachments>         v           show MIME attachments
-
-  5.3. pager
-
-   Table 7.6. Reference: Default Pager Function Bindings
-
-   Function                   Default Key Description
-   <bottom>                               jump to the bottom of the message
-   <bounce-message>           b           remail a message to another user
-   <change-folder>            c           open a different folder
-   <change-folder-readonly>   E-c         open a different folder in read
-                                          only mode
-   <check-traditional-pgp>    E-P         check for classic pgp
-   <copy-message>             C           copy a message to a file/mailbox
-   <create-alias>             a           create an alias from a message
-   <senderdecode-copy>        E-C         decode a message and copy it to a
-                                          file/mailbox
-   <decode-save>              E-s         decode a message and save it to a
-                                          file/mailbox
-   <delete-message>           d           delete the current entry
-   <delete-subthread>         E-d         delete all messages in subthread
-   <delete-thread>            C-D         delete all messages in thread
-   <display-address>          @           display full address of sender
-   <display-toggle-weed>      h           display message and toggle header
-                                          weeding
-   <edit>                     e           edit the current message
-   <edit-type>                C-E         edit the current message's
-                                          Content-Type
-   <enter-command>            :           enter a muttngrc command
-   <exit>                     i           return to the main-menu
-   <extract-keys>             C-K         extract PGP public keys
-   <flag-message>             F           toggle a message's 'important' flag
-   <forget-passphrase>        C-F         wipe PGP passphrase from memory
-   <forward-message>          f           forward a message with comments
-   <group-reply>              g           reply to all recipients
-   <half-up>                              move up one-half page
-   <half-down>                            move down one-half page
-   <help>                     ?           this screen
-   <list-reply>               L           reply to specified mailing list
-   <mail>                     m           compose a new mail message
-   <mail-key>                 E-k         mail a PGP public key
-   <mark-as-new>              N           toggle a message's 'new' flag
-   <next-line>                Return      scroll down one line
-   <next-entry>               J           move to the next entry
-   <next-new>                             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>           E-n         jump to the next subthread
-   <next-thread>              C-N         jump to the next thread
-   <next-undeleted>           j           move to the next undeleted message
-   <next-unread>                          jump to the next unread message
-   <parent-message>           P           jump to parent message in thread
-   <pipe-message>             |           pipe message/attachment to a shell
-                                          command
-   <previous-line>            BackSpace   scroll up one line
-   <previous-entry>           K           move to the previous entry
-   <previous-new>                         jump to the previous new message
-   <previous-new-then-unread>             jump to the previous new or unread
-                                          message
-   <previous-page>            -           move to the previous page
-   <previous-subthread>       E-p         jump to previous subthread
-   <previous-thread>          C-P         jump to previous thread
-   <previous-undeleted>       k           move to the last undelete message
-   <previous-unread>                      jump to the previous unread message
-   <print-message>            p           print the current entry
-   <quit>                     Q           save changes to mailbox and quit
-   <read-subthread>           E-r         mark the current subthread as read
-   <read-thread>              C-R         mark the current thread as read
-   <recall-message>           R           recall a postponed message
-   <redraw-screen>            C-L         clear and redraw the screen
-   <reply>                    r           reply to a message
-   <save-message>             s           save message/attachment to a file
-   <search>                   /           search for a regular expression
-   <search-next>              n           search for next match
-   <search-opposite>                      search for next match in opposite
-                                          direction
-   <search-reverse>           E-/         search backwards for a regular
-                                          expression
-   <search-toggle>            \           toggle search pattern coloring
-   <shell-escape>             !           invoke a command in a subshell
-   <show-version>             V           show the Mutt-ng version number and
-                                          date
-   <skip-quoted>              S           skip beyond quoted text
-   <sync-mailbox>             $           save changes to mailbox
-   <tag-message>              t           tag a message
-   <toggle-quoted>            T           toggle display of quoted text
-   <top>                      ^           jump to the top of the message
-   <undelete-message>         u           undelete the current entry
-   <undelete-subthread>       E-u         undelete all messages in subthread
-   <undelete-thread>          C-U         undelete all messages in thread
-   <view-attachments>         v           show MIME attachments
-
-  5.4. alias
-
-   Table 7.7. Reference: Default Alias Menu Function Bindings
+   Type: string
 
-   Function         Default Key Description
-   <search>         /           search for a regular expression
-   <search-next>    n           search for next match
-   <search-reverse> E-/         search backwards for a regular expression
+   Default: ""
 
-  5.5. query
+   This command is used to import a key from a message into the user's
+   public key ring. (PGP only)
 
-   Table 7.8. Reference: Default Query Menu Function Bindings
+203. $pgp_list_pubring_command
 
-   Function          Default Key Description
-   <create-alias>    a           create an alias from a message sender
-   <mail>            m           compose a new mail message
-   <query>           Q           query external program for addresses
-   <query-append>    A           append new query results to current results
-   <search>          /           search for a regular expression
-   <search-next>     n           search for next match
-   <search-opposite>             search for next match in opposite direction
-   <search-reverse>  E-/         search backwards for a regular expression
+   Type: string
 
-  5.6. attach
-
-   Table 7.9. Reference: Default Attachment Menu Function Bindings
-
-   Function              Default Key Description
-   <bounce-message>      b           remail a message to another user
-   <collapse-parts>      v           toggle display of subparts
-   <delete-entry>        d           delete the current entry
-   <display-toggle-weed> h           display message and toggle header
-                                     weeding
-   <edit-type>           C-E         edit the current entry's Content-Type
-   <extract-keys>        C-K         extract PGP public keys
-   <forward-message>     f           forward a message with comments
-   <group-reply>         g           reply to all recipients
-   <list-reply>          L           reply to specified mailing list
-   <pipe-entry>          |           pipe message/attachment to a shell
-                                     command
-   <print-entry>         p           print the current entry
-   <reply>               r           reply to a message
-   <resend-message>      E-e         resend message and preserve MIME
-                                     structure
-   <save-entry>          s           save message/attachment to a file
-   <undelete-entry>      u           undelete the current entry
-   <view-attach>         Return      view attachment using mailcap entry if
-                                     necessary
-   <view-mailcap>        m           force viewing of attachment using
-                                     mailcap
-   <view-text>           T           view attachment as text
-
-  5.7. compose
-
-   Table 7.10. Reference: Default Compose Menu Function Bindings
-
-   Function              Default Key Description
-   <attach-file>         a           attach a file(s) to this message
-   <attach-message>      A           attach message(s) to this message
-   <attach-key>          E-k         attach a PGP public key
-   <copy-file>           C           save message/attachment to a file
-   <detach-file>         D           delete the current entry
-   <display-toggle-weed> h           display message and toggle header
-                                     weeding
-   <edit-bcc>            b           edit the BCC list
-   <edit-cc>             c           edit the CC list
-   <edit-description>    d           edit attachment description
-   <edit-encoding>       C-E         edit attachment transfer-encoding
-   <edit-fcc>            f           enter a file to save a copy of this
-                                     message in
-   <edit-from>           E-f         edit the from: field
-   <edit-file>           C-X e       edit the file to be attached
-   <edit-headers>        E           edit the message with headers
-   <edit>                e           edit the message
-   <edit-mime>           m           edit attachment using mailcap entry
-   <edit-reply-to>       r           edit the Reply-To field
-   <edit-subject>        s           edit the subject of this message
-   <edit-to>             t           edit the TO list
-   <edit-type>           C-T         edit attachment type
-   <filter-entry>        F           filter attachment through a shell
-                                     command
-   <forget-passphrase>   C-F         wipe PGP passphrase from memory
-   <ispell>              i           run ispell on the message
-   <new-mime>            n           compose new attachment using mailcap
-                                     entry
-   <pgp-menu>            p           show PGP options
-   <pipe-entry>          |           pipe message/attachment to a shell
-                                     command
-   <postpone-message>    P           save this message to send later
-   <print-entry>         l           print the current entry
-   <rename-file>         R           rename/move an attached file
-   <send-message>        y           send the message
-   <toggle-unlink>       u           toggle whether to delete file after
-                                     sending it
-   <view-attach>         Return      view attachment using mailcap entry if
-                                     necessary
-   <write-fcc>           w           write the message to a folder
-
-  5.8. postpone
-
-   Table 7.11. Reference: Default Postpone Menu Function Bindings
+   Default: ""
 
-   Function         Default Key Description
-   <delete-entry>   d           delete the current entry
-   <undelete-entry> u           undelete the current entry
+   This command is used to list the public key ring's contents. The
+   output format must be analogous to the one used by gpg --list-keys
+   --with-colons.
 
-  5.9. browser
+   This format is also generated by the pgpring utility which comes with
+   Mutt-ng. (PGP only)
 
-   Table 7.12. Reference: Default Browser Menu Function Bindings
+204. $pgp_list_secring_command
 
-   Function            Default Key Description
-   <change-dir>        c           change directories
-   <check-new>         Tab         check mailboxes for new mail
-   <enter-mask>        m           enter a file mask
-   <search>            /           search for a regular expression
-   <search-next>       n           search for next match
-   <search-reverse>    E-/         search backwards for a regular expression
-   <select-new>        N           select a new file in this directory
-   <sort>              o           sort messages
-   <sort-reverse>      O           sort messages in reverse order
-   <toggle-mailboxes>  Tab         toggle whether to browse mailboxes or all
-                                   files
-   <view-file>         Space       view file
-   <subscribe>         s           subscribe to current mailbox (IMAP Only)
-   <unsubscribe>       u           unsubscribe to current mailbox (IMAP Only)
-   <toggle-subscribed> T           toggle view all/subscribed mailboxes (IMAP
-                                   Only)
+   Type: string
 
-  5.10. pgp
+   Default: ""
 
-   Table 7.13. Reference: Default PGP Menu Function Bindings
+   This command is used to list the secret key ring's contents. The
+   output format must be analogous to the one used by gpg --list-keys
+   --with-colons.
 
-   Function     Default Key Description
-   <view-name>  %           view the key's user id
-   <verify-key> c           verify a PGP public key
+   This format is also generated by the pgpring utility which comes with
+   Mutt-ng. (PGP only)
 
-  5.11. editor
+205. $pgp_long_ids
 
-   Table 7.14. Reference: Default Editor Function Bindings
+   Type: boolean
 
-   Function          Default Key Description
-   <backspace>       BackSpace   delete the char in front of the cursor
-   <backward-char>   C-B         move the cursor one character to the left
-   <backward-word>   E-b         move the cursor to the previous word
-   <bol>             C-A         jump to the beginning of the line
-   <buffy-cycle>     Space       cycle among incoming mailboxes
-   <capitalize-word> E-c         uppercase the first character in the word
-   <complete>        Tab         complete filename or alias
-   <complete-query>  C-T         complete address with query
-   <delete-char>     C-D         delete the char under the cursor
-   <downcase-word>   E-l         lowercase all characters in current word
-   <eol>             C-E         jump to the end of the line
-   <forward-char>    C-F         move the cursor one character to the right
-   <forward-word>    E-f         move the cursor to the next word
-   <history-down>                scroll down through the history list
-   <history-up>                  scroll up through the history list
-   <kill-eol>        C-K         delete chars from cursor to end of line
-   <kill-eow>        E-d         delete chars from cursor to end of word
-   <kill-line>       C-U         delete all chars on the line
-   <kill-word>       C-W         delete the word in front of the cursor
-   <quote-char>      C-V         quote the next typed key
-   <transpose-chars>             transpose character under cursor with
-                                 previous
-   <upcase-word>     E-u         uppercase all characters in current word
+   Default: no
 
-  5.12. sidebar
+   If _s_e_t, use 64 bit PGP key IDs. _U_n_s_e_t uses the normal 32 bit Key IDs.
+   (PGP only)
 
-   Table 7.15. Referene: Default Sidebar Function Bindings
+206. $pgp_mime_auto
 
-   Key Function              Description
-       <sidebar-scroll-up>   Scrolls the mailbox list up 1 page
-       <sidebar-scroll-down> Scrolls the mailbox list down 1 page
-       <sidebar-next>        Highlights the next mailbox
-       <sidebar-next-new>    Highlights the next mailbox with new mail
-       <sidebar-previous>    Highlights the previous mailbox
-       <sidebar-open>        Opens the currently highlighted mailbox
+   Type: quadoption
 
-Appendix A. Acknowledgments
+   Default: ask-yes
 
-   Kari Hurtta <kari.hurtta@fmi.fi> co-developed the original MIME >parsing
-   code back in the ELM-ME days.
+   This option controls whether Mutt-ng will prompt you for automatically
+   sending a (signed/encrypted) message using PGP/MIME when inline
+   (traditional) fails (for any reason).
 
-   The following people have been very helpful to the development of Mutt
-   (sorted by surnames):
+   Also note that using the old-style PGP message format is
+   _s_t_r_o_n_g_l_y_d_e_p_r_e_c_a_t_e_d. (PGP only)
 
-     o Vikas Agnihotri <vikasa@writeme.com>
-     o Francois Berjon < Francois.Berjon@aar.alcatel-alsthom.fr>
-     o Aric Blumer <aric@fore.com>
-     o John Capo <jc@irbs.com>
-     o David Champion <dgc@uchicago.edu>
-     o Brendan Cully <brendan@kublai.com>
-     o Liviu Daia <daia@stoilow.imar.ro>
-     o Thomas E. Dickey <dickey@herndon4.his.com>
-     o David DeSimone <fox@convex.hp.com>
-     o Nickolay N. Dudorov <nnd@wint.itfs.nsk.su>
-     o Ruslan Ermilov <ru@freebsd.org>
-     o Edmund Grimley Evans <edmundo@rano.org>
-     o Michael Finken <finken@conware.de>
-     o Sven Guckes <guckes@math.fu-berlin.de>
-     o Lars Hecking <lhecking@nmrc.ie>
-     o Mark Holloman <holloman@nando.net>
-     o Andreas Holzmann <holzmann@fmi.uni-passau.de>
-     o Marco d'Itri <md@linux.it>
-     o BjÃ¶rn Jacke <bjacke@suse.com>
-     o Byrial Jensen <byrial@image.dk>
-     o David Jeske <jeske@igcom.net>
-     o Christophe Kalt <kalt@hugo.int-evry.fr>
-     o Tommi Komulainen <Tommi.Komulainen@iki.fi>
-     o Felix von Leitner (a.k.a ``Fefe'') < leitner@math.fu-berlin.de >
-     o Brandon Long <blong@fiction.net>
-     o Jimmy MÃ¤keÃ¤ <jmy@flashback.net>
-     o Lars Marowsky-Bree <lmb@pointer.in-minden.de>
-     o Thomas ``Mike'' Michlmayr <mike@cosy.sbg.ac.at>
-     o Andrew W. Nosenko <awn@bcs.zp.ua>
-     o David O'Brien <obrien@Nuxi.cs.ucdavis.edu>
-     o Clint Olsen <olsenc@ichips.intel.com>
-     o Park Myeong Seok <pms@romance.kaist.ac.kr>
-     o Thomas Parmelan <tom@ankh.fr.eu.org>
-     o Ollivier Robert <roberto@keltia.freenix.fr>
-     o Thomas Roessler <roessler@does-not-exist.org>
-     o Roland Rosenfeld <roland@spinnaker.de>
-     o TAKIZAWA Takashi <taki@luna.email.ne.jp>
-     o Allain Thivillon <Allain.Thivillon@alma.fr>
-     o Gero Treuner <gero@70t.de>
-     o Vsevolod Volkov <vvv@lucky.net>
-     o Ken Weinert <kenw@ihs.com>
+207. $pgp_replyinline
 
-   Mutt-ng is developed by the following people:
+   Type: boolean
 
-     o Andreas Krennmair <ak@synflood.at>
-     o Nico Golde <nico@ngolde.de>
-     o Rocco Rutte <pdmef@cs.tu-berlin.de>
+   Default: no
 
-   The following people have been very helpful to the development of Mutt-ng
-   (sorted by surnames):
+   Setting this variable will cause Mutt-ng to always attempt to create
+   an inline (traditional) message when replying to a message which is
+   PGP encrypted/signed inline. This can be overridden by use of the
+   _p_g_p_-_m_e_n_u, when inline is not required. This option does not
+   automatically detect if the (replied-to) message is inline; instead it
+   relies on Mutt-ng internals for previously checked/flagged messages.
 
-     o Christian Gall <cg@cgall.de>
-     o Iain Lea <iain@bricbrac.de>
-     o Andreas Kneib <akneib@gmx.net>
-     o Felix Meinhold <felix.meinhold@gmx.net>
-     o Carsten Schoelzki <cjs@weisshuhn.de>
-     o Elimar Riesebieter <riesebie@lxtec.de>
+   Note that Mutt-ng might automatically use PGP/MIME for messages which
+   consist of more than a single MIME part. Mutt-ng can be configured to
+   ask before sending PGP/MIME messages when inline (traditional) would
+   not work. See also: ``$$ppggpp__mmiimmee__aauuttoo''.
 
-Appendix B. Hacking Documentation
+   Also note that using the old-style PGP message format is
+   _s_t_r_o_n_g_l_y_d_e_p_r_e_c_a_t_e_d. (PGP only)
 
-   This manual is written in XML and transformed via a XSLT stylesheet into
-   valid DocBook/XML and/or LaTeX to be again transformed via a XSLT
-   stylesheet into the final formats.
+208. $pgp_retainable_sigs
 
-   This two pass processing is required to keep the file size low and to
-   sanitize use, i.e. drastically lower the typing overhead.
+   Type: boolean
 
-   To achieve the latter, the sources come with a file called
-   muttng-manual.xsl introducing the muttng-doc namespace which offers the
-   following tags to be used (note: this is far from being complete, any help
-   towards consistency is highly appreciated).
+   Default: no
 
-   <muttng-doc:man name="" [sect=""]/>
+   If _s_e_t, signed and encrypted messages will consist of nested
+   multipart/signed and multipart/encrypted body parts.
 
-           References to manual pages. If the sect parameter is omitted,
-           it'll be 1 for the commands section. There's no auto-indexing yet.
+   This is useful for applications like encrypted and signed mailing
+   lists, where the outer layer (multipart/encrypted) can be easily
+   removed, while the inner multipart/signed part is retained. (PGP only)
 
-   <muttng-doc:envvar name=""/>
+209. $pgp_show_unusable
 
-           References to environment variables. The name parameter must
-           contain upper-case letters only without the dollar sign as it'll
-           be added automatically. Auto-indexing is done.
+   Type: boolean
 
-   <muttng-doc:hook name=""/>
+   Default: yes
 
-           References to hooks. The string -hook will be added automatically
-           to the value given in the name parameter. All entries will be
-           auto-indexed.
+   If _s_e_t, Mutt-ng will display non-usable keys on the PGP key selection
+   menu. This includes keys which have been revoked, have expired, or
+   have been marked as ``disabled'' by the user. (PGP only)
 
-   <muttng-doc:pattern name="" [full="1"]/>
+210. $pgp_sign_as
 
-           References to patterns. The name parameter must only contain the
-           letter/symbol for the pattern as the tilde symbol/equal sign will
-           be added automatically. Auto-indexing is done. If the full
-           parameter is given the equal sign as well as tilde will be printed
-           for a fully complete reference.
+   Type: string
 
-   <muttng-doc:key [mod="C|E"]>key</muttng-doc:key>
+   Default: ""
 
-           Referencing a key.. Because it's somewhat untrivial to always get
-           the right escaping for LaTeX, there's a tag for it. The optional
-           modifiers C or E stand for Control and Escape respectively. To
-           still allow escaping, the actual key sequences must be given
-           within the tag.
+   If you have more than one key pair, this option allows you to specify
+   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)
 
-   <muttng-doc:funcdef name=""/>
+211. $pgp_sign_command
 
-           Defining a command.. It's used to define a command with the name
-           given in the name parameter. The default key binding must be given
-           via <muttng-doc:key/> (see above). The string will be
-           automatically enclosed in <>. Auto-indexing is done. Also an
-           anchor with id func-[name] will be added with [name] being the
-           value of the name parameter.
+   Type: string
 
-   <muttng-doc:funcref name=""/>
+   Default: ""
 
-           References to functions.. This is practically the same as the
-           above except that there's no anchor defined.
+   This command is used to create the detached PGP signature for a
+   multipart/signed PGP/MIME body part. (PGP only)
 
-   <muttng-doc:vardef name=""/>
+212. $pgp_sort_keys
 
-           Defining a variable. This is to be used by makedoc only to define
-           a command with a given name and XML-normalized link given via id.
-           Auto-indexing is done. The name parameter's value will be prefixed
-           with a dollar sign as for environment variables.
+   Type: sort order
 
-   <muttng-doc:varref name=""/>
+   Default: address
 
-           References to variables. This practically is the same as above
-           except that the text inbetween won't be wrapped within a <sect1>
-           tag. Auto-indexing is the same as for the above. This one is
-           intended for manual use.
+   Specifies how the entries in the ``pgp keys'' menu are sorted. The
+   following are legal values:
 
-   <muttng-doc:web url""/>
+   address
+          sort alphabetically by user id
 
-           Pretty print a linked URL. As for E-Mail addresses where the text
-           (mostly) equals the link's target, URLs must be enclosed in <>
-           (also this reduced redudant URL typing).
+   keyid
+          sort alphabetically by key id
 
-   <muttng-doc:rfc num=""/>
+   date
+          sort by key creation date
 
-           References to RfC documents. Use this to produce links to RfC
-           document with number given as the num parameter. A link to
-           <http://www.faqs.org/> will be made. Auto-indexing is done under
-           RfC.
+   trust
+          sort by the trust of the key
 
-   <muttng-doc:cmddef name="" [noanchor="1"]/>
+   If you prefer reverse order of the above values, prefix it with
+   ``reverse-''. (PGP only)
 
-           Defining a configuration command. The name of the command is given
-           as the name parameter. In case a single command has multiple
-           possible calling sequences, specify noanchor="1" for subsequent
-           use. Auto-indexing is done. Specify the arguments within the tag.
+213. $pgp_strict_enc
 
-   <muttng-doc:cmdref name=""/>
+   Type: boolean
 
-           References to configuration commands. Use this to refer to
-           commands as it builds the proper internal reference name.
-           Auto-indexing is done.
+   Default: yes
 
-   <muttng-doc:lstconf/>, <muttng-doc:lstmail/>, <muttng-doc:lstshell/>
+   If _s_e_t, Mutt-ng will automatically encode PGP/MIME signed messages as
+   quoted-printable. Please note that unsetting this variable may lead to
+   problems with non-verifyable PGP signatures, so only change this if
+   you know what you are doing. (PGP only)
 
-           Screen layout by context. These are used to specify environments
-           for different types of screen output. For DocBook output, all of
-           these simply map to <screen/>. But as a possible future migration
-           to LaTeX may be ahead, different languages defined for the
-           listings.sty packages may be used to have proper syntax
-           highlighting for these so that there must be a context sensitive
-           distinction.
+214. $pgp_timeout
 
-   <muttng-doc:special [docbook=""] [latex=""]/>
+   Type: number
 
-           This is intended for specifying special strings for either
-           DocBook/XML or LaTeX.
+   Default: 300
 
-   Additional notes follow.
+   The number of seconds after which a cached passphrase will expire if
+   not used. Default: 300. (PGP only)
 
-     o To not fully bloat the XSL stylesheet procuding the LaTeX code, all
-       tables must have an attribute called texstr which is directly passed
-       to longtable.
+215. $pgp_use_gpg_agent
 
-Index
+   Type: boolean
 
-  Symbols
+   Default: no
 
-   ~$/ =$, Patterns
+   If _s_e_t, Mutt-ng will use a possibly-running gpg-agent process. (PGP
+   only)
 
-   ~*/ =*, Patterns
+216. $pgp_verify_command
 
-   ~=/ ==, Patterns
+   Type: string
 
-   ~A/ =A, Patterns
+   Default: ""
 
-   ~b/ =b, Complex Patterns, Patterns
+   This command is used to verify PGP signatures. (PGP only)
 
-   ~B/ =B, Patterns
+217. $pgp_verify_key_command
 
-   ~c/ =c, Patterns
+   Type: string
 
-   ~C/ =C, Patterns
+   Default: ""
 
-   ~d/ =d, Patterns and Dates, Patterns
+   This command is used to verify key information from the key selection
+   menu. (PGP only)
 
-   ~D/ =D, Patterns
+218. $pipe_decode
 
-   ~E/ =E, Patterns
+   Type: boolean
 
-   ~e/ =e, Patterns
+   Default: no
 
-   ~f/ =f, Complex Patterns, Patterns
+   Used in connection with the _p_i_p_e_-_m_e_s_s_a_g_e command. When _u_n_s_e_t, Mutt-ng
+   will pipe the messages without any preprocessing. When _s_e_t, Mutt-ng
+   will weed headers and will attempt to PGP/MIME decode the messages
+   first.
 
-   ~F/ =F, Patterns
+219. $pipe_sep
 
-   ~g/ =g, Patterns
+   Type: string
 
-   ~G/ =G, Patterns
+   Default: "\n"
 
-   ~H/ =H, Spam detection, Patterns
+   The separator to add between messages when piping a list of tagged
+   messages to an external Unix command.
 
-   ~h/ =h, Patterns
+220. $pipe_split
 
-   ~i/ =i, Patterns
+   Type: boolean
 
-   ~k/ =k, Patterns
+   Default: no
 
-   ~L/ =L, Patterns
+   Used in connection with the _p_i_p_e_-_m_e_s_s_a_g_e command and the ``tag-
+   prefix'' or ``tag-prefix-cond'' operators. If this variable is _u_n_s_e_t,
+   when piping a list of tagged messages Mutt-ng will concatenate the
+   messages and will pipe them as a single folder. When _s_e_t, Mutt-ng will
+   pipe the messages one by one. In both cases the messages are piped in
+   the current sorted order, and the ``$$ppiippee__sseepp'' separator is added
+   after each message.
 
-   ~l/ =l, Patterns
+221. $pop_auth_try_all
 
-   ~m/ =m, Patterns
+   Type: boolean
 
-   ~M/ =M, Patterns
+   Default: yes
 
-   ~n/ =n, Message Scoring, Patterns
+   Availability: POP
 
-   ~N/ =N, Patterns
+   If _s_e_t, Mutt-ng will try all available methods. When _u_n_s_e_t, Mutt-ng
+   will only fall back to other authentication methods if the previous
+   methods are unavailable. If a method is available but authentication
+   fails, Mutt-ng will not connect to the POP server.
 
-   ~O/ =O, Patterns
+222. $pop_authenticators
 
-   ~p/ =p, Patterns
+   Type: string
 
-   ~P/ =P, Patterns
+   Default: ""
 
-   ~Q/ =Q, Patterns
+   Availability: POP
 
-   ~R/ =R, Patterns
+   This is a colon-delimited list of authentication methods Mutt-ng may
+   attempt to use to log in to an POP server, in the order Mutt-ng should
+   try them. Authentication methods are either ``user'', ``apop'' or any
+   SASL mechanism, eg ``digest-md5'', ``gssapi'' or ``cram-md5''.
 
-   ~r/ =r, Patterns
+   This parameter is case-insensitive. If this parameter is _u_n_s_e_t (the
+   default) Mutt-ng will try all available methods, in order from
+   most-secure to least-secure.
 
-   ~s/ =s, Complex Patterns, Patterns
+   Example: set pop_authenticators="digest-md5:apop:user"
 
-   ~S/ =S, Patterns
+223. $pop_delete
 
-   ~T/ =T, Patterns
+   Type: quadoption
 
-   ~t/ =t, Patterns
+   Default: ask-no
 
-   ~U/ =U, Complex Patterns, Patterns
+   Availability: POP
 
-   ~u/ =u, Patterns
+   If _s_e_t, Mutt-ng will delete successfully downloaded messages from the
+   POP server when using the ``fetch-mail'' function. When _u_n_s_e_t, Mutt-ng
+   will download messages but also leave them on the POP server.
 
-   ~v/ =v, Patterns
+224. $pop_host
 
-   ~V/ =V, Patterns
+   Type: string
 
-   ~w/ =w, Patterns
+   Default: ""
 
-   ~x/ =x, Complex Patterns, Patterns
+   Availability: POP
 
-   ~X/ =X, Patterns
+   The name of your POP server for the ``fetch-mail'' function. You can
+   also specify an alternative port, username and password, i.e.:
 
-   ~y/ =y, Handling Mailing Lists, Patterns
+   [pop[s]://][username[:password]@]popserver[:port]
 
-   ~z/ =z, Patterns
+   _N_o_t_e_: Storing passwords in a configuration file presents a security
+   risk since the superuser of your machine may read it regardless of the
+   file's permissions.
 
-  A
+225. $pop_last
 
-   $abort_noattach , $abort_noattach
+   Type: boolean
 
-   $abort_nosubject , $abort_nosubject
+   Default: no
 
-   $abort_unmodified , $abort_unmodified
+   Availability: POP
 
-   account-hook, Managing multiple IMAP/POP/NNTP accounts (OPTIONAL),
-   Configuration Commands
+   If this variable is _s_e_t, Mutt-ng will try to use the ``LAST'' POP
+   command for retrieving only unread messages from the POP server when
+   using the ``fetch-mail'' function.
 
-   $agent_string , Configuration variables
+226. $pop_mail_check
 
-   $agent_string , $agent_string
+   Type: number
 
-   alias, Miscellaneous Functions, Defining/Using aliases, Configuration
-   Commands
+   Default: 60
 
-   $alias_file, Miscellaneous Functions, Defining/Using aliases
+   Availability: POP
 
-   $alias_file , $alias_file
+   This variable configures how often (in seconds) Mutt-ng should look
+   for new mail.
 
-   $alias_format , $alias_format
+227. $pop_pass
 
-   $allow_8bit , $allow_8bit
+   Type: string
 
-   $allow_ansi , $allow_ansi
+   Default: ""
 
-   alternates, Alternative addresses, Configuration Commands
+   Availability: POP
 
-   alternative_order, MIME Multipart/Alternative, Configuration Commands
+   Specifies the password for your POP account. If _u_n_s_e_t, Mutt-ng will
+   prompt you for your password when you open POP mailbox.
 
-   append-hook, Compressed folders Support (OPTIONAL), Append a message to a
-   compressed mailbox, Encrypted folders, Configuration Commands
+   _N_o_t_e_: Storing passwords in a configuration file presents a security
+   risk since the superuser of your machine may read it regardless of the
+   file's permissions.
 
-   $arrow_cursor , $arrow_cursor
+228. $pop_reconnect
 
-   $ascii_chars , $ascii_chars
+   Type: quadoption
 
-   $askbcc , $askbcc
+   Default: ask-yes
 
-   $askcc , $askcc
+   Availability: POP
 
-   $assumed_charset , $assumed_charset
+   Controls whether or not Mutt-ng will try to reconnect to a POP server
+   if the connection is lost.
 
-   <attach-file>, Composing new messages, compose
+229. $pop_user
 
-   <attach-key>, Composing new messages, compose
+   Type: string
 
-   <attach-message>, Composing new messages, compose
+   Default: ""
 
-   attachments, Attachment Searching and Counting
+   Availability: POP
 
-   $attach_format , $attach_format
+   Your login name on the POP server.
 
-   $attach_remind_regexp , $attach_remind_regexp
+   This variable defaults to your user name on the local machine.
 
-   $attach_sep , $attach_sep
+230. $post_indent_string
 
-   $attach_split , $attach_split
+   Type: string
 
-   $attribution, Change settings based upon message recipients, $attribution
+   Default: ""
 
-   $auto_tag, Using Tags
+   Similar to the ``$$aattttrriibbuuttiioonn'' variable, Mutt-ng will append this
+   string after the inclusion of a message which is being replied to.
 
-   $autoedit , $autoedit
+231. $postpone
 
-   $auto_tag , $auto_tag
+   Type: quadoption
 
-   auto_view, The Pager, Optional Fields, Search Order, MIME Autoview, MIME
-   Multipart/Alternative, Configuration Commands
+   Default: ask-yes
 
-  B
+   Controls whether or not messages are saved in the ``$$ppoossttppoonneedd''
+   mailbox when you elect not to send immediately.
 
-   <backspace>, Editing Input Fields, editor
+232. $postponed
 
-   <backward-char>, Editing Input Fields, editor
+   Type: path
 
-   <backward-word>, Editing Input Fields, editor
+   Default: "~/postponed"
 
-   $beep , $beep
+   Mutt-ng allows you to indefinitely ``ppoossttppoonnee sending a message''
+   which you are editing. When you choose to postpone a message, Mutt-ng
+   saves it in the mailbox specified by this variable. Also see the
+   ``$$ppoossttppoonnee'' variable.
 
-   $beep_new , $beep_new
+233. $preconnect
 
-   bind, Editing Input Fields, Changing the default key bindings, Keyboard
-   macros, Configuration Commands
+   Type: string
 
-   <bol>, Editing Input Fields, editor
+   Default: ""
 
-   <bottom>, pager
+   If _s_e_t, a shell command to be executed if Mutt-ng fails to establish a
+   connection to the server. This is useful for setting up secure
+   connections, e.g. with ssh(1). If the command returns a nonzero
+   status, Mutt-ng gives up opening the server. Example:
 
-   <bottom-page>, generic
+   preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net sleep 20 <
+   /dev/null > /dev/null"
 
-   <bounce>, Sending Mail, $bounce
+   Mailbox ``foo'' on mailhost.net can now be reached as
+   ``{localhost:1234}foo''.
 
-   <bounce-message>, index, pager, attach
+   _N_o_t_e_: For this example to work, you must be able to log in to the
+   remote machine without having to enter a password.
 
-   $bounce_delivered , $bounce_delivered
+234. $print
 
-   $braille_friendly , $braille_friendly
+   Type: quadoption
 
-   <buffy-cycle>, editor
+   Default: ask-no
 
-  C
+   Controls whether or not Mutt-ng really prints messages. This is set to
+   _a_s_k_-_n_o by default, because some people accidentally hit ``p'' often.
 
-   <capitalize-word>, Editing Input Fields, editor
+235. $print_command
 
-   $certificate_file , $certificate_file
+   Type: path
 
-   <change-dir>, browser
+   Default: "lpr"
 
-   <change-folder>, index, pager
+   This specifies the command pipe that should be used to print messages.
 
-   <change-folder-readonly>, index, pager
+236. $print_decode
 
-   $charset , $charset
+   Type: boolean
 
-   charset-hook, Defining aliases for character sets, Configuration Commands
+   Default: yes
 
-   <check-new>, browser
+   Used in connection with the print-message command. If this option is
+   _s_e_t, the message is decoded before it is passed to the external
+   command specified by $$pprriinntt__ccoommmmaanndd. If this option is _u_n_s_e_t, no
+   processing will be applied to the message when printing it. The latter
+   setting may be useful if you are using some advanced printer filter
+   which is able to properly format e-mail messages for printing.
 
-   <check-traditional-pgp>, Miscellaneous Functions, index, pager
+237. $print_split
 
-   $check_new , $check_new
+   Type: boolean
 
-   <clear-flag>, index
+   Default: no
 
-   close-hook, Compressed folders Support (OPTIONAL), Write a compressed
-   mailbox, Append a message to a compressed mailbox, Configuration Commands
+   Used in connection with the print-message command. If this option is
+   _s_e_t, the command specified by $$pprriinntt__ccoommmmaanndd is executed once for each
+   message which is to be printed. If this option is _u_n_s_e_t, the command
+   specified by $$pprriinntt__ccoommmmaanndd is executed only once, and all the
+   messages are concatenated, with a form feed as the message separator.
 
-   <collapse-all>, Threaded Mode
+   Those who use the enscript(1) program's mail-printing mode will most
+   likely want to set this option.
 
-   <collapse-parts>, attach
+238. $prompt_after
 
-   <collapse-thread>, Threaded Mode
+   Type: boolean
 
-   $collapse_unread , $collapse_unread
+   Default: yes
 
-   color, The Pager, Using color and mono video attributes, Configuration
-   Commands
+   If you use an _e_x_t_e_r_n_a_l ``$$ppaaggeerr'', setting this variable will cause
+   Mutt-ng to prompt you for a command when the pager exits rather than
+   returning to the index menu. If _u_n_s_e_t, Mutt-ng will return to the
+   index menu when the external pager exits.
 
-   $COLORFGBG, Using color and mono video attributes
+239. $query_command
 
-   <complete>, Editing Input Fields, editor
+   Type: path
 
-   <complete-query>, Editing Input Fields, editor
+   Default: ""
 
-   <compose>, Sending Mail
+   This specifies the command that Mutt-ng will use to make external
+   address queries. The string should contain a %s, which will be
+   substituted with the query string the user types. See ``qquueerryy'' for
+   more information.
 
-   $compose_format , $compose_format
+240. $quit
 
-   $config_charset , $config_charset
+   Type: quadoption
 
-   $confirmappend , $confirmappend
+   Default: yes
 
-   $confirmcreate , $confirmcreate
+   This variable controls whether ``quit'' and ``exit'' actually quit
+   from Mutt-ng. If it set to _y_e_s, they do quit, if it is set to _n_o, they
+   have no effect, and if it is set to _a_s_k_-_y_e_s or _a_s_k_-_n_o, you are
+   prompted for confirmation when you try to quit.
 
-   $connect_timeout , $connect_timeout
+241. $quote_empty
 
-   $content_type , $content_type
+   Type: boolean
 
-   $copy , $copy
+   Default: yes
 
-   <copy-file>, compose
+   Controls whether or not empty lines will be quoted using
+   ``iinnddeenntt__ssttrriinngg''.
 
-   <copy-message>, index, pager
+242. $quote_quoted
 
-   <create-alias>, Miscellaneous Functions, Defining/Using aliases, index,
-   pager, query
+   Type: boolean
 
-   $crypt_autoencrypt , Configuration variables
+   Default: no
 
-   $crypt_autosign , Configuration variables
+   Controls how quoted lines will be quoted. If _s_e_t, one quote character
+   will be added to the end of existing prefix. Otherwise, quoted lines
+   will be prepended by ``iinnddeenntt__ssttrriinngg''.
 
-   crypt-hook, Choosing the cryptographic key of the recipient, Configuration
-   Commands
+243. $quote_regexp
 
-   $crypt_replyencrypt , Configuration variables
+   Type: regular expression
 
-   $crypt_replysign , Configuration variables
+   Default: "^([ \t]*[|>:}#])+"
 
-   $crypt_replysignencrypted , Configuration variables
+   A regular expression used in the internal-pager to determine quoted
+   sections of text in the body of a message.
 
-   $crypt_verify_sig , Configuration variables
+   _N_o_t_e_: In order to use the _q_u_o_t_e_d_x patterns in the internal pager, you
+   need to set this to a regular expression that matches _e_x_a_c_t_l_y the
+   quote characters at the beginning of quoted lines.
 
-   $crypt_autoencrypt , $crypt_autoencrypt
+244. $read_inc
 
-   $crypt_autopgp , $crypt_autopgp
+   Type: number
 
-   $crypt_autosign , $crypt_autosign
+   Default: 10
 
-   $crypt_autosmime , $crypt_autosmime
+   If set to a value greater than 0, Mutt-ng will display which message
+   it is currently on when reading a mailbox. The message is printed
+   after _r_e_a_d___i_n_c messages have been read (e.g., if set to 25, Mutt-ng
+   will print a message when it reads message 25, and then again when it
+   gets to message 50). This variable is meant to indicate progress when
+   reading large mailboxes which may take some time. When set to 0, only
+   a single message will appear before the reading the mailbox.
 
-   $crypt_replyencrypt , $crypt_replyencrypt
+   Also see the ``$$wwrriittee__iinncc'' variable.
 
-   $crypt_replysign , $crypt_replysign
+245. $read_only
 
-   $crypt_replysignencrypted , $crypt_replysignencrypted
+   Type: boolean
 
-   $crypt_timestamp , $crypt_timestamp
+   Default: no
 
-   $crypt_use_gpgme , $crypt_use_gpgme
+   If set, all folders are opened in read-only mode.
 
-   $crypt_verify_sig , $crypt_verify_sig
+246. $realname
 
-   <current-bottom>, generic
+   Type: string
 
-   <current-middle>, generic
+   Default: ""
 
-   <current-top>, generic
+   This variable specifies what ``real'' or ``personal'' name should be
+   used when sending messages.
 
-  D
+   By default, this is the GECOS field from /etc/passwd.
 
-   $date_format , $date_format
+   _N_o_t_e_: This variable will _n_o_t be used when the user has set a real name
+   in the $$ffrroomm variable.
 
-   $debug_level , $debug_level
+247. $recall
 
-   <decode-copy>, index
+   Type: quadoption
 
-   <decode-save>, index, pager
+   Default: ask-yes
 
-   default-hook, Message Matching in Hooks
+   Controls whether or not Mutt-ng recalls postponed messages when
+   composing a new message. Also see ``$$ppoossttppoonneedd''.
 
-   $default_hook , $default_hook
+   Setting this variable to _y_e_s is not generally useful, and thus not
+   recommended.
 
-   $delete , $delete
+248. $record
 
-   <delete-char>, Editing Input Fields, editor
+   Type: path
 
-   <delete-entry>, attach, postpone
+   Default: ""
 
-   <delete-message>, index, pager
+   This specifies the file into which your outgoing messages should be
+   appended. (This is meant as the primary method for saving a copy of
+   your messages, but another way to do this is using the ``mmyy__hhddrr''
+   command to create a Bcc: header field with your email address in it.)
 
-   <delete-pattern>, index
+   The value of $$rreeccoorrdd is overridden by the ``$$ffoorrccee__nnaammee'' and
+   ``$$ssaavvee__nnaammee'' variables, and the ``  ffcccc--hhooookk'' command.
 
-   $delete_space, Additional Notes
+249. $reply_regexp
 
-   <delete-subthread>, Threaded Mode, index, pager
+   Type: regular expression
 
-   <delete-thread>, Threaded Mode, index, pager
+   Default: "^(re([\[0-9\]+])*|aw):[ \t]*"
 
-   $delete_space , $delete_space
+   A regular expression used to recognize reply messages when threading
+   and replying. The default value corresponds to the English ``Re:'' and
+   the German ``Aw:''.
 
-   $delete_untag , $delete_untag
+250. $reply_self
 
-   <detach-file>, Composing new messages, compose
+   Type: boolean
 
-   $digest_collapse , $digest_collapse
+   Default: no
 
-   <display-address>, index, pager
+   If _u_n_s_e_t and you are replying to a message sent by you, Mutt-ng will
+   assume that you want to reply to the recipients of that message rather
+   than to yourself.
 
-   <display-message>, index
+251. $reply_to
 
-   <display-toggle-weed>, Miscellaneous Functions, index, pager, attach,
-   compose
+   Type: quadoption
 
-   $display_filter , $display_filter
+   Default: ask-yes
 
-   $dotlock_program , $dotlock_program
+   If _s_e_t, when replying to a message, Mutt-ng will use the address
+   listed in the ``Reply-To:'' header field as the recipient of the
+   reply. If _u_n_s_e_t, it will use the address in the ``From:'' header field
+   instead.
 
-   <downcase-word>, Editing Input Fields, editor
+   This option is useful for reading a mailing list that sets the
+   ``Reply-To:'' header field to the list address and you want to send a
+   private message to the author of a message.
 
-   $dsn_notify, Delivery Status Notification (DSN) Support
+252. $resolve
 
-   $dsn_return, Delivery Status Notification (DSN) Support
+   Type: boolean
 
-   $dsn_notify , $dsn_notify
+   Default: yes
 
-   $dsn_return , $dsn_return
+   When set, the cursor will be automatically advanced to the next
+   (possibly undeleted) message whenever a command that modifies the
+   current message is executed.
 
-   $duplicate_threads , $duplicate_threads
+253. $reverse_alias
 
-  E
+   Type: boolean
 
-   <edit>, Miscellaneous Functions, index, pager, compose
+   Default: no
 
-   <edit-bcc>, Composing new messages, compose
+   This variable controls whether or not Mutt-ng will display the
+   ``personal'' name from your aliases in the index menu if it finds an
+   alias that matches the message's sender. For example, if you have the
+   following alias:
 
-   <edit-cc>, Composing new messages, compose
+   alias juser abd30425@somewhere.net (Joe User)
 
-   <edit-description>, Composing new messages, compose
+   and then you receive mail which contains the following header:
 
-   <edit-encoding>, compose
+   From: abd30425@somewhere.net
 
-   <edit-fcc>, Composing new messages, compose
+   It would be displayed in the index menu as ``Joe User'' instead of
+   ``abd30425@somewhere.net.'' This is useful when the person's e-mail
+   address is not human friendly (like CompuServe addresses).
 
-   <edit-file>, compose
+254. $reverse_name
 
-   <edit-from>, Composing new messages, compose
+   Type: boolean
 
-   $edit_headers, Editing the message header, User defined headers,
-   mailto:-style links, Configuration variables, compose
+   Default: no
 
-   <edit-mime>, compose
+   It may sometimes arrive that you receive mail to a certain machine,
+   move the messages to another machine, and reply to some the messages
+   from there. If this variable is _s_e_t, the default From: line of the
+   reply messages is built using the address where you received the
+   messages you are replying to _i_f that address matches your alternates.
+   If the variable is _u_n_s_e_t, or the address that would be used doesn't
+   match your alternates, the From: line will use your address on the
+   current machine.
 
-   <edit-reply-to>, Composing new messages, compose
+255. $reverse_realname
 
-   <edit-subject>, Composing new messages, compose
+   Type: boolean
 
-   <edit-to>, Composing new messages, compose
+   Default: yes
 
-   <edit-type>, Miscellaneous Functions, index, pager, attach, compose
+   This variable fine-tunes the behaviour of the rreevveerrssee__nnaammee feature.
+   When it is _s_e_t, Mutt-ng will use the address from incoming messages
+   as-is, possibly including eventual real names. When it is _u_n_s_e_t,
+   Mutt-ng will override any such real names with the setting of the
+   rreeaallnnaammee variable.
 
-   $EDITOR, Manual Conventions, Composing new messages
+256. $rfc2047_parameters
 
-   $editor , $editor
+   Type: boolean
 
-   $editor_headers, Editing the message header, Defining/Using aliases
+   Default: no
 
-   $editor_headers , $editor_headers
+   When this variable is _s_e_t, Mutt-ng will decode RFC-2047-encoded MIME
+   parameters. You want to set this variable when Mutt-ng suggests you to
+   save attachments to files named like this:
 
-   $edit_headers , $edit_headers
+   =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
 
-   $encode_from , $encode_from
+   When this variable is _s_e_t interactively, the change doesn't have the
+   desired effect before you have changed folders.
 
-   <enter-command>, Miscellaneous Functions, generic, pager
+   Note that this use of RFC 2047's encoding is explicitly, prohibited by
+   the standard, but nevertheless encountered in the wild.
 
-   <enter-mask>, browser
+   Also note that setting this parameter will _n_o_t have the effect that
+   Mutt-ng _g_e_n_e_r_a_t_e_s this kind of encoding. Instead, Mutt-ng will
+   unconditionally use the encoding specified in RFC 2231.
 
-   $entropy_file , $entropy_file
+257. $save_address
 
-   $envelope_from_address , $envelope_from_address
+   Type: boolean
 
-   <eol>, Editing Input Fields, editor
+   Default: no
 
-   $escape , $escape
+   If _s_e_t, Mutt-ng will take the sender's full address when choosing a
+   default folder for saving a mail. If ``$$ssaavvee__nnaammee'' or ``$$ffoorrccee__nnaammee''
+   is _s_e_t too, the selection of the fcc folder will be changed as well.
 
-   exec, Executing functions, Configuration Commands
+258. $save_empty
 
-   <exit>, generic, index, pager
+   Type: boolean
 
-   <extract-keys>, Miscellaneous Functions, index, pager, attach
+   Default: yes
 
-  F
+   When _u_n_s_e_t, mailboxes which contain no saved messages will be removed
+   when closed (the exception is ``$$ssppoooollffiillee'' which is never removed).
+   If _s_e_t, mailboxes are never removed.
 
-   $fast_reply , $fast_reply
+   _N_o_t_e_: This only applies to mbox and MMDF folders, Mutt-ng does not
+   delete MH and Maildir directories.
 
-   fcc-hook, Specify default Fcc: mailbox when composing, Specify default
-   save filename and default Fcc: mailbox at once, Using Hooks, Message
-   Matching in Hooks, Configuration Commands
+259. $save_name
 
-   fcc-save-hook, Specify default save filename, Specify default Fcc: mailbox
-   when composing, Specify default save filename and default Fcc: mailbox at
-   once, Using Hooks, Configuration Commands
+   Type: boolean
 
-   $fcc_attach , $fcc_attach
+   Default: no
 
-   $fcc_clear , $fcc_clear
+   This variable controls how copies of outgoing messages are saved. When
+   set, a check is made to see if a mailbox specified by the recipient
+   address exists (this is done by searching for a mailbox in the
+   ``$$ffoollddeerr'' directory with the _u_s_e_r_n_a_m_e part of the recipient
+   address). If the mailbox exists, the outgoing message will be saved to
+   that mailbox, otherwise the message is saved to the ``$$rreeccoorrdd''
+   mailbox.
 
-   <fetch-mail>, index
+   Also see the ``$$ffoorrccee__nnaammee'' variable.
 
-   $file_charset , $file_charset
+260. $score
 
-   <filter-entry>, compose
+   Type: boolean
 
-   <first-entry>, Moving Around in Menus, generic
+   Default: yes
 
-   <flag-message>, index, pager
+   When this variable is _u_n_s_e_t, scoring is turned off. This can be useful
+   to selectively disable scoring for certain folders when the
+   ``$$ssccoorree__tthhrreesshhoolldd__ddeelleettee'' variable and friends are used.
 
-   $folder, Configuration Variables, Defining mailboxes which receive mail,
-   Mailbox Shortcuts, $folder
+261. $score_threshold_delete
 
-   folder-hook, Setting variables based upon mailbox, Spam detection, Using
-   Hooks, Managing multiple IMAP/POP/NNTP accounts (OPTIONAL), Configuration
-   Commands
+   Type: number
 
-   $folder_format , $folder_format
+   Default: -1
 
-   $followup_to, Mailing lists, Handling Mailing Lists
+   Messages which have been assigned a score equal to or lower than the
+   value of this variable are automatically marked for deletion by
+   Mutt-ng. Since Mutt-ng scores are always greater than or equal to
+   zero, the default setting of this variable will never mark a message
+   for deletion.
 
-   $followup_to , $followup_to
+262. $score_threshold_flag
 
-   $force_buffy_check , $force_buffy_check
+   Type: number
 
-   $force_name , $force_name
+   Default: 9999
 
-   <forget-passphrase>, Miscellaneous Functions, Composing new messages,
-   index, pager, compose
+   Messages which have been assigned a score greater than or equal to
+   this variable's value are automatically marked ``flagged''.
 
-   <forward>, Sending Mail
+263. $score_threshold_read
 
-   <forward-char>, Editing Input Fields, editor
+   Type: number
 
-   $forward_decode , Configuration variables
+   Default: -1
 
-   $forward_decrypt , Configuration variables
+   Messages which have been assigned a score equal to or lower than the
+   value of this variable are automatically marked as read by Mutt-ng.
+   Since Mutt-ng scores are always greater than or equal to zero, the
+   default setting of this variable will never mark a message read.
 
-   $forward_format , Configuration variables
+264. $send_charset
 
-   <forward-message>, index, pager, attach
+   Type: string
 
-   $forward_quote , Configuration variables
+   Default: "us-ascii:iso-8859-1:utf-8"
 
-   <forward-word>, Editing Input Fields, editor
+   A list of character sets for outgoing messages. Mutt-ng will use the
+   first character set into which the text can be converted exactly. If
+   your ``$$cchhaarrsseett'' is not iso-8859-1 and recipients may not understand
+   UTF-8, it is advisable to include in the list an appropriate widely
+   used standard character set (such as iso-8859-2, koi8-r or
+   iso-2022-jp) either instead of or after iso-8859-1.
 
-   $forward_decode , $forward_decode
+265. $sendmail
 
-   $forward_decrypt , $forward_decrypt
+   Type: path
 
-   $forward_edit , $forward_edit
+   Default: "/usr/sbin/sendmail -oem -oi"
 
-   $forward_format , $forward_format
+   Specifies the program and arguments used to deliver mail sent by
+   Mutt-ng. Mutt-ng expects that the specified program interprets
+   additional arguments as recipient addresses.
 
-   $forward_quote , $forward_quote
+266. $sendmail_wait
 
-   $from , $from
+   Type: number
 
-  G
+   Default: 0
 
-   $gecos_mask , $gecos_mask
+   Specifies the number of seconds to wait for the ``$$sseennddmmaaiill'' process
+   to finish before giving up and putting delivery in the background.
 
-   <group-reply>, Sending Mail, index, pager, attach
+   Mutt-ng interprets the value of this variable as follows:
 
-  H
+   >0
+          number of seconds to wait for sendmail to finish before
+          continuing
 
-   <half-down>, generic, pager
+   0
+          wait forever for sendmail to finish
 
-   <half-up>, generic, pager
+   <0
+          always put sendmail in the background without waiting
 
-   $hdrs , $hdrs
+   Note that if you specify a value other than 0, the output of the child
+   process will be put in a temporary file. If there is some error, you
+   will be informed as to where to find the output.
 
-   hdr_order, Defining the order of headers when viewing messages,
-   Configuration Commands
+267. $shell
 
-   $header , $header
+   Type: path
 
-   $header_cache , $header_cache
+   Default: ""
 
-   $header_cache_compress , $header_cache_compress
+   Command to use when spawning a subshell. By default, the user's login
+   shell from /etc/passwd is used.
 
-   <help>, Moving Around in Menus, $help, generic, pager
+268. $sidebar_boundary
 
-   $hidden_host , $hidden_host
+   Type: string
 
-   $hide_limited , $hide_limited
+   Default: "."
 
-   $hide_missing , $hide_missing
+   When the sidebar is displayed and $$ssiiddeebbaarr__sshhoorrtteenn__hhiieerraarrcchhyy is _s_e_t,
+   this variable specifies the characters at which to split a folder name
+   into ``hierarchy items.''
 
-   $hide_thread_subject , $hide_thread_subject
+269. $sidebar_delim
 
-   $hide_top_limited , $hide_top_limited
+   Type: string
 
-   $hide_top_missing , $hide_top_missing
+   Default: "|"
 
-   $history , $history
+   This specifies the delimiter between the sidebar (if visible) and
+   other screens.
 
-   <history-down>, Editing Input Fields, editor
+270. $sidebar_newmail_only
 
-   <history-up>, Editing Input Fields, editor
+   Type: boolean
 
-   $HOME, MIME Type configuration with mime.types, MIME Viewer configuration
-   with mailcap
+   Default: no
 
-   $honor_followup_to, Miscellaneous Functions, Handling Mailing Lists
+   If _s_e_t, only folders with new mail will be shown in the sidebar.
 
-   $honor_followup_to , $honor_followup_to
+271. $sidebar_number_format
 
-   $HOSTNAME, Environment Variables
+   Type: string
 
-   $hostname , $hostname
+   Default: "%m%?n?(%n)?%?f?[%f]?"
 
-  I
+   This variable controls how message counts are printed when the sidebar
+   is enabled. If this variable is _e_m_p_t_y (_a_n_d_ _o_n_l_y_ _i_f), no numbers will
+   be printed _a_n_d Mutt-ng won't frequently count mail (which may be a
+   great speedup esp. with mbox-style mailboxes.)
 
-   iconv-hook, Defining aliases for character sets
+   The following printf(3)-like sequences are supported all of which may
+   be printed non-zero:
 
-   ignore, Miscellaneous Functions, Ignoring (weeding) unwanted message
-   headers, Configuration Commands
+   %d
+          Number of deleted messages. 1)
 
-   $ignore_list_reply_to , $ignore_list_reply_to
+   %F
+          Number of flagged messages.
 
-   $imap_authenticators, Authentication
+   %m
+          Total number of messages.
 
-   $imap_home_namespace, Configuration Variables
+   %M
+          Total number of messages shown, i.e. not hidden by a limit. 1)
 
-   $imap_list_subscribed, IMAP Support (OPTIONAL)
+   %n
+          Number of new messages.
 
-   $imap_mail_check, Manual Conventions, Conditional parts, IMAP Support
-   (OPTIONAL)
+   %t
+          Number of tagged messages. 1)
 
-   $imap_pass, Authentication
+   %u
+          Number of unread messages.
 
-   $imap_user, Authentication
+   1) These expandos only have a non-zero value for the current mailbox
+   and will always be zero otherwise.
 
-   $imap_authenticators , $imap_authenticators
+272. $sidebar_shorten_hierarchy
 
-   $imap_check_subscribed , $imap_check_subscribed
+   Type: boolean
 
-   $imap_delim_chars , $imap_delim_chars
+   Default: no
 
-   $imap_headers , $imap_headers
+   When _s_e_t, the ``hierarchy'' of the sidebar entries will be shortened
+   only if they cannot be printed in full length (because
+   ``$$ssiiddeebbaarr__wwiiddtthh'' is set to a too low value). For example, if the
+   newsgroup name ``de.alt.sysadmin.recovery'' doesn't fit on the screen,
+   it'll get shortened ``d.a.s.recovery'' while ``de.alt.d0'' still would
+   and thus will not get shortened.
 
-   $imap_home_namespace , $imap_home_namespace
+   At which characters this compression is done is controled via the
+   $$ssiiddeebbaarr__bboouunnddaarryy variable.
 
-   $imap_keepalive , $imap_keepalive
+273. $sidebar_visible
 
-   $imap_list_subscribed , $imap_list_subscribed
+   Type: boolean
 
-   $imap_login , $imap_login
+   Default: no
 
-   $imap_mail_check , $imap_mail_check
+   This specifies whether or not to show the sidebar (a list of folders
+   specified with the ``mailboxes'' command).
 
-   $imap_pass , $imap_pass
+274. $sidebar_width
 
-   $imap_passive , $imap_passive
+   Type: number
 
-   $imap_peek , $imap_peek
+   Default: 0
 
-   $imap_reconnect , $imap_reconnect
+   The width of the sidebar.
 
-   $imap_servernoise , $imap_servernoise
+275. $sig_dashes
 
-   $imap_user , $imap_user
+   Type: boolean
 
-   $implicit_autoview , $implicit_autoview
+   Default: yes
 
-   $include , $include
+   If set, a line containing ``-- '' (dash, dash, space) will be inserted
+   before your ``$$ssiiggnnaattuurree''. It is _s_t_r_o_n_g_l_y recommended that you not
+   unset this variable unless your ``signature'' contains just your name.
+   The reason for this is because many software packages use ``-- \n'' to
+   detect your signature.
 
-   $include_onlyfirst , $include_onlyfirst
+   For example, Mutt-ng has the ability to highlight the signature in a
+   different color in the builtin pager.
 
-   $indent_string , Configuration variables
+276. $sig_on_top
 
-   $indent_string , $indent_string
+   Type: boolean
 
-   $index_format, Threaded Mode, Spam detection, Handling Mailing Lists,
-   Configuration variables
+   Default: no
 
-   $index_format , $index_format
+   If _s_e_t, the signature will be included before any quoted or forwarded
+   text. It is _s_t_r_o_n_g_l_y recommended that you do not set this variable
+   unless you really know what you are doing, and are prepared to take
+   some heat from netiquette guardians.
 
-   <ispell>, Composing new messages, $ispell, compose
+277. $signature
 
-  J
+   Type: path
 
-   <jump>, generic
+   Default: "~/.signature"
 
-  K
+   Specifies the filename of your signature, which is appended to all
+   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.
 
-   $keep_flagged , $keep_flagged
+278. $signoff_string
 
-   <kill-eol>, Editing Input Fields, editor
+   Type: string
 
-   <kill-eow>, Editing Input Fields, editor
+   Default: ""
 
-   <kill-line>, Editing Input Fields, editor
+   If _s_e_t, this string will be inserted before the signature. This is
+   useful for people that want to sign off every message they send with
+   their name.
 
-   <kill-word>, Editing Input Fields, editor
+   If you want to insert your website's URL, additional contact
+   information or witty quotes into your mails, better use a signature
+   file instead of the signoff string.
 
-  L
+279. $simple_search
 
-   <last-entry>, Moving Around in Menus, generic
+   Type: string
 
-   <limit>, index
+   Default: "~f %s | ~s %s"
 
-   <list-reply>, Miscellaneous Functions, Sending Mail, index, pager, attach
+   Specifies how Mutt-ng should expand a simple search into a real search
+   pattern. A simple search is one that does not contain any of the ~
+   operators. See ``ppaatttteerrnnss'' for more information on search patterns.
 
-   lists, Miscellaneous Functions, Mailing lists, Handling Mailing Lists,
-   Configuration Commands
+   For example, if you simply type ``joe'' at a search or limit prompt,
+   Mutt-ng will automatically expand it to the value specified by this
+   variable. For the default value it would be:
 
-   $list_reply , $list_reply
+   ~f joe | ~s joe
 
-   $locale, Change settings based upon message recipients, $locale
+280. $sleep_time
 
-  M
+   Type: number
 
-   macro, Miscellaneous Functions, Keyboard macros, Adding key sequences to
-   the keyboard buffer, Using Tags, Configuration Commands
+   Default: 1
 
-   <mail>, index, pager, query
+   Specifies time, in seconds, to pause while displaying certain
+   informational messages, while moving from folder to folder and after
+   expunging messages from the current folder. The default is to pause
+   one second, so a value of zero for this option suppresses the pause.
 
-   <mail-key>, Sending Mail, index, pager
+281. $smart_wrap
 
-   mailboxes, Defining mailboxes which receive mail, Configuration Commands
+   Type: boolean
 
-   $mailcap_path, mailcap
+   Default: yes
 
-   $mailcap_sanitize, Secure use of mailcap, mailcap
+   Controls the display of lines longer than the screen width in the
+   internal pager. If _s_e_t, long lines are wrapped at a word boundary. If
+   _u_n_s_e_t, lines are simply wrapped at the screen edge. Also see the
+   ``$$mmaarrkkeerrss'' variable.
 
-   $mailcap_path , $mailcap_path
+282. $smileys
 
-   $mailcap_sanitize , $mailcap_sanitize
+   Type: regular expression
 
-   $maildir_header_cache_verify , $maildir_header_cache_verify
+   Default: "(>From )|(:[-^]?[][)(><}{|/DP])"
 
-   $maildir_trash , $maildir_trash
+   The _p_a_g_e_r uses this variable to catch some common false positives of
+   ``$$qquuoottee__rreeggeexxpp'', most notably smileys in the beginning of a line
 
-   $mail_check , $mail_check
+283. $smime_ask_cert_label
 
-   <mark-as-new>, pager
+   Type: boolean
 
-   $markers , $markers
+   Default: yes
 
-   $mark_old , $mark_old
+   This flag controls whether you want to be asked to enter a label for a
+   certificate about to be added to the database or not. It is _s_e_t by
+   default. (S/MIME only)
 
-   $mask , $mask
+284. $smime_ca_location
 
-   $max_display_recips , $max_display_recips
+   Type: path
 
-   $max_line_length , $max_line_length
+   Default: ""
 
-   $mbox, Mailbox Shortcuts, $mbox
+   This variable contains the name of either a directory, or a file which
+   contains trusted certificates for use with OpenSSL. (S/MIME only)
 
-   mbox-hook, Using Multiple spool mailboxes, Using Hooks, Configuration
-   Commands
+285. $smime_certificates
 
-   $mbox_type, Mailbox Formats, Append a message to a compressed mailbox
+   Type: path
 
-   $mbox_type , $mbox_type
+   Default: ""
 
-   $menu_context , $menu_context
+   Since there is no pubring/secring as with PGP, Mutt-ng has to handle
+   storage and retrieval of keys by itself. This is very basic right now,
+   and keys and certificates are stored in two different directories,
+   both named as the hash-value retrieved from OpenSSL. There is an index
+   file which contains mailbox-address keyid pairs, and which can be
+   manually edited. This one points to the location of the certificates.
+   (S/MIME only)
 
-   $menu_move_off , $menu_move_off
+286. $smime_decrypt_command
 
-   $menu_scroll , $menu_scroll
+   Type: string
 
-   $message_format , Configuration variables
+   Default: ""
 
-   message-hook, Change settings before formatting a message, Using Hooks,
-   Message Matching in Hooks, MIME Autoview, Configuration Commands
+   This format string specifies a command which is used to decrypt
+   application/x-pkcs7-mime attachments.
 
-   $message_format , $message_format
+   The OpenSSL command formats have their own set of printf(3)-like
+   sequences similar to PGP's:
 
-   $meta_key , $meta_key
+   %f
+          Expands to the name of a file containing a message.
 
-   $metoo , $metoo
+   %s
+          Expands to the name of a file containing the signature part of
+          a multipart/signed attachment when verifying it.
 
-   $mh_purge , $mh_purge
+   %k
+          The key-pair specified with $$ssmmiimmee__ddeeffaauulltt__kkeeyy
 
-   $mh_seq_flagged , $mh_seq_flagged
+   %c
+          One or more certificate IDs.
 
-   $mh_seq_replied , $mh_seq_replied
+   %a
+          The algorithm used for encryption.
 
-   $mh_seq_unseen , $mh_seq_unseen
+   %C
+          CA location: Depending on whether $$ssmmiimmee__ccaa__llooccaattiioonn points to
+          a directory or file, this expands to "-CApath
+          $$ssmmiimmee__ccaa__llooccaattiioonn" or "-CAfile $$ssmmiimmee__ccaa__llooccaattiioonn".
 
-   <middle-page>, generic
+   For examples on how to configure these formats, see the smime.rc in
+   the samples/ subdirectory which has been installed on your system
+   alongside the documentation. (S/MIME only)
 
-   $mime_forward , Configuration variables
+287. $smime_decrypt_use_default_key
 
-   $mime_forward , $mime_forward
+   Type: boolean
 
-   $mime_forward_decode , $mime_forward_decode
+   Default: yes
 
-   $mime_forward_rest , $mime_forward_rest
+   If _s_e_t (default) this tells Mutt-ng to use the default key for
+   decryption. Otherwise, if manage multiple certificate-key-pairs,
+   Mutt-ng will try to 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)
 
-   mime_lookup, MIME Lookup, Configuration Commands
+288. $smime_default_key
 
-   $mix_entry_format, Sending anonymous messages via mixmaster
+   Type: string
 
-   $mixmaster , $mixmaster
+   Default: ""
 
-   $mix_entry_format , $mix_entry_format
+   This is the default key-pair to use for signing. This must be set to
+   the keyid (the hash-value that OpenSSL generates) to work properly
+   (S/MIME only)
 
-   mono, Using color and mono video attributes, Configuration Commands
+289. $smime_encrypt_command
 
-   $move , $move
+   Type: string
 
-   $msgid_format, Message-ID: headers
+   Default: ""
 
-   $msgid_format , $msgid_format
+   This command is used to create encrypted S/MIME messages. (S/MIME
+   only)
 
-   $muttng_bindir , $muttng_bindir
+290. $smime_encrypt_with
 
-   $muttng_docdir , $muttng_docdir
+   Type: string
 
-   $muttng_folder_name , $muttng_folder_name
+   Default: ""
 
-   $muttng_folder_path , $muttng_folder_path
+   This sets the algorithm that should be used for encryption. Valid
+   choices are ``des'', ``des3'', ``rc2-40'', ``rc2-64'', ``\frc2-128''.
 
-   $muttng_hcache_backend , $muttng_hcache_backend
+   If _u_n_s_e_t ``_3_d_e_s'' (TripleDES) is used. (S/MIME only)
 
-   $muttng_pwd , $muttng_pwd
+291. $smime_get_cert_command
 
-   $muttng_revision , $muttng_revision
+   Type: string
 
-   $muttng_sysconfdir , $muttng_sysconfdir
+   Default: ""
 
-   $muttng_version , $muttng_version
+   This command is used to extract X509 certificates from a PKCS7
+   structure. (S/MIME only)
 
-   my_hdr, User defined headers, Configuration Commands
+292. $smime_get_cert_email_command
 
-  N
+   Type: string
 
-   $narrow_tree , $narrow_tree
+   Default: ""
 
-   $net_inc , $net_inc
+   This command is used to extract the mail address(es) used for storing
+   X509 certificates, and for verification purposes (to check whether the
+   certificate was issued for the sender's mailbox). (S/MIME only)
 
-   <new-mime>, compose
+293. $smime_get_signer_cert_command
 
-   <next-entry>, Moving Around in Menus, generic, pager
+   Type: string
 
-   <next-line>, generic, pager
+   Default: ""
 
-   <next-new>, index, pager
+   This command is used to extract only the signers X509 certificate from
+   a S/MIME signature, so that the certificate's owner may get compared
+   to the email's ``From:'' header field. (S/MIME only)
 
-   <next-new-then-unread>, index, pager
+294. $smime_import_cert_command
 
-   <next-page>, generic, pager
+   Type: string
 
-   <next-subthread>, Threaded Mode, index, pager
+   Default: ""
 
-   <next-thread>, Threaded Mode, index, pager
+   This command is used to import a certificate via smime_keysng. (S/MIME
+   only)
 
-   <next-undeleted>, index, pager
+295. $smime_is_default
 
-   <next-unread>, index, pager
+   Type: boolean
 
-   $nntp_ask_followup_to , Configuration variables
+   Default: no
 
-   $nntp_ask_x_comment_to , Configuration variables
+   The default behaviour of Mutt-ng is to use PGP on all
+   auto-sign/encryption operations. To override and to use OpenSSL
+   instead this must be _s_e_t.
 
-   $nntp_cache_dir , Configuration variables
+   However, this has no effect while replying, since Mutt-ng will
+   automatically select the same application that was used to
+   sign/encrypt the original message.
 
-   $nntp_catchup , Configuration variables
+   (Note that this variable can be overridden by unsetting
+   $$ccrryypptt__aauuttoossmmiimmee.) (S/MIME only)
 
-   $nntp_followup_to_poster , Configuration variables
+296. $smime_keys
 
-   $nntp_group_index_format , Configuration variables
+   Type: path
 
-   $nntp_host , Configuration variables
+   Default: ""
 
-   $nntp_inews , Configuration variables
+   Since there is no pubring/secring as with PGP, Mutt-ng has to handle
+   storage ad retrieval of keys/certs by itself. This is very basic right
+   now, and stores keys and certificates in two different directories,
+   both named as the hash-value retrieved from OpenSSL. There is an index
+   file 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)
 
-   $nntp_mail_check , Configuration variables
+297. $smime_pk7out_command
 
-   $nntp_mime_subject , Configuration variables
+   Type: string
 
-   $nntp_newsrc, NNTP Support (OPTIONAL), Configuration variables
+   Default: ""
 
-   $nntp_post_moderated , Configuration variables
+   This command is used to extract PKCS7 structures of S/MIME signatures,
+   in order to extract the public X509 certificate(s). (S/MIME only)
 
-   $nntp_save_unsubscribed , Configuration variables
+298. $smime_sign_command
 
-   $nntp_show_new_news , Configuration variables
+   Type: string
 
-   $nntp_show_only_unread , Configuration variables
+   Default: ""
 
-   $nntp_x_comment_to , Configuration variables
+   This command is used to created S/MIME signatures of type
+   multipart/signed, which can be read by all mail clients. (S/MIME only)
 
-   $NNTPSERVER, NNTP Support (OPTIONAL)
+299. $smime_sign_opaque_command
 
-   $nntp_ask_followup_to , $nntp_ask_followup_to
+   Type: string
 
-   $nntp_ask_x_comment_to , $nntp_ask_x_comment_to
+   Default: ""
 
-   $nntp_cache_dir , $nntp_cache_dir
+   This command is used to created S/MIME signatures of type
+   application/x-pkcs7-signature, which can only be handled by mail
+   clients supporting the S/MIME extension. (S/MIME only)
 
-   $nntp_catchup , $nntp_catchup
+300. $smime_timeout
 
-   $nntp_context , $nntp_context
+   Type: number
 
-   $nntp_followup_to_poster , $nntp_followup_to_poster
+   Default: 300
 
-   $nntp_group_index_format , $nntp_group_index_format
+   The number of seconds after which a cached passphrase will expire if
+   not used. (S/MIME only)
 
-   $nntp_host , $nntp_host
+301. $smime_verify_command
 
-   $nntp_inews , $nntp_inews
+   Type: string
 
-   $nntp_load_description , $nntp_load_description
+   Default: ""
 
-   $nntp_mail_check , $nntp_mail_check
+   This command is used to verify S/MIME signatures of type
+   multipart/signed. (S/MIME only)
 
-   $nntp_mime_subject , $nntp_mime_subject
+302. $smime_verify_opaque_command
 
-   $nntp_newsrc , $nntp_newsrc
+   Type: string
 
-   $nntp_pass , $nntp_pass
+   Default: ""
 
-   $nntp_post_moderated , $nntp_post_moderated
+   This command is used to verify S/MIME signatures of type
+   application/x-pkcs7-mime. (S/MIME only)
 
-   $nntp_reconnect , $nntp_reconnect
+303. $smtp_host
 
-   $nntp_save_unsubscribed , $nntp_save_unsubscribed
+   Type: string
 
-   $nntp_show_new_news , $nntp_show_new_news
+   Default: ""
 
-   $nntp_show_only_unread , $nntp_show_only_unread
+   Availability: SMTP
 
-   $nntp_user , $nntp_user
+   Defines the SMTP host which will be used to deliver mail, as opposed
+   to invoking the sendmail binary. Setting this variable overrides the
+   value of ``$$sseennddmmaaiill'', and any associated variables.
 
-   $nntp_x_comment_to , $nntp_x_comment_to
+304. $smtp_pass
 
-   nospam, Spam detection, Configuration Commands
+   Type: string
 
-  O
+   Default: ""
 
-   open-hook, Compressed folders Support (OPTIONAL), Open a compressed
-   mailbox for reading, Write a compressed mailbox, Append a message to a
-   compressed mailbox, Configuration Commands
+   Availability: SMTP
 
-   $operating_system , $operating_system
+   Defines the password to use with SMTP AUTH. If ``$$ssmmttpp__uusseerr'' is set,
+   but this variable is not, you will be prompted for a password when
+   sending.
 
-  P
+   _N_o_t_e_: Storing passwords in a configuration file presents a security
+   risk since the superuser of your machine may read it regardless of the
+   file's permissions.
 
-   <page-down>, Moving Around in Menus
+305. $smtp_port
 
-   <page-up>, Moving Around in Menus
+   Type: number
 
-   $pager , $pager
+   Default: 25
 
-   $pager_index_lines, Conditional parts
+   Availability: SMTP
 
-   $pager_context , $pager_context
+   Defines the port that the SMTP host is listening on for mail delivery.
+   Must be specified as a number.
 
-   $pager_format , $pager_format
+   Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP
+   servers will probably desire 587, the mail submission port.
 
-   $pager_index_lines , $pager_index_lines
+306. $smtp_use_tls
 
-   $pager_stop , $pager_stop
+   Type: string
 
-   <parent-message>, Threaded Mode, index, pager
+   Default: ""
 
-   pattern-hook, Specify default save filename, Specify default Fcc: mailbox
-   when composing, Change settings based upon message recipients, Change
-   settings before formatting a message
+   Availability: SMTP (and SSL)
 
-   $pgp_autoinline , Configuration variables
+   Defines wether to use STARTTLS. If this option is set to ``_r_e_q_u_i_r_e_d''
+   and the server does not support STARTTLS or there is an error in the
+   TLS Handshake, the connection will fail. Setting this to ``_e_n_a_b_l_e_d''
+   will try 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.
 
-   $pgp_entry_format, Using Mutt-ng with PGP
+307. $smtp_user
 
-   <pgp-menu>, Composing new messages, compose
+   Type: string
 
-   $pgp_replyinline , Configuration variables
+   Default: ""
 
-   $pgp_sign_as, Using Mutt-ng with PGP
+   Availability: SMTP
 
-   $pgp_autoinline , $pgp_autoinline
+   Defines the username to use with SMTP AUTH. Setting this variable will
+   cause Mutt-ng to attempt to use SMTP AUTH when sending.
 
-   $pgp_auto_decode , $pgp_auto_decode
+308. $sort
 
-   $pgp_check_exit , $pgp_check_exit
+   Type: sort order
 
-   $pgp_clearsign_command , $pgp_clearsign_command
+   Default: date
 
-   $pgp_decode_command , $pgp_decode_command
+   Specifies how to sort messages in the _i_n_d_e_x menu. Valid values are:
 
-   $pgp_decrypt_command , $pgp_decrypt_command
+   date or date-sent
+   date-received
+   from
+   mailbox-order (unsorted)
+   score
+   size
+   spam
+   subject
+   threads
+   to
 
-   $pgp_encrypt_only_command , $pgp_encrypt_only_command
+   You may optionally use the ``reverse-'' prefix to specify reverse
+   sorting order (example: set sort=reverse-date-sent).
 
-   $pgp_encrypt_sign_command , $pgp_encrypt_sign_command
+309. $sort_alias
 
-   $pgp_entry_format , $pgp_entry_format
+   Type: sort order
 
-   $pgp_export_command , $pgp_export_command
+   Default: alias
 
-   $pgp_getkeys_command , $pgp_getkeys_command
+   Specifies how the entries in the ``alias'' menu are sorted. The
+   following are legal values:
 
-   $pgp_good_sign , $pgp_good_sign
+   address (sort alphabetically by email address)
+   alias (sort alphabetically by alias name)
+   unsorted (leave in order specified in .muttrc)
 
-   $pgp_ignore_subkeys , $pgp_ignore_subkeys
+310. $sort_aux
 
-   $pgp_import_command , $pgp_import_command
+   Type: sort order
 
-   $pgp_list_pubring_command , $pgp_list_pubring_command
+   Default: date
 
-   $pgp_list_secring_command , $pgp_list_secring_command
+   When sorting by threads, this variable controls how threads are sorted
+   in relation to other threads, and how the branches of the thread trees
+   are sorted. This can be set to any value that ``$$ssoorrtt'' can, except
+   threads (in that case, Mutt-ng will just use date-sent). You can also
+   specify the ``last-'' prefix in addition to ``reverse-'' prefix, but
+   last- must come after reverse-. The last- prefix causes messages to be
+   sorted against its siblings by which has the last descendant, using
+   the rest of sort_aux as an ordering.
 
-   $pgp_long_ids , $pgp_long_ids
+   For instance, set sort_aux=last-date-received would mean that if a new
+   message is received in a thread, that thread becomes the last one
+   displayed (or the first, if you have set sort=reverse-threads.)
 
-   $pgp_mime_auto , $pgp_mime_auto
+   _N_o_t_e_: For reversed ``$$ssoorrtt'' order $$ssoorrtt__aauuxx is reversed again (which
+   is not the right thing to do, but kept to not break any existing
+   configuration setting).
 
-   $pgp_replyinline , $pgp_replyinline
+311. $sort_browser
 
-   $pgp_retainable_sigs , $pgp_retainable_sigs
+   Type: sort order
 
-   $pgp_show_unusable , $pgp_show_unusable
+   Default: alpha
 
-   $pgp_sign_as , $pgp_sign_as
+   Specifies how to sort entries in the file browser. By default, the
+   entries are sorted alphabetically. Valid values:
 
-   $pgp_sign_command , $pgp_sign_command
+   alpha (alphabetically)
+   date
+   size
+   unsorted
 
-   $pgp_sort_keys , $pgp_sort_keys
+   You may optionally use the ``reverse-'' prefix to specify reverse
+   sorting order (example: set sort_browser=reverse-date).
 
-   $pgp_strict_enc , $pgp_strict_enc
+312. $sort_re
 
-   $pgp_timeout , $pgp_timeout
+   Type: boolean
 
-   $pgp_use_gpg_agent , $pgp_use_gpg_agent
+   Default: yes
 
-   $pgp_verify_command , $pgp_verify_command
+   This variable is only useful when sorting by threads with
+   ``$$ssttrriicctt__tthhrreeaaddss'' _u_n_s_e_t. In that case, it changes the heuristic
+   Mutt-ng uses to thread messages by subject. With $$ssoorrtt__rree_s_e_t, Mutt-ng
+   will only attach a message as the child of another message by subject
+   if the subject of the child message starts with a substring matching
+   the setting of ``$$rreeppllyy__rreeggeexxpp''. With $$ssoorrtt__rree_u_n_s_e_t, Mutt-ng will
+   attach the message whether or not this is the case, as long as the
+   non-``$$rreeppllyy__rreeggeexxpp'' parts of both messages are identical.
 
-   $pgp_verify_key_command , $pgp_verify_key_command
+313. $spam_separator
 
-   $pipe_decode, Miscellaneous Functions
+   Type: string
 
-   <pipe-entry>, attach, compose
+   Default: ","
 
-   <pipe-message>, Miscellaneous Functions, index, pager
+   ``ssppaamm__sseeppaarraattoorr'' controls what happens when multiple spam headers
+   are matched: if _u_n_s_e_t, each successive header will overwrite any
+   previous matches value for the spam label. If _s_e_t, each successive
+   match will append to the previous, using ``ssppaamm__sseeppaarraattoorr'' as a
+   separator.
 
-   $pipe_split, Miscellaneous Functions
+314. $spoolfile
 
-   $pipe_decode , $pipe_decode
+   Type: path
 
-   $pipe_sep , $pipe_sep
+   Default: ""
 
-   $pipe_split , $pipe_split
+   If your spool mailbox is in a non-default place where Mutt-ng cannot
+   find it, you can specify its location with this variable. Mutt-ng will
+   automatically set this variable to the value of the environment
+   variable $MAIL if it is not set.
 
-   $pop_mail_check, POP3 Support (OPTIONAL), Configuration variables
+315. $ssl_ca_certificates_file
 
-   $pop_authenticators , $pop_authenticators
+   Type: path
 
-   $pop_auth_try_all , $pop_auth_try_all
+   Default: ""
 
-   $pop_delete , $pop_delete
+   This variable specifies a file containing trusted CA certificates. Any
+   server certificate that is signed with one of these CA certificates
+   are also automatically accepted.
 
-   $pop_host , $pop_host
+   Example: set
+   ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
 
-   $pop_last , $pop_last
+316. $ssl_client_cert
 
-   $pop_mail_check , $pop_mail_check
+   Type: path
 
-   $pop_pass , $pop_pass
+   Default: ""
 
-   $pop_reconnect , $pop_reconnect
+   Availability: SSL
 
-   $pop_user , $pop_user
+   The file containing a client certificate and its associated private
+   key.
 
-   $post_indent_string , Configuration variables
+317. $ssl_force_tls
 
-   $postpone, Postponing Mail, $postpone
+   Type: boolean
 
-   <postpone-message>, Composing new messages, compose
+   Default: no
 
-   $postponed, Postponing Mail, $postponed
+   If this variable is _s_e_t, Mutt-ng will require that all connections to
+   remote servers be encrypted. Furthermore it will attempt to negotiate
+   TLS even if the server does not advertise the capability, since it
+   would otherwise have to abort the connection anyway. This option
+   supersedes ``$$ssssll__ssttaarrttttllss''.
 
-   $post_indent_string , $post_indent_string
+318. $ssl_min_dh_prime_bits
 
-   $preconnect , $preconnect
+   Type: number
 
-   <previous-entry>, Moving Around in Menus, generic, pager
+   Default: 0
 
-   <previous-line>, generic, pager
+   Availability: GNUTLS
 
-   <previous-new>, index, pager
+   This variable specifies the minimum acceptable prime size (in bits)
+   for use in any Diffie-Hellman key exchange. A value of 0 will use the
+   default from the GNUTLS library.
 
-   <previous-new-then-unread>, index, pager
+319. $ssl_starttls
 
-   <previous-page>, generic, index, pager
+   Type: quadoption
 
-   <previous-subthread>, Threaded Mode, index, pager
+   Default: yes
 
-   <previous-thread>, Threaded Mode, index, pager
+   Availability: SSL or GNUTLS
 
-   <previous-undeleted>, index, pager
+   If _s_e_t (the default), Mutt-ng will attempt to use STARTTLS on servers
+   advertising the capability. When _u_n_s_e_t, Mutt-ng will not attempt to
+   use STARTTLS regardless of the server's capabilities.
 
-   <previous-unread>, index, pager
+320. $ssl_use_sslv2
 
-   $print , $print
+   Type: boolean
 
-   $print_command , Configuration variables
+   Default: no
 
-   <print-entry>, attach, compose
+   Availability: SSL
 
-   <print-message>, index, pager
+   This variables specifies whether to attempt to use SSLv2 in the SSL
+   authentication process.
 
-   $print_command , $print_command
+321. $ssl_use_sslv3
 
-   $print_decode , $print_decode
+   Type: boolean
 
-   $print_split , $print_split
+   Default: yes
 
-   $prompt_after , $prompt_after
+   Availability: SSL or GNUTLS
 
-   push, Adding key sequences to the keyboard buffer, Using Tags,
-   Configuration Commands
+   This variables specifies whether to attempt to use SSLv3 in the SSL
+   authentication process.
 
-  Q
+322. $ssl_use_tlsv1
 
-   <query>, index, query
+   Type: boolean
 
-   <query-append>, query
+   Default: yes
 
-   $query_command, External Address Queries
+   Availability: SSL or GNUTLS
 
-   $query_command , $query_command
+   This variables specifies whether to attempt to use TLSv1 in the SSL
+   authentication process.
 
-   <quit>, Moving Around in Menus, Composing new messages, $quit, index,
-   pager
+323. $ssl_usesystemcerts
 
-   <quote-char>, Editing Input Fields, editor
+   Type: boolean
 
-   $quote_regexp, Miscellaneous Functions, Using color and mono video
-   attributes
+   Default: yes
 
-   $quote_empty , $quote_empty
+   Availability: SSL
 
-   $quote_quoted , $quote_quoted
+   If set to _y_e_s, Mutt-ng will use CA certificates in the system-wide
+   certificate store when checking if server certificate is signed by a
+   trusted CA.
 
-   $quote_regexp , $quote_regexp
+324. $status_chars
 
-  R
+   Type: string
 
-   <read-subthread>, Threaded Mode, index, pager
+   Default: "-*%A"
 
-   <read-thread>, Threaded Mode, index, pager
+   Controls the characters used by the ``%r'' indicator in
+   ``$$ssttaattuuss__ffoorrmmaatt''. The first character is used when the mailbox is
+   unchanged. The second is used when the mailbox has been changed, and
+   it needs to be resynchronized. The third is used if the mailbox is in
+   read-only mode, or if the mailbox will not be written when exiting
+   that mailbox (You can toggle whether to write changes to a mailbox
+   with the toggle-write operation, bound by default to ``%''). The
+   fourth is used to indicate that the current folder has been opened in
+   attach-message mode (Certain operations like composing a new mail,
+   replying, forwarding, etc. are not permitted in this mode).
+
+325. $status_format
 
-   $read_inc , $read_inc
+   Type: string
 
-   $read_only , $read_only
+   Default: "-%r-Mutt-ng: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d?
+   Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l?
+   %l?]---(%s/%S)-%>-(%P)---"
 
-   $realname , $realname
+   Controls the format of the status line displayed in the _i_n_d_e_x menu.
+   This string is similar to ``$$iinnddeexx__ffoorrmmaatt'', but has its own set of
+   printf(3)-like sequences:
 
-   $recall , $recall
+   %b
+          number of mailboxes with new mail *
 
-   <recall-message>, index, pager
+   %B
+          the short pathname of the current mailbox
 
-   $record, Environment Variables, Specify default Fcc: mailbox when
-   composing, Mailbox Shortcuts, $record
+   %d
+          number of deleted messages *
 
-   <redraw-screen>, pager
+   %f
+          the full pathname of the current mailbox
 
-   <refresh>, generic
+   %F
+          number of flagged messages *
 
-   <rename-file>, compose
+   %h
+          local hostname
 
-   <reply>, Sending Mail, index, pager, attach
+   %l
+          size (in bytes) of the current mailbox *
 
-   reply-hook, Change settings based upon message recipients, Configuration
-   Commands
+   %L
+          size (in bytes) of the messages shown (i.e., which match the
+          current limit) *
 
-   $reply_to, Alternative addresses, Handling Mailing Lists
+   %m
+          the number of messages in the mailbox *
 
-   $reply_regexp , $reply_regexp
+   %M
+          the number of messages shown (i.e., which match the current
+          limit) *
 
-   $reply_self , $reply_self
+   %n
+          number of new messages in the mailbox *
 
-   $reply_to , $reply_to
+   %o
+          number of old unread messages *
 
-   <resend-message>, Miscellaneous Functions, The Attachment Menu, index,
-   attach
+   %p
+          number of postponed messages *
 
-   reset, Setting variables, Configuration Commands
+   %P
+          percentage of the way through the index
 
-   $resolve , $resolve
+   %r
+          modified/read-only/won't-write/attach-message indicator,
+          according to $$ssttaattuuss__cchhaarrss
 
-   $reverse_alias , $reverse_alias
+   %s
+          current sorting mode ($$ssoorrtt)
 
-   $reverse_name , $reverse_name
+   %S
+          current aux sorting method ($$ssoorrtt__aauuxx)
 
-   $reverse_realname , $reverse_realname
+   %t
+          number of tagged messages *
 
-   RfC
+   %u
+          number of unread messages *
 
-                1524, MIME Viewer configuration with mailcap, Command
-                Expansion, mailcap
+   %v
+          Mutt-ng version string
 
-                1894, Delivery Status Notification (DSN) Support
+   %V
+          currently active limit pattern, if any *
 
-                2822, Again: Scoring
+   %>X
+          right justify the rest of the string and pad with "X"
 
-                3676, Sending
+   %|X
+          pad to the end of the line with "X"
 
-                822, User defined headers
+   * = can be optionally printed if nonzero
 
-   $rfc2047_parameters , $rfc2047_parameters
+   Some of the above sequences can be used to optionally print a string
+   if their value is nonzero. For example, you may only want to see the
+   number of flagged messages if such messages exist, since zero is not
+   particularly meaningful. To optionally print a string based upon one
+   of the above sequences, the following construct is used
 
-  S
+   %?<sequence_char>?<optional_string>?
 
-   $save_empty, Compressed folders Support (OPTIONAL)
+   where _s_e_q_u_e_n_c_e___c_h_a_r is a character from the table above, and
+   _o_p_t_i_o_n_a_l___s_t_r_i_n_g is the string you would like printed if _s_e_q_u_e_n_c_e___c_h_a_r
+   is nonzero. _o_p_t_i_o_n_a_l___s_t_r_i_n_g_m_a_y contain other sequences as well as
+   normal text, but you may _n_o_t nest optional strings.
 
-   <save-entry>, attach
+   Here is an example illustrating how to optionally print the number of
+   new messages in a mailbox:
 
-   save-hook, Specify default save filename, Specify default save filename
-   and default Fcc: mailbox at once, Using Hooks, Message Matching in Hooks,
-   Mailbox Shortcuts, Configuration Commands
+   %?n?%n new messages.?
 
-   <save-message>, index, pager
+   Additionally you can switch between two strings, the first one, if a
+   value is zero, the second one, if the value is nonzero, by using the
+   following construct:
 
-   $save_address , $save_address
+   %?<sequence_char>?<if_string>&<else_string>?
 
-   $save_empty , $save_empty
+   You can additionally force the result of any printf(3)-like sequence
+   to be lowercase by prefixing the sequence character with an underscore
+   (_) sign. For example, if you want to display the local hostname in
+   lowercase, you would use:
 
-   $save_name , $save_name
+   %_h
 
-   score, Message Scoring, Configuration Commands, $score
+   If you prefix the sequence character with a colon (:) character,
+   Mutt-ng will replace any dots in the expansion by underscores. This
+   might be helpful with IMAP folders that don't like dots in folder
+   names.
 
-   $score_threshold_delete, Message Scoring
+326. $status_on_top
 
-   $score_threshold_flag, Message Scoring
+   Type: boolean
 
-   $score_threshold_read, Message Scoring
+   Default: no
 
-   $score_threshold_delete , $score_threshold_delete
+   Setting this variable causes the ``status bar'' to be displayed on the
+   first line of the screen rather than near the bottom.
 
-   $score_threshold_flag , $score_threshold_flag
+327. $strict_mailto
 
-   $score_threshold_read , $score_threshold_read
+   Type: boolean
 
-   <search>, generic, pager, alias, query, browser
+   Default: yes
 
-   <search-next>, generic, pager, alias, query, browser
+   With mailto: style links, a body as well as arbitrary header
+   information may be embedded. This may lead to (user) headers being
+   overwriten without note if ``$$eeddiitt__hheeaaddeerrss'' is unset.
 
-   <search-opposite>, generic, pager, query
+   If this variable is _s_e_t, Mutt-ng is strict and allows anything to be
+   changed. If it's _u_n_s_e_t, all headers given will be prefixed with
+   ``X-Mailto-'' and the message including headers will be shown in the
+   editor regardless of what ``$$eeddiitt__hheeaaddeerrss'' is set to.
 
-   <search-reverse>, generic, pager, alias, query, browser
+328. $strict_mime
 
-   <search-toggle>, pager
+   Type: boolean
 
-   <select-entry>, generic
+   Default: yes
 
-   <select-new>, browser
+   When _u_n_s_e_t, non MIME-compliant messages that doesn't have any charset
+   indication in the ``Content-Type:'' header field can be displayed (non
+   MIME-compliant messages are often generated by old mailers or buggy
+   mailers like MS Outlook Express). See also $$aassssuummeedd__cchhaarrsseett.
 
-   send-hook, Change settings based upon message recipients, Using Hooks,
-   Message Matching in Hooks, Configuration Commands
+   This option also replaces linear-white-space between encoded-word and
+   *text to a single space to prevent the display of MIME-encoded
+   ``Subject:'' header field from being devided into multiple lines.
 
-   <send-message>, Composing new messages, compose
+329. $strict_threads
 
-   send2-hook, Change settings based upon message recipients
+   Type: boolean
 
-   <senderdecode-copy>, pager
+   Default: no
 
-   $sendmail, Change settings based upon message recipients, $sendmail
+   If _s_e_t, threading will only make use of the ``In-Reply-To:'' and
+   ``References:'' header fields when you ``$$ssoorrtt'' by message threads.
+   By 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. See also
+   ``$$ssoorrtt__rree'' for a less drastic way of controlling this behaviour.
 
-   $sendmail_wait , $sendmail_wait
+330. $strip_was
 
-   $send_charset , $send_charset
+   Type: boolean
 
-   set, Setting variables, Configuration Commands
+   Default: no
 
-   <set-flag>, index
+   When _s_e_t, Mutt-ng will remove the trailing part of the ``Subject:''
+   line which matches $$ssttrriipp__wwaass__rreeggeexx when replying. This is useful to
+   properly react on subject changes and reduce ``subject noise.'' (esp.
+   in Usenet)
 
-   $shell , $shell
+331. $strip_was_regex
 
-   <shell-escape>, Miscellaneous Functions, generic, pager
+   Type: regular expression
 
-   <show-limit>, index
+   Default: "\([Ww][Aa][RrSs]: .*\)[ ]*$"
 
-   <show-version>, index, pager
+   When non-empty and $$ssttrriipp__wwaass is _s_e_t, Mutt-ng will remove this
+   trailing part of the ``Subject'' line when replying if it won't be
+   empty afterwards.
 
-   <sidebar-next>, sidebar
+332. $stuff_quoted
 
-   <sidebar-next-new>, sidebar
+   Type: boolean
 
-   <sidebar-open>, sidebar
+   Default: no
 
-   <sidebar-previous>, sidebar
+   If _s_e_t, attachments with flowed format will have their quoting
+   ``stuffed'', i.e. a space will be inserted between the quote
+   characters and the actual text.
 
-   <sidebar-scroll-down>, sidebar
+333. $suspend
 
-   <sidebar-scroll-up>, sidebar
+   Type: boolean
 
-   $sidebar_shorten_hierarchy , Configuration variables
+   Default: yes
 
-   $sidebar_boundary , $sidebar_boundary
+   When _u_n_s_e_t, Mutt-ng won't stop when the user presses the terminal's
+   _s_u_s_p key, usually CTRL+Z. This is useful if you run Mutt-ng inside an
+   xterm using a command like ``xterm -e muttng.''
 
-   $sidebar_delim , $sidebar_delim
+334. $text_flowed
 
-   $sidebar_newmail_only , $sidebar_newmail_only
+   Type: boolean
 
-   $sidebar_number_format , $sidebar_number_format
+   Default: no
 
-   $sidebar_shorten_hierarchy , $sidebar_shorten_hierarchy
+   When _s_e_t, Mutt-ng will generate text/plain; format=flowed attachments.
+   This format is easier to handle for some mailing software, and
+   generally just looks like ordinary text. To actually make use of this
+   format's features, you'll need support in your editor.
 
-   $sidebar_visible , $sidebar_visible
+   Note that $$iinnddeenntt__ssttrriinngg is ignored when this option is set.
 
-   $sidebar_width , $sidebar_width
+335. $thorough_search
 
-   $signature, Change settings based upon message recipients, $signature
+   Type: boolean
 
-   $signoff_string , $signoff_string
+   Default: no
 
-   $sig_dashes , $sig_dashes
+   Affects the ~b and ~h search operations described in section
+   ``ppaatttteerrnnss'' above. If _s_e_t, the headers and attachments of messages to
+   be searched are decoded before searching. If _u_n_s_e_t, messages are
+   searched as they appear in the folder.
 
-   $sig_on_top , $sig_on_top
+336. $thread_received
 
-   $simple_search , $simple_search
+   Type: boolean
 
-   <skip-quoted>, Miscellaneous Functions, pager
+   Default: no
 
-   $sleep_time , $sleep_time
+   When _s_e_t, Mutt-ng uses the date received rather than the date sent to
+   thread messages by subject.
 
-   $smart_wrap , $smart_wrap
+337. $tilde
 
-   $smileys , $smileys
+   Type: boolean
 
-   $smime_default_key , Configuration variables
+   Default: no
 
-   <smime-menu>, Composing new messages
+   When _s_e_t, the internal-pager will pad blank lines to the bottom of the
+   screen with a tilde (~).
 
-   $smime_ask_cert_label , $smime_ask_cert_label
+338. $timeout
 
-   $smime_ca_location , $smime_ca_location
+   Type: number
 
-   $smime_certificates , $smime_certificates
+   Default: 600
 
-   $smime_decrypt_command , $smime_decrypt_command
+   This variable controls the _n_u_m_b_e_r_ _o_f_ _s_e_c_o_n_d_s Mutt-ng will wait for a
+   key 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.
 
-   $smime_decrypt_use_default_key , $smime_decrypt_use_default_key
+339. $tmpdir
 
-   $smime_default_key , $smime_default_key
+   Type: path
 
-   $smime_encrypt_command , $smime_encrypt_command
+   Default: ""
 
-   $smime_encrypt_with , $smime_encrypt_with
+   This variable allows you to specify where Mutt-ng will place its
+   temporary files needed for displaying and composing messages. If this
+   variable is not set, the environment variable $TMPDIR is used. If
+   $TMPDIR is not set then "/tmp" is used.
 
-   $smime_get_cert_command , $smime_get_cert_command
+340. $to_chars
 
-   $smime_get_cert_email_command , $smime_get_cert_email_command
+   Type: string
 
-   $smime_get_signer_cert_command , $smime_get_signer_cert_command
+   Default: " +TCFL"
 
-   $smime_import_cert_command , $smime_import_cert_command
+   Controls the character used to indicate mail addressed to you. The
+   first character is the one used when the mail is NOT addressed to your
+   address (default: space). The second is used when you are the only
+   recipient of the message (default: +). The third is when your address
+   appears in the ``To:'' header field, but you are not the only
+   recipient of the message (default: T). The fourth character is used
+   when your address is specified in the ``Cc:'' header field, but you
+   are not the only recipient. The fifth character is used to indicate
+   mail that was sent by _y_o_u. The sixth character is used to indicate
+   when a mail was sent to a mailing-list you're subscribe to (default:
+   L).
 
-   $smime_is_default , $smime_is_default
+341. $trash
 
-   $smime_keys , $smime_keys
+   Type: path
 
-   $smime_pk7out_command , $smime_pk7out_command
+   Default: ""
 
-   $smime_sign_command , $smime_sign_command
+   If _s_e_t, this variable specifies the path of the trash folder where the
+   mails marked for deletion will be moved, instead of being irremediably
+   purged.
 
-   $smime_sign_opaque_command , $smime_sign_opaque_command
+   _N_o_t_e: When you delete a message in the trash folder, it is really
+   deleted, so that there is no way to recover mail.
 
-   $smime_timeout , $smime_timeout
+342. $tunnel
 
-   $smime_verify_command , $smime_verify_command
+   Type: string
 
-   $smime_verify_opaque_command , $smime_verify_opaque_command
+   Default: ""
 
-   $smtp_envelope, SMTP Support (OPTIONAL)
+   Setting this variable will cause Mutt-ng to open a pipe to a command
+   instead of a raw socket. You may be able to use this to set up
+   preauthenticated connections to your IMAP/POP3 server. Example:
 
-   $smtp_host, SMTP Support (OPTIONAL)
+   tunnel="ssh -q mailhost.net /usr/local/libexec/imapd"
 
-   $smtp_pass, SMTP Support (OPTIONAL), Configuration variables
+   _N_o_t_e_: For this example to work you must be able to log in to the
+   remote machine without having to enter a password.
 
-   $smtp_use_tls, SMTP Support (OPTIONAL)
+343. $umask
 
-   $smtp_user, SMTP Support (OPTIONAL), Configuration variables
+   Type: number
 
-   $smtp_host , $smtp_host
+   Default: 0077
 
-   $smtp_pass , $smtp_pass
+   This sets the umask that will be used by Mutt-ng when creating all
+   kinds of files. If _u_n_s_e_t, the default value is 077.
 
-   $smtp_port , $smtp_port
+344. $uncollapse_jump
 
-   $smtp_user , $smtp_user
+   Type: boolean
 
-   $smtp_use_tls , $smtp_use_tls
+   Default: no
 
-   $sort , $sort, browser
+   When _s_e_t, Mutt-ng will jump to the next unread message, if any, when
+   the current thread is _u_ncollapsed.
 
-   <sort-mailbox>, index
+345. $use_8bitmime
 
-   <sort-reverse>, index, browser
+   Type: boolean
 
-   $sort_alias , $sort_alias
+   Default: no
 
-   $sort_aux , $sort_aux
+   _W_a_r_n_i_n_g_: do not set this variable unless you are using a version of
+   sendmail which supports the -B8BITMIME flag (such as sendmail 8.8.x)
+   or in connection with the SMTP support via libESMTP. Otherwise you may
+   not be able to send mail.
 
-   $sort_browser , $sort_browser
+   When _s_e_t, Mutt-ng will either invoke ``$$sseennddmmaaiill'' with the -B8BITMIME
+   flag when sending 8-bit messages to enable ESMTP negotiation or tell
+   libESMTP to do so.
 
-   $sort_re , $sort_re
+346. $use_domain
 
-   source, Miscellaneous Functions, Defining/Using aliases, Reading
-   initialization commands from another file, Configuration Commands
+   Type: boolean
 
-   spam, Spam detection, Configuration Commands
+   Default: yes
 
-   $spam_separator , $spam_separator
+   When _s_e_t, Mutt-ng will qualify all local addresses (ones without the
+   @host portion) with the value of ``$$hhoossttnnaammee''. If _u_n_s_e_t, no addresses
+   will be qualified.
 
-   $spoolfile, Setting variables based upon mailbox, Defining mailboxes which
-   receive mail, Mailbox Shortcuts, POP3 Support (OPTIONAL), $spoolfile
+347. $use_envelope_from
 
-   $ssl_ca_certificates_file , $ssl_ca_certificates_file
+   Type: boolean
 
-   $ssl_client_cert , $ssl_client_cert
+   Default: no
 
-   $ssl_force_tls , $ssl_force_tls
+   When _s_e_t, Mutt-ng will use ``$$eennvveellooppee__ffrroomm__aaddddrreessss'' as the _e_n_v_e_l_o_p_e
+   sender if that is set, otherwise it will attempt to derive it from the
+   "From:" header.
 
-   $ssl_min_dh_prime_bits , $ssl_min_dh_prime_bits
+   _N_o_t_e_: This information is passed to sendmail command using the "-f"
+   command line switch and passed to the SMTP server for libESMTP (if
+   support is compiled in).
 
-   $ssl_starttls , $ssl_starttls
+348. $use_from
 
-   $ssl_usesystemcerts , $ssl_usesystemcerts
+   Type: boolean
 
-   $ssl_use_sslv2 , $ssl_use_sslv2
+   Default: yes
 
-   $ssl_use_sslv3 , $ssl_use_sslv3
+   When _s_e_t, Mutt-ng will generate the ``From:'' header field when
+   sending messages. If _u_n_s_e_t, no ``From:'' header field will be
+   generated unless the user explicitly sets one using the ``mmyy__hhddrr''
+   command.
 
-   $ssl_use_tlsv1 , $ssl_use_tlsv1
+349. $use_idn
 
-   $status_format, Composing new messages, Introduction
+   Type: boolean
 
-   $status_chars , $status_chars
+   Default: yes
 
-   $status_format , $status_format
+   Availability: IDN
 
-   $status_on_top , $status_on_top
+   When _s_e_t, Mutt-ng will show you international domain names decoded.
 
-   $strict_mailto, mailto:-style links
+   _N_o_t_e_: You can use IDNs for addresses even if this is _u_n_s_e_t. This
+   variable only affects decoding.
 
-   $strict_threads, Threaded Mode
+350. $use_ipv6
 
-   $strict_mailto , $strict_mailto
+   Type: boolean
 
-   $strict_mime , $strict_mime
+   Default: yes
 
-   $strict_threads , $strict_threads
+   When _s_e_t, Mutt-ng will look for IPv6 addresses of hosts it tries to
+   contact. If this option is _u_n_s_e_t, Mutt-ng will restrict itself to IPv4
+   addresses. Normally, the default should work.
 
-   $strip_was , $strip_was
+351. $visual
 
-   $strip_was_regex , $strip_was_regex
+   Type: path
 
-   $stuff_quoted , $stuff_quoted
+   Default: ""
 
-   subscribe, Mailing lists, Configuration Commands, browser
+   Specifies the visual editor to invoke when the _~_v command is given in
+   the builtin editor.
 
-   $suspend , $suspend
+352. $wait_key
 
-   <sync-mailbox>, Manual Conventions, index, pager
+   Type: boolean
 
-  T
+   Default: yes
 
-   <tag-entry>, generic
+   Controls whether Mutt-ng will ask you to press a key after _s_h_e_l_l_-
+   _e_s_c_a_p_e, _p_i_p_e_-_m_e_s_s_a_g_e, _p_i_p_e_-_e_n_t_r_y, _p_r_i_n_t_-_m_e_s_s_a_g_e, and _p_r_i_n_t_-_e_n_t_r_y
+   commands.
 
-   <tag-message>, pager
+   It is also used when viewing attachments with ``aauuttoo__vviieeww'', provided
+   that the corresponding mailcap entry has a needsterminal flag, and the
+   external program is interactive.
 
-   <tag-pattern>, index
+   When _s_e_t, Mutt-ng will always ask for a key. When _u_n_s_e_t, Mutt-ng will
+   wait for a key only if the external command returned a non-zero
+   status.
 
-   <tag-prefix>, generic
+353. $weed
 
-   <tag-prefix-cond>, generic
+   Type: boolean
 
-   <tag-thread>, Threaded Mode, index
+   Default: yes
 
-   $text_flowed , $text_flowed
+   When _s_e_t, Mutt-ng will weed headers when displaying, forwarding,
+   printing, or replying to messages.
 
-   $thorough_search , $thorough_search
+354. $wrap_search
 
-   $thread_received , $thread_received
+   Type: boolean
 
-   $tilde , $tilde
+   Default: yes
 
-   $timeout, IMAP Support (OPTIONAL), $timeout
+   Controls whether searches wrap around the end of the mailbox.
 
-   $tmpdir, Temporary Files, $tmpdir
+   When _s_e_t, searches will wrap around the first (or last) message. When
+   _u_n_s_e_t, searches will not wrap.
 
-   $to_chars, Status Flags
+355. $wrapmargin
 
-   toggle, Setting variables, Configuration Commands
+   Type: number
 
-   <toggle-mailboxes>, browser
+   Default: 0
 
-   <toggle-new>, index
+   Controls the size of the margin remaining at the right side of the
+   terminal when Mutt-ng's pager does smart wrapping.
 
-   <toggle-quoted>, Miscellaneous Functions, pager
+356. $write_bcc
 
-   <toggle-subscribed>, browser
+   Type: boolean
 
-   <toggle-unlink>, compose
+   Default: yes
 
-   <toggle-write>, index
+   Controls whether Mutt-ng writes out the Bcc header when preparing
+   messages to be sent. Exim users may wish to _u_n_s_e_t this.
 
-   <top>, pager
+357. $write_inc
 
-   <top-page>, generic
+   Type: number
 
-   $to_chars , $to_chars
+   Default: 10
 
-   <transpose-chars>, editor
+   When writing a mailbox, a message will be printed every _w_r_i_t_e___i_n_c
+   messages to indicate progress. If set to 0, only a single message will
+   be displayed before writing a mailbox.
 
-   $trash , $trash
+   Also see the ``$$rreeaadd__iinncc'' variable.
 
-   $tunnel , $tunnel
+358. $xterm_icon
 
-  U
+   Type: string
 
-   $umask, Temporary Files, $umask
+   Default: "M%?n?AIL&ail?"
 
-   unalias, Defining/Using aliases, Configuration Commands
+   Controls the format of the X11 icon title, as long as
+   $$xxtteerrmm__sseett__ttiittlleess is _s_e_t. This string is identical in formatting to
+   the one used by ``$$ssttaattuuss__ffoorrmmaatt''.
 
-   unalternates, Alternative addresses, Configuration Commands
+359. $xterm_leave
 
-   unalternative_order, MIME Multipart/Alternative, Configuration Commands
+   Type: string
 
-   unattachments, Attachment Searching and Counting
+   Default: ""
 
-   unauto_view, MIME Autoview, Configuration Commands
+   If $$xxtteerrmm__sseett__ttiittlleess is _s_e_t, this string will be used to set the title
+   when leaving Mutt-ng. For terminal-based programs, there's no easy and
+   portable way to read the current title so Mutt-ng cannot read it upon
+   startup and restore it when exiting.
 
-   $uncollapse_jump , $uncollapse_jump
+   Based on the xterm FAQ, the following might work:
 
-   uncolor, Using color and mono video attributes, Configuration Commands
+   set xterm_leave = "`test x$DISPLAY != x && xprop -id $WINDOWID | grep
+   WM_NAME | cut -d '"' -f 2`"
 
-   <undelete-entry>, attach, postpone
+360. $xterm_set_titles
 
-   <undelete-message>, index, pager
+   Type: boolean
 
-   <undelete-pattern>, index
+   Default: no
 
-   <undelete-subthread>, Threaded Mode, index, pager
+   Controls whether Mutt-ng sets the xterm title bar and icon name (as
+   long as you're in an appropriate terminal). The default must be _u_n_s_e_t
+   to force in the validity checking.
 
-   <undelete-thread>, Threaded Mode, index, pager
+361. $xterm_title
 
-   unhdr_order, Defining the order of headers when viewing messages,
-   Configuration Commands
+   Type: string
 
-   unhook, Removing hooks, Configuration Commands
+   Default: "Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?"
 
-   unignore, Ignoring (weeding) unwanted message headers, Configuration
-   Commands
+   Controls the format of the title bar of the xterm provided that
+   $$xxtteerrmm__sseett__ttiittlleess has been _s_e_t. This string is identical in formatting
+   to the one used by ``$$ssttaattuuss__ffoorrmmaatt''.
 
-   unlists, Mailing lists, Configuration Commands
+5. Functions
 
-   unmailboxes, Defining mailboxes which receive mail
+   The following is the list of available functions listed by the mapping
+   in which they are available. The default key setting is given, and an
+   explanation of what the function does. The key bindings of these
+   functions can be changed with the bbiinndd command.
+
+5.1. generic
+
+   The _g_e_n_e_r_i_c menu is not a real menu, but specifies common functions
+   (such as movement) available in all menus except for _p_a_g_e_r and _e_d_i_t_o_r.
+   Changing settings for this menu will affect the default bindings for
+   all menus (except as noted).
+
+   _T_a_b_l_e_ _7_._4_._ _R_e_f_e_r_e_n_c_e_:_ _D_e_f_a_u_l_t_ _G_e_n_e_r_i_c_ _F_u_n_c_t_i_o_n_ _B_i_n_d_i_n_g_s
+   Function Default Key Description
+   <bottom-page> L move to the bottom of the page
+   <current-bottom>   move current entry to bottom of page
+   <current-middle>   move current entry to middle of page
+   <current-top>   move current entry to top of page
+   <enter-command> : enter a muttngrc command
+   <exit> q exit this menu
+   <first-entry> = move to the first entry
+   <half-down> ] scroll down 1/2 page
+   <half-up> [ scroll up 1/2 page
+   <help> ? this screen
+   <jump> number jump to an index number
+   <last-entry> * move to the last entry
+   <middle-page> M move to the middle of the page
+   <next-entry> j move to the next entry
+   <next-line> > scroll down one line
+   <next-page> z move to the next page
+   <previous-entry> k move to the previous entry
+   <previous-line> > scroll up one line
+   <previous-page> Z move to the previous page
+   <rebuild-cache>   cycle through all defined mailboxes to rebuild all
+   header caches
+   <refresh> C-L clear and redraw the screen
+   <search> / search for a regular expression
+   <search-next> n search for next match
+   <search-opposite>   search for next match in opposite direction
+   <search-reverse> E-/ search backwards for a regular expression
+   <select-entry> Return select the current entry
+   <shell-escape> ! run a program in a subshell
+   <tag-entry> t toggle the tag on the current entry
+   <tag-prefix> ; apply next command to tagged entries
+   <tag-prefix-cond>   apply next function ONLY to tagged messages
+   <top-page> H move to the top of the page
+   <what-key>   display the keycode for a key press
+
+5.2. index
+
+   _T_a_b_l_e_ _7_._5_._ _R_e_f_e_r_e_n_c_e_:_ _D_e_f_a_u_l_t_ _I_n_d_e_x_ _F_u_n_c_t_i_o_n_ _B_i_n_d_i_n_g_s
+   Function Default Key Description
+   <bounce-message> b remail a message to another user
+   <change-folder> c open a different folder
+   <change-folder-readonly> E-c open a different folder in read only mode
+   <check-traditional-pgp> E-P check for classic pgp
+   <clear-flag> W clear a status flag from a message
+   <copy-message> C copy a message to a file/mailbox
+   <create-alias> a create an alias from a message sender
+   <decode-copy> E-C decode a message and copy it to a file/mailbox
+   <decode-save> E-s decode a message and save it to a file/mailbox
+   <delete-message> d delete the current entry
+   <delete-pattern> D delete messages matching a pattern
+   <delete-subthread> E-d delete all messages in subthread
+   <delete-thread> C-D delete all messages in thread
+   <display-address> @ display full address of sender
+   <display-toggle-weed> h display message and toggle header weeding
+   <display-message> Return display a message
+   <edit> e edit the current message
+   <edit-type> C-E edit the current message's Content-Type
+   <exit> x exit without saving changes
+   <extract-keys> C-K extract PGP public keys
+   <fetch-mail> G retrieve mail from POP server
+   <flag-message> F toggle a message's 'important' flag
+   <forget-passphrase> C-F wipe PGP passphrase from memory
+   <forward-message> f forward a message with comments
+   <group-reply> g reply to all recipients
+   <limit> l show only messages matching a pattern
+   <list-reply> L reply to specified mailing list
+   <mail> m compose a new mail message
+   <mail-key> E-k mail a PGP public key
+   <next-new>   jump to the next new message
+   <next-new-then-unread> Tab jump to the next new or unread message
+   <next-subthread> E-n jump to the next subthread
+   <next-thread> C-N jump to the next thread
+   <next-undeleted> j move to the next undeleted message
+   <next-unread>   jump to the next unread message
+   <parent-message> P jump to parent message in thread
+   <pipe-message> | pipe message/attachment to a shell command
+   <previous-new>   jump to the previous new message
+   <previous-new-then-unread> E-Tab jump to the previous new or unread
+   message
+   <previous-page> Z move to the previous page
+   <previous-subthread> E-p jump to previous subthread
+   <previous-thread> C-P jump to previous thread
+   <previous-undeleted> k move to the last undelete message
+   <previous-unread>   jump to the previous unread message
+   <print-message> p print the current entry
+   <query> Q query external program for addresses
+   <quit> q save changes to mailbox and quit
+   <read-subthread> E-r mark the current subthread as read
+   <read-thread> C-R mark the current thread as read
+   <recall-message> R recall a postponed message
+   <reply> r reply to a message
+   <resend-message> E-e resend message and preserve MIME structure
+   <save-message> s save message/attachment to a file
+   <set-flag> w set a status flag on a message
+   <show-version> V show the Mutt-ng version number and date
+   <show-limit> E-l show currently active limit pattern, if any
+   <sort-mailbox> o sort messages
+   <sort-reverse> O sort messages in reverse order
+   <sync-mailbox> $ save changes to mailbox
+   <tag-pattern> T tag messages matching a pattern
+   <tag-thread> E-t tag/untag all messages in the current thread
+   <toggle-new> N toggle a message's 'new' flag
+   <toggle-write> % toggle whether the mailbox will be rewritten
+   <undelete-message> u undelete the current entry
+   <undelete-pattern> U undelete messages matching a pattern
+   <undelete-subthread> E-u undelete all messages in subthread
+   <undelete-thread> C-U undelete all messages in thread
+   <untag-pattern> C-T untag messages matching a pattern
+   <view-attachments> v show MIME attachments
+
+5.3. pager
+
+   _T_a_b_l_e_ _7_._6_._ _R_e_f_e_r_e_n_c_e_:_ _D_e_f_a_u_l_t_ _P_a_g_e_r_ _F_u_n_c_t_i_o_n_ _B_i_n_d_i_n_g_s
+   Function Default Key Description
+   <bottom>   jump to the bottom of the message
+   <bounce-message> b remail a message to another user
+   <change-folder> c open a different folder
+   <change-folder-readonly> E-c open a different folder in read only mode
+   <check-traditional-pgp> E-P check for classic pgp
+   <copy-message> C copy a message to a file/mailbox
+   <create-alias> a create an alias from a message
+   <senderdecode-copy> E-C decode a message and copy it to a file/mailbox
+   <decode-save> E-s decode a message and save it to a file/mailbox
+   <delete-message> d delete the current entry
+   <delete-subthread> E-d delete all messages in subthread
+   <delete-thread> C-D delete all messages in thread
+   <display-address> @ display full address of sender
+   <display-toggle-weed> h display message and toggle header weeding
+   <edit> e edit the current message
+   <edit-type> C-E edit the current message's Content-Type
+   <enter-command> : enter a muttngrc command
+   <exit> i return to the main-menu
+   <extract-keys> C-K extract PGP public keys
+   <flag-message> F toggle a message's 'important' flag
+   <forget-passphrase> C-F wipe PGP passphrase from memory
+   <forward-message> f forward a message with comments
+   <group-reply> g reply to all recipients
+   <half-up>   move up one-half page
+   <half-down>   move down one-half page
+   <help> ? this screen
+   <list-reply> L reply to specified mailing list
+   <mail> m compose a new mail message
+   <mail-key> E-k mail a PGP public key
+   <mark-as-new> N toggle a message's 'new' flag
+   <next-line> Return scroll down one line
+   <next-entry> J move to the next entry
+   <next-new>   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> E-n jump to the next subthread
+   <next-thread> C-N jump to the next thread
+   <next-undeleted> j move to the next undeleted message
+   <next-unread>   jump to the next unread message
+   <parent-message> P jump to parent message in thread
+   <pipe-message> | pipe message/attachment to a shell command
+   <previous-line> BackSpace scroll up one line
+   <previous-entry> K move to the previous entry
+   <previous-new>   jump to the previous new message
+   <previous-new-then-unread>   jump to the previous new or unread
+   message
+   <previous-page> - move to the previous page
+   <previous-subthread> E-p jump to previous subthread
+   <previous-thread> C-P jump to previous thread
+   <previous-undeleted> k move to the last undelete message
+   <previous-unread>   jump to the previous unread message
+   <print-message> p print the current entry
+   <quit> Q save changes to mailbox and quit
+   <read-subthread> E-r mark the current subthread as read
+   <read-thread> C-R mark the current thread as read
+   <recall-message> R recall a postponed message
+   <redraw-screen> C-L clear and redraw the screen
+   <reply> r reply to a message
+   <save-message> s save message/attachment to a file
+   <search> / search for a regular expression
+   <search-next> n search for next match
+   <search-opposite>   search for next match in opposite direction
+   <search-reverse> E-/ search backwards for a regular expression
+   <search-toggle> \ toggle search pattern coloring
+   <shell-escape> ! invoke a command in a subshell
+   <show-version> V show the Mutt-ng version number and date
+   <skip-quoted> S skip beyond quoted text
+   <sync-mailbox> $ save changes to mailbox
+   <tag-message> t tag a message
+   <toggle-quoted> T toggle display of quoted text
+   <top> ^ jump to the top of the message
+   <undelete-message> u undelete the current entry
+   <undelete-subthread> E-u undelete all messages in subthread
+   <undelete-thread> C-U undelete all messages in thread
+   <view-attachments> v show MIME attachments
+
+5.4. alias
+
+   _T_a_b_l_e_ _7_._7_._ _R_e_f_e_r_e_n_c_e_:_ _D_e_f_a_u_l_t_ _A_l_i_a_s_ _M_e_n_u_ _F_u_n_c_t_i_o_n_ _B_i_n_d_i_n_g_s
+   Function         Default Key Description
+   <search>         /           search for a regular expression
+   <search-next>    n           search for next match
+   <search-reverse> E-/         search backwards for a regular expression
 
-   unmime_lookup, MIME Lookup, Configuration Commands
+5.5. query
 
-   unmono, Using color and mono video attributes, Configuration Commands
+   _T_a_b_l_e_ _7_._8_._ _R_e_f_e_r_e_n_c_e_:_ _D_e_f_a_u_l_t_ _Q_u_e_r_y_ _M_e_n_u_ _F_u_n_c_t_i_o_n_ _B_i_n_d_i_n_g_s
+   Function          Default Key Description
+   <create-alias>    a           create an alias from a message sender
+   <mail>            m           compose a new mail message
+   <query>           Q           query external program for addresses
+   <query-append>    A           append new query results to current results
+   <search>          /           search for a regular expression
+   <search-next>     n           search for next match
+   <search-opposite>             search for next match in opposite direction
+   <search-reverse>  E-/         search backwards for a regular expression
 
-   unmy_hdr, User defined headers, Configuration Commands
+5.6. attach
+
+   _T_a_b_l_e_ _7_._9_._ _R_e_f_e_r_e_n_c_e_:_ _D_e_f_a_u_l_t_ _A_t_t_a_c_h_m_e_n_t_ _M_e_n_u_ _F_u_n_c_t_i_o_n_ _B_i_n_d_i_n_g_s
+   Function Default Key Description
+   <bounce-message> b remail a message to another user
+   <collapse-parts> v toggle display of subparts
+   <delete-entry> d delete the current entry
+   <display-toggle-weed> h display message and toggle header weeding
+   <edit-type> C-E edit the current entry's Content-Type
+   <extract-keys> C-K extract PGP public keys
+   <forward-message> f forward a message with comments
+   <group-reply> g reply to all recipients
+   <list-reply> L reply to specified mailing list
+   <pipe-entry> | pipe message/attachment to a shell command
+   <print-entry> p print the current entry
+   <reply> r reply to a message
+   <resend-message> E-e resend message and preserve MIME structure
+   <save-entry> s save message/attachment to a file
+   <undelete-entry> u undelete the current entry
+   <view-attach> Return view attachment using mailcap entry if necessary
+   <view-mailcap> m force viewing of attachment using mailcap
+   <view-text> T view attachment as text
+
+5.7. compose
+
+   _T_a_b_l_e_ _7_._1_0_._ _R_e_f_e_r_e_n_c_e_:_ _D_e_f_a_u_l_t_ _C_o_m_p_o_s_e_ _M_e_n_u_ _F_u_n_c_t_i_o_n_ _B_i_n_d_i_n_g_s
+   Function Default Key Description
+   <attach-file> a attach a file(s) to this message
+   <attach-message> A attach message(s) to this message
+   <attach-key> E-k attach a PGP public key
+   <copy-file> C save message/attachment to a file
+   <detach-file> D delete the current entry
+   <display-toggle-weed> h display message and toggle header weeding
+   <edit-bcc> b edit the BCC list
+   <edit-cc> c edit the CC list
+   <edit-description> d edit attachment description
+   <edit-encoding> C-E edit attachment transfer-encoding
+   <edit-fcc> f enter a file to save a copy of this message in
+   <edit-from> E-f edit the from: field
+   <edit-file> C-X e edit the file to be attached
+   <edit-headers> E edit the message with headers
+   <edit> e edit the message
+   <edit-mime> m edit attachment using mailcap entry
+   <edit-reply-to> r edit the Reply-To field
+   <edit-subject> s edit the subject of this message
+   <edit-to> t edit the TO list
+   <edit-type> C-T edit attachment type
+   <filter-entry> F filter attachment through a shell command
+   <forget-passphrase> C-F wipe PGP passphrase from memory
+   <ispell> i run ispell on the message
+   <new-mime> n compose new attachment using mailcap entry
+   <pgp-menu> p show PGP options
+   <pipe-entry> | pipe message/attachment to a shell command
+   <postpone-message> P save this message to send later
+   <print-entry> l print the current entry
+   <rename-file> R rename/move an attached file
+   <send-message> y send the message
+   <toggle-unlink> u toggle whether to delete file after sending it
+   <view-attach> Return view attachment using mailcap entry if necessary
+   <write-fcc> w write the message to a folder
+
+5.8. postpone
+
+   _T_a_b_l_e_ _7_._1_1_._ _R_e_f_e_r_e_n_c_e_:_ _D_e_f_a_u_l_t_ _P_o_s_t_p_o_n_e_ _M_e_n_u_ _F_u_n_c_t_i_o_n_ _B_i_n_d_i_n_g_s
+   Function         Default Key Description
+   <delete-entry>   d           delete the current entry
+   <undelete-entry> u           undelete the current entry
 
-   unscore, Message Scoring, Configuration Commands
+5.9. browser
+
+   _T_a_b_l_e_ _7_._1_2_._ _R_e_f_e_r_e_n_c_e_:_ _D_e_f_a_u_l_t_ _B_r_o_w_s_e_r_ _M_e_n_u_ _F_u_n_c_t_i_o_n_ _B_i_n_d_i_n_g_s
+   Function Default Key Description
+   <change-dir> c change directories
+   <check-new> Tab check mailboxes for new mail
+   <enter-mask> m enter a file mask
+   <search> / search for a regular expression
+   <search-next> n search for next match
+   <search-reverse> E-/ search backwards for a regular expression
+   <select-new> N select a new file in this directory
+   <sort> o sort messages
+   <sort-reverse> O sort messages in reverse order
+   <toggle-mailboxes> Tab toggle whether to browse mailboxes or all files
+   <view-file> Space view file
+   <subscribe> s subscribe to current mailbox (IMAP Only)
+   <unsubscribe> u unsubscribe to current mailbox (IMAP Only)
+   <toggle-subscribed> T toggle view all/subscribed mailboxes (IMAP Only)
+
+5.10. pgp
+
+   _T_a_b_l_e_ _7_._1_3_._ _R_e_f_e_r_e_n_c_e_:_ _D_e_f_a_u_l_t_ _P_G_P_ _M_e_n_u_ _F_u_n_c_t_i_o_n_ _B_i_n_d_i_n_g_s
+   Function     Default Key Description
+   <view-name>  %           view the key's user id
+   <verify-key> c           verify a PGP public key
 
-   unset, Setting variables, Configuration Commands
+5.11. editor
 
-   unsubscribe, Mailing lists, Configuration Commands, browser
+   _T_a_b_l_e_ _7_._1_4_._ _R_e_f_e_r_e_n_c_e_:_ _D_e_f_a_u_l_t_ _E_d_i_t_o_r_ _F_u_n_c_t_i_o_n_ _B_i_n_d_i_n_g_s
+   Function          Default Key Description
+   <backspace>       BackSpace   delete the char in front of the cursor
+   <backward-char>   C-B         move the cursor one character to the left
+   <backward-word>   E-b         move the cursor to the previous word
+   <bol>             C-A         jump to the beginning of the line
+   <buffy-cycle>     Space       cycle among incoming mailboxes
+   <capitalize-word> E-c         uppercase the first character in the word
+   <complete>        Tab         complete filename or alias
+   <complete-query>  C-T         complete address with query
+   <delete-char>     C-D         delete the char under the cursor
+   <downcase-word>   E-l         lowercase all characters in current word
+   <eol>             C-E         jump to the end of the line
+   <forward-char>    C-F         move the cursor one character to the right
+   <forward-word>    E-f         move the cursor to the next word
+   <history-down>                scroll down through the history list
+   <history-up>                  scroll up through the history list
+   <kill-eol>        C-K         delete chars from cursor to end of line
+   <kill-eow>        E-d         delete chars from cursor to end of word
+   <kill-line>       C-U         delete all chars on the line
+   <kill-word>       C-W         delete the word in front of the cursor
+   <quote-char>      C-V         quote the next typed key
+   <transpose-chars>             transpose character under cursor with previous
+   <upcase-word>     E-u         uppercase all characters in current word
 
-   <untag-pattern>, index
+5.12. sidebar
 
-   <upcase-word>, Editing Input Fields, editor
+   _T_a_b_l_e_ _7_._1_5_._ _R_e_f_e_r_e_n_e_:_ _D_e_f_a_u_l_t_ _S_i_d_e_b_a_r_ _F_u_n_c_t_i_o_n_ _B_i_n_d_i_n_g_s
+   Key Function              Description
+       <sidebar-scroll-up>   Scrolls the mailbox list up 1 page
+       <sidebar-scroll-down> Scrolls the mailbox list down 1 page
+       <sidebar-next>        Highlights the next mailbox
+       <sidebar-next-new>    Highlights the next mailbox with new mail
+       <sidebar-previous>    Highlights the previous mailbox
+       <sidebar-open>        Opens the currently highlighted mailbox
 
-   $use_8bitmime, SMTP Support (OPTIONAL)
+Appendix A. Acknowledgments
 
-   $use_8bitmime , $use_8bitmime
+   Kari Hurtta <kkaarrii..hhuurrttttaa@@ffmmii..ffii> co-developed the original MIME
+   >parsing code back in the ELM-ME days.
 
-   $use_domain , $use_domain
+   The following people have been very helpful to the development of Mutt
+   (sorted by surnames):
 
-   $use_envelope_from , $use_envelope_from
+     * Vikas Agnihotri <vviikkaassaa@@wwrriitteemmee..ccoomm>
+     * Francois Berjon < FFrraannccooiiss..BBeerrjjoonn@@aaaarr..aallccaatteell--aallsstthhoomm..ffrr>
+     * Aric Blumer <aarriicc@@ffoorree..ccoomm>
+     * John Capo <jjcc@@iirrbbss..ccoomm>
+     * David Champion <ddggcc@@uucchhiiccaaggoo..eedduu>
+     * Brendan Cully <bbrreennddaann@@kkuubbllaaii..ccoomm>
+     * Liviu Daia <ddaaiiaa@@ssttooiillooww..iimmaarr..rroo>
+     * Thomas E. Dickey <ddiicckkeeyy@@hheerrnnddoonn44..hhiiss..ccoomm>
+     * David DeSimone <ffooxx@@ccoonnvveexx..hhpp..ccoomm>
+     * Nickolay N. Dudorov <nnnndd@@wwiinntt..iittffss..nnsskk..ssuu>
+     * Ruslan Ermilov <rruu@@ffrreeeebbssdd..oorrgg>
+     * Edmund Grimley Evans <eeddmmuunnddoo@@rraannoo..oorrgg>
+     * Michael Finken <ffiinnkkeenn@@ccoonnwwaarree..ddee>
+     * Sven Guckes <gguucckkeess@@mmaatthh..ffuu--bbeerrlliinn..ddee>
+     * Lars Hecking <llhheecckkiinngg@@nnmmrrcc..iiee>
+     * Mark Holloman <hhoolllloommaann@@nnaannddoo..nneett>
+     * Andreas Holzmann <hhoollzzmmaannnn@@ffmmii..uunnii--ppaassssaauu..ddee>
+     * Marco d'Itri <mmdd@@lliinnuuxx..iitt>
+     * Björn Jacke <bbjjaacckkee@@ssuussee..ccoomm>
+     * Byrial Jensen <bbyyrriiaall@@iimmaaggee..ddkk>
+     * David Jeske <jjeesskkee@@iiggccoomm..nneett>
+     * Christophe Kalt <kkaalltt@@hhuuggoo..iinntt--eevvrryy..ffrr>
+     * Tommi Komulainen <TToommmmii..KKoommuullaaiinneenn@@iikkii..ffii>
+     * Felix von Leitner (a.k.a ``Fefe'') < lleeiittnneerr@@mmaatthh..ffuu--bbeerrlliinn..ddee >
+     * Brandon Long <bblloonngg@@ffiiccttiioonn..nneett>
+     * Jimmy Mäkeä <jjmmyy@@ffllaasshhbbaacckk..nneett>
+     * Lars Marowsky-Bree <llmmbb@@ppooiinntteerr..iinn--mmiinnddeenn..ddee>
+     * Thomas ``Mike'' Michlmayr <mmiikkee@@ccoossyy..ssbbgg..aacc..aatt>
+     * Andrew W. Nosenko <aawwnn@@bbccss..zzpp..uuaa>
+     * David O'Brien <oobbrriieenn@@NNuuxxii..ccss..uuccddaavviiss..eedduu>
+     * Clint Olsen <oollsseenncc@@iicchhiippss..iinntteell..ccoomm>
+     * Park Myeong Seok <ppmmss@@rroommaannccee..kkaaiisstt..aacc..kkrr>
+     * Thomas Parmelan <ttoomm@@aannkkhh..ffrr..eeuu..oorrgg>
+     * Ollivier Robert <rroobbeerrttoo@@kkeellttiiaa..ffrreeeenniixx..ffrr>
+     * Thomas Roessler <rrooeesssslleerr@@ddooeess--nnoott--eexxiisstt..oorrgg>
+     * Roland Rosenfeld <rroollaanndd@@ssppiinnnnaakkeerr..ddee>
+     * TAKIZAWA Takashi <ttaakkii@@lluunnaa..eemmaaiill..nnee..jjpp>
+     * Allain Thivillon <AAllllaaiinn..TThhiivviilllloonn@@aallmmaa..ffrr>
+     * Gero Treuner <ggeerroo@@7700tt..ddee>
+     * Vsevolod Volkov <vvvvvv@@lluucckkyy..nneett>
+     * Ken Weinert <kkeennww@@iihhss..ccoomm>
 
-   $use_from , $use_from
+   Mutt-ng is developed by the following people:
 
-   $use_idn , $use_idn
+     * Andreas Krennmair <aakk@@ssyynnfflloooodd..aatt>
+     * Nico Golde <nniiccoo@@nnggoollddee..ddee>
+     * Rocco Rutte <ppddmmeeff@@ccss..ttuu--bbeerrlliinn..ddee>
 
-   $use_ipv6 , $use_ipv6
+   The following people have been very helpful to the development of
+   Mutt-ng (sorted by surnames):
 
-  V
+     * Christian Gall <ccgg@@ccggaallll..ddee>
+     * Iain Lea <iiaaiinn@@bbrriiccbbrraacc..ddee>
+     * Andreas Kneib <aakknneeiibb@@ggmmxx..nneett>
+     * Felix Meinhold <ffeelliixx..mmeeiinnhhoolldd@@ggmmxx..nneett>
+     * Carsten Schoelzki <ccjjss@@wweeiisssshhuuhhnn..ddee>
+     * Elimar Riesebieter <rriieesseebbiiee@@llxxtteecc..ddee>
 
-   <verify-key>, pgp
+Appendix B. Hacking Documentation
 
-   <view-attach>, attach, compose
+   This manual is written in XML and transformed via a XSLT stylesheet
+   into valid DocBook/XML and/or LaTeX to be again transformed via a XSLT
+   stylesheet into the final formats.
 
-   <view-attachments>, index, pager
+   This two pass processing is required to keep the file size low and to
+   sanitize use, i.e. drastically lower the typing overhead.
 
-   <view-file>, browser
+   To achieve the latter, the sources come with a file called
+   muttng-manual.xsl introducing the muttng-doc namespace which offers
+   the following tags to be used (_n_o_t_e_:_ _t_h_i_s_ _i_s_ _f_a_r_ _f_r_o_m_ _b_e_i_n_g_ _c_o_m_p_l_e_t_e_,
+   _a_n_y_ _h_e_l_p_ _t_o_w_a_r_d_s_ _c_o_n_s_i_s_t_e_n_c_y_ _i_s_ _h_i_g_h_l_y_ _a_p_p_r_e_c_i_a_t_e_d).
 
-   <view-mailcap>, attach
+   <muttng-doc:man name="" [sect=""]/>
+          _R_e_f_e_r_e_n_c_e_s_ _t_o_ _m_a_n_u_a_l_ _p_a_g_e_s_. If the sect parameter is omitted,
+          it'll be 1 for the commands section. There's no auto-indexing
+          yet.
 
-   <view-name>, pgp
+   <muttng-doc:envvar name=""/>
+          _R_e_f_e_r_e_n_c_e_s_ _t_o_ _e_n_v_i_r_o_n_m_e_n_t_ _v_a_r_i_a_b_l_e_s_. The name parameter must
+          contain upper-case letters only without the dollar sign as
+          it'll be added automatically. Auto-indexing is done.
 
-   <view-text>, attach
+   <muttng-doc:hook name=""/>
+          _R_e_f_e_r_e_n_c_e_s_ _t_o_ _h_o_o_k_s_. The string -hook will be added
+          automatically to the value given in the name parameter. All
+          entries will be auto-indexed.
 
-   $VISUAL, Composing new messages
+   <muttng-doc:pattern name="" [full="1"]/>
+          _R_e_f_e_r_e_n_c_e_s_ _t_o_ _p_a_t_t_e_r_n_s_. The name parameter must only contain
+          the letter/symbol for the pattern as the tilde symbol/equal
+          sign will be added automatically. Auto-indexing is done. If the
+          full parameter is given the equal sign as well as tilde will be
+          printed for a fully complete reference.
 
-   $visual , $visual
+   <muttng-doc:key [mod="C|E"]>key</muttng-doc:key>
+          _R_e_f_e_r_e_n_c_i_n_g_ _a_ _k_e_y_.. Because it's somewhat untrivial to always
+          get the right escaping for LaTeX, there's a tag for it. The
+          optional modifiers C or E stand for Control and Escape
+          respectively. To still allow escaping, the actual key sequences
+          must be given within the tag.
 
-  W
+   <muttng-doc:funcdef name=""/>
+          _D_e_f_i_n_i_n_g_ _a_ _c_o_m_m_a_n_d_.. It's used to define a command with the
+          name given in the name parameter. The default key binding must
+          be given via <muttng-doc:key/> (see above). The string will be
+          automatically enclosed in <>. Auto-indexing is done. Also an
+          anchor with id func-[name] will be added with [name] being the
+          value of the name parameter.
 
-   $wait_key, Miscellaneous Functions, Optional Fields
+   <muttng-doc:funcref name=""/>
+          _R_e_f_e_r_e_n_c_e_s_ _t_o_ _f_u_n_c_t_i_o_n_s_.. This is practically the same as the
+          above except that there's no anchor defined.
 
-   $wait_key , $wait_key
+   <muttng-doc:vardef name=""/>
+          _D_e_f_i_n_i_n_g_ _a_ _v_a_r_i_a_b_l_e_. This is to be used by makedoc only to
+          define a command with a given name and XML-normalized link
+          given via id. Auto-indexing is done. The name parameter's value
+          will be prefixed with a dollar sign as for environment
+          variables.
 
-   $weed, Miscellaneous Functions, $weed
+   <muttng-doc:varref name=""/>
+          _R_e_f_e_r_e_n_c_e_s_ _t_o_ _v_a_r_i_a_b_l_e_s_. This practically is the same as above
+          except that the text inbetween won't be wrapped within a
+          <sect1> tag. Auto-indexing is the same as for the above. This
+          one is intended for manual use.
 
-   <what-key>, generic
+   <muttng-doc:web url""/>
+          _P_r_e_t_t_y_ _p_r_i_n_t_ _a_ _l_i_n_k_e_d_ _U_R_L. As for E-Mail addresses where the
+          text (mostly) equals the link's target, URLs must be enclosed
+          in <> (also this reduced redudant URL typing).
 
-   $wrapmargin , $wrapmargin
+   <muttng-doc:rfc num=""/>
+          _R_e_f_e_r_e_n_c_e_s_ _t_o_ _R_f_C_ _d_o_c_u_m_e_n_t_s_. Use this to produce links to RfC
+          document with number given as the num parameter. A link to
+          <<hhttttpp::////wwwwww..ffaaqqss..oorrgg//>> will be made. Auto-indexing is done
+          under _R_f_C.
 
-   $wrap_search , $wrap_search
+   <muttng-doc:cmddef name="" [noanchor="1"]/>
+          _D_e_f_i_n_i_n_g_ _a_ _c_o_n_f_i_g_u_r_a_t_i_o_n_ _c_o_m_m_a_n_d_. The name of the command is
+          given as the name parameter. In case a single command has
+          multiple possible calling sequences, specify noanchor="1" for
+          subsequent use. Auto-indexing is done. Specify the arguments
+          within the tag.
 
-   <write-fcc>, Composing new messages, compose
+   <muttng-doc:cmdref name=""/>
+          _R_e_f_e_r_e_n_c_e_s_ _t_o_ _c_o_n_f_i_g_u_r_a_t_i_o_n_ _c_o_m_m_a_n_d_s_. Use this to refer to
+          commands as it builds the proper internal reference name.
+          Auto-indexing is done.
 
-   $write_bcc , $write_bcc
+   <muttng-doc:lstconf/>, <muttng-doc:lstmail/>, <muttng-doc:lstshell/>
+          _S_c_r_e_e_n_ _l_a_y_o_u_t_ _b_y_ _c_o_n_t_e_x_t_. These are used to specify
+          environments for different types of screen output. For DocBook
+          output, all of these simply map to <screen/>. But as a possible
+          future migration to LaTeX may be ahead, different languages
+          defined for the listings.sty packages may be used to have
+          proper syntax highlighting for these so that there must be a
+          context sensitive distinction.
 
-   $write_inc , $write_inc
+   <muttng-doc:special [docbook=""] [latex=""]/>
+          This is intended for specifying special strings for either
+          DocBook/XML or LaTeX.
 
-  X
+   Additional notes follow.
 
-   $xterm_icon , $xterm_icon
+     * To not fully bloat the XSL stylesheet procuding the LaTeX code,
+       all tables _m_u_s_t have an attribute called texstr which is directly
+       passed to longtable.
 
-   $xterm_leave , $xterm_leave
+Index
 
-   $xterm_set_titles , $xterm_set_titles
+Symbols
+
+   ~$/ =$, PPaatttteerrnnss
+   ~*/ =*, PPaatttteerrnnss
+   ~=/ ==, PPaatttteerrnnss
+   ~A/ =A, PPaatttteerrnnss
+   ~b/ =b, CCoommpplleexx  PPaatttteerrnnss, PPaatttteerrnnss
+   ~B/ =B, PPaatttteerrnnss
+   ~c/ =c, PPaatttteerrnnss
+   ~C/ =C, PPaatttteerrnnss
+   ~d/ =d, PPaatttteerrnnss  aanndd  DDaatteess, PPaatttteerrnnss
+   ~D/ =D, PPaatttteerrnnss
+   ~E/ =E, PPaatttteerrnnss
+   ~e/ =e, PPaatttteerrnnss
+   ~f/ =f, CCoommpplleexx  PPaatttteerrnnss, PPaatttteerrnnss
+   ~F/ =F, PPaatttteerrnnss
+   ~g/ =g, PPaatttteerrnnss
+   ~G/ =G, PPaatttteerrnnss
+   ~H/ =H, SSppaamm  ddeetteeccttiioonn, PPaatttteerrnnss
+   ~h/ =h, PPaatttteerrnnss
+   ~i/ =i, PPaatttteerrnnss
+   ~k/ =k, PPaatttteerrnnss
+   ~L/ =L, PPaatttteerrnnss
+   ~l/ =l, PPaatttteerrnnss
+   ~m/ =m, PPaatttteerrnnss
+   ~M/ =M, PPaatttteerrnnss
+   ~n/ =n, MMeessssaaggee  SSccoorriinngg, PPaatttteerrnnss
+   ~N/ =N, PPaatttteerrnnss
+   ~O/ =O, PPaatttteerrnnss
+   ~p/ =p, PPaatttteerrnnss
+   ~P/ =P, PPaatttteerrnnss
+   ~Q/ =Q, PPaatttteerrnnss
+   ~R/ =R, PPaatttteerrnnss
+   ~r/ =r, PPaatttteerrnnss
+   ~s/ =s, CCoommpplleexx  PPaatttteerrnnss, PPaatttteerrnnss
+   ~S/ =S, PPaatttteerrnnss
+   ~T/ =T, PPaatttteerrnnss
+   ~t/ =t, PPaatttteerrnnss
+   ~U/ =U, CCoommpplleexx  PPaatttteerrnnss, PPaatttteerrnnss
+   ~u/ =u, PPaatttteerrnnss
+   ~v/ =v, PPaatttteerrnnss
+   ~V/ =V, PPaatttteerrnnss
+   ~w/ =w, PPaatttteerrnnss
+   ~x/ =x, CCoommpplleexx  PPaatttteerrnnss, PPaatttteerrnnss
+   ~X/ =X, PPaatttteerrnnss
+   ~y/ =y, HHaannddlliinngg  MMaaiilliinngg  LLiissttss, PPaatttteerrnnss
+   ~z/ =z, PPaatttteerrnnss
+
+A
+
+   $abort_noattach , $$aabboorrtt__nnooaattttaacchh
+   $abort_nosubject , $$aabboorrtt__nnoossuubbjjeecctt
+   $abort_unmodified , $$aabboorrtt__uunnmmooddiiffiieedd
+   account-hook, MMaannaaggiinngg  mmuullttiippllee  IIMMAAPP//PPOOPP//NNNNTTPP  aaccccoouunnttss  ((OOPPTTIIOONNAALL)),
+          CCoonnffiigguurraattiioonn  CCoommmmaannddss
+
+   $agent_string , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $agent_string , $$aaggeenntt__ssttrriinngg
+   alias, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, DDeeffiinniinngg//UUssiinngg  aalliiaasseess, CCoonnffiigguurraattiioonn
+          CCoommmmaannddss
+
+   $alias_file, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, DDeeffiinniinngg//UUssiinngg  aalliiaasseess
+   $alias_file , $$aalliiaass__ffiillee
+   $alias_format , $$aalliiaass__ffoorrmmaatt
+   $allow_8bit , $$aallllooww__88bbiitt
+   $allow_ansi , $$aallllooww__aannssii
+   alternates, AAlltteerrnnaattiivvee  aaddddrreesssseess, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+   alternative_order, MMIIMMEE  MMuullttiippaarrtt//AAlltteerrnnaattiivvee, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+   append-hook, CCoommpprreesssseedd  ffoollddeerrss  SSuuppppoorrtt  ((OOPPTTIIOONNAALL)), AAppppeenndd  aa  mmeessssaaggee
+          ttoo  aa  ccoommpprreesssseedd  mmaaiillbbooxx, EEnnccrryypptteedd  ffoollddeerrss, CCoonnffiigguurraattiioonn
+          CCoommmmaannddss
+
+   $arrow_cursor , $$aarrrrooww__ccuurrssoorr
+   $ascii_chars , $$aasscciiii__cchhaarrss
+   $askbcc , $$aasskkbbcccc
+   $askcc , $$aasskkcccc
+   $assumed_charset , $$aassssuummeedd__cchhaarrsseett
+   <attach-file>, CCoommppoossiinngg  nneeww  mmeessssaaggeess, ccoommppoossee
+   <attach-key>, CCoommppoossiinngg  nneeww  mmeessssaaggeess, ccoommppoossee
+   <attach-message>, CCoommppoossiinngg  nneeww  mmeessssaaggeess, ccoommppoossee
+   attachments, AAttttaacchhmmeenntt  SSeeaarrcchhiinngg  aanndd  CCoouunnttiinngg
+   $attach_format , $$aattttaacchh__ffoorrmmaatt
+   $attach_remind_regexp , $$aattttaacchh__rreemmiinndd__rreeggeexxpp
+   $attach_sep , $$aattttaacchh__sseepp
+   $attach_split , $$aattttaacchh__sspplliitt
+   $attribution, CChhaannggee  sseettttiinnggss  bbaasseedd  uuppoonn  mmeessssaaggee  rreecciippiieennttss,
+          $$aattttrriibbuuttiioonn
+
+   $auto_tag, UUssiinngg  TTaaggss
+   $autoedit , $$aauuttooeeddiitt
+   $auto_tag , $$aauuttoo__ttaagg
+   auto_view, TThhee  PPaaggeerr, OOppttiioonnaall  FFiieellddss, SSeeaarrcchh  OOrrddeerr, MMIIMMEE  AAuuttoovviieeww,
+          MMIIMMEE  MMuullttiippaarrtt//AAlltteerrnnaattiivvee, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+
+B
+
+   <backspace>, EEddiittiinngg  IInnppuutt  FFiieellddss, eeddiittoorr
+   <backward-char>, EEddiittiinngg  IInnppuutt  FFiieellddss, eeddiittoorr
+   <backward-word>, EEddiittiinngg  IInnppuutt  FFiieellddss, eeddiittoorr
+   $beep , $$bbeeeepp
+   $beep_new , $$bbeeeepp__nneeww
+   bind, EEddiittiinngg  IInnppuutt  FFiieellddss, CChhaannggiinngg  tthhee  ddeeffaauulltt  kkeeyy  bbiinnddiinnggss,
+          KKeeyybbooaarrdd  mmaaccrrooss, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+
+   <bol>, EEddiittiinngg  IInnppuutt  FFiieellddss, eeddiittoorr
+   <bottom>, ppaaggeerr
+   <bottom-page>, ggeenneerriicc
+   <bounce>, SSeennddiinngg  MMaaiill, $$bboouunnccee
+   <bounce-message>, iinnddeexx, ppaaggeerr, aattttaacchh
+   $bounce_delivered , $$bboouunnccee__ddeelliivveerreedd
+   $braille_friendly , $$bbrraaiillllee__ffrriieennddllyy
+   <buffy-cycle>, eeddiittoorr
+
+C
+
+   <capitalize-word>, EEddiittiinngg  IInnppuutt  FFiieellddss, eeddiittoorr
+   $certificate_file , $$cceerrttiiffiiccaattee__ffiillee
+   <change-dir>, bbrroowwsseerr
+   <change-folder>, iinnddeexx, ppaaggeerr
+   <change-folder-readonly>, iinnddeexx, ppaaggeerr
+   $charset , $$cchhaarrsseett
+   charset-hook, DDeeffiinniinngg  aalliiaasseess  ffoorr  cchhaarraacctteerr  sseettss, CCoonnffiigguurraattiioonn
+          CCoommmmaannddss
+
+   <check-new>, bbrroowwsseerr
+   <check-traditional-pgp>, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, iinnddeexx, ppaaggeerr
+   $check_new , $$cchheecckk__nneeww
+   <clear-flag>, iinnddeexx
+   close-hook, CCoommpprreesssseedd  ffoollddeerrss  SSuuppppoorrtt  ((OOPPTTIIOONNAALL)), WWrriittee  aa  ccoommpprreesssseedd
+          mmaaiillbbooxx, AAppppeenndd  aa  mmeessssaaggee  ttoo  aa  ccoommpprreesssseedd  mmaaiillbbooxx,
+          CCoonnffiigguurraattiioonn  CCoommmmaannddss
+
+   <collapse-all>, TThhrreeaaddeedd  MMooddee
+   <collapse-parts>, aattttaacchh
+   <collapse-thread>, TThhrreeaaddeedd  MMooddee
+   $collapse_unread , $$ccoollllaappssee__uunnrreeaadd
+   color, TThhee  PPaaggeerr, UUssiinngg  ccoolloorr  aanndd  mmoonnoo  vviiddeeoo  aattttrriibbuutteess, CCoonnffiigguurraattiioonn
+          CCoommmmaannddss
+
+   $COLORFGBG, UUssiinngg  ccoolloorr  aanndd  mmoonnoo  vviiddeeoo  aattttrriibbuutteess
+   <complete>, EEddiittiinngg  IInnppuutt  FFiieellddss, eeddiittoorr
+   <complete-query>, EEddiittiinngg  IInnppuutt  FFiieellddss, eeddiittoorr
+   <compose>, SSeennddiinngg  MMaaiill
+   $compose_format , $$ccoommppoossee__ffoorrmmaatt
+   $config_charset , $$ccoonnffiigg__cchhaarrsseett
+   $confirmappend , $$ccoonnffiirrmmaappppeenndd
+   $confirmcreate , $$ccoonnffiirrmmccrreeaattee
+   $connect_timeout , $$ccoonnnneecctt__ttiimmeeoouutt
+   $content_type , $$ccoonntteenntt__ttyyppee
+   $copy , $$ccooppyy
+   <copy-file>, ccoommppoossee
+   <copy-message>, iinnddeexx, ppaaggeerr
+   $count_attachments, AAttttaacchhmmeenntt  SSeeaarrcchhiinngg  aanndd  CCoouunnttiinngg
+   $count_attachments , $$ccoouunntt__aattttaacchhmmeennttss
+   <create-alias>, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, DDeeffiinniinngg//UUssiinngg  aalliiaasseess,
+          iinnddeexx, ppaaggeerr, qquueerryy
+
+   $crypt_autoencrypt , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $crypt_autosign , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   crypt-hook, CChhoooossiinngg  tthhee  ccrryyppttooggrraapphhiicc  kkeeyy  ooff  tthhee  rreecciippiieenntt,
+          CCoonnffiigguurraattiioonn  CCoommmmaannddss
+
+   $crypt_replyencrypt , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $crypt_replysign , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $crypt_replysignencrypted , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $crypt_verify_sig , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $crypt_autoencrypt , $$ccrryypptt__aauuttooeennccrryypptt
+   $crypt_autopgp , $$ccrryypptt__aauuttooppggpp
+   $crypt_autosign , $$ccrryypptt__aauuttoossiiggnn
+   $crypt_autosmime , $$ccrryypptt__aauuttoossmmiimmee
+   $crypt_replyencrypt , $$ccrryypptt__rreeppllyyeennccrryypptt
+   $crypt_replysign , $$ccrryypptt__rreeppllyyssiiggnn
+   $crypt_replysignencrypted , $$ccrryypptt__rreeppllyyssiiggnneennccrryypptteedd
+   $crypt_timestamp , $$ccrryypptt__ttiimmeessttaammpp
+   $crypt_use_gpgme , $$ccrryypptt__uussee__ggppggmmee
+   $crypt_verify_sig , $$ccrryypptt__vveerriiffyy__ssiigg
+   <current-bottom>, ggeenneerriicc
+   <current-middle>, ggeenneerriicc
+   <current-top>, ggeenneerriicc
+
+D
+
+   $date_format , $$ddaattee__ffoorrmmaatt
+   $debug_level , $$ddeebbuugg__lleevveell
+   <decode-copy>, iinnddeexx
+   <decode-save>, iinnddeexx, ppaaggeerr
+   default-hook, MMeessssaaggee  MMaattcchhiinngg  iinn  HHooookkss
+   $default_hook , $$ddeeffaauulltt__hhooookk
+   $delete , $$ddeelleettee
+   <delete-char>, EEddiittiinngg  IInnppuutt  FFiieellddss, eeddiittoorr
+   <delete-entry>, aattttaacchh, ppoossttppoonnee
+   <delete-message>, iinnddeexx, ppaaggeerr
+   <delete-pattern>, iinnddeexx
+   $delete_space, AAddddiittiioonnaall  NNootteess
+   <delete-subthread>, TThhrreeaaddeedd  MMooddee, iinnddeexx, ppaaggeerr
+   <delete-thread>, TThhrreeaaddeedd  MMooddee, iinnddeexx, ppaaggeerr
+   $delete_space , $$ddeelleettee__ssppaaccee
+   $delete_untag , $$ddeelleettee__uunnttaagg
+   <detach-file>, CCoommppoossiinngg  nneeww  mmeessssaaggeess, ccoommppoossee
+   $digest_collapse , $$ddiiggeesstt__ccoollllaappssee
+   <display-address>, iinnddeexx, ppaaggeerr
+   <display-message>, iinnddeexx
+   <display-toggle-weed>, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, iinnddeexx, ppaaggeerr, aattttaacchh,
+          ccoommppoossee
+
+   $display_filter , $$ddiissppllaayy__ffiilltteerr
+   $dotlock_program , $$ddoottlloocckk__pprrooggrraamm
+   <downcase-word>, EEddiittiinngg  IInnppuutt  FFiieellddss, eeddiittoorr
+   $dsn_notify, DDeelliivveerryy  SSttaattuuss  NNoottiiffiiccaattiioonn  ((DDSSNN))  SSuuppppoorrtt
+   $dsn_return, DDeelliivveerryy  SSttaattuuss  NNoottiiffiiccaattiioonn  ((DDSSNN))  SSuuppppoorrtt
+   $dsn_notify , $$ddssnn__nnoottiiffyy
+   $dsn_return , $$ddssnn__rreettuurrnn
+   $duplicate_threads , $$dduupplliiccaattee__tthhrreeaaddss
+
+E
+
+   <edit>, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, iinnddeexx, ppaaggeerr, ccoommppoossee
+   <edit-bcc>, CCoommppoossiinngg  nneeww  mmeessssaaggeess, ccoommppoossee
+   <edit-cc>, CCoommppoossiinngg  nneeww  mmeessssaaggeess, ccoommppoossee
+   <edit-description>, CCoommppoossiinngg  nneeww  mmeessssaaggeess, ccoommppoossee
+   <edit-encoding>, ccoommppoossee
+   <edit-fcc>, CCoommppoossiinngg  nneeww  mmeessssaaggeess, ccoommppoossee
+   <edit-file>, ccoommppoossee
+   <edit-from>, CCoommppoossiinngg  nneeww  mmeessssaaggeess, ccoommppoossee
+   $edit_headers, EEddiittiinngg  tthhee  mmeessssaaggee  hheeaaddeerr, UUsseerr  ddeeffiinneedd  hheeaaddeerrss,
+          mmaaiillttoo::--ssttyyllee  lliinnkkss, CCoonnffiigguurraattiioonn  vvaarriiaabblleess, ccoommppoossee
+
+   <edit-mime>, ccoommppoossee
+   <edit-reply-to>, CCoommppoossiinngg  nneeww  mmeessssaaggeess, ccoommppoossee
+   <edit-subject>, CCoommppoossiinngg  nneeww  mmeessssaaggeess, ccoommppoossee
+   <edit-to>, CCoommppoossiinngg  nneeww  mmeessssaaggeess, ccoommppoossee
+   <edit-type>, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, iinnddeexx, ppaaggeerr, aattttaacchh, ccoommppoossee
+   $EDITOR, MMaannuuaall  CCoonnvveennttiioonnss, CCoommppoossiinngg  nneeww  mmeessssaaggeess
+   $editor , $$eeddiittoorr
+   $editor_headers, EEddiittiinngg  tthhee  mmeessssaaggee  hheeaaddeerr, DDeeffiinniinngg//UUssiinngg  aalliiaasseess
+   $editor_headers , $$eeddiittoorr__hheeaaddeerrss
+   $edit_headers , $$eeddiitt__hheeaaddeerrss
+   $encode_from , $$eennccooddee__ffrroomm
+   <enter-command>, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, ggeenneerriicc, ppaaggeerr
+   <enter-mask>, bbrroowwsseerr
+   $entropy_file , $$eennttrrooppyy__ffiillee
+   $envelope_from_address , $$eennvveellooppee__ffrroomm__aaddddrreessss
+   <eol>, EEddiittiinngg  IInnppuutt  FFiieellddss, eeddiittoorr
+   $escape , $$eessccaappee
+   exec, EExxeeccuuttiinngg  ffuunnccttiioonnss, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+   <exit>, ggeenneerriicc, iinnddeexx, ppaaggeerr
+   <extract-keys>, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, iinnddeexx, ppaaggeerr, aattttaacchh
+
+F
+
+   $fast_reply , $$ffaasstt__rreeppllyy
+   fcc-hook, SSppeecciiffyy  ddeeffaauulltt  FFcccc::  mmaaiillbbooxx  wwhheenn  ccoommppoossiinngg, SSppeecciiffyy  ddeeffaauulltt
+          ssaavvee  ffiilleennaammee  aanndd  ddeeffaauulltt  FFcccc::  mmaaiillbbooxx  aatt  oonnccee, UUssiinngg  HHooookkss,
+          MMeessssaaggee  MMaattcchhiinngg  iinn  HHooookkss, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+
+   fcc-save-hook, SSppeecciiffyy  ddeeffaauulltt  ssaavvee  ffiilleennaammee, SSppeecciiffyy  ddeeffaauulltt  FFcccc::
+          mmaaiillbbooxx  wwhheenn  ccoommppoossiinngg, SSppeecciiffyy  ddeeffaauulltt  ssaavvee  ffiilleennaammee  aanndd
+          ddeeffaauulltt  FFcccc::  mmaaiillbbooxx  aatt  oonnccee, UUssiinngg  HHooookkss, CCoonnffiigguurraattiioonn
+          CCoommmmaannddss
+
+   $fcc_attach , $$ffcccc__aattttaacchh
+   $fcc_clear , $$ffcccc__cclleeaarr
+   <fetch-mail>, iinnddeexx
+   $file_charset , $$ffiillee__cchhaarrsseett
+   <filter-entry>, ccoommppoossee
+   <first-entry>, MMoovviinngg  AArroouunndd  iinn  MMeennuuss, ggeenneerriicc
+   <flag-message>, iinnddeexx, ppaaggeerr
+   $folder, CCoonnffiigguurraattiioonn  VVaarriiaabblleess, DDeeffiinniinngg  mmaaiillbbooxxeess  wwhhiicchh  rreecceeiivvee
+          mmaaiill, MMaaiillbbooxx  SShhoorrttccuuttss, $$ffoollddeerr
+
+   folder-hook, SSeettttiinngg  vvaarriiaabblleess  bbaasseedd  uuppoonn  mmaaiillbbooxx, SSppaamm  ddeetteeccttiioonn,
+          UUssiinngg  HHooookkss, MMaannaaggiinngg  mmuullttiippllee  IIMMAAPP//PPOOPP//NNNNTTPP  aaccccoouunnttss
+          ((OOPPTTIIOONNAALL)), CCoonnffiigguurraattiioonn  CCoommmmaannddss
+
+   $folder_format , $$ffoollddeerr__ffoorrmmaatt
+   $followup_to, MMaaiilliinngg  lliissttss, HHaannddlliinngg  MMaaiilliinngg  LLiissttss
+   $followup_to , $$ffoolllloowwuupp__ttoo
+   $force_buffy_check , $$ffoorrccee__bbuuffffyy__cchheecckk
+   $force_list_reply , $$ffoorrccee__lliisstt__rreeppllyy
+   $force_name , $$ffoorrccee__nnaammee
+   <forget-passphrase>, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, CCoommppoossiinngg  nneeww  mmeessssaaggeess,
+          iinnddeexx, ppaaggeerr, ccoommppoossee
+
+   <forward>, SSeennddiinngg  MMaaiill
+   <forward-char>, EEddiittiinngg  IInnppuutt  FFiieellddss, eeddiittoorr
+   $forward_decode , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $forward_decrypt , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $forward_format , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   <forward-message>, iinnddeexx, ppaaggeerr, aattttaacchh
+   $forward_quote , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   <forward-word>, EEddiittiinngg  IInnppuutt  FFiieellddss, eeddiittoorr
+   $forward_decode , $$ffoorrwwaarrdd__ddeeccooddee
+   $forward_decrypt , $$ffoorrwwaarrdd__ddeeccrryypptt
+   $forward_edit , $$ffoorrwwaarrdd__eeddiitt
+   $forward_format , $$ffoorrwwaarrdd__ffoorrmmaatt
+   $forward_quote , $$ffoorrwwaarrdd__qquuoottee
+   $from , $$ffrroomm
+
+G
+
+   $gecos_mask , $$ggeeccooss__mmaasskk
+   <group-reply>, SSeennddiinngg  MMaaiill, iinnddeexx, ppaaggeerr, aattttaacchh
+
+H
+
+   <half-down>, ggeenneerriicc, ppaaggeerr
+   <half-up>, ggeenneerriicc, ppaaggeerr
+   $hdrs , $$hhddrrss
+   hdr_order, DDeeffiinniinngg  tthhee  oorrddeerr  ooff  hheeaaddeerrss  wwhheenn  vviieewwiinngg  mmeessssaaggeess,
+          CCoonnffiigguurraattiioonn  CCoommmmaannddss
+
+   $header , $$hheeaaddeerr
+   $header_cache , $$hheeaaddeerr__ccaacchhee
+   $header_cache_compress , $$hheeaaddeerr__ccaacchhee__ccoommpprreessss
+   <help>, MMoovviinngg  AArroouunndd  iinn  MMeennuuss, $$hheellpp, ggeenneerriicc, ppaaggeerr
+   $hidden_host , $$hhiiddddeenn__hhoosstt
+   $hide_limited , $$hhiiddee__lliimmiitteedd
+   $hide_missing , $$hhiiddee__mmiissssiinngg
+   $hide_thread_subject , $$hhiiddee__tthhrreeaadd__ssuubbjjeecctt
+   $hide_top_limited , $$hhiiddee__ttoopp__lliimmiitteedd
+   $hide_top_missing , $$hhiiddee__ttoopp__mmiissssiinngg
+   $history , $$hhiissttoorryy
+   <history-down>, EEddiittiinngg  IInnppuutt  FFiieellddss, eeddiittoorr
+   <history-up>, EEddiittiinngg  IInnppuutt  FFiieellddss, eeddiittoorr
+   $HOME, MMIIMMEE  TTyyppee  ccoonnffiigguurraattiioonn  wwiitthh  mmiimmee..ttyyppeess, MMIIMMEE  VViieewweerr
+          ccoonnffiigguurraattiioonn  wwiitthh  mmaaiillccaapp
+
+   $honor_followup_to, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, HHaannddlliinngg  MMaaiilliinngg  LLiissttss
+   $honor_followup_to , $$hhoonnoorr__ffoolllloowwuupp__ttoo
+   $HOSTNAME, EEnnvviirroonnmmeenntt  VVaarriiaabblleess
+   $hostname , $$hhoossttnnaammee
+
+I
+
+   iconv-hook, DDeeffiinniinngg  aalliiaasseess  ffoorr  cchhaarraacctteerr  sseettss
+   ignore, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, IIggnnoorriinngg  ((wweeeeddiinngg))  uunnwwaanntteedd  mmeessssaaggee
+          hheeaaddeerrss, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+
+   $ignore_list_reply_to , $$iiggnnoorree__lliisstt__rreeppllyy__ttoo
+   $imap_authenticators, AAuutthheennttiiccaattiioonn
+   $imap_home_namespace, CCoonnffiigguurraattiioonn  VVaarriiaabblleess
+   $imap_list_subscribed, IIMMAAPP  SSuuppppoorrtt  ((OOPPTTIIOONNAALL))
+   $imap_mail_check, MMaannuuaall  CCoonnvveennttiioonnss, CCoonnddiittiioonnaall  ppaarrttss, IIMMAAPP  SSuuppppoorrtt
+          ((OOPPTTIIOONNAALL))
+
+   $imap_pass, AAuutthheennttiiccaattiioonn
+   $imap_user, AAuutthheennttiiccaattiioonn
+   $imap_authenticators , $$iimmaapp__aauutthheennttiiccaattoorrss
+   $imap_check_subscribed , $$iimmaapp__cchheecckk__ssuubbssccrriibbeedd
+   $imap_delim_chars , $$iimmaapp__ddeelliimm__cchhaarrss
+   $imap_headers , $$iimmaapp__hheeaaddeerrss
+   $imap_home_namespace , $$iimmaapp__hhoommee__nnaammeessppaaccee
+   $imap_keepalive , $$iimmaapp__kkeeeeppaalliivvee
+   $imap_list_subscribed , $$iimmaapp__lliisstt__ssuubbssccrriibbeedd
+   $imap_login , $$iimmaapp__llooggiinn
+   $imap_mail_check , $$iimmaapp__mmaaiill__cchheecckk
+   $imap_pass , $$iimmaapp__ppaassss
+   $imap_passive , $$iimmaapp__ppaassssiivvee
+   $imap_peek , $$iimmaapp__ppeeeekk
+   $imap_reconnect , $$iimmaapp__rreeccoonnnneecctt
+   $imap_servernoise , $$iimmaapp__sseerrvveerrnnooiissee
+   $imap_user , $$iimmaapp__uusseerr
+   $implicit_autoview , $$iimmpplliicciitt__aauuttoovviieeww
+   $include , $$iinncclluuddee
+   $include_onlyfirst , $$iinncclluuddee__oonnllyyffiirrsstt
+   $indent_string , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $indent_string , $$iinnddeenntt__ssttrriinngg
+   $index_format, TThhrreeaaddeedd  MMooddee, SSppaamm  ddeetteeccttiioonn, HHaannddlliinngg  MMaaiilliinngg  LLiissttss,
+          CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+
+   $index_format , $$iinnddeexx__ffoorrmmaatt
+   <ispell>, CCoommppoossiinngg  nneeww  mmeessssaaggeess, $$iissppeellll, ccoommppoossee
+
+J
+
+   <jump>, ggeenneerriicc
+
+K
+
+   $keep_flagged , $$kkeeeepp__ffllaaggggeedd
+   <kill-eol>, EEddiittiinngg  IInnppuutt  FFiieellddss, eeddiittoorr
+   <kill-eow>, EEddiittiinngg  IInnppuutt  FFiieellddss, eeddiittoorr
+   <kill-line>, EEddiittiinngg  IInnppuutt  FFiieellddss, eeddiittoorr
+   <kill-word>, EEddiittiinngg  IInnppuutt  FFiieellddss, eeddiittoorr
+
+L
+
+   <last-entry>, MMoovviinngg  AArroouunndd  iinn  MMeennuuss, ggeenneerriicc
+   <limit>, iinnddeexx
+   <list-reply>, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, SSeennddiinngg  MMaaiill, iinnddeexx, ppaaggeerr,
+          aattttaacchh
+
+   lists, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, MMaaiilliinngg  lliissttss, HHaannddlliinngg  MMaaiilliinngg  LLiissttss,
+          CCoonnffiigguurraattiioonn  CCoommmmaannddss
+
+   $locale, CChhaannggee  sseettttiinnggss  bbaasseedd  uuppoonn  mmeessssaaggee  rreecciippiieennttss, $$llooccaallee
+
+M
+
+   macro, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, KKeeyybbooaarrdd  mmaaccrrooss, AAddddiinngg  kkeeyy  sseeqquueenncceess
+          ttoo  tthhee  kkeeyybbooaarrdd  bbuuffffeerr, UUssiinngg  TTaaggss, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+
+   <mail>, iinnddeexx, ppaaggeerr, qquueerryy
+   <mail-key>, SSeennddiinngg  MMaaiill, iinnddeexx, ppaaggeerr
+   mailboxes, DDeeffiinniinngg  mmaaiillbbooxxeess  wwhhiicchh  rreecceeiivvee  mmaaiill, CCoonnffiigguurraattiioonn
+          CCoommmmaannddss
+
+   $mailcap_path, mmaaiillccaapp
+   $mailcap_sanitize, SSeeccuurree  uussee  ooff  mmaaiillccaapp, mmaaiillccaapp
+   $mailcap_path , $$mmaaiillccaapp__ppaatthh
+   $mailcap_sanitize , $$mmaaiillccaapp__ssaanniittiizzee
+   $maildir_header_cache_verify , $$mmaaiillddiirr__hheeaaddeerr__ccaacchhee__vveerriiffyy
+   $maildir_trash , $$mmaaiillddiirr__ttrraasshh
+   $mail_check , $$mmaaiill__cchheecckk
+   <mark-as-new>, ppaaggeerr
+   $markers , $$mmaarrkkeerrss
+   $mark_old , $$mmaarrkk__oolldd
+   $mask , $$mmaasskk
+   $max_display_recips , $$mmaaxx__ddiissppllaayy__rreecciippss
+   $max_line_length , $$mmaaxx__lliinnee__lleennggtthh
+   $mbox, MMaaiillbbooxx  SShhoorrttccuuttss, $$mmbbooxx
+   mbox-hook, UUssiinngg  MMuullttiippllee  ssppooooll  mmaaiillbbooxxeess, UUssiinngg  HHooookkss, CCoonnffiigguurraattiioonn
+          CCoommmmaannddss
+
+   $mbox_type, MMaaiillbbooxx  FFoorrmmaattss, AAppppeenndd  aa  mmeessssaaggee  ttoo  aa  ccoommpprreesssseedd  mmaaiillbbooxx
+   $mbox_type , $$mmbbooxx__ttyyppee
+   $menu_context , $$mmeennuu__ccoonntteexxtt
+   $menu_move_off , $$mmeennuu__mmoovvee__ooffff
+   $menu_scroll , $$mmeennuu__ssccrroollll
+   $message_format , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   message-hook, CChhaannggee  sseettttiinnggss  bbeeffoorree  ffoorrmmaattttiinngg  aa  mmeessssaaggee, UUssiinngg
+          HHooookkss, MMeessssaaggee  MMaattcchhiinngg  iinn  HHooookkss, MMIIMMEE  AAuuttoovviieeww, CCoonnffiigguurraattiioonn
+          CCoommmmaannddss
+
+   $message_format , $$mmeessssaaggee__ffoorrmmaatt
+   $meta_key , $$mmeettaa__kkeeyy
+   $metoo , $$mmeettoooo
+   $mh_purge , $$mmhh__ppuurrggee
+   $mh_seq_flagged , $$mmhh__sseeqq__ffllaaggggeedd
+   $mh_seq_replied , $$mmhh__sseeqq__rreepplliieedd
+   $mh_seq_unseen , $$mmhh__sseeqq__uunnsseeeenn
+   <middle-page>, ggeenneerriicc
+   $mime_forward , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $mime_forward , $$mmiimmee__ffoorrwwaarrdd
+   $mime_forward_decode , $$mmiimmee__ffoorrwwaarrdd__ddeeccooddee
+   $mime_forward_rest , $$mmiimmee__ffoorrwwaarrdd__rreesstt
+   mime_lookup, MMIIMMEE  LLooookkuupp, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+   $mix_entry_format, SSeennddiinngg  aannoonnyymmoouuss  mmeessssaaggeess  vviiaa  mmiixxmmaasstteerr
+   $mixmaster , $$mmiixxmmaasstteerr
+   $mix_entry_format , $$mmiixx__eennttrryy__ffoorrmmaatt
+   mono, UUssiinngg  ccoolloorr  aanndd  mmoonnoo  vviiddeeoo  aattttrriibbuutteess, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+   $move , $$mmoovvee
+   $msgid_format, MMeessssaaggee--IIDD::  hheeaaddeerrss
+   $msgid_format , $$mmssggiidd__ffoorrmmaatt
+   $muttng_bindir , $$mmuuttttnngg__bbiinnddiirr
+   $muttng_docdir , $$mmuuttttnngg__ddooccddiirr
+   $muttng_folder_name , $$mmuuttttnngg__ffoollddeerr__nnaammee
+   $muttng_folder_path , $$mmuuttttnngg__ffoollddeerr__ppaatthh
+   $muttng_hcache_backend , $$mmuuttttnngg__hhccaacchhee__bbaacckkeenndd
+   $muttng_pwd , $$mmuuttttnngg__ppwwdd
+   $muttng_revision , $$mmuuttttnngg__rreevviissiioonn
+   $muttng_sysconfdir , $$mmuuttttnngg__ssyyssccoonnffddiirr
+   $muttng_version , $$mmuuttttnngg__vveerrssiioonn
+   my_hdr, UUsseerr  ddeeffiinneedd  hheeaaddeerrss, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+
+N
+
+   $narrow_tree , $$nnaarrrrooww__ttrreeee
+   $net_inc , $$nneett__iinncc
+   <new-mime>, ccoommppoossee
+   <next-entry>, MMoovviinngg  AArroouunndd  iinn  MMeennuuss, ggeenneerriicc, ppaaggeerr
+   <next-line>, ggeenneerriicc, ppaaggeerr
+   <next-new>, iinnddeexx, ppaaggeerr
+   <next-new-then-unread>, iinnddeexx, ppaaggeerr
+   <next-page>, ggeenneerriicc, ppaaggeerr
+   <next-subthread>, TThhrreeaaddeedd  MMooddee, iinnddeexx, ppaaggeerr
+   <next-thread>, TThhrreeaaddeedd  MMooddee, iinnddeexx, ppaaggeerr
+   <next-undeleted>, iinnddeexx, ppaaggeerr
+   <next-unread>, iinnddeexx, ppaaggeerr
+   $nntp_ask_followup_to , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $nntp_ask_x_comment_to , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $nntp_cache_dir , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $nntp_catchup , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $nntp_followup_to_poster , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $nntp_group_index_format , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $nntp_host , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $nntp_inews , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $nntp_mail_check , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $nntp_mime_subject , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $nntp_newsrc, NNNNTTPP  SSuuppppoorrtt  ((OOPPTTIIOONNAALL)), CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $nntp_post_moderated , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $nntp_save_unsubscribed , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $nntp_show_new_news , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $nntp_show_only_unread , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $nntp_x_comment_to , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $NNTPSERVER, NNNNTTPP  SSuuppppoorrtt  ((OOPPTTIIOONNAALL))
+   $nntp_ask_followup_to , $$nnnnttpp__aasskk__ffoolllloowwuupp__ttoo
+   $nntp_ask_x_comment_to , $$nnnnttpp__aasskk__xx__ccoommmmeenntt__ttoo
+   $nntp_cache_dir , $$nnnnttpp__ccaacchhee__ddiirr
+   $nntp_catchup , $$nnnnttpp__ccaattcchhuupp
+   $nntp_context , $$nnnnttpp__ccoonntteexxtt
+   $nntp_followup_to_poster , $$nnnnttpp__ffoolllloowwuupp__ttoo__ppoosstteerr
+   $nntp_group_index_format , $$nnnnttpp__ggrroouupp__iinnddeexx__ffoorrmmaatt
+   $nntp_host , $$nnnnttpp__hhoosstt
+   $nntp_inews , $$nnnnttpp__iinneewwss
+   $nntp_load_description , $$nnnnttpp__llooaadd__ddeessccrriippttiioonn
+   $nntp_mail_check , $$nnnnttpp__mmaaiill__cchheecckk
+   $nntp_mime_subject , $$nnnnttpp__mmiimmee__ssuubbjjeecctt
+   $nntp_newsrc , $$nnnnttpp__nneewwssrrcc
+   $nntp_pass , $$nnnnttpp__ppaassss
+   $nntp_post_moderated , $$nnnnttpp__ppoosstt__mmooddeerraatteedd
+   $nntp_reconnect , $$nnnnttpp__rreeccoonnnneecctt
+   $nntp_save_unsubscribed , $$nnnnttpp__ssaavvee__uunnssuubbssccrriibbeedd
+   $nntp_show_new_news , $$nnnnttpp__sshhooww__nneeww__nneewwss
+   $nntp_show_only_unread , $$nnnnttpp__sshhooww__oonnllyy__uunnrreeaadd
+   $nntp_user , $$nnnnttpp__uusseerr
+   $nntp_x_comment_to , $$nnnnttpp__xx__ccoommmmeenntt__ttoo
+   nospam, SSppaamm  ddeetteeccttiioonn, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+
+O
+
+   open-hook, CCoommpprreesssseedd  ffoollddeerrss  SSuuppppoorrtt  ((OOPPTTIIOONNAALL)), OOppeenn  aa  ccoommpprreesssseedd
+          mmaaiillbbooxx  ffoorr  rreeaaddiinngg, WWrriittee  aa  ccoommpprreesssseedd  mmaaiillbbooxx, AAppppeenndd  aa
+          mmeessssaaggee  ttoo  aa  ccoommpprreesssseedd  mmaaiillbbooxx, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+
+   $operating_system , $$ooppeerraattiinngg__ssyysstteemm
+
+P
+
+   <page-down>, MMoovviinngg  AArroouunndd  iinn  MMeennuuss
+   <page-up>, MMoovviinngg  AArroouunndd  iinn  MMeennuuss
+   $pager , $$ppaaggeerr
+   $pager_index_lines, CCoonnddiittiioonnaall  ppaarrttss
+   $pager_context , $$ppaaggeerr__ccoonntteexxtt
+   $pager_format , $$ppaaggeerr__ffoorrmmaatt
+   $pager_index_lines , $$ppaaggeerr__iinnddeexx__lliinneess
+   $pager_stop , $$ppaaggeerr__ssttoopp
+   <parent-message>, TThhrreeaaddeedd  MMooddee, iinnddeexx, ppaaggeerr
+   pattern-hook, SSppeecciiffyy  ddeeffaauulltt  ssaavvee  ffiilleennaammee, SSppeecciiffyy  ddeeffaauulltt  FFcccc::
+          mmaaiillbbooxx  wwhheenn  ccoommppoossiinngg, CChhaannggee  sseettttiinnggss  bbaasseedd  uuppoonn  mmeessssaaggee
+          rreecciippiieennttss, CChhaannggee  sseettttiinnggss  bbeeffoorree  ffoorrmmaattttiinngg  aa  mmeessssaaggee
+
+   $pgp_autoinline , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $pgp_entry_format, UUssiinngg  MMuutttt--nngg  wwiitthh  PPGGPP
+   <pgp-menu>, CCoommppoossiinngg  nneeww  mmeessssaaggeess, ccoommppoossee
+   $pgp_replyinline , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $pgp_sign_as, UUssiinngg  MMuutttt--nngg  wwiitthh  PPGGPP
+   $pgp_autoinline , $$ppggpp__aauuttooiinnlliinnee
+   $pgp_auto_decode , $$ppggpp__aauuttoo__ddeeccooddee
+   $pgp_check_exit , $$ppggpp__cchheecckk__eexxiitt
+   $pgp_clearsign_command , $$ppggpp__cclleeaarrssiiggnn__ccoommmmaanndd
+   $pgp_decode_command , $$ppggpp__ddeeccooddee__ccoommmmaanndd
+   $pgp_decrypt_command , $$ppggpp__ddeeccrryypptt__ccoommmmaanndd
+   $pgp_encrypt_only_command , $$ppggpp__eennccrryypptt__oonnllyy__ccoommmmaanndd
+   $pgp_encrypt_sign_command , $$ppggpp__eennccrryypptt__ssiiggnn__ccoommmmaanndd
+   $pgp_entry_format , $$ppggpp__eennttrryy__ffoorrmmaatt
+   $pgp_export_command , $$ppggpp__eexxppoorrtt__ccoommmmaanndd
+   $pgp_getkeys_command , $$ppggpp__ggeettkkeeyyss__ccoommmmaanndd
+   $pgp_good_sign , $$ppggpp__ggoooodd__ssiiggnn
+   $pgp_ignore_subkeys , $$ppggpp__iiggnnoorree__ssuubbkkeeyyss
+   $pgp_import_command , $$ppggpp__iimmppoorrtt__ccoommmmaanndd
+   $pgp_list_pubring_command , $$ppggpp__lliisstt__ppuubbrriinngg__ccoommmmaanndd
+   $pgp_list_secring_command , $$ppggpp__lliisstt__sseeccrriinngg__ccoommmmaanndd
+   $pgp_long_ids , $$ppggpp__lloonngg__iiddss
+   $pgp_mime_auto , $$ppggpp__mmiimmee__aauuttoo
+   $pgp_replyinline , $$ppggpp__rreeppllyyiinnlliinnee
+   $pgp_retainable_sigs , $$ppggpp__rreettaaiinnaabbllee__ssiiggss
+   $pgp_show_unusable , $$ppggpp__sshhooww__uunnuussaabbllee
+   $pgp_sign_as , $$ppggpp__ssiiggnn__aass
+   $pgp_sign_command , $$ppggpp__ssiiggnn__ccoommmmaanndd
+   $pgp_sort_keys , $$ppggpp__ssoorrtt__kkeeyyss
+   $pgp_strict_enc , $$ppggpp__ssttrriicctt__eenncc
+   $pgp_timeout , $$ppggpp__ttiimmeeoouutt
+   $pgp_use_gpg_agent , $$ppggpp__uussee__ggppgg__aaggeenntt
+   $pgp_verify_command , $$ppggpp__vveerriiffyy__ccoommmmaanndd
+   $pgp_verify_key_command , $$ppggpp__vveerriiffyy__kkeeyy__ccoommmmaanndd
+   $pipe_decode, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss
+   <pipe-entry>, aattttaacchh, ccoommppoossee
+   <pipe-message>, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, iinnddeexx, ppaaggeerr
+   $pipe_split, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss
+   $pipe_decode , $$ppiippee__ddeeccooddee
+   $pipe_sep , $$ppiippee__sseepp
+   $pipe_split , $$ppiippee__sspplliitt
+   $pop_mail_check, PPOOPP33  SSuuppppoorrtt  ((OOPPTTIIOONNAALL)), CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $pop_authenticators , $$ppoopp__aauutthheennttiiccaattoorrss
+   $pop_auth_try_all , $$ppoopp__aauutthh__ttrryy__aallll
+   $pop_delete , $$ppoopp__ddeelleettee
+   $pop_host , $$ppoopp__hhoosstt
+   $pop_last , $$ppoopp__llaasstt
+   $pop_mail_check , $$ppoopp__mmaaiill__cchheecckk
+   $pop_pass , $$ppoopp__ppaassss
+   $pop_reconnect , $$ppoopp__rreeccoonnnneecctt
+   $pop_user , $$ppoopp__uusseerr
+   $post_indent_string , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $postpone, PPoossttppoonniinngg  MMaaiill, $$ppoossttppoonnee
+   <postpone-message>, CCoommppoossiinngg  nneeww  mmeessssaaggeess, ccoommppoossee
+   $postponed, PPoossttppoonniinngg  MMaaiill, $$ppoossttppoonneedd
+   $post_indent_string , $$ppoosstt__iinnddeenntt__ssttrriinngg
+   $preconnect , $$pprreeccoonnnneecctt
+   <previous-entry>, MMoovviinngg  AArroouunndd  iinn  MMeennuuss, ggeenneerriicc, ppaaggeerr
+   <previous-line>, ggeenneerriicc, ppaaggeerr
+   <previous-new>, iinnddeexx, ppaaggeerr
+   <previous-new-then-unread>, iinnddeexx, ppaaggeerr
+   <previous-page>, ggeenneerriicc, iinnddeexx, ppaaggeerr
+   <previous-subthread>, TThhrreeaaddeedd  MMooddee, iinnddeexx, ppaaggeerr
+   <previous-thread>, TThhrreeaaddeedd  MMooddee, iinnddeexx, ppaaggeerr
+   <previous-undeleted>, iinnddeexx, ppaaggeerr
+   <previous-unread>, iinnddeexx, ppaaggeerr
+   $print , $$pprriinntt
+   $print_command , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   <print-entry>, aattttaacchh, ccoommppoossee
+   <print-message>, iinnddeexx, ppaaggeerr
+   $print_command , $$pprriinntt__ccoommmmaanndd
+   $print_decode , $$pprriinntt__ddeeccooddee
+   $print_split , $$pprriinntt__sspplliitt
+   $prompt_after , $$pprroommpptt__aafftteerr
+   push, AAddddiinngg  kkeeyy  sseeqquueenncceess  ttoo  tthhee  kkeeyybbooaarrdd  bbuuffffeerr, UUssiinngg  TTaaggss,
+          CCoonnffiigguurraattiioonn  CCoommmmaannddss
+
+Q
+
+   <query>, iinnddeexx, qquueerryy
+   <query-append>, qquueerryy
+   $query_command, EExxtteerrnnaall  AAddddrreessss  QQuueerriieess
+   $query_command , $$qquueerryy__ccoommmmaanndd
+   <quit>, MMoovviinngg  AArroouunndd  iinn  MMeennuuss, CCoommppoossiinngg  nneeww  mmeessssaaggeess, $$qquuiitt, iinnddeexx,
+          ppaaggeerr
+
+   <quote-char>, EEddiittiinngg  IInnppuutt  FFiieellddss, eeddiittoorr
+   $quote_regexp, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, UUssiinngg  ccoolloorr  aanndd  mmoonnoo  vviiddeeoo
+          aattttrriibbuutteess
+
+   $quote_empty , $$qquuoottee__eemmppttyy
+   $quote_quoted , $$qquuoottee__qquuootteedd
+   $quote_regexp , $$qquuoottee__rreeggeexxpp
+
+R
+
+   <read-subthread>, TThhrreeaaddeedd  MMooddee, iinnddeexx, ppaaggeerr
+   <read-thread>, TThhrreeaaddeedd  MMooddee, iinnddeexx, ppaaggeerr
+   $read_inc , $$rreeaadd__iinncc
+   $read_only , $$rreeaadd__oonnllyy
+   $realname , $$rreeaallnnaammee
+   <rebuild-cache>, ggeenneerriicc
+   $recall , $$rreeccaallll
+   <recall-message>, iinnddeexx, ppaaggeerr
+   $record, EEnnvviirroonnmmeenntt  VVaarriiaabblleess, SSppeecciiffyy  ddeeffaauulltt  FFcccc::  mmaaiillbbooxx  wwhheenn
+          ccoommppoossiinngg, MMaaiillbbooxx  SShhoorrttccuuttss, $$rreeccoorrdd
+
+   <redraw-screen>, ppaaggeerr
+   <refresh>, ggeenneerriicc
+   <rename-file>, ccoommppoossee
+   <reply>, SSeennddiinngg  MMaaiill, iinnddeexx, ppaaggeerr, aattttaacchh
+   reply-hook, CChhaannggee  sseettttiinnggss  bbaasseedd  uuppoonn  mmeessssaaggee  rreecciippiieennttss,
+          CCoonnffiigguurraattiioonn  CCoommmmaannddss
+
+   $reply_to, AAlltteerrnnaattiivvee  aaddddrreesssseess, HHaannddlliinngg  MMaaiilliinngg  LLiissttss
+   $reply_regexp , $$rreeppllyy__rreeggeexxpp
+   $reply_self , $$rreeppllyy__sseellff
+   $reply_to , $$rreeppllyy__ttoo
+   <resend-message>, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, TThhee  AAttttaacchhmmeenntt  MMeennuu, iinnddeexx,
+          aattttaacchh
+
+   reset, SSeettttiinngg  vvaarriiaabblleess, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+   $resolve , $$rreessoollvvee
+   $reverse_alias , $$rreevveerrssee__aalliiaass
+   $reverse_name , $$rreevveerrssee__nnaammee
+   $reverse_realname , $$rreevveerrssee__rreeaallnnaammee
+   RfC
 
-   $xterm_title , $xterm_title
+        1524, MMIIMMEE  VViieewweerr  ccoonnffiigguurraattiioonn  wwiitthh  mmaaiillccaapp, CCoommmmaanndd  EExxppaannssiioonn,
+                mmaaiillccaapp
+
+        1894, DDeelliivveerryy  SSttaattuuss  NNoottiiffiiccaattiioonn  ((DDSSNN))  SSuuppppoorrtt
+        2822, AAggaaiinn::  SSccoorriinngg
+        3676, SSeennddiinngg
+        822, UUsseerr  ddeeffiinneedd  hheeaaddeerrss
+
+   $rfc2047_parameters , $$rrffcc22004477__ppaarraammeetteerrss
+
+S
+
+   $save_empty, CCoommpprreesssseedd  ffoollddeerrss  SSuuppppoorrtt  ((OOPPTTIIOONNAALL))
+   <save-entry>, aattttaacchh
+   save-hook, SSppeecciiffyy  ddeeffaauulltt  ssaavvee  ffiilleennaammee, SSppeecciiffyy  ddeeffaauulltt  ssaavvee
+          ffiilleennaammee  aanndd  ddeeffaauulltt  FFcccc::  mmaaiillbbooxx  aatt  oonnccee, UUssiinngg  HHooookkss, MMeessssaaggee
+          MMaattcchhiinngg  iinn  HHooookkss, MMaaiillbbooxx  SShhoorrttccuuttss, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+
+   <save-message>, iinnddeexx, ppaaggeerr
+   $save_address , $$ssaavvee__aaddddrreessss
+   $save_empty , $$ssaavvee__eemmppttyy
+   $save_name , $$ssaavvee__nnaammee
+   score, MMeessssaaggee  SSccoorriinngg, CCoonnffiigguurraattiioonn  CCoommmmaannddss, $$ssccoorree
+   $score_threshold_delete, MMeessssaaggee  SSccoorriinngg
+   $score_threshold_flag, MMeessssaaggee  SSccoorriinngg
+   $score_threshold_read, MMeessssaaggee  SSccoorriinngg
+   $score_threshold_delete , $$ssccoorree__tthhrreesshhoolldd__ddeelleettee
+   $score_threshold_flag , $$ssccoorree__tthhrreesshhoolldd__ffllaagg
+   $score_threshold_read , $$ssccoorree__tthhrreesshhoolldd__rreeaadd
+   <search>, ggeenneerriicc, ppaaggeerr, aalliiaass, qquueerryy, bbrroowwsseerr
+   <search-next>, ggeenneerriicc, ppaaggeerr, aalliiaass, qquueerryy, bbrroowwsseerr
+   <search-opposite>, ggeenneerriicc, ppaaggeerr, qquueerryy
+   <search-reverse>, ggeenneerriicc, ppaaggeerr, aalliiaass, qquueerryy, bbrroowwsseerr
+   <search-toggle>, ppaaggeerr
+   <select-entry>, ggeenneerriicc
+   <select-new>, bbrroowwsseerr
+   send-hook, CChhaannggee  sseettttiinnggss  bbaasseedd  uuppoonn  mmeessssaaggee  rreecciippiieennttss, UUssiinngg  HHooookkss,
+          MMeessssaaggee  MMaattcchhiinngg  iinn  HHooookkss, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+
+   <send-message>, CCoommppoossiinngg  nneeww  mmeessssaaggeess, ccoommppoossee
+   send2-hook, CChhaannggee  sseettttiinnggss  bbaasseedd  uuppoonn  mmeessssaaggee  rreecciippiieennttss
+   <senderdecode-copy>, ppaaggeerr
+   $sendmail, CChhaannggee  sseettttiinnggss  bbaasseedd  uuppoonn  mmeessssaaggee  rreecciippiieennttss, $$sseennddmmaaiill
+   $sendmail_wait , $$sseennddmmaaiill__wwaaiitt
+   $send_charset , $$sseenndd__cchhaarrsseett
+   set, SSeettttiinngg  vvaarriiaabblleess, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+   <set-flag>, iinnddeexx
+   $shell , $$sshheellll
+   <shell-escape>, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, ggeenneerriicc, ppaaggeerr
+   <show-limit>, iinnddeexx
+   <show-version>, iinnddeexx, ppaaggeerr
+   <sidebar-next>, ssiiddeebbaarr
+   <sidebar-next-new>, ssiiddeebbaarr
+   <sidebar-open>, ssiiddeebbaarr
+   <sidebar-previous>, ssiiddeebbaarr
+   <sidebar-scroll-down>, ssiiddeebbaarr
+   <sidebar-scroll-up>, ssiiddeebbaarr
+   $sidebar_shorten_hierarchy , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $sidebar_boundary , $$ssiiddeebbaarr__bboouunnddaarryy
+   $sidebar_delim , $$ssiiddeebbaarr__ddeelliimm
+   $sidebar_newmail_only , $$ssiiddeebbaarr__nneewwmmaaiill__oonnllyy
+   $sidebar_number_format , $$ssiiddeebbaarr__nnuummbbeerr__ffoorrmmaatt
+   $sidebar_shorten_hierarchy , $$ssiiddeebbaarr__sshhoorrtteenn__hhiieerraarrcchhyy
+   $sidebar_visible , $$ssiiddeebbaarr__vviissiibbllee
+   $sidebar_width , $$ssiiddeebbaarr__wwiiddtthh
+   $signature, CChhaannggee  sseettttiinnggss  bbaasseedd  uuppoonn  mmeessssaaggee  rreecciippiieennttss, $$ssiiggnnaattuurree
+   $signoff_string , $$ssiiggnnooffff__ssttrriinngg
+   $sig_dashes , $$ssiigg__ddaasshheess
+   $sig_on_top , $$ssiigg__oonn__ttoopp
+   $simple_search , $$ssiimmppllee__sseeaarrcchh
+   <skip-quoted>, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, ppaaggeerr
+   $sleep_time , $$sslleeeepp__ttiimmee
+   $smart_wrap , $$ssmmaarrtt__wwrraapp
+   $smileys , $$ssmmiilleeyyss
+   $smime_default_key , CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   <smime-menu>, CCoommppoossiinngg  nneeww  mmeessssaaggeess
+   $smime_ask_cert_label , $$ssmmiimmee__aasskk__cceerrtt__llaabbeell
+   $smime_ca_location , $$ssmmiimmee__ccaa__llooccaattiioonn
+   $smime_certificates , $$ssmmiimmee__cceerrttiiffiiccaatteess
+   $smime_decrypt_command , $$ssmmiimmee__ddeeccrryypptt__ccoommmmaanndd
+   $smime_decrypt_use_default_key , $$ssmmiimmee__ddeeccrryypptt__uussee__ddeeffaauulltt__kkeeyy
+   $smime_default_key , $$ssmmiimmee__ddeeffaauulltt__kkeeyy
+   $smime_encrypt_command , $$ssmmiimmee__eennccrryypptt__ccoommmmaanndd
+   $smime_encrypt_with , $$ssmmiimmee__eennccrryypptt__wwiitthh
+   $smime_get_cert_command , $$ssmmiimmee__ggeett__cceerrtt__ccoommmmaanndd
+   $smime_get_cert_email_command , $$ssmmiimmee__ggeett__cceerrtt__eemmaaiill__ccoommmmaanndd
+   $smime_get_signer_cert_command , $$ssmmiimmee__ggeett__ssiiggnneerr__cceerrtt__ccoommmmaanndd
+   $smime_import_cert_command , $$ssmmiimmee__iimmppoorrtt__cceerrtt__ccoommmmaanndd
+   $smime_is_default , $$ssmmiimmee__iiss__ddeeffaauulltt
+   $smime_keys , $$ssmmiimmee__kkeeyyss
+   $smime_pk7out_command , $$ssmmiimmee__ppkk77oouutt__ccoommmmaanndd
+   $smime_sign_command , $$ssmmiimmee__ssiiggnn__ccoommmmaanndd
+   $smime_sign_opaque_command , $$ssmmiimmee__ssiiggnn__ooppaaqquuee__ccoommmmaanndd
+   $smime_timeout , $$ssmmiimmee__ttiimmeeoouutt
+   $smime_verify_command , $$ssmmiimmee__vveerriiffyy__ccoommmmaanndd
+   $smime_verify_opaque_command , $$ssmmiimmee__vveerriiffyy__ooppaaqquuee__ccoommmmaanndd
+   $smtp_envelope, SSMMTTPP  SSuuppppoorrtt  ((OOPPTTIIOONNAALL))
+   $smtp_host, SSMMTTPP  SSuuppppoorrtt  ((OOPPTTIIOONNAALL))
+   $smtp_pass, SSMMTTPP  SSuuppppoorrtt  ((OOPPTTIIOONNAALL)), CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $smtp_use_tls, SSMMTTPP  SSuuppppoorrtt  ((OOPPTTIIOONNAALL))
+   $smtp_user, SSMMTTPP  SSuuppppoorrtt  ((OOPPTTIIOONNAALL)), CCoonnffiigguurraattiioonn  vvaarriiaabblleess
+   $smtp_host , $$ssmmttpp__hhoosstt
+   $smtp_pass , $$ssmmttpp__ppaassss
+   $smtp_port , $$ssmmttpp__ppoorrtt
+   $smtp_user , $$ssmmttpp__uusseerr
+   $smtp_use_tls , $$ssmmttpp__uussee__ttllss
+   $sort , $$ssoorrtt, bbrroowwsseerr
+   <sort-mailbox>, iinnddeexx
+   <sort-reverse>, iinnddeexx, bbrroowwsseerr
+   $sort_alias , $$ssoorrtt__aalliiaass
+   $sort_aux , $$ssoorrtt__aauuxx
+   $sort_browser , $$ssoorrtt__bbrroowwsseerr
+   $sort_re , $$ssoorrtt__rree
+   source, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, DDeeffiinniinngg//UUssiinngg  aalliiaasseess, RReeaaddiinngg
+          iinniittiiaalliizzaattiioonn  ccoommmmaannddss  ffrroomm  aannootthheerr  ffiillee, CCoonnffiigguurraattiioonn
+          CCoommmmaannddss
+
+   spam, SSppaamm  ddeetteeccttiioonn, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+   $spam_separator , $$ssppaamm__sseeppaarraattoorr
+   $spoolfile, SSeettttiinngg  vvaarriiaabblleess  bbaasseedd  uuppoonn  mmaaiillbbooxx, DDeeffiinniinngg  mmaaiillbbooxxeess
+          wwhhiicchh  rreecceeiivvee  mmaaiill, MMaaiillbbooxx  SShhoorrttccuuttss, PPOOPP33  SSuuppppoorrtt  ((OOPPTTIIOONNAALL)),
+          $$ssppoooollffiillee
+
+   $ssl_ca_certificates_file , $$ssssll__ccaa__cceerrttiiffiiccaatteess__ffiillee
+   $ssl_client_cert , $$ssssll__cclliieenntt__cceerrtt
+   $ssl_force_tls , $$ssssll__ffoorrccee__ttllss
+   $ssl_min_dh_prime_bits , $$ssssll__mmiinn__ddhh__pprriimmee__bbiittss
+   $ssl_starttls , $$ssssll__ssttaarrttttllss
+   $ssl_usesystemcerts , $$ssssll__uusseessyysstteemmcceerrttss
+   $ssl_use_sslv2 , $$ssssll__uussee__ssssllvv22
+   $ssl_use_sslv3 , $$ssssll__uussee__ssssllvv33
+   $ssl_use_tlsv1 , $$ssssll__uussee__ttllssvv11
+   $status_format, CCoommppoossiinngg  nneeww  mmeessssaaggeess, IInnttrroodduuccttiioonn
+   $status_chars , $$ssttaattuuss__cchhaarrss
+   $status_format , $$ssttaattuuss__ffoorrmmaatt
+   $status_on_top , $$ssttaattuuss__oonn__ttoopp
+   $strict_mailto, mmaaiillttoo::--ssttyyllee  lliinnkkss
+   $strict_threads, TThhrreeaaddeedd  MMooddee
+   $strict_mailto , $$ssttrriicctt__mmaaiillttoo
+   $strict_mime , $$ssttrriicctt__mmiimmee
+   $strict_threads , $$ssttrriicctt__tthhrreeaaddss
+   $strip_was , $$ssttrriipp__wwaass
+   $strip_was_regex , $$ssttrriipp__wwaass__rreeggeexx
+   $stuff_quoted , $$ssttuuffff__qquuootteedd
+   subscribe, MMaaiilliinngg  lliissttss, CCoonnffiigguurraattiioonn  CCoommmmaannddss, bbrroowwsseerr
+   $suspend , $$ssuussppeenndd
+   <sync-mailbox>, MMaannuuaall  CCoonnvveennttiioonnss, iinnddeexx, ppaaggeerr
+
+T
+
+   <tag-entry>, ggeenneerriicc
+   <tag-message>, ppaaggeerr
+   <tag-pattern>, iinnddeexx
+   <tag-prefix>, ggeenneerriicc
+   <tag-prefix-cond>, ggeenneerriicc
+   <tag-thread>, TThhrreeaaddeedd  MMooddee, iinnddeexx
+   $text_flowed , $$tteexxtt__fflloowweedd
+   $thorough_search , $$tthhoorroouugghh__sseeaarrcchh
+   $thread_received , $$tthhrreeaadd__rreecceeiivveedd
+   $tilde , $$ttiillddee
+   $timeout, IIMMAAPP  SSuuppppoorrtt  ((OOPPTTIIOONNAALL)), $$ttiimmeeoouutt
+   $tmpdir, TTeemmppoorraarryy  FFiilleess, $$ttmmppddiirr
+   $to_chars, SSttaattuuss  FFllaaggss
+   toggle, SSeettttiinngg  vvaarriiaabblleess, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+   <toggle-mailboxes>, bbrroowwsseerr
+   <toggle-new>, iinnddeexx
+   <toggle-quoted>, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, ppaaggeerr
+   <toggle-subscribed>, bbrroowwsseerr
+   <toggle-unlink>, ccoommppoossee
+   <toggle-write>, iinnddeexx
+   <top>, ppaaggeerr
+   <top-page>, ggeenneerriicc
+   $to_chars , $$ttoo__cchhaarrss
+   <transpose-chars>, eeddiittoorr
+   $trash , $$ttrraasshh
+   $tunnel , $$ttuunnnneell
+
+U
+
+   $umask, TTeemmppoorraarryy  FFiilleess, $$uummaasskk
+   unalias, DDeeffiinniinngg//UUssiinngg  aalliiaasseess, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+   unalternates, AAlltteerrnnaattiivvee  aaddddrreesssseess, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+   unalternative_order, MMIIMMEE  MMuullttiippaarrtt//AAlltteerrnnaattiivvee, CCoonnffiigguurraattiioonn
+          CCoommmmaannddss
+
+   unattachments, AAttttaacchhmmeenntt  SSeeaarrcchhiinngg  aanndd  CCoouunnttiinngg
+   unauto_view, MMIIMMEE  AAuuttoovviieeww, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+   $uncollapse_jump , $$uunnccoollllaappssee__jjuummpp
+   uncolor, UUssiinngg  ccoolloorr  aanndd  mmoonnoo  vviiddeeoo  aattttrriibbuutteess, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+
+   <undelete-entry>, aattttaacchh, ppoossttppoonnee
+   <undelete-message>, iinnddeexx, ppaaggeerr
+   <undelete-pattern>, iinnddeexx
+   <undelete-subthread>, TThhrreeaaddeedd  MMooddee, iinnddeexx, ppaaggeerr
+   <undelete-thread>, TThhrreeaaddeedd  MMooddee, iinnddeexx, ppaaggeerr
+   unhdr_order, DDeeffiinniinngg  tthhee  oorrddeerr  ooff  hheeaaddeerrss  wwhheenn  vviieewwiinngg  mmeessssaaggeess,
+          CCoonnffiigguurraattiioonn  CCoommmmaannddss
+
+   unhook, RReemmoovviinngg  hhooookkss, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+   unignore, IIggnnoorriinngg  ((wweeeeddiinngg))  uunnwwaanntteedd  mmeessssaaggee  hheeaaddeerrss, CCoonnffiigguurraattiioonn
+          CCoommmmaannddss
+
+   unlists, MMaaiilliinngg  lliissttss, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+   unmailboxes, DDeeffiinniinngg  mmaaiillbbooxxeess  wwhhiicchh  rreecceeiivvee  mmaaiill
+   unmime_lookup, MMIIMMEE  LLooookkuupp, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+   unmono, UUssiinngg  ccoolloorr  aanndd  mmoonnoo  vviiddeeoo  aattttrriibbuutteess, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+   unmy_hdr, UUsseerr  ddeeffiinneedd  hheeaaddeerrss, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+   unscore, MMeessssaaggee  SSccoorriinngg, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+   unset, SSeettttiinngg  vvaarriiaabblleess, CCoonnffiigguurraattiioonn  CCoommmmaannddss
+   unsubscribe, MMaaiilliinngg  lliissttss, CCoonnffiigguurraattiioonn  CCoommmmaannddss, bbrroowwsseerr
+   <untag-pattern>, iinnddeexx
+   <upcase-word>, EEddiittiinngg  IInnppuutt  FFiieellddss, eeddiittoorr
+   $use_8bitmime, SSMMTTPP  SSuuppppoorrtt  ((OOPPTTIIOONNAALL))
+   $use_8bitmime , $$uussee__88bbiittmmiimmee
+   $use_domain , $$uussee__ddoommaaiinn
+   $use_envelope_from , $$uussee__eennvveellooppee__ffrroomm
+   $use_from , $$uussee__ffrroomm
+   $use_idn , $$uussee__iiddnn
+   $use_ipv6 , $$uussee__iippvv66
+
+V
+
+   <verify-key>, ppggpp
+   <view-attach>, aattttaacchh, ccoommppoossee
+   <view-attachments>, iinnddeexx, ppaaggeerr
+   <view-file>, bbrroowwsseerr
+   <view-mailcap>, aattttaacchh
+   <view-name>, ppggpp
+   <view-text>, aattttaacchh
+   $VISUAL, CCoommppoossiinngg  nneeww  mmeessssaaggeess
+   $visual , $$vviissuuaall
+
+W
+
+   $wait_key, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, OOppttiioonnaall  FFiieellddss
+   $wait_key , $$wwaaiitt__kkeeyy
+   $weed, MMiisscceellllaanneeoouuss  FFuunnccttiioonnss, $$wweeeedd
+   <what-key>, ggeenneerriicc
+   $wrapmargin , $$wwrraappmmaarrggiinn
+   $wrap_search , $$wwrraapp__sseeaarrcchh
+   <write-fcc>, CCoommppoossiinngg  nneeww  mmeessssaaggeess, ccoommppoossee
+   $write_bcc , $$wwrriittee__bbcccc
+   $write_inc , $$wwrriittee__iinncc
+
+X
+
+   $xterm_icon , $$xxtteerrmm__iiccoonn
+   $xterm_leave , $$xxtteerrmm__lleeaavvee
+   $xterm_set_titles , $$xxtteerrmm__sseett__ttiittlleess
+   $xterm_title , $$xxtteerrmm__ttiittllee