- The Mutt Next Generation E-Mail Client
- Andreas Krennmair
+The Mutt Next Generation E-Mail Client
- <ak@synflood.at>
+Andreas Krennmair
- Michael Elkins
+ <a\bak\bk@\b@s\bsy\byn\bnf\bfl\blo\boo\bod\bd.\b.a\bat\bt>
- <me@cs.hmc.edu>
+Michael Elkins
- version devel-r545
+ <m\bme\be@\b@c\bcs\bs.\b.h\bhm\bmc\bc.\b.e\bed\bdu\bu>
- Abstract
+ version devel-r553
- Michael Elinks on mutt, circa 1995: ``All mail clients suck. This one just
- sucks less.''
+ _\bA_\bb_\bs_\bt_\br_\ba_\bc_\bt
+
+ 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!''
+ _________________________________________________________________
+
+ _\bT_\ba_\bb_\bl_\be_\b _\bo_\bf_\b _\bC_\bo_\bn_\bt_\be_\bn_\bt_\bs
+
+ 1\b1.\b. \b I\bIn\bnt\btr\bro\bod\bdu\buc\bct\bti\bio\bon\bn
+
+ 1\b1.\b. \b O\bOv\bve\ber\brv\bvi\bie\bew\bw
+ 2\b2.\b. \b M\bMu\but\btt\bt-\b-n\bng\bg \b H\bHo\bom\bme\be \b P\bPa\bag\bge\be
+ 3\b3.\b. \b M\bMa\bai\bil\bli\bin\bng\bg \b L\bLi\bis\bst\bts\bs
+ 4\b4.\b. \b S\bSo\bof\bft\btw\bwa\bar\bre\be \b D\bDi\bis\bst\btr\bri\bib\bbu\but\bti\bio\bon\bn \b S\bSi\bit\bte\bes\bs
+ 5\b5.\b. \b I\bIR\bRC\bC
+ 6\b6.\b. \b W\bWe\beb\bbl\blo\bog\bg
+ 7\b7.\b. \b C\bCo\bop\bpy\byr\bri\big\bgh\bht\bt
+ 8\b8.\b. \b M\bMa\ban\bnu\bua\bal\bl \b C\bCo\bon\bnv\bve\ben\bnt\bti\bio\bon\bns\bs
+
+ 2\b2.\b. \b G\bGe\bet\btt\bti\bin\bng\bg \b S\bSt\bta\bar\brt\bte\bed\bd
+
+ 1\b1.\b. \b B\bBa\bas\bsi\bic\bc \b C\bCo\bon\bnc\bce\bep\bpt\bts\bs
+
+ 1\b1.\b.1\b1.\b. \b S\bSc\bcr\bre\bee\ben\bns\bs \b a\ban\bnd\bd \b M\bMe\ben\bnu\bus\bs
+ 1\b1.\b.2\b2.\b. \b C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn
+ 1\b1.\b.3\b3.\b. \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs
+ 1\b1.\b.4\b4.\b. \b I\bIn\bnt\bte\ber\bra\bac\bct\bti\bio\bon\bn
+ 1\b1.\b.5\b5.\b. \b M\bMo\bod\bdu\bul\bla\bar\bri\biz\bza\bat\bti\bio\bon\bn
+ 1\b1.\b.6\b6.\b. \b P\bPa\bat\btt\bte\ber\brn\bns\bs
+
+ 2\b2.\b. \b S\bSc\bcr\bre\bee\ben\bns\bs \b a\ban\bnd\bd \b M\bMe\ben\bnu\bus\bs
+
+ 2\b2.\b.1\b1.\b. \b I\bIn\bnd\bde\bex\bx
+ 2\b2.\b.2\b2.\b. \b P\bPa\bag\bge\ber\br
+ 2\b2.\b.3\b3.\b. \b F\bFi\bil\ble\be \b B\bBr\bro\bow\bws\bse\ber\br
+ 2\b2.\b.4\b4.\b. \b S\bSi\bid\bde\beb\bba\bar\br
+ 2\b2.\b.5\b5.\b. \b H\bHe\bel\blp\bp
+ 2\b2.\b.6\b6.\b. \b C\bCo\bom\bmp\bpo\bos\bse\be \b M\bMe\ben\bnu\bu
+ 2\b2.\b.7\b7.\b. \b A\bAl\bli\bia\bas\bs \b M\bMe\ben\bnu\bu
+ 2\b2.\b.8\b8.\b. \b A\bAt\btt\bta\bac\bch\bhm\bme\ben\bnt\bt \b M\bMe\ben\bnu\bu
+ 2\b2.\b.9\b9.\b. \b K\bKe\bey\by \b M\bMe\ben\bnu\bu
+
+ 3\b3.\b. \b M\bMo\bov\bvi\bin\bng\bg \b A\bAr\bro\bou\bun\bnd\bd \b i\bin\bn \b M\bMe\ben\bnu\bus\bs
+ 4\b4.\b. \b E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs
+ 5\b5.\b. \b R\bRe\bea\bad\bdi\bin\bng\bg \b M\bMa\bai\bil\bl \b -\b- \b T\bTh\bhe\be \b I\bIn\bnd\bde\bex\bx \b a\ban\bnd\bd \b P\bPa\bag\bge\ber\br
+
+ 5\b5.\b.1\b1.\b. \b T\bTh\bhe\be \b M\bMe\bes\bss\bsa\bag\bge\be \b I\bIn\bnd\bde\bex\bx
+ 5\b5.\b.2\b2.\b. \b T\bTh\bhe\be \b P\bPa\bag\bge\ber\br
+ 5\b5.\b.3\b3.\b. \b T\bTh\bhr\bre\bea\bad\bde\bed\bd \b M\bMo\bod\bde\be
+ 5\b5.\b.4\b4.\b. \b M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs
+
+ 6\b6.\b. \b S\bSe\ben\bnd\bdi\bin\bng\bg \b M\bMa\bai\bil\bl
+
+ 6\b6.\b.1\b1.\b. \b C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs
+ 6\b6.\b.2\b2.\b. \b R\bRe\bep\bpl\bly\byi\bin\bng\bg
+ 6\b6.\b.3\b3.\b. \b E\bEd\bdi\bit\bti\bin\bng\bg \b t\bth\bhe\be \b m\bme\bes\bss\bsa\bag\bge\be \b h\bhe\bea\bad\bde\ber\br
+ 6\b6.\b.4\b4.\b. \b U\bUs\bsi\bin\bng\bg \b M\bMu\but\btt\bt-\b-n\bng\bg \b w\bwi\bit\bth\bh \b P\bPG\bGP\bP
+ 6\b6.\b.5\b5.\b. \b S\bSe\ben\bnd\bdi\bin\bng\bg \b a\ban\bno\bon\bny\bym\bmo\bou\bus\bs \b m\bme\bes\bss\bsa\bag\bge\bes\bs \b v\bvi\bia\ba \b m\bmi\bix\bxm\bma\bas\bst\bte\ber\br
+
+ 7\b7.\b. \b F\bFo\bor\brw\bwa\bar\brd\bdi\bin\bng\bg \b a\ban\bnd\bd \b B\bBo\bou\bun\bnc\bci\bin\bng\bg \b M\bMa\bai\bil\bl
+ 8\b8.\b. \b P\bPo\bos\bst\btp\bpo\bon\bni\bin\bng\bg \b M\bMa\bai\bil\bl
+
+ 3\b3.\b. \b C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn
+
+ 1\b1.\b. \b L\bLo\boc\bca\bat\bti\bio\bon\bns\bs \b o\bof\bf \b C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b F\bFi\bil\ble\bes\bs
+ 2\b2.\b. \b B\bBa\bas\bsi\bic\bc \b S\bSy\byn\bnt\bta\bax\bx \b o\bof\bf \b I\bIn\bni\bit\bti\bia\bal\bli\biz\bza\bat\bti\bio\bon\bn \b F\bFi\bil\ble\bes\bs
+ 3\b3.\b. \b E\bEx\bxp\bpa\ban\bns\bsi\bio\bon\bn \b w\bwi\bit\bth\bhi\bin\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+
+ 3\b3.\b.1\b1.\b. \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs'\b' \b O\bOu\but\btp\bpu\but\bt
+ 3\b3.\b.2\b2.\b. \b E\bEn\bnv\bvi\bir\bro\bon\bnm\bme\ben\bnt\bt \b V\bVa\bar\bri\bia\bab\bbl\ble\bes\bs
+ 3\b3.\b.3\b3.\b. \b C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b V\bVa\bar\bri\bia\bab\bbl\ble\bes\bs
+ 3\b3.\b.4\b4.\b. \b S\bSe\bel\blf\bf-\b-D\bDe\bef\bfi\bin\bne\bed\bd \b V\bVa\bar\bri\bia\bab\bbl\ble\bes\bs
+ 3\b3.\b.5\b5.\b. \b P\bPr\bre\be-\b-D\bDe\bef\bfi\bin\bne\bed\bd \b V\bVa\bar\bri\bia\bab\bbl\ble\bes\bs
+ 3\b3.\b.6\b6.\b. \b T\bTy\byp\bpe\be \b C\bCo\bon\bnv\bve\ber\brs\bsi\bio\bon\bns\bs
+
+ 4\b4.\b. \b D\bDe\bef\bfi\bin\bni\bin\bng\bg/\b/U\bUs\bsi\bin\bng\bg \b a\bal\bli\bia\bas\bse\bes\bs
+ 5\b5.\b. \b C\bCh\bha\ban\bng\bgi\bin\bng\bg \b t\bth\bhe\be \b d\bde\bef\bfa\bau\bul\blt\bt \b k\bke\bey\by \b b\bbi\bin\bnd\bdi\bin\bng\bgs\bs
+ 6\b6.\b. \b D\bDe\bef\bfi\bin\bni\bin\bng\bg \b a\bal\bli\bia\bas\bse\bes\bs \b f\bfo\bor\br \b c\bch\bha\bar\bra\bac\bct\bte\ber\br \b s\bse\bet\bts\bs
+ 7\b7.\b. \b S\bSe\bet\btt\bti\bin\bng\bg \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs \b b\bba\bas\bse\bed\bd \b u\bup\bpo\bon\bn \b m\bma\bai\bil\blb\bbo\box\bx
+ 8\b8.\b. \b K\bKe\bey\byb\bbo\boa\bar\brd\bd \b m\bma\bac\bcr\bro\bos\bs
+ 9\b9.\b. \b U\bUs\bsi\bin\bng\bg \b c\bco\bol\blo\bor\br \b a\ban\bnd\bd \b m\bmo\bon\bno\bo \b v\bvi\bid\bde\beo\bo \b a\bat\btt\btr\bri\bib\bbu\but\bte\bes\bs
+ 1\b10\b0.\b. \b I\bIg\bgn\bno\bor\bri\bin\bng\bg \b (\b(w\bwe\bee\bed\bdi\bin\bng\bg)\b) \b u\bun\bnw\bwa\ban\bnt\bte\bed\bd \b m\bme\bes\bss\bsa\bag\bge\be \b h\bhe\bea\bad\bde\ber\brs\bs
+ 1\b11\b1.\b. \b A\bAl\blt\bte\ber\brn\bna\bat\bti\biv\bve\be \b a\bad\bdd\bdr\bre\bes\bss\bse\bes\bs
+ 1\b12\b2.\b. \b F\bFo\bor\brm\bma\bat\bt \b =\b= \b F\bFl\blo\bow\bwe\bed\bd
+
+ 1\b12\b2.\b.1\b1.\b. \b I\bIn\bnt\btr\bro\bod\bdu\buc\bct\bti\bio\bon\bn
+ 1\b12\b2.\b.2\b2.\b. \b R\bRe\bec\bce\bei\biv\bvi\bin\bng\bg:\b: \b D\bDi\bis\bsp\bpl\bla\bay\by \b S\bSe\bet\btu\bup\bp
+ 1\b12\b2.\b.3\b3.\b. \b S\bSe\ben\bnd\bdi\bin\bng\bg
+ 1\b12\b2.\b.4\b4.\b. \b A\bAd\bdd\bdi\bit\bti\bio\bon\bna\bal\bl \b N\bNo\bot\bte\bes\bs
+
+ 1\b13\b3.\b. \b M\bMa\bai\bil\bli\bin\bng\bg \b l\bli\bis\bst\bts\bs
+ 1\b14\b4.\b. \b U\bUs\bsi\bin\bng\bg \b M\bMu\bul\blt\bti\bip\bpl\ble\be \b s\bsp\bpo\boo\bol\bl \b m\bma\bai\bil\blb\bbo\box\bxe\bes\bs
+ 1\b15\b5.\b. \b D\bDe\bef\bfi\bin\bni\bin\bng\bg \b m\bma\bai\bil\blb\bbo\box\bxe\bes\bs \b w\bwh\bhi\bic\bch\bh \b r\bre\bec\bce\bei\biv\bve\be \b m\bma\bai\bil\bl
+ 1\b16\b6.\b. \b U\bUs\bse\ber\br \b d\bde\bef\bfi\bin\bne\bed\bd \b h\bhe\bea\bad\bde\ber\brs\bs
+ 1\b17\b7.\b. \b D\bDe\bef\bfi\bin\bni\bin\bng\bg \b t\bth\bhe\be \b o\bor\brd\bde\ber\br \b o\bof\bf \b h\bhe\bea\bad\bde\ber\brs\bs \b w\bwh\bhe\ben\bn \b v\bvi\bie\bew\bwi\bin\bng\bg \b m\bme\bes\bss\bsa\bag\bge\bes\bs
+ 1\b18\b8.\b. \b S\bSp\bpe\bec\bci\bif\bfy\by \b d\bde\bef\bfa\bau\bul\blt\bt \b s\bsa\bav\bve\be \b f\bfi\bil\ble\ben\bna\bam\bme\be
+ 1\b19\b9.\b. \b S\bSp\bpe\bec\bci\bif\bfy\by \b d\bde\bef\bfa\bau\bul\blt\bt \b F\bFc\bcc\bc:\b: \b m\bma\bai\bil\blb\bbo\box\bx \b w\bwh\bhe\ben\bn \b c\bco\bom\bmp\bpo\bos\bsi\bin\bng\bg
+ 2\b20\b0.\b. \b S\bSp\bpe\bec\bci\bif\bfy\by \b d\bde\bef\bfa\bau\bul\blt\bt \b s\bsa\bav\bve\be \b f\bfi\bil\ble\ben\bna\bam\bme\be \b a\ban\bnd\bd \b d\bde\bef\bfa\bau\bul\blt\bt \b F\bFc\bcc\bc:\b: \b m\bma\bai\bil\blb\bbo\box\bx \b a\bat\bt
+ o\bon\bnc\bce\be
+
+ 2\b21\b1.\b. \b C\bCh\bha\ban\bng\bge\be \b s\bse\bet\btt\bti\bin\bng\bgs\bs \b b\bba\bas\bse\bed\bd \b u\bup\bpo\bon\bn \b m\bme\bes\bss\bsa\bag\bge\be \b r\bre\bec\bci\bip\bpi\bie\ben\bnt\bts\bs
+ 2\b22\b2.\b. \b C\bCh\bha\ban\bng\bge\be \b s\bse\bet\btt\bti\bin\bng\bgs\bs \b b\bbe\bef\bfo\bor\bre\be \b f\bfo\bor\brm\bma\bat\btt\bti\bin\bng\bg \b a\ba \b m\bme\bes\bss\bsa\bag\bge\be
+ 2\b23\b3.\b. \b C\bCh\bho\boo\bos\bsi\bin\bng\bg \b t\bth\bhe\be \b c\bcr\bry\byp\bpt\bto\bog\bgr\bra\bap\bph\bhi\bic\bc \b k\bke\bey\by \b o\bof\bf \b t\bth\bhe\be \b r\bre\bec\bci\bip\bpi\bie\ben\bnt\bt
+ 2\b24\b4.\b. \b A\bAd\bdd\bdi\bin\bng\bg \b k\bke\bey\by \b s\bse\beq\bqu\bue\ben\bnc\bce\bes\bs \b t\bto\bo \b t\bth\bhe\be \b k\bke\bey\byb\bbo\boa\bar\brd\bd \b b\bbu\buf\bff\bfe\ber\br
+ 2\b25\b5.\b. \b E\bEx\bxe\bec\bcu\but\bti\bin\bng\bg \b f\bfu\bun\bnc\bct\bti\bio\bon\bns\bs
+ 2\b26\b6.\b. \b M\bMe\bes\bss\bsa\bag\bge\be \b S\bSc\bco\bor\bri\bin\bng\bg
+ 2\b27\b7.\b. \b S\bSp\bpa\bam\bm \b d\bde\bet\bte\bec\bct\bti\bio\bon\bn
+ 2\b28\b8.\b. \b S\bSe\bet\btt\bti\bin\bng\bg \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ 2\b29\b9.\b. \b R\bRe\bea\bad\bdi\bin\bng\bg \b i\bin\bni\bit\bti\bia\bal\bli\biz\bza\bat\bti\bio\bon\bn \b c\bco\bom\bmm\bma\ban\bnd\bds\bs \b f\bfr\bro\bom\bm \b a\ban\bno\bot\bth\bhe\ber\br \b f\bfi\bil\ble\be
+ 3\b30\b0.\b. \b R\bRe\bem\bmo\bov\bvi\bin\bng\bg \b h\bho\boo\bok\bks\bs
+ 3\b31\b1.\b. \b S\bSh\bha\bar\bri\bin\bng\bg \b S\bSe\bet\btu\bup\bps\bs
+
+ 3\b31\b1.\b.1\b1.\b. \b C\bCh\bha\bar\bra\bac\bct\bte\ber\br \b S\bSe\bet\bts\bs
+ 3\b31\b1.\b.2\b2.\b. \b M\bMo\bod\bdu\bul\bla\bar\bri\biz\bza\bat\bti\bio\bon\bn
+ 3\b31\b1.\b.3\b3.\b. \b C\bCo\bon\bnd\bdi\bit\bti\bio\bon\bna\bal\bl \b p\bpa\bar\brt\bts\bs
+
+ 3\b32\b2.\b. \b O\bOb\bbs\bso\bol\ble\bet\bte\be \b V\bVa\bar\bri\bia\bab\bbl\ble\bes\bs
+
+ 4\b4.\b. \b A\bAd\bdv\bva\ban\bnc\bce\bed\bd \b U\bUs\bsa\bag\bge\be
+
+ 1\b1.\b. \b R\bRe\beg\bgu\bul\bla\bar\br \b E\bEx\bxp\bpr\bre\bes\bss\bsi\bio\bon\bns\bs
+ 2\b2.\b. \b P\bPa\bat\btt\bte\ber\brn\bns\bs
+
+ 2\b2.\b.1\b1.\b. \b C\bCo\bom\bmp\bpl\ble\bex\bx \b P\bPa\bat\btt\bte\ber\brn\bns\bs
+ 2\b2.\b.2\b2.\b. \b P\bPa\bat\btt\bte\ber\brn\bns\bs \b a\ban\bnd\bd \b D\bDa\bat\bte\bes\bs
+
+ 3\b3.\b. \b F\bFo\bor\brm\bma\bat\bt \b S\bSt\btr\bri\bin\bng\bgs\bs
+
+ 3\b3.\b.1\b1.\b. \b I\bIn\bnt\btr\bro\bod\bdu\buc\bct\bti\bio\bon\bn
+ 3\b3.\b.2\b2.\b. \b C\bCo\bon\bnd\bdi\bit\bti\bio\bon\bna\bal\bl \b E\bEx\bxp\bpa\ban\bns\bsi\bio\bon\bn
+ 3\b3.\b.3\b3.\b. \b M\bMo\bod\bdi\bif\bfi\bic\bca\bat\bti\bio\bon\bns\bs \b a\ban\bnd\bd \b P\bPa\bad\bdd\bdi\bin\bng\bg
+
+ 4\b4.\b. \b U\bUs\bsi\bin\bng\bg \b T\bTa\bag\bgs\bs
+ 5\b5.\b. \b U\bUs\bsi\bin\bng\bg \b H\bHo\boo\bok\bks\bs
+
+ 5\b5.\b.1\b1.\b. \b M\bMe\bes\bss\bsa\bag\bge\be \b M\bMa\bat\btc\bch\bhi\bin\bng\bg \b i\bin\bn \b H\bHo\boo\bok\bks\bs
+
+ 6\b6.\b. \b U\bUs\bsi\bin\bng\bg \b t\bth\bhe\be \b s\bsi\bid\bde\beb\bba\bar\br
+ 7\b7.\b. \b E\bEx\bxt\bte\ber\brn\bna\bal\bl \b A\bAd\bdd\bdr\bre\bes\bss\bs \b Q\bQu\bue\ber\bri\bie\bes\bs
+ 8\b8.\b. \b M\bMa\bai\bil\blb\bbo\box\bx \b F\bFo\bor\brm\bma\bat\bts\bs
+ 9\b9.\b. \b M\bMa\bai\bil\blb\bbo\box\bx \b S\bSh\bho\bor\brt\btc\bcu\but\bts\bs
+ 1\b10\b0.\b. \b H\bHa\ban\bnd\bdl\bli\bin\bng\bg \b M\bMa\bai\bil\bli\bin\bng\bg \b L\bLi\bis\bst\bts\bs
+ 1\b11\b1.\b. \b E\bEd\bdi\bit\bti\bin\bng\bg \b t\bth\bhr\bre\bea\bad\bds\bs
+
+ 1\b11\b1.\b.1\b1.\b. \b L\bLi\bin\bnk\bki\bin\bng\bg \b t\bth\bhr\bre\bea\bad\bds\bs
+ 1\b11\b1.\b.2\b2.\b. \b B\bBr\bre\bea\bak\bki\bin\bng\bg \b t\bth\bhr\bre\bea\bad\bds\bs
+
+ 1\b12\b2.\b. \b D\bDe\bel\bli\biv\bve\ber\bry\by \b S\bSt\bta\bat\btu\bus\bs \b N\bNo\bot\bti\bif\bfi\bic\bca\bat\bti\bio\bon\bn \b (\b(D\bDS\bSN\bN)\b) \b S\bSu\bup\bpp\bpo\bor\brt\bt
+ 1\b13\b3.\b. \b P\bPO\bOP\bP3\b3 \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
+ 1\b14\b4.\b. \b I\bIM\bMA\bAP\bP \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
+
+ 1\b14\b4.\b.1\b1.\b. \b T\bTh\bhe\be \b F\bFo\bol\bld\bde\ber\br \b B\bBr\bro\bow\bws\bse\ber\br
+ 1\b14\b4.\b.2\b2.\b. \b A\bAu\but\bth\bhe\ben\bnt\bti\bic\bca\bat\bti\bio\bon\bn
+
+ 1\b15\b5.\b. \b N\bNN\bNT\bTP\bP \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
+
+ 1\b15\b5.\b.1\b1.\b. \b A\bAg\bga\bai\bin\bn:\b: \b S\bSc\bco\bor\bri\bin\bng\bg
+
+ 1\b16\b6.\b. \b S\bSM\bMT\bTP\bP \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
+ 1\b17\b7.\b. \b M\bMa\ban\bna\bag\bgi\bin\bng\bg \b m\bmu\bul\blt\bti\bip\bpl\ble\be \b I\bIM\bMA\bAP\bP/\b/P\bPO\bOP\bP/\b/N\bNN\bNT\bTP\bP \b a\bac\bcc\bco\bou\bun\bnt\bts\bs \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
+ 1\b18\b8.\b. \b S\bSt\bta\bar\brt\bt \b a\ba \b W\bWW\bWW\bW \b B\bBr\bro\bow\bws\bse\ber\br \b o\bon\bn \b U\bUR\bRL\bLs\bs \b (\b(E\bEX\bXT\bTE\bER\bRN\bNA\bAL\bL)\b)
+ 1\b19\b9.\b. \b C\bCo\bom\bmp\bpr\bre\bes\bss\bse\bed\bd \b f\bfo\bol\bld\bde\ber\brs\bs \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
+
+ 1\b19\b9.\b.1\b1.\b. \b O\bOp\bpe\ben\bn \b a\ba \b c\bco\bom\bmp\bpr\bre\bes\bss\bse\bed\bd \b m\bma\bai\bil\blb\bbo\box\bx \b f\bfo\bor\br \b r\bre\bea\bad\bdi\bin\bng\bg
+ 1\b19\b9.\b.2\b2.\b. \b W\bWr\bri\bit\bte\be \b a\ba \b c\bco\bom\bmp\bpr\bre\bes\bss\bse\bed\bd \b m\bma\bai\bil\blb\bbo\box\bx
+ 1\b19\b9.\b.3\b3.\b. \b A\bAp\bpp\bpe\ben\bnd\bd \b a\ba \b m\bme\bes\bss\bsa\bag\bge\be \b t\bto\bo \b a\ba \b c\bco\bom\bmp\bpr\bre\bes\bss\bse\bed\bd \b m\bma\bai\bil\blb\bbo\box\bx
+ 1\b19\b9.\b.4\b4.\b. \b E\bEn\bnc\bcr\bry\byp\bpt\bte\bed\bd \b f\bfo\bol\bld\bde\ber\brs\bs
+
+ 5\b5.\b. \b M\bMu\but\btt\bt-\b-n\bng\bg'\b's\bs \b M\bMI\bIM\bME\bE \b S\bSu\bup\bpp\bpo\bor\brt\bt
+
+ 1\b1.\b. \b U\bUs\bsi\bin\bng\bg \b M\bMI\bIM\bME\bE \b i\bin\bn \b M\bMu\but\btt\bt
+
+ 1\b1.\b.1\b1.\b. \b V\bVi\bie\bew\bwi\bin\bng\bg \b M\bMI\bIM\bME\bE \b m\bme\bes\bss\bsa\bag\bge\bes\bs \b i\bin\bn \b t\bth\bhe\be \b p\bpa\bag\bge\ber\br
+ 1\b1.\b.2\b2.\b. \b T\bTh\bhe\be \b A\bAt\btt\bta\bac\bch\bhm\bme\ben\bnt\bt \b M\bMe\ben\bnu\bu
+ 1\b1.\b.3\b3.\b. \b T\bTh\bhe\be \b C\bCo\bom\bmp\bpo\bos\bse\be \b M\bMe\ben\bnu\bu
+
+ 2\b2.\b. \b M\bMI\bIM\bME\bE \b T\bTy\byp\bpe\be \b c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b w\bwi\bit\bth\bh \b m\bmi\bim\bme\be.\b.t\bty\byp\bpe\bes\bs
+ 3\b3.\b. \b M\bMI\bIM\bME\bE \b V\bVi\bie\bew\bwe\ber\br \b c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b w\bwi\bit\bth\bh \b m\bma\bai\bil\blc\bca\bap\bp
+
+ 3\b3.\b.1\b1.\b. \b T\bTh\bhe\be \b B\bBa\bas\bsi\bic\bcs\bs \b o\bof\bf \b t\bth\bhe\be \b m\bma\bai\bil\blc\bca\bap\bp \b f\bfi\bil\ble\be
+ 3\b3.\b.2\b2.\b. \b S\bSe\bec\bcu\bur\bre\be \b u\bus\bse\be \b o\bof\bf \b m\bma\bai\bil\blc\bca\bap\bp
+ 3\b3.\b.3\b3.\b. \b A\bAd\bdv\bva\ban\bnc\bce\bed\bd \b m\bma\bai\bil\blc\bca\bap\bp \b U\bUs\bsa\bag\bge\be
+ 3\b3.\b.4\b4.\b. \b E\bEx\bxa\bam\bmp\bpl\ble\be \b m\bma\bai\bil\blc\bca\bap\bp \b f\bfi\bil\ble\bes\bs
+
+ 4\b4.\b. \b M\bMI\bIM\bME\bE \b A\bAu\but\bto\bov\bvi\bie\bew\bw
+ 5\b5.\b. \b M\bMI\bIM\bME\bE \b M\bMu\bul\blt\bti\bip\bpa\bar\brt\bt/\b/A\bAl\blt\bte\ber\brn\bna\bat\bti\biv\bve\be
+ 6\b6.\b. \b A\bAt\btt\bta\bac\bch\bhm\bme\ben\bnt\bt \b S\bSe\bea\bar\brc\bch\bhi\bin\bng\bg \b a\ban\bnd\bd \b C\bCo\bou\bun\bnt\bti\bin\bng\bg
+ 7\b7.\b. \b M\bMI\bIM\bME\bE \b L\bLo\boo\bok\bku\bup\bp
+
+ 6\b6.\b. \b S\bSe\bec\bcu\bur\bri\bit\bty\by \b C\bCo\bon\bns\bsi\bid\bde\ber\bra\bat\bti\bio\bon\bns\bs
+
+ 1\b1.\b. \b P\bPa\bas\bss\bsw\bwo\bor\brd\bds\bs
+ 2\b2.\b. \b T\bTe\bem\bmp\bpo\bor\bra\bar\bry\by \b F\bFi\bil\ble\bes\bs
+ 3\b3.\b. \b I\bIn\bnf\bfo\bor\brm\bma\bat\bti\bio\bon\bn \b L\bLe\bea\bak\bks\bs
+
+ 3\b3.\b.1\b1.\b. \b M\bMe\bes\bss\bsa\bag\bge\be-\b-I\bID\bD:\b: \b h\bhe\bea\bad\bde\ber\brs\bs
+ 3\b3.\b.2\b2.\b. \b m\bma\bai\bil\blt\bto\bo:\b:-\b-s\bst\bty\byl\ble\be \b l\bli\bin\bnk\bks\bs
+
+ 4\b4.\b. \b E\bEx\bxt\bte\ber\brn\bna\bal\bl \b a\bap\bpp\bpl\bli\bic\bca\bat\bti\bio\bon\bns\bs
+
+ 4\b4.\b.1\b1.\b. \b m\bma\bai\bil\blc\bca\bap\bp
+ 4\b4.\b.2\b2.\b. \b O\bOt\bth\bhe\ber\br
+
+ 7\b7.\b. \b R\bRe\bef\bfe\ber\bre\ben\bnc\bce\be
+
+ 1\b1.\b. \b C\bCo\bom\bmm\bma\ban\bnd\bd \b l\bli\bin\bne\be \b o\bop\bpt\bti\bio\bon\bns\bs
+ 2\b2.\b. \b P\bPa\bat\btt\bte\ber\brn\bns\bs
+ 3\b3.\b. \b C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ 4\b4.\b. \b C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ 5\b5.\b. \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs
+
+ 5\b5.\b.1\b1.\b. \b g\bge\ben\bne\ber\bri\bic\bc
+ 5\b5.\b.2\b2.\b. \b i\bin\bnd\bde\bex\bx
+ 5\b5.\b.3\b3.\b. \b p\bpa\bag\bge\ber\br
+ 5\b5.\b.4\b4.\b. \b a\bal\bli\bia\bas\bs
+ 5\b5.\b.5\b5.\b. \b q\bqu\bue\ber\bry\by
+ 5\b5.\b.6\b6.\b. \b a\bat\btt\bta\bac\bch\bh
+ 5\b5.\b.7\b7.\b. \b c\bco\bom\bmp\bpo\bos\bse\be
+ 5\b5.\b.8\b8.\b. \b p\bpo\bos\bst\btp\bpo\bon\bne\be
+ 5\b5.\b.9\b9.\b. \b b\bbr\bro\bow\bws\bse\ber\br
+ 5\b5.\b.1\b10\b0.\b. \b p\bpg\bgp\bp
+ 5\b5.\b.1\b11\b1.\b. \b e\bed\bdi\bit\bto\bor\br
+ 5\b5.\b.1\b12\b2.\b. \b s\bsi\bid\bde\beb\bba\bar\br
+
+ A\bA.\b. \b A\bAc\bck\bkn\bno\bow\bwl\ble\bed\bdg\bgm\bme\ben\bnt\bts\bs
+ B\bB.\b. \b H\bHa\bac\bck\bki\bin\bng\bg \b D\bDo\boc\bcu\bum\bme\ben\bnt\bta\bat\bti\bio\bon\bn
+ I\bIn\bnd\bde\bex\bx
+
+ _\bL_\bi_\bs_\bt_\b _\bo_\bf_\b _\bT_\ba_\bb_\bl_\be_\bs
+
+ 2.1. M\bMo\bos\bst\bt \b c\bco\bom\bmm\bmo\bon\bnl\bly\by \b u\bus\bse\bed\bd \b m\bmo\bov\bve\bem\bme\ben\bnt\bt \b b\bbi\bin\bnd\bdi\bin\bng\bgs\bs
+ 2.2. L\bLi\bin\bne\be \b E\bEd\bdi\bit\bto\bor\br \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs
+ 2.3. M\bMo\bos\bst\bt \b c\bco\bom\bmm\bmo\bon\bnl\bly\by \b u\bus\bse\bed\bd \b I\bIn\bnd\bde\bex\bx \b B\bBi\bin\bnd\bdi\bin\bng\bgs\bs
+ 2.4. M\bMo\bos\bst\bt \b c\bco\bom\bmm\bmo\bon\bnl\bly\by \b u\bus\bse\bed\bd \b P\bPa\bag\bge\ber\br \b B\bBi\bin\bnd\bdi\bin\bng\bgs\bs
+ 2.5. A\bAN\bNS\bSI\bI \b E\bEs\bsc\bca\bap\bpe\be \b S\bSe\beq\bqu\bue\ben\bnc\bce\bes\bs
+ 2.6. A\bAN\bNS\bSI\bI \b C\bCo\bol\blo\bor\brs\bs
+ 2.7. M\bMo\bos\bst\bt \b c\bco\bom\bmm\bmo\bon\bnl\bly\by \b u\bus\bse\bed\bd \b t\bth\bhr\bre\bea\bad\bd-\b-r\bre\bel\bla\bat\bte\bed\bd \b b\bbi\bin\bnd\bdi\bin\bng\bgs\bs
+ 2.8. M\bMo\bos\bst\bt \b c\bco\bom\bmm\bmo\bon\bnl\bly\by \b u\bus\bse\bed\bd \b M\bMa\bai\bil\bl \b C\bCo\bom\bmp\bpo\bos\bsi\bit\bti\bio\bon\bn \b B\bBi\bin\bnd\bdi\bin\bng\bgs\bs
+ 2.9. M\bMo\bos\bst\bt \b c\bco\bom\bmm\bmo\bon\bnl\bly\by \b u\bus\bse\bed\bd \b C\bCo\bom\bmp\bpo\bos\bse\be \b M\bMe\ben\bnu\bu \b B\bBi\bin\bnd\bdi\bin\bng\bgs\bs
+ 2.10. P\bPG\bGP\bP \b K\bKe\bey\by \b M\bMe\ben\bnu\bu \b F\bFl\bla\bag\bgs\bs
+ 3.1. A\bAl\blt\bte\ber\brn\bna\bat\bti\biv\bve\be \b K\bKe\bey\by \b N\bNa\bam\bme\bes\bs
+ 7.1. R\bRe\bef\bfe\ber\bre\ben\bnc\bce\be:\b: \b C\bCo\bom\bmm\bma\ban\bnd\bd \b L\bLi\bin\bne\be \b O\bOp\bpt\bti\bio\bon\bns\bs
+ 7.2. R\bRe\bef\bfe\ber\bre\ben\bnc\bce\be:\b: \b P\bPa\bat\btt\bte\ber\brn\bns\bs
+ 7.3. R\bRe\bef\bfe\ber\bre\ben\bnc\bce\be:\b: \b O\bOb\bbs\bso\bol\ble\bet\bte\be \b V\bVa\bar\bri\bia\bab\bbl\ble\bes\bs
+ 7.4. R\bRe\bef\bfe\ber\bre\ben\bnc\bce\be:\b: \b D\bDe\bef\bfa\bau\bul\blt\bt \b G\bGe\ben\bne\ber\bri\bic\bc \b F\bFu\bun\bnc\bct\bti\bio\bon\bn \b B\bBi\bin\bnd\bdi\bin\bng\bgs\bs
+ 7.5. R\bRe\bef\bfe\ber\bre\ben\bnc\bce\be:\b: \b D\bDe\bef\bfa\bau\bul\blt\bt \b I\bIn\bnd\bde\bex\bx \b F\bFu\bun\bnc\bct\bti\bio\bon\bn \b B\bBi\bin\bnd\bdi\bin\bng\bgs\bs
+ 7.6. R\bRe\bef\bfe\ber\bre\ben\bnc\bce\be:\b: \b D\bDe\bef\bfa\bau\bul\blt\bt \b P\bPa\bag\bge\ber\br \b F\bFu\bun\bnc\bct\bti\bio\bon\bn \b B\bBi\bin\bnd\bdi\bin\bng\bgs\bs
+ 7.7. R\bRe\bef\bfe\ber\bre\ben\bnc\bce\be:\b: \b D\bDe\bef\bfa\bau\bul\blt\bt \b A\bAl\bli\bia\bas\bs \b M\bMe\ben\bnu\bu \b F\bFu\bun\bnc\bct\bti\bio\bon\bn \b B\bBi\bin\bnd\bdi\bin\bng\bgs\bs
+ 7.8. R\bRe\bef\bfe\ber\bre\ben\bnc\bce\be:\b: \b D\bDe\bef\bfa\bau\bul\blt\bt \b Q\bQu\bue\ber\bry\by \b M\bMe\ben\bnu\bu \b F\bFu\bun\bnc\bct\bti\bio\bon\bn \b B\bBi\bin\bnd\bdi\bin\bng\bgs\bs
+ 7.9. R\bRe\bef\bfe\ber\bre\ben\bnc\bce\be:\b: \b D\bDe\bef\bfa\bau\bul\blt\bt \b A\bAt\btt\bta\bac\bch\bhm\bme\ben\bnt\bt \b M\bMe\ben\bnu\bu \b F\bFu\bun\bnc\bct\bti\bio\bon\bn \b B\bBi\bin\bnd\bdi\bin\bng\bgs\bs
+ 7.10. R\bRe\bef\bfe\ber\bre\ben\bnc\bce\be:\b: \b D\bDe\bef\bfa\bau\bul\blt\bt \b C\bCo\bom\bmp\bpo\bos\bse\be \b M\bMe\ben\bnu\bu \b F\bFu\bun\bnc\bct\bti\bio\bon\bn \b B\bBi\bin\bnd\bdi\bin\bng\bgs\bs
+ 7.11. R\bRe\bef\bfe\ber\bre\ben\bnc\bce\be:\b: \b D\bDe\bef\bfa\bau\bul\blt\bt \b P\bPo\bos\bst\btp\bpo\bon\bne\be \b M\bMe\ben\bnu\bu \b F\bFu\bun\bnc\bct\bti\bio\bon\bn \b B\bBi\bin\bnd\bdi\bin\bng\bgs\bs
+ 7.12. R\bRe\bef\bfe\ber\bre\ben\bnc\bce\be:\b: \b D\bDe\bef\bfa\bau\bul\blt\bt \b B\bBr\bro\bow\bws\bse\ber\br \b M\bMe\ben\bnu\bu \b F\bFu\bun\bnc\bct\bti\bio\bon\bn \b B\bBi\bin\bnd\bdi\bin\bng\bgs\bs
+ 7.13. R\bRe\bef\bfe\ber\bre\ben\bnc\bce\be:\b: \b D\bDe\bef\bfa\bau\bul\blt\bt \b P\bPG\bGP\bP \b M\bMe\ben\bnu\bu \b F\bFu\bun\bnc\bct\bti\bio\bon\bn \b B\bBi\bin\bnd\bdi\bin\bng\bgs\bs
+ 7.14. R\bRe\bef\bfe\ber\bre\ben\bnc\bce\be:\b: \b D\bDe\bef\bfa\bau\bul\blt\bt \b E\bEd\bdi\bit\bto\bor\br \b F\bFu\bun\bnc\bct\bti\bio\bon\bn \b B\bBi\bin\bnd\bdi\bin\bng\bgs\bs
+ 7.15. R\bRe\bef\bfe\ber\bre\ben\bne\be:\b: \b D\bDe\bef\bfa\bau\bul\blt\bt \b S\bSi\bid\bde\beb\bba\bar\br \b F\bFu\bun\bnc\bct\bti\bio\bon\bn \b B\bBi\bin\bnd\bdi\bin\bng\bgs\bs
- --------------------------------------------------------------------------
+Chapter 1. Introduction
- Table of Contents
+ _\bT_\ba_\bb_\bl_\be_\b _\bo_\bf_\b _\bC_\bo_\bn_\bt_\be_\bn_\bt_\bs
- 1. Introduction
+ 1\b1.\b. \b O\bOv\bve\ber\brv\bvi\bie\bew\bw
+ 2\b2.\b. \b M\bMu\but\btt\bt-\b-n\bng\bg \b H\bHo\bom\bme\be \b P\bPa\bag\bge\be
+ 3\b3.\b. \b M\bMa\bai\bil\bli\bin\bng\bg \b L\bLi\bis\bst\bts\bs
+ 4\b4.\b. \b S\bSo\bof\bft\btw\bwa\bar\bre\be \b D\bDi\bis\bst\btr\bri\bib\bbu\but\bti\bio\bon\bn \b S\bSi\bit\bte\bes\bs
+ 5\b5.\b. \b I\bIR\bRC\bC
+ 6\b6.\b. \b W\bWe\beb\bbl\blo\bog\bg
+ 7\b7.\b. \b C\bCo\bop\bpy\byr\bri\big\bgh\bht\bt
+ 8\b8.\b. \b M\bMa\ban\bnu\bua\bal\bl \b C\bCo\bon\bnv\bve\ben\bnt\bti\bio\bon\bns\bs
- 1. Overview
+1. Overview
- 2. Mutt-ng Home Page
+ _\bM_\bu_\bt_\bt_\b-_\bn_\bg 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 _\bM_\bu_\bt_\bt_\b-_\bN_\bG ,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
+ <\b<h\bht\btt\btp\bp:\b:/\b//\b/w\bww\bww\bw.\b.m\bmu\but\btt\btn\bng\bg.\b.o\bor\brg\bg/\b/>\b>
- 6. Weblog
+3. Mailing Lists
- 7. Copyright
+ * <m\bmu\but\btt\bt-\b-n\bng\bg-\b-u\bus\bse\ber\brs\bs@\b@l\bli\bis\bst\bts\bs.\b.b\bbe\ber\brl\bli\bio\bos\bs.\b.d\bde\be>: This is where the mutt-ng user
+ support happens.
+ * <m\bmu\but\btt\bt-\b-n\bng\bg-\b-d\bde\bev\bve\bel\bl@\b@l\bli\bis\bst\bts\bs.\b.b\bbe\ber\brl\bli\bio\bos\bs.\b.d\bde\be>: 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 <\b<h\bht\btt\btp\bp:\b:/\b//\b/m\bmu\but\btt\bt-\b-n\bng\bg.\b.b\bbe\ber\brl\bli\bio\bos\bs.\b.d\bde\be/\b/s\bsn\bna\bap\bps\bsh\bho\bot\bts\bs/\b/>\b>
- 1. Basic Concepts
+5. IRC
- 1.1. Screens and Menus
+ Visit channel _\b#_\bm_\bu_\bt_\bt_\bn_\bg on i\bir\brc\bc.\b.f\bfr\bre\bee\ben\bno\bod\bde\be.\b.n\bne\bet\bt \b (\b(w\bww\bww\bw.\b.f\bfr\bre\bee\ben\bno\bod\bde\be.\b.n\bne\bet\bt)\b) 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\bMu\but\btt\bt-\b-n\bng\bg \b d\bde\bev\bve\bel\blo\bop\bpm\bme\ben\bnt\bt \b w\bwe\beb\bbl\blo\bog\bg.
- 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.
+ $\b$i\bim\bma\bap\bp_\b_m\bma\bai\bil\bl_\b_c\bch\bhe\bec\bck\bk 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\bmu\but\btt\bt-\b-n\bng\bg-\b-d\bde\bev\bve\bel\bl@\b@l\bli\bis\bst\bts\bs.\b.b\bbe\ber\brl\bli\bio\bos\bs.\b.d\bde\be> to report it.
- 2.6. Compose Menu
+Chapter 2. Getting Started
- 2.7. Alias Menu
+ _\bT_\ba_\bb_\bl_\be_\b _\bo_\bf_\b _\bC_\bo_\bn_\bt_\be_\bn_\bt_\bs
- 2.8. Attachment Menu
+ 1\b1.\b. \b B\bBa\bas\bsi\bic\bc \b C\bCo\bon\bnc\bce\bep\bpt\bts\bs
- 2.9. Key Menu
+ 1\b1.\b.1\b1.\b. \b S\bSc\bcr\bre\bee\ben\bns\bs \b a\ban\bnd\bd \b M\bMe\ben\bnu\bus\bs
+ 1\b1.\b.2\b2.\b. \b C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn
+ 1\b1.\b.3\b3.\b. \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs
+ 1\b1.\b.4\b4.\b. \b I\bIn\bnt\bte\ber\bra\bac\bct\bti\bio\bon\bn
+ 1\b1.\b.5\b5.\b. \b M\bMo\bod\bdu\bul\bla\bar\bri\biz\bza\bat\bti\bio\bon\bn
+ 1\b1.\b.6\b6.\b. \b P\bPa\bat\btt\bte\ber\brn\bns\bs
- 3. Moving Around in Menus
+ 2\b2.\b. \b S\bSc\bcr\bre\bee\ben\bns\bs \b a\ban\bnd\bd \b M\bMe\ben\bnu\bus\bs
- 4. Editing Input Fields
+ 2\b2.\b.1\b1.\b. \b I\bIn\bnd\bde\bex\bx
+ 2\b2.\b.2\b2.\b. \b P\bPa\bag\bge\ber\br
+ 2\b2.\b.3\b3.\b. \b F\bFi\bil\ble\be \b B\bBr\bro\bow\bws\bse\ber\br
+ 2\b2.\b.4\b4.\b. \b S\bSi\bid\bde\beb\bba\bar\br
+ 2\b2.\b.5\b5.\b. \b H\bHe\bel\blp\bp
+ 2\b2.\b.6\b6.\b. \b C\bCo\bom\bmp\bpo\bos\bse\be \b M\bMe\ben\bnu\bu
+ 2\b2.\b.7\b7.\b. \b A\bAl\bli\bia\bas\bs \b M\bMe\ben\bnu\bu
+ 2\b2.\b.8\b8.\b. \b A\bAt\btt\bta\bac\bch\bhm\bme\ben\bnt\bt \b M\bMe\ben\bnu\bu
+ 2\b2.\b.9\b9.\b. \b K\bKe\bey\by \b M\bMe\ben\bnu\bu
- 5. Reading Mail - The Index and Pager
+ 3\b3.\b. \b M\bMo\bov\bvi\bin\bng\bg \b A\bAr\bro\bou\bun\bnd\bd \b i\bin\bn \b M\bMe\ben\bnu\bus\bs
+ 4\b4.\b. \b E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs
+ 5\b5.\b. \b R\bRe\bea\bad\bdi\bin\bng\bg \b M\bMa\bai\bil\bl \b -\b- \b T\bTh\bhe\be \b I\bIn\bnd\bde\bex\bx \b a\ban\bnd\bd \b P\bPa\bag\bge\ber\br
- 5.1. The Message Index
+ 5\b5.\b.1\b1.\b. \b T\bTh\bhe\be \b M\bMe\bes\bss\bsa\bag\bge\be \b I\bIn\bnd\bde\bex\bx
+ 5\b5.\b.2\b2.\b. \b T\bTh\bhe\be \b P\bPa\bag\bge\ber\br
+ 5\b5.\b.3\b3.\b. \b T\bTh\bhr\bre\bea\bad\bde\bed\bd \b M\bMo\bod\bde\be
+ 5\b5.\b.4\b4.\b. \b M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs
- 5.2. The Pager
+ 6\b6.\b. \b S\bSe\ben\bnd\bdi\bin\bng\bg \b M\bMa\bai\bil\bl
- 5.3. Threaded Mode
+ 6\b6.\b.1\b1.\b. \b C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs
+ 6\b6.\b.2\b2.\b. \b R\bRe\bep\bpl\bly\byi\bin\bng\bg
+ 6\b6.\b.3\b3.\b. \b E\bEd\bdi\bit\bti\bin\bng\bg \b t\bth\bhe\be \b m\bme\bes\bss\bsa\bag\bge\be \b h\bhe\bea\bad\bde\ber\br
+ 6\b6.\b.4\b4.\b. \b U\bUs\bsi\bin\bng\bg \b M\bMu\but\btt\bt-\b-n\bng\bg \b w\bwi\bit\bth\bh \b P\bPG\bGP\bP
+ 6\b6.\b.5\b5.\b. \b S\bSe\ben\bnd\bdi\bin\bng\bg \b a\ban\bno\bon\bny\bym\bmo\bou\bus\bs \b m\bme\bes\bss\bsa\bag\bge\bes\bs \b v\bvi\bia\ba \b m\bmi\bix\bxm\bma\bas\bst\bte\ber\br
- 5.4. Miscellaneous Functions
+ 7\b7.\b. \b F\bFo\bor\brw\bwa\bar\brd\bdi\bin\bng\bg \b a\ban\bnd\bd \b B\bBo\bou\bun\bnc\bci\bin\bng\bg \b M\bMa\bai\bil\bl
+ 8\b8.\b. \b P\bPo\bos\bst\btp\bpo\bon\bni\bin\bng\bg \b M\bMa\bai\bil\bl
- 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 _\bi_\bn_\bd_\be_\bx displays the contents of the currently opened mailbox.
+ * The _\bp_\ba_\bg_\be_\br is responsible for displaying messages, that is, the
+ header, the body and all attached parts.
+ * The _\bf_\bi_\bl_\be_\b _\bb_\br_\bo_\bw_\bs_\be_\br offers operations on and displays information of
+ all folders mutt-ng should watch for mail.
+ * The _\bs_\bi_\bd_\be_\bb_\ba_\br offers a permanent view of which mailboxes contain how
+ many total, new and/or flagged mails.
+ * The _\bh_\be_\bl_\bp_\b _\bs_\bc_\br_\be_\be_\bn lists for all currently available commands how to
+ invoke them as well as a short description.
+ * The _\bc_\bo_\bm_\bp_\bo_\bs_\be menu is a comfortable interface take last actions
+ before sending mail: change subjects, attach files, remove
+ attachements, etc.
+ * The _\ba_\bt_\bt_\ba_\bc_\bh_\be_\bm_\be_\bn_\bt menu gives a summary and the tree structure of the
+ attachements of the current message.
+ * The _\ba_\bl_\bi_\ba_\bs menu lists all or a fraction of the aliases a user has
+ defined.
+ * The _\bk_\be_\by 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 _\bn_\bo_\bt feature an internal configuration interface or menu
+ due to the simple fact that this would be too complex to handle
+ (currently there are several _\bh_\bu_\bn_\bd_\br_\be_\bd 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 _\bh_\bo_\bo_\bk_\bs.
+ 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
+ _\bT_\ba_\bb_\bl_\be_\b _\b2_\b._\b1_\b._\b _\bM_\bo_\bs_\bt_\b _\bc_\bo_\bm_\bm_\bo_\bn_\bl_\by_\b _\bu_\bs_\be_\bd_\b _\bm_\bo_\bv_\be_\bm_\be_\bn_\bt_\b _\bb_\bi_\bn_\bd_\bi_\bn_\bg_\bs
+ 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
+ _\bT_\ba_\bb_\bl_\be_\b _\b2_\b._\b2_\b._\b _\bL_\bi_\bn_\be_\b _\bE_\bd_\bi_\bt_\bo_\br_\b _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\bs
+ 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 _\be_\bd_\bi_\bt_\bo_\br functions using the b\bbi\bin\bnd\bd command. For
+ example, to make the _\bD_\be_\bl_\be_\bt_\be 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
+ _\bT_\ba_\bb_\bl_\be_\b _\b2_\b._\b3_\b._\b _\bM_\bo_\bs_\bt_\b _\bc_\bo_\bm_\bm_\bo_\bn_\bl_\by_\b _\bu_\bs_\be_\bd_\b _\bI_\bn_\bd_\be_\bx_\b _\bB_\bi_\bn_\bd_\bi_\bn_\bg_\bs
+ 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
+ * _\bs_\be_\bt_\b-_\bf_\bl_\ba_\bg (default: w)
+ * _\bc_\bl_\be_\ba_\br_\b-_\bf_\bl_\ba_\bg (default: W)
- 31.3. Conditional parts
+ Furthermore, the following flags reflect who the message is addressed
+ to. They can be customized with the $\b$t\bto\bo_\b_c\bch\bha\bar\brs\bs 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 _\bl_\be_\bs_\bs though
+ not nearly as featureful.
+
+ _\bT_\ba_\bb_\bl_\be_\b _\b2_\b._\b4_\b._\b _\bM_\bo_\bs_\bt_\b _\bc_\bo_\bm_\bm_\bo_\bn_\bl_\by_\b _\bu_\bs_\be_\bd_\b _\bP_\ba_\bg_\be_\br_\b _\bB_\bi_\bn_\bd_\bi_\bn_\bg_\bs
+ 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 _\bi_\bn_\bd_\be_\bx are available in the
+ pager, such as _\bd_\be_\bl_\be_\bt_\be_\b-_\bm_\be_\bs_\bs_\ba_\bg_\be or _\bc_\bo_\bp_\by_\b-_\bm_\be_\bs_\bs_\ba_\bg_\be (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\bco\bol\blo\bor\br 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).
+
+ _\bT_\ba_\bb_\bl_\be_\b _\b2_\b._\b5_\b._\b _\bA_\bN_\bS_\bI_\b _\bE_\bs_\bc_\ba_\bp_\be_\b _\bS_\be_\bq_\bu_\be_\bn_\bc_\be_\bs
+ 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
+ _\bT_\ba_\bb_\bl_\be_\b _\b2_\b._\b6_\b._\b _\bA_\bN_\bS_\bI_\b _\bC_\bo_\bl_\bo_\br_\bs
+ 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\bau\but\bto\bo_\b_v\bvi\bie\bew\bw script for highlighting
+ purposes. _\bN_\bo_\bt_\be_\b: 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\bso\bor\brt\bte\bed\bd by _\bt_\bh_\br_\be_\ba_\bd_\bs ,there are a few additional
+ functions available in the _\bi_\bn_\bd_\be_\bx and _\bp_\ba_\bg_\be_\br modes.
+
+ _\bT_\ba_\bb_\bl_\be_\b _\b2_\b._\b7_\b._\b _\bM_\bo_\bs_\bt_\b _\bc_\bo_\bm_\bm_\bo_\bn_\bl_\by_\b _\bu_\bs_\be_\bd_\b _\bt_\bh_\br_\be_\ba_\bd_\b-_\br_\be_\bl_\ba_\bt_\be_\bd_\b _\bb_\bi_\bn_\bd_\bi_\bn_\bg_\bs
+ 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
+
+ _\bN_\bo_\bt_\be_\b: 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 $\b$i\bin\bnd\bde\bex\bx_\b_f\bfo\bor\brm\bma\bat\bt.
+
+ For example, you could use %?M?(#%03M)&(%4l)? in $\b$i\bin\bnd\bde\bex\bx_\b_f\bfo\bor\brm\bma\bat\bt to
+ optionally display the number of hidden messages if the thread is
+ collapsed.
- 3.3. Modifications and Padding
+ See also the $\b$s\bst\btr\bri\bic\bct\bt_\b_t\bth\bhr\bre\bea\bad\bds\bs 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\bal\bli\bia\bas\bs command is added to the
+ file specified by the $\b$a\bal\bli\bia\bas\bs_\b_f\bfi\bil\ble\be variable for future use. _\bN_\bo_\bt_\be_\b:
+ Specifying an $\b$a\bal\bli\bia\bas\bs_\b_f\bfi\bil\ble\be does not add the aliases specified there-in,
+ you must also s\bso\bou\bur\brc\bce\be 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\big\bgn\bno\bor\bre\be
+ 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\bat\btt\bta\bac\bch\bh-\b-m\bme\ben\bnu\bu, 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\bco\bom\bmp\bpo\bos\bse\be-\b-m\bme\ben\bnu\bu .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\bma\bac\bcr\bro\bo 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\bli\bis\bst\bts\bs commands, but
+ also honor any Mail-Followup-To header(s) if the $\b$h\bho\bon\bno\bor\br_\b_f\bfo\bol\bll\blo\bow\bwu\bup\bp_\b_t\bto\bo
+ 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 $\b$p\bpi\bip\bpe\be_\b_d\bde\bec\bco\bod\bde\be, $\b$p\bpi\bip\bpe\be_\b_s\bsp\bpl\bli\bit\bt,
+ $\b$p\bpi\bip\bpe\be_\b_d\bde\bec\bco\bod\bde\be and $\b$w\bwa\bai\bit\bt_\b_k\bke\bey\by 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 $\b$w\bwe\bee\bed\bd
+ 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 $\b$w\bwa\bai\bit\bt_\b_k\bke\bey\by 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 _\bp_\ba_\bg_\be_\br uses the $\b$q\bqu\buo\bot\bte\be_\b_r\bre\beg\bge\bex\bxp\bp 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 _\bi_\bn_\bd_\be_\bx for sending
+ messages.
- 3.1. The Basics of the mailcap file
+ _\bT_\ba_\bb_\bl_\be_\b _\b2_\b._\b8_\b._\b _\bM_\bo_\bs_\bt_\b _\bc_\bo_\bm_\bm_\bo_\bn_\bl_\by_\b _\bu_\bs_\be_\bd_\b _\bM_\ba_\bi_\bl_\b _\bC_\bo_\bm_\bp_\bo_\bs_\bi_\bt_\bi_\bo_\bn_\b _\bB_\bi_\bn_\bd_\bi_\bn_\bg_\bs
+ 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\bfo\bor\brw\bwa\bar\brd\bdi\bin\bng\bg-\b-m\bma\bai\bil\bl.
- 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 _\bc_\bo_\bm_\bp_\bo_\bs_\be menu. The following options are available:
- 2. Temporary Files
+ _\bT_\ba_\bb_\bl_\be_\b _\b2_\b._\b9_\b._\b _\bM_\bo_\bs_\bt_\b _\bc_\bo_\bm_\bm_\bo_\bn_\bl_\by_\b _\bu_\bs_\be_\bd_\b _\bC_\bo_\bm_\bp_\bo_\bs_\be_\b _\bM_\be_\bn_\bu_\b _\bB_\bi_\bn_\bd_\bi_\bn_\bg_\bs
+ 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
+ _\bN_\bo_\bt_\be_\b: 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
+ $\b$s\bst\bta\bat\btu\bus\bs_\b_f\bfo\bor\brm\bma\bat\bt 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 _\bb_\be_\bl_\bo_\bw 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 _\bn_\bo_\bt 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:_\bf_\bi_\bl_\be_\bn_\ba_\bm_\be Mutt-ng will pick up _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be just as if
+ you had used the _\be_\bd_\bi_\bt_\b-_\bf_\bc_\bc function in the _\bc_\bo_\bm_\bp_\bo_\bs_\be menu.
- 5.5. query
+ You can also attach files to your message by specifying
+Attach: filename [description]
- 5.6. attach
+ where _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be is the file to attach and _\bd_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn is an optional
+ string to use as the description of the attached file.
- 5.7. compose
+ When replying to messages, if you remove the _\bI_\bn_\b-_\bR_\be_\bp_\bl_\by_\b-_\bT_\bo_\b: field from
+ the header field, Mutt-ng will not generate a _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\bs_\b: field, which
+ allows you to create a new message thread.
- 5.8. postpone
+ Also see the $\b$e\bed\bdi\bit\bt_\b_h\bhe\bea\bad\bde\ber\brs\bs and $\b$e\bed\bdi\bit\bto\bor\br_\b_h\bhe\bea\bad\bde\ber\brs\bs 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 $\b$p\bpg\bgp\bp_\b_s\bsi\big\bgn\bn_\b_a\bas\bs 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
+ $\b$p\bpg\bgp\bp_\b_e\ben\bnt\btr\bry\by_\b_f\bfo\bor\brm\bma\bat\bt) 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
+ _\bT_\ba_\bb_\bl_\be_\b _\b2_\b._\b1_\b0_\b._\b _\bP_\bG_\bP_\b _\bK_\be_\by_\b _\bM_\be_\bn_\bu_\b _\bF_\bl_\ba_\bg_\bs
+ 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 (_\b- )means that the key
+ cannot be used for encryption. A dot (_\b. )means that it's marked as a
+ signature key in one of the user IDs, but may also be used for
+ encryption. The letter _\be indicates that this key can be used for
+ encryption.
+
+ The second character indicates the key's signing capabilities. Once
+ again, a ``_\b-'' implies ``not for signing'', ``_\b.'' implies that the key
+ is marked as an encryption key in one of the user-ids, and ``_\bs''
+ 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 (_\b?) indicates undefined validity, a minus
+ character (_\b-) marks an untrusted association, a space character means
+ a partially trusted association, and a plus character (_\b+ ) 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
+ $\b$m\bmi\bix\bx_\b_e\ben\bnt\btr\bry\by_\b_f\bfo\bor\brm\bma\bat\bt). 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
+ _\bb_\bo_\bu_\bn_\bc_\bi_\bn_\bg: 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 _\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\b-_\bm_\be_\bs_\bs_\ba_\bg_\be function is used
+ in the _\bc_\bo_\bm_\bp_\bo_\bs_\be menu, the body of your message and attachments are
+ stored in the mailbox specified by the $\b$p\bpo\bos\bst\btp\bpo\bon\bne\bed\bd 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 _\bc_\bo_\bm_\bp_\bo_\bs_\be a
+ new message from the _\bi_\bn_\bd_\be_\bx or _\bp_\ba_\bg_\be_\br you will be prompted if postponed
+ messages exist. If multiple messages are currently postponed, the
+ _\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd menu will pop up and you can select which message you would
+ like to resume.
- 7.9. Reference: Default Attachment Menu Function Bindings
+ _\bN_\bo_\bt_\be_\b: 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 $\b$p\bpo\bos\bst\btp\bpo\bon\bne\be quad-option.
- 7.11. Reference: Default Postpone Menu Function Bindings
+Chapter 3. Configuration
- 7.12. Reference: Default Browser Menu Function Bindings
+ _\bT_\ba_\bb_\bl_\be_\b _\bo_\bf_\b _\bC_\bo_\bn_\bt_\be_\bn_\bt_\bs
+
+ 1\b1.\b. \b L\bLo\boc\bca\bat\bti\bio\bon\bns\bs \b o\bof\bf \b C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b F\bFi\bil\ble\bes\bs
+ 2\b2.\b. \b B\bBa\bas\bsi\bic\bc \b S\bSy\byn\bnt\bta\bax\bx \b o\bof\bf \b I\bIn\bni\bit\bti\bia\bal\bli\biz\bza\bat\bti\bio\bon\bn \b F\bFi\bil\ble\bes\bs
+ 3\b3.\b. \b E\bEx\bxp\bpa\ban\bns\bsi\bio\bon\bn \b w\bwi\bit\bth\bhi\bin\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+
+ 3\b3.\b.1\b1.\b. \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs'\b' \b O\bOu\but\btp\bpu\but\bt
+ 3\b3.\b.2\b2.\b. \b E\bEn\bnv\bvi\bir\bro\bon\bnm\bme\ben\bnt\bt \b V\bVa\bar\bri\bia\bab\bbl\ble\bes\bs
+ 3\b3.\b.3\b3.\b. \b C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b V\bVa\bar\bri\bia\bab\bbl\ble\bes\bs
+ 3\b3.\b.4\b4.\b. \b S\bSe\bel\blf\bf-\b-D\bDe\bef\bfi\bin\bne\bed\bd \b V\bVa\bar\bri\bia\bab\bbl\ble\bes\bs
+ 3\b3.\b.5\b5.\b. \b P\bPr\bre\be-\b-D\bDe\bef\bfi\bin\bne\bed\bd \b V\bVa\bar\bri\bia\bab\bbl\ble\bes\bs
+ 3\b3.\b.6\b6.\b. \b T\bTy\byp\bpe\be \b C\bCo\bon\bnv\bve\ber\brs\bsi\bio\bon\bns\bs
+
+ 4\b4.\b. \b D\bDe\bef\bfi\bin\bni\bin\bng\bg/\b/U\bUs\bsi\bin\bng\bg \b a\bal\bli\bia\bas\bse\bes\bs
+ 5\b5.\b. \b C\bCh\bha\ban\bng\bgi\bin\bng\bg \b t\bth\bhe\be \b d\bde\bef\bfa\bau\bul\blt\bt \b k\bke\bey\by \b b\bbi\bin\bnd\bdi\bin\bng\bgs\bs
+ 6\b6.\b. \b D\bDe\bef\bfi\bin\bni\bin\bng\bg \b a\bal\bli\bia\bas\bse\bes\bs \b f\bfo\bor\br \b c\bch\bha\bar\bra\bac\bct\bte\ber\br \b s\bse\bet\bts\bs
+ 7\b7.\b. \b S\bSe\bet\btt\bti\bin\bng\bg \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs \b b\bba\bas\bse\bed\bd \b u\bup\bpo\bon\bn \b m\bma\bai\bil\blb\bbo\box\bx
+ 8\b8.\b. \b K\bKe\bey\byb\bbo\boa\bar\brd\bd \b m\bma\bac\bcr\bro\bos\bs
+ 9\b9.\b. \b U\bUs\bsi\bin\bng\bg \b c\bco\bol\blo\bor\br \b a\ban\bnd\bd \b m\bmo\bon\bno\bo \b v\bvi\bid\bde\beo\bo \b a\bat\btt\btr\bri\bib\bbu\but\bte\bes\bs
+ 1\b10\b0.\b. \b I\bIg\bgn\bno\bor\bri\bin\bng\bg \b (\b(w\bwe\bee\bed\bdi\bin\bng\bg)\b) \b u\bun\bnw\bwa\ban\bnt\bte\bed\bd \b m\bme\bes\bss\bsa\bag\bge\be \b h\bhe\bea\bad\bde\ber\brs\bs
+ 1\b11\b1.\b. \b A\bAl\blt\bte\ber\brn\bna\bat\bti\biv\bve\be \b a\bad\bdd\bdr\bre\bes\bss\bse\bes\bs
+ 1\b12\b2.\b. \b F\bFo\bor\brm\bma\bat\bt \b =\b= \b F\bFl\blo\bow\bwe\bed\bd
+
+ 1\b12\b2.\b.1\b1.\b. \b I\bIn\bnt\btr\bro\bod\bdu\buc\bct\bti\bio\bon\bn
+ 1\b12\b2.\b.2\b2.\b. \b R\bRe\bec\bce\bei\biv\bvi\bin\bng\bg:\b: \b D\bDi\bis\bsp\bpl\bla\bay\by \b S\bSe\bet\btu\bup\bp
+ 1\b12\b2.\b.3\b3.\b. \b S\bSe\ben\bnd\bdi\bin\bng\bg
+ 1\b12\b2.\b.4\b4.\b. \b A\bAd\bdd\bdi\bit\bti\bio\bon\bna\bal\bl \b N\bNo\bot\bte\bes\bs
+
+ 1\b13\b3.\b. \b M\bMa\bai\bil\bli\bin\bng\bg \b l\bli\bis\bst\bts\bs
+ 1\b14\b4.\b. \b U\bUs\bsi\bin\bng\bg \b M\bMu\bul\blt\bti\bip\bpl\ble\be \b s\bsp\bpo\boo\bol\bl \b m\bma\bai\bil\blb\bbo\box\bxe\bes\bs
+ 1\b15\b5.\b. \b D\bDe\bef\bfi\bin\bni\bin\bng\bg \b m\bma\bai\bil\blb\bbo\box\bxe\bes\bs \b w\bwh\bhi\bic\bch\bh \b r\bre\bec\bce\bei\biv\bve\be \b m\bma\bai\bil\bl
+ 1\b16\b6.\b. \b U\bUs\bse\ber\br \b d\bde\bef\bfi\bin\bne\bed\bd \b h\bhe\bea\bad\bde\ber\brs\bs
+ 1\b17\b7.\b. \b D\bDe\bef\bfi\bin\bni\bin\bng\bg \b t\bth\bhe\be \b o\bor\brd\bde\ber\br \b o\bof\bf \b h\bhe\bea\bad\bde\ber\brs\bs \b w\bwh\bhe\ben\bn \b v\bvi\bie\bew\bwi\bin\bng\bg \b m\bme\bes\bss\bsa\bag\bge\bes\bs
+ 1\b18\b8.\b. \b S\bSp\bpe\bec\bci\bif\bfy\by \b d\bde\bef\bfa\bau\bul\blt\bt \b s\bsa\bav\bve\be \b f\bfi\bil\ble\ben\bna\bam\bme\be
+ 1\b19\b9.\b. \b S\bSp\bpe\bec\bci\bif\bfy\by \b d\bde\bef\bfa\bau\bul\blt\bt \b F\bFc\bcc\bc:\b: \b m\bma\bai\bil\blb\bbo\box\bx \b w\bwh\bhe\ben\bn \b c\bco\bom\bmp\bpo\bos\bsi\bin\bng\bg
+ 2\b20\b0.\b. \b S\bSp\bpe\bec\bci\bif\bfy\by \b d\bde\bef\bfa\bau\bul\blt\bt \b s\bsa\bav\bve\be \b f\bfi\bil\ble\ben\bna\bam\bme\be \b a\ban\bnd\bd \b d\bde\bef\bfa\bau\bul\blt\bt \b F\bFc\bcc\bc:\b: \b m\bma\bai\bil\blb\bbo\box\bx \b a\bat\bt \b o\bon\bnc\bce\be
+ 2\b21\b1.\b. \b C\bCh\bha\ban\bng\bge\be \b s\bse\bet\btt\bti\bin\bng\bgs\bs \b b\bba\bas\bse\bed\bd \b u\bup\bpo\bon\bn \b m\bme\bes\bss\bsa\bag\bge\be \b r\bre\bec\bci\bip\bpi\bie\ben\bnt\bts\bs
+ 2\b22\b2.\b. \b C\bCh\bha\ban\bng\bge\be \b s\bse\bet\btt\bti\bin\bng\bgs\bs \b b\bbe\bef\bfo\bor\bre\be \b f\bfo\bor\brm\bma\bat\btt\bti\bin\bng\bg \b a\ba \b m\bme\bes\bss\bsa\bag\bge\be
+ 2\b23\b3.\b. \b C\bCh\bho\boo\bos\bsi\bin\bng\bg \b t\bth\bhe\be \b c\bcr\bry\byp\bpt\bto\bog\bgr\bra\bap\bph\bhi\bic\bc \b k\bke\bey\by \b o\bof\bf \b t\bth\bhe\be \b r\bre\bec\bci\bip\bpi\bie\ben\bnt\bt
+ 2\b24\b4.\b. \b A\bAd\bdd\bdi\bin\bng\bg \b k\bke\bey\by \b s\bse\beq\bqu\bue\ben\bnc\bce\bes\bs \b t\bto\bo \b t\bth\bhe\be \b k\bke\bey\byb\bbo\boa\bar\brd\bd \b b\bbu\buf\bff\bfe\ber\br
+ 2\b25\b5.\b. \b E\bEx\bxe\bec\bcu\but\bti\bin\bng\bg \b f\bfu\bun\bnc\bct\bti\bio\bon\bns\bs
+ 2\b26\b6.\b. \b M\bMe\bes\bss\bsa\bag\bge\be \b S\bSc\bco\bor\bri\bin\bng\bg
+ 2\b27\b7.\b. \b S\bSp\bpa\bam\bm \b d\bde\bet\bte\bec\bct\bti\bio\bon\bn
+ 2\b28\b8.\b. \b S\bSe\bet\btt\bti\bin\bng\bg \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ 2\b29\b9.\b. \b R\bRe\bea\bad\bdi\bin\bng\bg \b i\bin\bni\bit\bti\bia\bal\bli\biz\bza\bat\bti\bio\bon\bn \b c\bco\bom\bmm\bma\ban\bnd\bds\bs \b f\bfr\bro\bom\bm \b a\ban\bno\bot\bth\bhe\ber\br \b f\bfi\bil\ble\be
+ 3\b30\b0.\b. \b R\bRe\bem\bmo\bov\bvi\bin\bng\bg \b h\bho\boo\bok\bks\bs
+ 3\b31\b1.\b. \b S\bSh\bha\bar\bri\bin\bng\bg \b S\bSe\bet\btu\bup\bps\bs
+
+ 3\b31\b1.\b.1\b1.\b. \b C\bCh\bha\bar\bra\bac\bct\bte\ber\br \b S\bSe\bet\bts\bs
+ 3\b31\b1.\b.2\b2.\b. \b M\bMo\bod\bdu\bul\bla\bar\bri\biz\bza\bat\bti\bio\bon\bn
+ 3\b31\b1.\b.3\b3.\b. \b C\bCo\bon\bnd\bdi\bit\bti\bio\bon\bna\bal\bl \b p\bpa\bar\brt\bts\bs
+
+ 3\b32\b2.\b. \b O\bOb\bbs\bso\bol\ble\bet\bte\be \b V\bVa\bar\bri\bia\bab\bbl\ble\bes\bs
- 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\bco\bom\bmm\bma\ban\bnd\bdl\bli\bin\bne\be 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\bco\bom\bmm\bma\ban\bnd\bds\bs 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\bco\bom\bmm\bma\ban\bnd\bds\bs. 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 _\bn_\bo_\bt 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\bco\bom\bmm\bma\ban\bnd\bds\bs.
-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
+set record=+sent_on_$HOSTNAME
- So far, there are no official releases of Mutt-ng, but you can download
- daily snapshots from <http://mutt-ng.berlios.de/snapshots/>
+ sets the $\b$r\bre\bec\bco\bor\brd\bd variable to the string _\b+_\bs_\be_\bn_\bt_\b__\bo_\bn_\b_ and appends the
+ value of the evironment variable $HOSTNAME.
-5. IRC
+ _\bN_\bo_\bt_\be_\b: There will be no warning if an environment variable is not
+ defined. The result will of the expansion will then be empty.
- Visit channel #muttng on irc.freenode.net (www.freenode.net) to chat with
- other people interested in Mutt-ng.
+3.3. Configuration Variables
-6. Weblog
+ As for environment variables, the values of all configuration
+ variables as string can be used in the same way, too. For example,
- 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.
+set imap_home_namespace = $folder
-7. Copyright
+ would set the value of $\b$i\bim\bma\bap\bp_\b_h\bho\bom\bme\be_\b_n\bna\bam\bme\bes\bsp\bpa\bac\bce\be to the value to which
+ $\b$f\bfo\bol\bld\bde\ber\br is _\bc_\bu_\br_\br_\be_\bn_\bt_\bl_\by set to.
- Mutt is Copyright (C) 1996-2000 Michael R. Elkins <me@cs.hmc.edu> and
- others
+ _\bN_\bo_\bt_\be_\b: There're no logical links established in such cases so that the
+ the value for $\b$i\bim\bma\bap\bp_\b_h\bho\bom\bme\be_\b_n\bna\bam\bme\bes\bsp\bpa\bac\bce\be won't change even if $\b$f\bfo\bol\bld\bde\ber\br gets
+ changed.
- 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.
+ _\bN_\bo_\bt_\be_\b: 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.
- 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.
+3.4. Self-Defined Variables
- 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.
+ 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.
-8. Manual Conventions
+ For example, to view the manual, users can either define two macros
+ like the following
- This manual contains several (hopefully consistent) conventions to
- specially layout different items in different fashions.
+macro generic <F1> "!less -r /path/to/manual" "Show manual"
+macro pager <F1> "!less -r /path/to/manual" "Show manual"
- 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.
+ for generic, pager and index .The alternative is to define a custom
+ variable like so:
- o Muttng-specific functions are enclosed in <> and printed in a
- typewriter font, too, as in <sync-mailbox>.
+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"
- 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.
+ to re-use the command sequence as in:
- 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.
+macro index <F2> "$user_manualcmd | grep '\^[ ]\\+~. '" "Show Patterns"
- 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.
+ 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.
-Chapter 2. Getting Started
+ 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.
- Table of Contents
+ The complete removal is done via the unset keyword.
- 1. Basic Concepts
+ After the following sequence:
- 1.1. Screens and Menus
+set user_foo = 42
+set user_foo = 666
- 1.2. Configuration
+ the variable $user_foo has a current value of 666 and an initial of
+ 42. The query
- 1.3. Functions
+set ?user_foo
- 1.4. Interaction
+ will show 666. After doing the reset via
- 1.5. Modularization
+reset user_foo
- 1.6. Patterns
+ a following query will give 42 as the result. After unsetting it via
- 2. Screens and Menus
+unset user_foo
- 2.1. Index
+ any query or operation (except the noted expansion within other
+ statements) will lead to an error message.
- 2.2. Pager
+3.5. Pre-Defined Variables
- 2.3. File Browser
+ 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.
- 2.4. Sidebar
+ _\bP_\bl_\be_\ba_\bs_\be_\b _\bc_\bo_\bn_\bs_\bu_\bl_\bt_\b _\bt_\bh_\be_\b _\bl_\bo_\bc_\ba_\bl_\b _\bc_\bo_\bp_\by_\b _\bo_\bf_\b _\by_\bo_\bu_\br_\b _\bm_\ba_\bn_\bu_\ba_\bl_\b _\bf_\bo_\br_\b _\bt_\bh_\be_\bi_\br_\b _\bv_\ba_\bl_\bu_\be_\bs_\b _\ba_\bs_\b _\bt_\bh_\be_\by
+ _\bm_\ba_\by_\b _\bd_\bi_\bf_\bf_\be_\br_\b _\bf_\br_\bo_\bm_\b _\bd_\bi_\bf_\bf_\be_\br_\be_\bn_\bt_\b _\bm_\ba_\bn_\bu_\ba_\bl_\b _\bs_\bo_\bu_\br_\bc_\be_\bs_\b. Where the manual is
+ installed in can be queried (already using such a variable) by
+ running:
- 2.5. Help
+$ muttng -Q muttng_docdir
- 2.6. Compose Menu
+ 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:
- 2.7. Alias Menu
+set user_manualcmd = '!less -r /path/to_manual'
- 2.8. Attachment Menu
+ to:
- 2.9. Key Menu
+set user_manualcmd = "!less -r $muttng_docdir/manual.txt"
- 3. Moving Around in Menus
+ which works everywhere if a manual is installed.
- 4. Editing Input Fields
+ 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.
- 5. Reading Mail - The Index and Pager
+ For example, the statement
- 5.1. The Message Index
+folder-hook . "set user_current_folder = $muttng_folder_name"
- 5.2. The Pager
+ will be already be translated to the following when reading the
+ startup files:
- 5.3. Threaded Mode
+folder-hook . "set user_current_folder = some_folder"
- 5.4. Miscellaneous Functions
+ with some_folder being the name of the first folder muttng opens. On
+ the contrary,
- 6. Sending Mail
+folder-hook . 'set user_current_folder = $muttng_folder_name'
- 6.1. Composing new messages
+ 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.
- 6.2. Replying
+ A more practical example is:
- 6.3. Editing the message header
+folder-hook . 'source ~/.mutt/score-$muttng_folder_name'
- 6.4. Using Mutt-ng with PGP
+ which can be used to source files containing score commands depending
+ on the folder the user enters.
- 6.5. Sending anonymous messages via mixmaster
+3.6. Type Conversions
- 7. Forwarding and Bouncing Mail
+ 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
- 8. Postponing Mail
+4. Defining/Using aliases
-1. Basic Concepts
+ Usage: alias_\bk_\be_\by_\b _\ba_\bd_\bd_\br_\be_\bs_\bs_\b _\b[_\b,_\b _\ba_\bd_\bd_\br_\be_\bs_\bs_\b,_\b._\b._\b._\b]
- 1.1. Screens and Menus
+ 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.
- mutt-ng offers different screens of which every has its special purpose:
+ _\bN_\bo_\bt_\be_\b: if you want to create an alias for a group (by specifying more
+ than one address), you _\bm_\bu_\bs_\bt separate the addresses with a comma
+ (``,'').
- o The index displays the contents of the currently opened mailbox.
+ To remove an alias or aliases (``*'' means all aliases):
- o The pager is responsible for displaying messages, that is, the header,
- the body and all attached parts.
+ Usage: unalias_\b[_\b*_\b _\b|_\b _\bk_\be_\by_\b _\b._\b._\b._\b _\b]
- o The file browser offers operations on and displays information of all
- folders mutt-ng should watch for mail.
+alias muttdude me@cs.hmc.edu (Michael Elkins)
+alias theguys manny, moe, jack
- o The sidebar offers a permanent view of which mailboxes contain how
- many total, new and/or flagged mails.
+ 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\bso\bou\bur\brc\bce\be. Consequently, you
+ can have multiple alias files, or you can have all aliases defined in
+ your muttrc.
- o The help screen lists for all currently available commands how to
- invoke them as well as a short description.
+ On the other hand, the <create-alias> function can use only one file,
+ the one pointed to by the $\b$a\bal\bli\bia\bas\bs_\b_f\bfi\bil\ble\be 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\bso\bou\bur\brc\bce\be this file too.
- o The compose menu is a comfortable interface take last actions before
- sending mail: change subjects, attach files, remove attachements, etc.
+ For example:
- o The attachement menu gives a summary and the tree structure of the
- attachements of the current message.
+source /usr/local/share/Mutt-ng.aliases
+source ~/.mail_aliases
+set alias_file=~/.mail_aliases
- o The alias menu lists all or a fraction of the aliases a user has
- defined.
+ To use aliases, you merely use the alias at any place in mutt where
+ muttprompts for addresses, such as the _\bT_\bo_\b: or _\bC_\bc_\b: prompt. You can also
+ enter aliases in your editor at the appropriate headers if you have
+ the $\b$e\bed\bdi\bit\bto\bor\br_\b_h\bhe\bea\bad\bde\ber\brs\bs variable set.
- o The key menu used in connection with encryption lets users choose the
- right key to encrypt with.
+ 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.
- When mutt-ng is started without any further options, it'll open the users
- default mailbox and display the index.
+ In the alias menu, you can select as many aliases as you want with the
+ _\bs_\be_\bl_\be_\bc_\bt_\b-_\be_\bn_\bt_\br_\by key (default: RET), and use the _\be_\bx_\bi_\bt key (default: q) to
+ return to the address prompt.
- 1.2. Configuration
+5. Changing the default key bindings
- 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.)
+ Usage: bind_\bm_\ba_\bp_\b _\bk_\be_\by_\b _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn
- Mutt-ng is configured using configuration files which allow users to add
- comments or manage them via version control systems to ease maintenance.
+ This command allows you to change the default key bindings (operation
+ invoked when pressing a key).
- 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.
+ _\bm_\ba_\bp 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:
- 1.3. Functions
+ 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.
- 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.
+ 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).
- 1.4. Interaction
+ attach
+ The attachment menu is used to access the attachments on
+ received messages.
- Mutt-ng has two basic concepts of user interaction:
+ browser
+ The browser is used for both browsing the local directory
+ structure, and for listing all of your incoming mailboxes.
- 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.
+ editor
+ The editor is the line-based editor the user enters text data.
- 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.
+ index
+ The index is the list of messages contained in a mailbox.
- 1.5. Modularization
+ compose
+ The compose menu is the screen used when sending a new message.
- 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.
+ pager
+ The pager is the mode used to display message/attachment data,
+ and help listings.
- 1.6. Patterns
+ pgp
+ The pgp menu is used to select the OpenPGP keys used for
+ encrypting outgoing messages.
- 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.
+ 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.
-2. Screens and Menus
+ _\bk_\be_\by is the key (or key sequence) you wish to bind. To specify a
+ control character, use the sequence _\b\_\bC_\bx, where _\bx is the letter of the
+ control character (for example, to specify control-A use ``\Ca'').
+ Note that the case of _\bx as well as _\b\_\bC is ignored, so that _\b\_\bC_\bA, _\b\_\bC_\ba,
+ _\b\_\bc_\bA and _\b\_\bc_\ba are all equivalent. An alternative form is to specify the
+ key as a three digit octal number prefixed with a ``\'' (for example
+ _\b\_\b1_\b7_\b7 is equivalent to _\b\_\bc_\b?).
- 2.1. Index
+ In addition, _\bk_\be_\by may consist of:
- 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.
+ _\bT_\ba_\bb_\bl_\be_\b _\b3_\b._\b1_\b._\b _\bA_\bl_\bt_\be_\br_\bn_\ba_\bt_\bi_\bv_\be_\b _\bK_\be_\by_\b _\bN_\ba_\bm_\be_\bs
+ 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
- 2.2. Pager
+ _\bk_\be_\by does not need to be enclosed in quotes unless it contains a space
+ (`` '').
- 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.
+ _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn specifies which action to take when _\bk_\be_\by is pressed. For a
+ complete list of functions, see the f\bfu\bun\bnc\bct\bti\bio\bon\bns\bs. The special function
+ noop unbinds the specified key sequence.
- 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
+6. Defining aliases for character sets
- FIXME
+ Usage: c\bch\bha\bar\brs\bse\bet\bt-\b-h\bho\boo\bok\bk_\ba_\bl_\bi_\ba_\bs_\bc_\bh_\ba_\br_\bs_\be_\bt
-3. Moving Around in Menus
+ Usage: i\bic\bco\bon\bnv\bv-\b-h\bho\boo\bok\bk_\bc_\bh_\ba_\br_\bs_\be_\bt_\bl_\bo_\bc_\ba_\bl_\b-_\bc_\bh_\ba_\br_\bs_\be_\bt
- Information is presented in menus, very similar to ELM. Here is a
- tableshowing the common keys used to navigate menus in Mutt-ng.
+ The c\bch\bha\bar\brs\bse\bet\bt-\b-h\bho\boo\bok\bk 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.
- Table 2.1. Most commonly used movement bindings
+ The i\bic\bco\bon\bnv\bv-\b-h\bho\boo\bok\bk 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.
- 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
+7. Setting variables based upon mailbox
-4. Editing Input Fields
+ Usage: f\bfo\bol\bld\bde\ber\br-\b-h\bho\boo\bok\bk [!]_\br_\be_\bg_\be_\bx_\bp_\bc_\bo_\bm_\bm_\ba_\bn_\bd
- 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.
+ It is often desirable to change settings based on which mailbox you
+ are reading. The f\bfo\bol\bld\bde\ber\br-\b-h\bho\boo\bok\bk command provides a method by which you
+ can execute any configuration command. _\br_\be_\bg_\be_\bx_\bp is a regular expression
+ specifying in which mailboxes to execute _\bc_\bo_\bm_\bm_\ba_\bn_\bd before loading. If a
+ mailbox matches multiple f\bfo\bol\bld\bde\ber\br-\b-h\bho\boo\bok\bk's, they are executed in the order
+ given in the muttrc.
- Table 2.2. Line Editor Functions
+ _\bN_\bo_\bt_\be_\b: if you use the ``!'' shortcut for $\b$s\bsp\bpo\boo\bol\blf\bfi\bil\ble\be at the beginning of
+ the pattern, you must place it inside of double or single quotes in
+ order to distinguish it from the logical _\bn_\bo_\bt operator for the
+ expression.
- 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
+ Note that the settings are _\bn_\bo_\bt restored when you leave the mailbox.
+ For example, a command action to perform is to change the sorting
+ methodbased upon the mailbox being read:
- 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
+folder-hook mutt set sort=threads
- bind editor <delete> backspace
+ However, the sorting method is not restored to its previous value when
+ reading a different mailbox. To specify a _\bd_\be_\bf_\ba_\bu_\bl_\bt command, use the
+ pattern ``.'':
-5. Reading Mail - The Index and Pager
+folder-hook . set sort=date-sent
- 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.''
+8. Keyboard macros
- The next few sections describe the functions provided in each of these
- modes.
+ Usage: macro_\bm_\be_\bn_\bu_\b _\bk_\be_\by_\b _\bs_\be_\bq_\bu_\be_\bn_\bc_\be_\b _\b[_\bd_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn_\b]
- 5.1. The Message Index
+ Macros are useful when you would like a single key to perform a series
+ of actions. When you press _\bk_\be_\by in menu _\bm_\be_\bn_\bu ,Mutt-ng will behave as if
+ you had typed _\bs_\be_\bq_\bu_\be_\bn_\bc_\be. So if you have a common sequence of commands
+ you type, you can create a macro to execute those commands with a
+ singlekey.
- Table 2.3. Most commonly used Index Bindings
+ _\bm_\be_\bn_\bu is the m\bma\bap\bps\bs 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 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
+ _\bk_\be_\by and _\bs_\be_\bq_\bu_\be_\bn_\bc_\be are expanded by the same rules as the b\bbi\bin\bnd\bd. There are
+ some additions however. The first is that control characters in
+ _\bs_\be_\bq_\bu_\be_\bn_\bc_\be 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 _\bu_\bp or to invoke a function directly, you can use the format _\b<_\bk_\be_\by
+ _\bn_\ba_\bm_\be_\b> and _\b<_\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\b _\bn_\ba_\bm_\be_\b> .For a listing of key names see the section
+ on b\bbi\bin\bnd\bd. Functions are listed in the f\bfu\bun\bnc\bct\bti\bio\bon\bns\bs.
- 5.1.1. Status Flags
+ 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).
- 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:
+ Optionally you can specify a descriptive text after _\bs_\be_\bq_\bu_\be_\bn_\bc_\be, which is
+ shown in the help screens.
- D
+ _\bN_\bo_\bt_\be_\b: Macro definitions (if any) listed in the help screen(s), are
+ silently truncated at the screen width, and are not wrapped.
- message is deleted (is marked for deletion)
+9. Using color and mono video attributes
- d
+ Usage: color_\bo_\bb_\bj_\be_\bc_\bt_\b _\bf_\bo_\br_\be_\bg_\br_\bo_\bu_\bn_\bd_\b _\bb_\ba_\bc_\bk_\bg_\br_\bo_\bu_\bn_\bd_\b _\b[_\br_\be_\bg_\be_\bx_\bp_\b]
+
+ Usage: color_\bi_\bn_\bd_\be_\bx_\b _\bf_\bo_\br_\be_\bg_\br_\bo_\bu_\bn_\bd_\b _\bp_\ba_\bt_\bt_\be_\br_\bn
+
+ Usage: uncolor_\bi_\bn_\bd_\be_\bx_\b _\bp_\ba_\bt_\bt_\be_\br_\bn_\b _\b[_\bp_\ba_\bt_\bt_\be_\br_\bn_\b _\b._\b._\b._\b]
+
+ 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 _\ba_\bn_\bd a
+ background color (it is not possible to only specify one or the
+ other).
+
+ _\bo_\bb_\bj_\be_\bc_\bt can be one of:
+
+ * attachment
+ * body (match _\br_\be_\bg_\be_\bx_\bp in the body of messages)
+ * bold (highlighting bold patterns in the body of messages)
+ * error (error messages printed by Mutt-ng)
+ * header (match _\br_\be_\bg_\be_\bx_\bp in the message header)
+ * hdrdefault (default color of the message header in the pager)
+ * index (match _\bp_\ba_\bt_\bt_\be_\br_\bn 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 $\b$q\bqu\buo\bot\bte\be_\b_r\bre\beg\bge\bex\bxp\bp in the body of a message)
+ * quoted1, quoted2, ..., quoted_\bN (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)
+
+ _\bf_\bo_\br_\be_\bg_\br_\bo_\bu_\bn_\bd and _\bb_\ba_\bc_\bk_\bg_\br_\bo_\bu_\bn_\bd can be one of the following:
+
+ * white
+ * black
+ * green
+ * magenta
+ * blue
+ * cyan
+ * yellow
+ * red
+ * default
+ * color_\bx
+
+ _\bf_\bo_\br_\be_\bg_\br_\bo_\bu_\bn_\bd 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 _\bd_\be_\bf_\ba_\bu_\bl_\bt can be used
+ as a transparent color. The value _\bb_\br_\bi_\bg_\bh_\bt_\bd_\be_\bf_\ba_\bu_\bl_\bt is also valid. If
+ Mutt-ng is linked against the _\bS_\b-_\bL_\ba_\bn_\bg 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
+
+ _\bN_\bo_\bt_\be_\b: The _\bS_\b-_\bL_\ba_\bn_\bg library requires you to use the _\bl_\bi_\bg_\bh_\bt_\bg_\br_\ba_\by and _\bb_\br_\bo_\bw_\bn
+ keywords instead of _\bw_\bh_\bi_\bt_\be and _\by_\be_\bl_\bl_\bo_\bw when setting this variable.
+
+ _\bN_\bo_\bt_\be_\b: The uncolor command can be applied to the index object only. It
+ removes entries from the list. You _\bm_\bu_\bs_\bt 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 _\bc_\bo_\bl_\bo_\br_\b0, _\bc_\bo_\bl_\bo_\br_\b1 ,..., _\bc_\bo_\bl_\bo_\br_\bN_\b-_\b1 (_\bN
+ 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 _\bc_\bo_\bl_\bo_\br_\b2 for your xterm), since color names
+ may then lose their normal meaning.
- message have attachments marked for deletion
+ If your terminal does not support color, it is still possible change
+ the video attributes through the use of the ``mono'' command:
- K
+ Usage: mono_\bo_\bb_\bj_\be_\bc_\bt_\b _\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\be_\b _\b[_\br_\be_\bg_\be_\bx_\bp_\b]
- contains a PGP public key
+ Usage: mono_\bi_\bn_\bd_\be_\bx_\b _\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\be_\b _\bp_\ba_\bt_\bt_\be_\br_\bn
- N
+ Usage: unmono_\bi_\bn_\bd_\be_\bx_\b _\bp_\ba_\bt_\bt_\be_\br_\bn_\b _\b[_\bp_\ba_\bt_\bt_\be_\br_\bn_\b _\b._\b._\b._\b]
- message is new
+ where _\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\be is one of the following:
- O
+ * none
+ * bold
+ * underline
+ * reverse
+ * standout
- message is old
+10. Ignoring (weeding) unwanted message headers
- P
+ Usage: ignore_\bp_\ba_\bt_\bt_\be_\br_\bn_\b _\b[_\bp_\ba_\bt_\bt_\be_\br_\bn_\b _\b._\b._\b._\b]
- message is PGP encrypted
+ Usage: unignore_\bp_\ba_\bt_\bt_\be_\br_\bn_\b _\b[_\bp_\ba_\bt_\bt_\be_\br_\bn_\b _\b._\b._\b._\b]
- r
+ 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.
- message has been replied to
+ 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.
- S
+ 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''.
- message is signed, and the signature is succesfully verified
+ ``unignore *'' will remove all tokens from the ignore list.
- s
+ 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:
- message is signed
+11. Alternative addresses
- !
+ Usage: alternates_\br_\be_\bg_\be_\bx_\bp_\b _\b[_\br_\be_\bg_\be_\bx_\bp_\b _\b._\b._\b._\b]
- message is flagged
+ Usage: unalternates_\br_\be_\bg_\be_\bx_\bp_\b _\b[_\br_\be_\bg_\be_\bx_\bp_\b _\b._\b._\b._\b]
- *
+ 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 $\b$r\bre\bep\bpl\bly\by_\b_t\bto\bo.)
- message is tagged
+ 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.
- Some of the status flags can be turned on or off using
+ 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.
- o set-flag (default: w)
+ To remove a regular expression from the alternates list, use the
+ unalternates command with exactly the same _\br_\be_\bg_\be_\bx_\bp . Likewise, if the
+ _\br_\be_\bg_\be_\bx_\bp for a alternates command matches an entry on the unalternates
+ list, that unalternates entry will be removed. If the _\br_\be_\bg_\be_\bx_\bp for
+ unalternates is ``*'', _\ba_\bl_\bl_\b _\be_\bn_\bt_\br_\bi_\be_\bs on alternates will be removed.
- o clear-flag (default: W)
+12. Format = Flowed
- Furthermore, the following flags reflect who the message is addressed to.
- They can be customized with the $to_chars variable.
+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.
- message is to you and you only
+ For introductory information on format=flowed messages, see
+ <\b<h\bht\btt\btp\bp:\b:/\b//\b/w\bww\bww\bw.\b.j\bjo\boe\bec\bcl\bla\bar\brk\bk.\b.o\bor\brg\bg/\b/f\bff\bfa\baq\bq.\b.h\bht\btm\bml\bl>\b>.
- T
+12.2. Receiving: Display Setup
- message is to you, but also to or cc'ed to others
+ 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:
- C
+set wrapmargin = 10
- message is cc'ed to you
+ The code above makes the line break 10 columns before the right side
+ of the terminal.
- F
+ If your terminal is so wide that the lines are embarrassingly long,
+ you can also set a maximum line length:
- message is from you
+set max_line_length = 120
- L
+ The example above will give you lines not longer than 120 characters.
- message is sent to a subscribed mailing list
+ When you view at format=flowed messages, you will often see the
+ quoting hierarchy like in the following example:
- 5.2. The Pager
+>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.
- 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.
+ 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:
- Table 2.4. Most commonly used Pager Bindings
+set stuff_quoted
- 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
+ This will lead to a nicer result that is easier to read:
- 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)
+> 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.
- Table 2.6. ANSI Colors
+12.3. Sending
- Number Color
- 0 black
- 1 red
- 2 green
- 3 yellow
- 4 blue
- 5 magenta
- 6 cyan
- 7 white
+ If you want mutt-ng to send emails with format=flowed set, you need to
+ explicitly set it:
- 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.
+set text_flowed
- See also the $strict_threads variable.
+ 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 _\bf_\bo_\br_\bm_\ba_\bt_\b=_\bf_\bl_\bo_\bw_\be_\bd 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\bRf\bfC\bC \b 3\b36\b67\b76\b6) as it does not space-stuff lines
+ starting with:
+
+ * > This is _\bn_\bo_\bt the quote character but a right angle used for other
+ reasons
- 5.4. Miscellaneous Functions
+ Please make sure that you manually prepend a space to each of them.
- <create-alias> (default: a)
+12.4. Additional Notes
- 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.
+ For completeness, the $\b$d\bde\bel\ble\bet\bte\be_\b_s\bsp\bpa\bac\bce\be variable provides the mechanism to
+ generate a DelSp=yes parameter on _\bo_\bu_\bt_\bg_\bo_\bi_\bn_\bg 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 _\bw_\bi_\bt_\bh_\bo_\bu_\bt 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.
- <check-traditional-pgp> (default: E-P)
+13. Mailing lists
- 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.
+ Usage: lists_\br_\be_\bg_\be_\bx_\bp_\b _\b[_\br_\be_\bg_\be_\bx_\bp_\b _\b._\b._\b._\b]
- <display-toggle-weed> (default: h)
+ Usage: unlists_\br_\be_\bg_\be_\bx_\bp_\b _\b[_\br_\be_\bg_\be_\bx_\bp_\b _\b._\b._\b._\b]
- Toggles the weeding of message header fields specified by ignore commands.
+ Usage: subscribe_\br_\be_\bg_\be_\bx_\bp_\b _\b[_\br_\be_\bg_\be_\bx_\bp_\b _\b._\b._\b._\b]
- <edit> (default: e)
+ Usage: unsubscribe_\br_\be_\bg_\be_\bx_\bp_\b _\b[_\br_\be_\bg_\be_\bx_\bp_\b _\b._\b._\b._\b]
- 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.
+ Mutt-ng has a few nice features for u\bus\bsi\bin\bng\bg-\b-l\bli\bis\bst\bts\bs. 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\bli\bis\bst\bt-\b-r\bre\bep\bpl\bly\by 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
+ $\b$f\bfo\bol\bll\blo\bow\bwu\bup\bp_\b_t\bto\bo 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.
- <edit-type> (default: ) (default: C-E on the attachment menu, and in the
- pager and index menus; C-T on the compose menu)
+ 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 _\bm_\bu_\bt_\bt_\b-_\bu_\bs_\be_\br_\bs_\b@_\bm_\bu_\bt_\bt_\b._\bo_\br_\bg. 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
+ _\bm_\bu_\bt_\bt_\b-_\bu_\bs_\be_\br_\bs_\b@_\be_\bx_\ba_\bm_\bp_\bl_\be_\b._\bc_\bo_\bm, 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 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.
+14. Using Multiple spool mailboxes
- 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.
+ Usage: m\bmb\bbo\box\bx-\b-h\bho\boo\bok\bk [!]_\bp_\ba_\bt_\bt_\be_\br_\bn_\bm_\ba_\bi_\bl_\bb_\bo_\bx
- <enter-command> (default: :)
+ This command is used to move read messages from a specified mailbox to
+ adifferent mailbox automatically when you quit or change folders.
+ _\bp_\ba_\bt_\bt_\be_\br_\bn is a regular expression specifying the mailbox to treat as a
+ ``spool'' mailbox and _\bm_\ba_\bi_\bl_\bb_\bo_\bx specifies where mail should be saved
+ when read.
- 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.
+ Unlike some of the other _\bh_\bo_\bo_\bk commands, only the _\bf_\bi_\br_\bs_\bt matching
+ pattern is used (it is not possible to save read mail in more than a
+ single mailbox).
- <extract-keys> (default: C-K)
+15. Defining mailboxes which receive mail
- This command extracts PGP public keys from the current or tagged
- message(s) and adds them to your PGP public key ring.
+ Usage: mailboxes_\b[_\b!_\b]_\bf_\bi_\bl_\be_\bn_\ba_\bm_\be_\b _\b[_\bf_\bi_\bl_\be_\bn_\ba_\bm_\be_\b _\b._\b._\b._\b _\b]
- <forget-passphrase> (default: C-F)
+ Usage: unmailboxes_\b[_\b!_\b]_\bf_\bi_\bl_\be_\bn_\ba_\bm_\be_\b _\b[_\bf_\bi_\bl_\be_\bn_\ba_\bm_\be_\b _\b._\b._\b._\b _\b]
- This command wipes the passphrase(s) from memory. It is useful, if you
- misspelled the passphrase.
+ 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.
- <list-reply> (default: L)
+ When changing folders, pressing _\bs_\bp_\ba_\bc_\be will cycle through folders with
+ new mail.
- 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.
+ 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.
- <pipe-message> (default: )
+ The ``unmailboxes'' command is used to remove a token from the list of
+ folders which receive mail. Use ``unmailboxes *'' to remove all
+ tokens.
+
+ _\bN_\bo_\bt_\be_\b: 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.
+
+ _\bN_\bo_\bt_\be_\b: the filenames in the mailboxes command are resolved when the
+ command is executed, so if these names contain s\bsh\bho\bor\brt\btc\bcu\but\bts\bs (such as
+ ``='' and ``!''), any variable definition that affect these characters
+ (like $\b$f\bfo\bol\bld\bde\ber\br and $\b$s\bsp\bpo\boo\bol\blf\bfi\bil\ble\be) should be executed before the mailboxes
+ command.
- 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.
+16. User defined headers
- <resend-message> (default: E-e)
+ Usage: my_hdr_\bs_\bt_\br_\bi_\bn_\bg
- 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.
+ Usage: unmy_hdr_\bf_\bi_\be_\bl_\bd_\b _\b[_\bf_\bi_\be_\bl_\bd_\b _\b._\b._\b._\b]
- 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.
+ The ``my_hdr'' command allows you to create your own header fields
+ which will be added to every message you send.
- <shell-escape> (default: !)
+ For example, if you would like to add an ``Organization:'' header
+ field to all of your outgoing messages, you can put the command
- 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.
+my_hdr Organization: A Really Big Company, Anytown, USA
- <toggle-quoted> (default: T)
+ in your .muttrc.
- 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.
+ _\bN_\bo_\bt_\be_\b: space characters are _\bn_\bo_\bt allowed between the keyword and the
+ colon (``:''). The standard for electronic mail (R\bRf\bfC\bC \b 8\b82\b22\b2) says that
+ space is illegal there, so Mutt-ng enforces the rule.
- <skip-quoted> (default: S)
+ If you would like to add a header field to a single message, you
+ should either set the $\b$e\bed\bdi\bit\bt_\b_h\bhe\bea\bad\bde\ber\brs\bs variable, or use the _\be_\bd_\bi_\bt_\b-_\bh_\be_\ba_\bd_\be_\br_\bs
+ function (default: ``E'') in the send-menu so that you can edit the
+ header of your message along with the body.
- This function will go to the next line of non-quoted text which come after
- a line of quoted text in the internal pager.
+ 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:
-6. Sending Mail
+unmy_hdr to cc
- The following bindings are available in the index for sending messages.
+17. Defining the order of headers when viewing messages
- Table 2.8. Most commonly used Mail Composition Bindings
+ Usage: hdr_order_\bh_\be_\ba_\bd_\be_\br_\b _\bh_\be_\ba_\bd_\be_\br_\b _\b[_\bh_\be_\ba_\bd_\be_\br_\b _\b._\b._\b._\b]
- 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
+ Usage: unhdr_order_\b[_\b _\b*_\b _\b|_\b _\bh_\be_\ba_\bd_\be_\br_\b _\bh_\be_\ba_\bd_\be_\br_\b _\b._\b._\b._\b]
- 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.
+ With this command, you can specify an order in which mutt will attempt
+ to present headers to you when viewing messages.
- 6.1. Composing new 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.
- 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:
+hdr_order From Date: From: To: Cc: Subject:
- To:
+18. Specify default save filename
- 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.
+ Usage: s\bsa\bav\bve\be-\b-h\bho\boo\bok\bk [!]_\bp_\ba_\bt_\bt_\be_\br_\bn_\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
- The editor that is called is selected in the following way: you can e.g.
- set it in the mutt-ng configuration:
+ This command is used to override the default filename used when saving
+ messages. _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be will be used as the default filename if the message
+ is _\bF_\br_\bo_\bm_\b: an address matching _\br_\be_\bg_\be_\bx_\bp or if you are the author and the
+ message is addressed _\bt_\bo_\b: something matching _\br_\be_\bg_\be_\bx_\bp .
- set editor = "vim +/^$/ -c ':set tw=72'"
- set editor = "nano"
- set editor = "emacs"
+ See p\bpa\bat\btt\bte\ber\brn\bn-\b-h\bho\boo\bok\bk for information on the exact format of _\bp_\ba_\bt_\bt_\be_\br_\bn.
- 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
+ Examples:
- Once you have finished editing the body of your mail message, you are
- returned to the compose menu. The following options are available:
+save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
+save-hook aol\\.com$ +spam
- Table 2.9. Most commonly used Compose Menu Bindings
+ Also see the f\bfc\bcc\bc-\b-s\bsa\bav\bve\be-\b-h\bho\boo\bok\bk command.
- 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
+19. Specify default Fcc: mailbox when composing
- 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.
+ Usage: f\bfc\bcc\bc-\b-h\bho\boo\bok\bk [!]_\bp_\ba_\bt_\bt_\be_\br_\bn_\bm_\ba_\bi_\bl_\bb_\bo_\bx
- 6.2. Replying
+ This command is used to save outgoing mail in a mailbox other than
+ $\b$r\bre\bec\bco\bor\brd\bd. Mutt-ng searches the initial list of message recipients for
+ the first matching _\br_\be_\bg_\be_\bx_\bp and uses _\bm_\ba_\bi_\bl_\bb_\bo_\bx as the default Fcc:
+ mailbox. If no match is found the message will be saved to $\b$r\bre\bec\bco\bor\brd\bd
+ mailbox.
- 6.2.1. Simple Replies
+ See p\bpa\bat\btt\bte\ber\brn\bn-\b-h\bho\boo\bok\bk for information on the exact format of _\bp_\ba_\bt_\bt_\be_\br_\bn.
- 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.
+ Example:
- 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.
+fcc-hook [@.]aol\\.com$ +spammers
- 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 above will save a copy of all messages going to the aol.com domain
+ to the `+spammers' mailbox by default. Also see the f\bfc\bcc\bc-\b-s\bsa\bav\bve\be-\b-h\bho\boo\bok\bk
+ command.
- The quote attribution is configurable, by default it is set to
+20. Specify default save filename and default Fcc: mailbox at once
- set attribution = "On %d, %n wrote:"
+ Usage: f\bfc\bcc\bc-\b-s\bsa\bav\bve\be-\b-h\bho\boo\bok\bk [!]_\bp_\ba_\bt_\bt_\be_\br_\bn_\bm_\ba_\bi_\bl_\bb_\bo_\bx
- It can also be set to something more compact, e.g.
+ This command is a shortcut, equivalent to doing both a f\bfc\bcc\bc-\b-h\bho\boo\bok\bk and a
+ s\bsa\bav\bve\be-\b-h\bho\boo\bok\bk with its arguments.
- set attribution = "attribution="* %n <%a> [%(%y-%m-%d %H:%M)]:"
+21. Change settings based upon message recipients
- The example above results in the following attribution:
+ Usage: r\bre\bep\bpl\bly\by-\b-h\bho\boo\bok\bk [!]_\bp_\ba_\bt_\bt_\be_\br_\bn_\bc_\bo_\bm_\bm_\ba_\bn_\bd
- * 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.
+ Usage: s\bse\ben\bnd\bd-\b-h\bho\boo\bok\bk [!]_\bp_\ba_\bt_\bt_\be_\br_\bn_\bc_\bo_\bm_\bm_\ba_\bn_\bd
- 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.
+ Usage: s\bse\ben\bnd\bd2\b2-\b-h\bho\boo\bok\bk [!]_\bp_\ba_\bt_\bt_\be_\br_\bn_\bc_\bo_\bm_\bm_\ba_\bn_\bd
- 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.
+ These commands can be used to execute arbitrary configuration commands
+ based upon recipients of the message. _\bp_\ba_\bt_\bt_\be_\br_\bn is a regular expression
+ matching the desired address. _\bc_\bo_\bm_\bm_\ba_\bn_\bd is executed when _\br_\be_\bg_\be_\bx_\bp matches
+ recipients of the message.
- 6.2.2. Group Replies
+ r\bre\bep\bpl\bly\by-\b-h\bho\boo\bok\bk is matched against the message you are _\br_\be_\bp_\bl_\by_\bi_\bn_\bg _\bt_\bo, instead
+ of the message you are _\bs_\be_\bn_\bd_\bi_\bn_\bg . \b s\bse\ben\bnd\bd-\b-h\bho\boo\bok\bk is matched against all
+ messages, both _\bn_\be_\bw and _\br_\be_\bp_\bl_\bi_\be_\bs ._\bN_\bo_\bt_\be_\b:r\bre\bep\bpl\bly\by-\b-h\bho\boo\bok\bks are matched _\bb_\be_\bf_\bo_\br_\be
+ the s\bse\ben\bnd\bd-\b-h\bho\boo\bok\bk, _\br_\be_\bg_\ba_\br_\bd_\bl_\be_\bs_\bs of the order specified in the users's
+ configuration file.
- 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.
+ s\bse\ben\bnd\bd2\b2-\b-h\bho\boo\bok\bk 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\bse\ben\bnd\bd2\b2-\b-h\bho\boo\bok\bk is executed after s\bse\ben\bnd\bd-\b-h\bho\boo\bok\bk ,and can, e.g., be
+ used to set parameters such as the $\b$s\bse\ben\bnd\bdm\bma\bai\bil\bl variable depending on the
+ message's sender address.
- 6.2.3. List Replies
+ For each type of s\bse\ben\bnd\bd-\b-h\bho\boo\bok\bk or r\bre\bep\bpl\bly\by-\b-h\bho\boo\bok\bk, when multiple matches occur,
+ commands are executed in the order they are specified in the muttrc
+ (for that type of hook).
- 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.
+ See p\bpa\bat\btt\bte\ber\brn\bn-\b-h\bho\boo\bok\bk for information on the exact format of _\bp_\ba_\bt_\bt_\be_\br_\bn.
- 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.
+ Example: send-hook mutt "set mime_forward signature=''"
- lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@
+ Another typical use for this command is to change the values of the
+ $\b$a\bat\btt\btr\bri\bib\bbu\but\bti\bio\bon\bn, $\b$s\bsi\big\bgn\bna\bat\btu\bur\bre\be and $\b$l\blo\boc\bca\bal\ble\be variables in order to change the
+ language of the attributions and signatures based upon the recipients.
- 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.
+ _\bN_\bo_\bt_\be_\b: the s\bse\ben\bnd\bd-\b-h\bho\boo\bok\bk'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\bse\ben\bnd\bd-\b-h\bho\boo\bok\bk 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\bse\ben\bnd\bd-\b-h\bho\boo\bok\bk.
- 6.3. Editing the message header
+22. Change settings before formatting a message
- When editing the header of your outgoing message, there are a couple of
- special features available.
+ Usage: m\bme\bes\bss\bsa\bag\bge\be-\b-h\bho\boo\bok\bk [!]_\bp_\ba_\bt_\bt_\be_\br_\bn_\bc_\bo_\bm_\bm_\ba_\bn_\bd
- 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.
+ This command can be used to execute arbitrary configuration commands
+ before viewing or formatting a message based upon information about
+ the message. _\bc_\bo_\bm_\bm_\ba_\bn_\bd is executed if the _\bp_\ba_\bt_\bt_\be_\br_\bn matches the message to
+ be displayed. When multiple matches occur, commands are executed in
+ the order they are specified in the muttrc.
- You can also attach files to your message by specifying
+ See p\bpa\bat\btt\bte\ber\brn\bn-\b-h\bho\boo\bok\bk for information on the exact format of _\bp_\ba_\bt_\bt_\be_\br_\bn.
- Attach: filename [description]
+ Example:
+message-hook ~A 'set pager=builtin'
+message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject:.*\""'
- where filename is the file to attach and description is an optional string
- to use as the description of the attached file.
+23. Choosing the cryptographic key of the recipient
- 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.
+ Usage: c\bcr\bry\byp\bpt\bt-\b-h\bho\boo\bok\bk_\bp_\ba_\bt_\bt_\be_\br_\bn_\bk_\be_\by_\bi_\bd
- Also see the $edit_headers and $editor_headers variables
+ 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\bcr\bry\byp\bpt\bt-\b-h\bho\boo\bok\bk 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.
- 6.4. Using Mutt-ng with PGP
+ 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.
- If you want to use PGP, you can specify
+24. Adding key sequences to the keyboard buffer
- Pgp: [E | S | S id]
+ Usage: push_\bs_\bt_\br_\bi_\bn_\bg
- ``E'' encrypts, ``S'' signs and ``S<id>'' signs with the given key,
- setting $pgp_sign_as permanently.
+ 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\bma\bac\bcr\bro\bo 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>'
- 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.
+25. Executing functions
- 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.
+ Usage: exec_\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\b _\b[_\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\b _\b._\b._\b._\b _\b]
- Once you have successfully finished the key selection, the message will be
- encrypted using the selected public keys, and sent out.
+ This command can be used to execute any function. Functions are listed
+ in the f\bfu\bun\bnc\bct\bti\bio\bon\bns\bs. ``exec function'' is equivalent to ``push
+ <function>''.
- 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.
+26. Message Scoring
- The flags sequence (%f) will expand to one of the following flags:
+ Usage: score_\bp_\ba_\bt_\bt_\be_\br_\bn_\b _\bv_\ba_\bl_\bu_\be
- Table 2.10. PGP Key Menu Flags
+ Usage: unscore_\bp_\ba_\bt_\bt_\be_\br_\bn_\b _\b[_\bp_\ba_\bt_\bt_\be_\br_\bn_\b _\b._\b._\b._\b _\b]
- 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.
+ 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''.
- 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.
+ 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.
- 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.
+score "~f nion@muttng\.org" 50
+score "~f @sco\.com" -100
- 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.
+ 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:
- 6.5. Sending anonymous messages via mixmaster
+score "~f santaclaus@northpole\.int" =666
- 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.
+ What is important to note is that negative score values will be
+ rounded up to 0.
- 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.
+ To make scoring actually useful, the score must be applied in some
+ way. That's what the _\bs_\bc_\bo_\br_\be_\b _\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\bs are for. Currently, there are
+ three score thresholds:
- 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.
+ * 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.
- 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.
+ These three thresholds can be set via the variables
+ $\b$s\bsc\bco\bor\bre\be_\b_t\bth\bhr\bre\bes\bsh\bho\bol\bld\bd_\b_r\bre\bea\bad\bd, $\b$s\bsc\bco\bor\bre\be_\b_t\bth\bhr\bre\bes\bsh\bho\bol\bld\bd_\b_f\bfl\bla\bag\bg and
+ $\b$s\bsc\bco\bor\bre\be_\b_t\bth\bhr\bre\bes\bsh\bho\bol\bld\bd_\b_d\bde\bel\ble\bet\bte\be.
-7. Forwarding and Bouncing Mail
+ By default, $\b$s\bsc\bco\bor\bre\be_\b_t\bth\bhr\bre\bes\bsh\bho\bol\bld\bd_\b_r\bre\bea\bad\bd and $\b$s\bsc\bco\bor\bre\be_\b_t\bth\bhr\bre\bes\bsh\bho\bol\bld\bd_\b_d\bde\bel\ble\bet\bte\be are set
+ to -1, which means that in the default threshold configuration no
+ message will ever get marked as read or deleted.
- Often, it is necessary to forward mails to other people. Therefore,
- mutt-ng supports forwarding messages in two different ways.
+ Scoring gets especially interesting when combined with the color
+ command and the ~n pattern:
- 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:
+color index black yellow "~n 10-"
+color index red yellow "~n 100-"
- ----- Forwarded message from Lucas User <luser@example.com> -----
+ 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.
- From: Lucas User <luser@example.com>
- Date: Thu, 02 Dec 2004 03:08:34 +0100
- To: Michael Random <mrandom@example.com>
- Subject: Re: blackmail
+27. Spam detection
- Pay me EUR 50,000.- cash or your favorite stuffed animal will die
- a horrible death.
+ Usage: spam_\bp_\ba_\bt_\bt_\be_\br_\bn_\b _\bf_\bo_\br_\bm_\ba_\bt
- ----- End forwarded message -----
+ Usage: nospam_\bp_\ba_\bt_\bt_\be_\br_\bn
- 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.
+ Mutt-ng has generalized support for external spam-scoring filters. By
+ defining your spam patterns with the spam and nospam commands, you can
+ _\bl_\bi_\bm_\bi_\bt, _\bs_\be_\ba_\br_\bc_\bh, and _\bs_\bo_\br_\bt 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
+ $\b$i\bin\bnd\bde\bex\bx_\b_f\bfo\bor\brm\bma\bat\bt variable. (Tip: try %?H?[%H] ? to display spam tags only
+ when they are defined for a given message.)
- 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.
+ Your first step is to define your external filter's spam patterns
+ using the spam command. _\bp_\ba_\bt_\bt_\be_\br_\bn 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 _\bf_\bo_\br_\bm_\ba_\bt parameter. _\bf_\bo_\br_\bm_\ba_\bt can be any static text, but
+ it also can include back-references from the _\bp_\ba_\bt_\bt_\be_\br_\bn 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 _\bf_\bo_\br_\bm_\ba_\bt strings joined together, with the
+ value of $spam_separator separating them.
- 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.
+ 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=", "
-8. Postponing Mail
+ 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''.)
- 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.
+ If the $spam_separator variable is unset, then each spam pattern match
+ supersedes the previous one. Instead of getting joined _\bf_\bo_\br_\bm_\ba_\bt strings,
+ you'll get only the last one to match.
- 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.
+ 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 _\bs_\be_\ba_\br_\bc_\bh and _\bl_\bi_\bm_\bi_\bt
+ 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 _\bl_\be_\bx_\bi_\bc_\ba_\bl_\bl_\by -- 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 _\ba_\bn_\by 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 _\bp_\ba_\bt_\bt_\be_\br_\bn given to nospam is exactly the same as the _\bp_\ba_\bt_\bt_\be_\br_\bn 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
+ _\bp_\ba_\bt_\bt_\be_\br_\bn for a spam command matches an entry on the nospam list, that
+ nospam entry will be removed. If the _\bp_\ba_\bt_\bt_\be_\br_\bn for nospam is ``*'', _\ba_\bl_\bl
+ _\be_\bn_\bt_\br_\bi_\be_\bs_\b _\bo_\bn_\b _\bb_\bo_\bt_\bh_\b _\bl_\bi_\bs_\bt_\bs will be removed. This might be the default
+ action if you use spam and nospam in conjunction with a f\bfo\bol\bld\bde\ber\br-\b-h\bho\boo\bok\bk.
+
+ 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"
- 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.
+28. Setting variables
- See also the $postpone quad-option.
+ Usage: set_\b[_\bn_\bo_\b|_\bi_\bn_\bv_\b]_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\b _\b[_\b=_\bv_\ba_\bl_\bu_\be_\b]_\b _\b[_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\b._\b._\b._\b]
-Chapter 3. Configuration
+ Usage: toggle_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\b _\b[_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\b _\b._\b._\b._\b]
- Table of Contents
+ Usage: unset_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\b _\b[_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\b _\b._\b._\b._\b]
- 1. Locations of Configuration Files
+ Usage: reset_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\b _\b[_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\b _\b._\b._\b._\b]
- 2. Basic Syntax of Initialization Files
+ This command is used to set (and unset) v\bva\bar\bri\bia\bab\bbl\ble\bes\bs. There are four
+ basic types of variables: boolean, number, string and quadoption.
+ _\bb_\bo_\bo_\bl_\be_\ba_\bn variables can be _\bs_\be_\bt (true) or _\bu_\bn_\bs_\be_\bt (false). _\bn_\bu_\bm_\bb_\be_\br variables
+ can be assigned a positive integer value.
- 3. Expansion within variables
+ _\bs_\bt_\br_\bi_\bn_\bg variables consist of any number of printable characters.
+ _\bs_\bt_\br_\bi_\bn_\bg_\bs must be enclosed in quotes if they contain spaces or tabs. You
+ may also use the ``C'' escape sequences _\b\_\bn and _\b\_\bt for newline and tab,
+ respectively.
- 3.1. Commands' Output
+ _\bq_\bu_\ba_\bd_\bo_\bp_\bt_\bi_\bo_\bn variables are used to control whether or not to be prompted
+ for certain actions, or to specify a default action. A value of _\by_\be_\bs
+ will cause the action to be carried out automatically as if you had
+ answered yes to the question. Similarly, a value of _\bn_\bo will cause the
+ the action to be carried out as if you had answered ``no.'' A value of
+ _\ba_\bs_\bk_\b-_\by_\be_\bs will cause a prompt with a default answer of ``yes'' and
+ _\ba_\bs_\bk_\b-_\bn_\bo will provide a default answer of ``no.''
- 3.2. Environment Variables
+ Prefixing a variable with ``no'' will unset it. Example: set noaskbcc
+ .
- 3.3. Configuration Variables
+ For _\bb_\bo_\bo_\bl_\be_\ba_\bn 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.
- 3.4. Self-Defined Variables
+ The toggle command automatically prepends the inv prefix to all
+ specified variables.
- 3.5. Pre-Defined Variables
+ The unset command automatically prepends the no prefix to all
+ specified variables.
- 3.6. Type Conversions
+ Using the enter-command function in the _\bi_\bn_\bd_\be_\bx menu, you can query the
+ value of a variable by prefixing the name of the variable with a
+ question mark:
- 4. Defining/Using aliases
+set ?allow_8bit
- 5. Changing the default key bindings
+ The question mark is actually only required for boolean and quadoption
+ variables.
- 6. Defining aliases for character sets
+ 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.
- 7. Setting variables based upon mailbox
+ With the reset command there exists the special variable ``all'',
+ which allows you to reset all variables to their system defaults.
- 8. Keyboard macros
+29. Reading initialization commands from another file
- 9. Using color and mono video attributes
+ Usage: source_\bf_\bi_\bl_\be_\bn_\ba_\bm_\be_\b _\b[_\bf_\bi_\bl_\be_\bn_\ba_\bm_\be_\b _\b._\b._\b._\b]
- 10. Ignoring (weeding) unwanted message headers
+ 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.
- 11. Alternative addresses
+ If the filename begins with a tilde (``~''), it will be expanded to
+ the path of your home directory.
- 12. Format = Flowed
+ If the filename ends with a vertical bar (|), then _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be is
+ considered to be an executable program from which to read input (eg.
+ source ~/bin/myscript|).
- 12.1. Introduction
+30. Removing hooks
- 12.2. Receiving: Display Setup
+ Usage: unhook_\b[_\b*_\b _\b|_\b _\bh_\bo_\bo_\bk_\b-_\bt_\by_\bp_\be_\b]
- 12.3. Sending
+ 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.
- 12.4. Additional Notes
+31. Sharing Setups
- 13. Mailing lists
+31.1. Character Sets
- 14. Using Multiple spool mailboxes
+ 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.
- 15. Defining mailboxes which receive mail
+ 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:
- 16. User defined headers
+set config_charset = "..."
- 17. Defining the order of headers when viewing messages
+ 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:
- 18. Specify default save filename
+# vim:fileencoding=...:
- 19. Specify default Fcc: mailbox when composing
+ while, again, replacing the dots with the appropriate name. This tells
+ vim(1) as which character set to read and save the file.
- 20. Specify default save filename and default Fcc: mailbox at once
+31.2. Modularization
- 21. Change settings based upon message recipients
+ ``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.
- 22. Change settings before formatting a message
+ When using separation, setups may be, as a whole or in fractions,
+ shared over different systems.
- 23. Choosing the cryptographic key of the recipient
+31.3. Conditional parts
- 24. Adding key sequences to the keyboard buffer
+ 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.
- 25. Executing functions
+ To solve this, mutt-ng contain a feature based on the ``ifdef'' patch
+ written for mutt. Its basic syntax is:
- 26. Message Scoring
+ifdef <item> <command>
+ifndef <item> <command>
- 27. Spam detection
+ ...whereby <item> can be one of:
- 28. Setting variables
+ * a function name
+ * a variable name
+ * a menu name
+ * a feature name
- 29. Reading initialization commands from another file
+ 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
- 30. Removing hooks
+ As an example, one can use the following in ~/.muttngrc:
- 31. Sharing Setups
+ifdef feature_imap 'source ~/.mutt-ng/setup-imap'
+ifdef feature_pop 'source ~/.mutt-ng/setup-pop'
+ifdef feature_nntp 'source ~/.mutt-ng/setup-nntp'
- 31.1. Character Sets
+ ...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.
- 31.2. Modularization
+ 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 $\b$i\bim\bma\bap\bp_\b_m\bma\bai\bil\bl_\b_c\bch\bhe\bec\bck\bk
+ use:
- 31.3. Conditional parts
+ifdef imap_mail_check 'set imap_mail_check = 300'
- 32. Obsolete Variables
+ Provided for completeness is the test for menu names. To set
+ $\b$p\bpa\bag\bge\ber\br_\b_i\bin\bnd\bde\bex\bx_\b_l\bli\bin\bne\bes\bs only if the pager menu is available, use:
-1. Locations of Configuration Files
+ifdef pager 'set pager_index_lines = 10'
- 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.
+ 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:
- .muttrc (or .muttngrc for Mutt-ng) is the file where you will usually
- place your commands to configure Mutt-ng.
+ifdef feature_ncurses 'source ~/.mutt-ng/setup-ncurses'
+ifndef feature_ncurses 'source ~/.mutt-ng/setup-slang'
-2. Basic Syntax of Initialization Files
+ ...and...
- 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 (;).
+ifdef feature_slang 'source ~/.mutt-ng/setup-slang'
+ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses'
- set realname='Mutt-ng user' ; ignore x-
+32. Obsolete Variables
- 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,
+ 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\bse\bec\bct\bt-\b-o\bob\bbs\bso\bol\ble\bet\bte\be for a complete list.
- my_hdr X-Disclaimer: Why are you listening to me? # This is a comment
+Chapter 4. Advanced Usage
- 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.
+ _\bT_\ba_\bb_\bl_\be_\b _\bo_\bf_\b _\bC_\bo_\bn_\bt_\be_\bn_\bt_\bs
- \ 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.
+ 1\b1.\b. \b R\bRe\beg\bgu\bul\bla\bar\br \b E\bEx\bxp\bpr\bre\bes\bss\bsi\bio\bon\bns\bs
+ 2\b2.\b. \b P\bPa\bat\btt\bte\ber\brn\bns\bs
- set realname="Michael \"MuttDude\" Elkins"
+ 2\b2.\b.1\b1.\b. \b C\bCo\bom\bmp\bpl\ble\bex\bx \b P\bPa\bat\btt\bte\ber\brn\bns\bs
+ 2\b2.\b.2\b2.\b. \b P\bPa\bat\btt\bte\ber\brn\bns\bs \b a\ban\bnd\bd \b D\bDa\bat\bte\bes\bs
- ``\\'' means to insert a literal ``\'' into the line. ``\n'' and ``\r''
- have their usual C meanings of linefeed and carriage-return, respectively.
+ 3\b3.\b. \b F\bFo\bor\brm\bma\bat\bt \b S\bSt\btr\bri\bin\bng\bgs\bs
- 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.
+ 3\b3.\b.1\b1.\b. \b I\bIn\bnt\btr\bro\bod\bdu\buc\bct\bti\bio\bon\bn
+ 3\b3.\b.2\b2.\b. \b C\bCo\bon\bnd\bdi\bit\bti\bio\bon\bna\bal\bl \b E\bEx\bxp\bpa\ban\bns\bsi\bio\bon\bn
+ 3\b3.\b.3\b3.\b. \b M\bMo\bod\bdi\bif\bfi\bic\bca\bat\bti\bio\bon\bns\bs \b a\ban\bnd\bd \b P\bPa\bad\bdd\bdi\bin\bng\bg
- 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 ``#''.
+ 4\b4.\b. \b U\bUs\bsi\bin\bng\bg \b T\bTa\bag\bgs\bs
+ 5\b5.\b. \b U\bUs\bsi\bin\bng\bg \b H\bHo\boo\bok\bks\bs
- # folder-hook . \
- set realname="Michael \"MuttDude\" Elkins"
+ 5\b5.\b.1\b1.\b. \b M\bMe\bes\bss\bsa\bag\bge\be \b M\bMa\bat\btc\bch\bhi\bin\bng\bg \b i\bin\bn \b H\bHo\boo\bok\bks\bs
- 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!
+ 6\b6.\b. \b U\bUs\bsi\bin\bng\bg \b t\bth\bhe\be \b s\bsi\bid\bde\beb\bba\bar\br
+ 7\b7.\b. \b E\bEx\bxt\bte\ber\brn\bna\bal\bl \b A\bAd\bdd\bdr\bre\bes\bss\bs \b Q\bQu\bue\ber\bri\bie\bes\bs
+ 8\b8.\b. \b M\bMa\bai\bil\blb\bbo\box\bx \b F\bFo\bor\brm\bma\bat\bts\bs
+ 9\b9.\b. \b M\bMa\bai\bil\blb\bbo\box\bx \b S\bSh\bho\bor\brt\btc\bcu\but\bts\bs
+ 1\b10\b0.\b. \b H\bHa\ban\bnd\bdl\bli\bin\bng\bg \b M\bMa\bai\bil\bli\bin\bng\bg \b L\bLi\bis\bst\bts\bs
+ 1\b11\b1.\b. \b E\bEd\bdi\bit\bti\bin\bng\bg \b t\bth\bhr\bre\bea\bad\bds\bs
- Abstract example:
+ 1\b11\b1.\b.1\b1.\b. \b L\bLi\bin\bnk\bki\bin\bng\bg \b t\bth\bhr\bre\bea\bad\bds\bs
+ 1\b11\b1.\b.2\b2.\b. \b B\bBr\bre\bea\bak\bki\bin\bng\bg \b t\bth\bhr\bre\bea\bad\bds\bs
- line1\
- line2a # line2b\
- line3\
- line4
- line5
+ 1\b12\b2.\b. \b D\bDe\bel\bli\biv\bve\ber\bry\by \b S\bSt\bta\bat\btu\bus\bs \b N\bNo\bot\bti\bif\bfi\bic\bca\bat\bti\bio\bon\bn \b (\b(D\bDS\bSN\bN)\b) \b S\bSu\bup\bpp\bpo\bor\brt\bt
+ 1\b13\b3.\b. \b P\bPO\bOP\bP3\b3 \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
+ 1\b14\b4.\b. \b I\bIM\bMA\bAP\bP \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
- 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.
+ 1\b14\b4.\b.1\b1.\b. \b T\bTh\bhe\be \b F\bFo\bol\bld\bde\ber\br \b B\bBr\bro\bow\bws\bse\ber\br
+ 1\b14\b4.\b.2\b2.\b. \b A\bAu\but\bth\bhe\ben\bnt\bti\bic\bca\bat\bti\bio\bon\bn
- The commands understood by mutt are explained in the next paragraphs. For
- a complete list, see the commands.
+ 1\b15\b5.\b. \b N\bNN\bNT\bTP\bP \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
-3. Expansion within variables
+ 1\b15\b5.\b.1\b1.\b. \b A\bAg\bga\bai\bin\bn:\b: \b S\bSc\bco\bor\bri\bin\bng\bg
- Besides just assign static content to variables, there's plenty of ways of
- adding external and more or less dynamic content.
+ 1\b16\b6.\b. \b S\bSM\bMT\bTP\bP \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
+ 1\b17\b7.\b. \b M\bMa\ban\bna\bag\bgi\bin\bng\bg \b m\bmu\bul\blt\bti\bip\bpl\ble\be \b I\bIM\bMA\bAP\bP/\b/P\bPO\bOP\bP/\b/N\bNN\bNT\bTP\bP \b a\bac\bcc\bco\bou\bun\bnt\bts\bs \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
+ 1\b18\b8.\b. \b S\bSt\bta\bar\brt\bt \b a\ba \b W\bWW\bWW\bW \b B\bBr\bro\bow\bws\bse\ber\br \b o\bon\bn \b U\bUR\bRL\bLs\bs \b (\b(E\bEX\bXT\bTE\bER\bRN\bNA\bAL\bL)\b)
+ 1\b19\b9.\b. \b C\bCo\bom\bmp\bpr\bre\bes\bss\bse\bed\bd \b f\bfo\bol\bld\bde\ber\brs\bs \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
- 3.1. Commands' Output
+ 1\b19\b9.\b.1\b1.\b. \b O\bOp\bpe\ben\bn \b a\ba \b c\bco\bom\bmp\bpr\bre\bes\bss\bse\bed\bd \b m\bma\bai\bil\blb\bbo\box\bx \b f\bfo\bor\br \b r\bre\bea\bad\bdi\bin\bng\bg
+ 1\b19\b9.\b.2\b2.\b. \b W\bWr\bri\bit\bte\be \b a\ba \b c\bco\bom\bmp\bpr\bre\bes\bss\bse\bed\bd \b m\bma\bai\bil\blb\bbo\box\bx
+ 1\b19\b9.\b.3\b3.\b. \b A\bAp\bpp\bpe\ben\bnd\bd \b a\ba \b m\bme\bes\bss\bsa\bag\bge\be \b t\bto\bo \b a\ba \b c\bco\bom\bmp\bpr\bre\bes\bss\bse\bed\bd \b m\bma\bai\bil\blb\bbo\box\bx
+ 1\b19\b9.\b.4\b4.\b. \b E\bEn\bnc\bcr\bry\byp\bpt\bte\bed\bd \b f\bfo\bol\bld\bde\ber\brs\bs
- 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:
+1. Regular Expressions
- my_hdr X-Operating-System: `uname -a`
+ All string patterns in Mutt-ng including those in more complex
+ p\bpa\bat\btt\bte\ber\brn\bns\bs 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\bmu\but\btt\btr\brc\bc-\b-s\bsy\byn\bnt\bta\bax\bx for more information on " and ' delimiter
+ processing. To match a literal " or ' you must preface it with \
+ (backslash).
- 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.
+ 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.
- 3.2. Environment Variables
+ 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.
- 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,
+ 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 _\bn_\bo_\bt in the list. For example, the
+ regular expression _\b]_\b0_\b1_\b2_\b3_\b4_\b5_\b6_\b7_\b8_\b9_\b] 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.
- set record=+sent_on_$HOSTNAME
+ 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:
- sets the $record variable to the string +sent_on_ and appends the value of
- the evironment variable $HOSTNAME.
+ [:alnum:]
+ Alphanumeric characters.
- Note: There will be no warning if an environment variable is not defined.
- The result will of the expansion will then be empty.
+ [:alpha:]
+ Alphabetic characters.
- 3.3. Configuration Variables
+ [:blank:]
+ Space or tab characters.
- As for environment variables, the values of all configuration variables as
- string can be used in the same way, too. For example,
+ [:cntrl:]
+ Control characters.
- set imap_home_namespace = $folder
+ [:digit:]
+ Numeric characters.
- would set the value of $imap_home_namespace to the value to which $folder
- is currently set to.
+ [:graph:]
+ Characters that are both printable and visible. (A space is
+ printable, but not visible, while an ``a'' is both.)
- 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.
+ [:lower:]
+ Lower-case alphabetic characters.
- 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.
+ [:print:]
+ Printable characters (characters that are not control
+ characters.)
- 3.4. Self-Defined Variables
+ [:punct:]
+ Punctuation characters (characters that are not letter, digits,
+ control characters, or space characters).
- 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.
+ [:space:]
+ Space characters (such as space, tab and formfeed, to name a
+ few).
- For example, to view the manual, users can either define two macros like
- the following
+ [:upper:]
+ Upper-case alphabetic characters.
- macro generic <F1> "!less -r /path/to/manual" "Show manual"
- macro pager <F1> "!less -r /path/to/manual" "Show manual"
+ [:xdigit:]
+ Characters that are hexadecimal digits.
- for generic, pager and index .The alternative is to define a custom
- variable like so:
+ 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, _\b[_\b[_\b:_\bd_\bi_\bg_\bi_\bt_\b:_\b]_\b]
+ is equivalent to _\b[_\b0_\b-_\b9_\b].
- 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"
+ 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:
- to re-use the command sequence as in:
+ Collating Symbols
+ A collating symbol is a multi-character collating element
+ enclosed in ``[.'' and ``.]''. For example, if ``ch'' is a
+ collating element, then _\b[_\b[_\b._\bc_\bh_\b._\b]_\b] is a regexp that matches this
+ collating element, while _\b[_\bc_\bh_\b] is a regexp that matches either
+ ``c'' or ``h''.
- macro index <F2> "$user_manualcmd | grep '\^[ ]\\+~. '" "Show Patterns"
+ 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, _\b[_\b[_\b=_\be_\b=_\b]_\b]
+ is a regexp that matches any of ``è'', ``é'' and ``e''.
- 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.
+ A regular expression matching a single character may be followed by
+ one of several repetition operators:
- 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 preceding item is optional and matched at most once.
- The complete removal is done via the unset keyword.
+ *
+ The preceding item will be matched zero or more times.
- After the following sequence:
+ +
+ The preceding item will be matched one or more times.
- set user_foo = 42
- set user_foo = 666
+ {n}
+ The preceding item is matched exactly _\bn times.
- the variable $user_foo has a current value of 666 and an initial of 42.
- The query
+ {n,}
+ The preceding item is matched _\bn or more times.
- set ?user_foo
+ {,m}
+ The preceding item is matched at most _\bm times.
- will show 666. After doing the reset via
+ {n,m}
+ The preceding item is matched at least _\bn times, but no more
+ than _\bm times.
- reset user_foo
+ Two regular expressions may be concatenated; the resulting regular
+ expression matches any string formed by concatenating two substrings
+ that respectively match the concatenated subexpressions.
- a following query will give 42 as the result. After unsetting it via
+ Two regular expressions may be joined by the infix operator ``|''; the
+ resulting regular expression matches any string matching either
+ subexpression.
- unset user_foo
+ 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.
- any query or operation (except the noted expansion within other
- statements) will lead to an error message.
+ _\bN_\bo_\bt_\be_\b: If you compile Mutt-ng with the GNU _\br_\bx package, the following
+ operators may also be used in regular expressions:
- 3.5. Pre-Defined Variables
+ \\y
+ Matches the empty string at either the beginning or the end of
+ a word.
- 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.
+ \\B
+ Matches the empty string within a word.
- 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:
+ \\<
+ Matches the empty string at the beginning of a word.
- $ muttng -Q muttng_docdir
+ \\>
+ Matches the empty string at the end of a word.
- 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:
+ \\w
+ Matches any word-constituent character (letter, digit, or
+ underscore).
- set user_manualcmd = '!less -r /path/to_manual'
+ \\W
+ Matches any character that is not word-constituent.
- to:
+ \\`
+ Matches the empty string at the beginning of a buffer (string).
- set user_manualcmd = "!less -r $muttng_docdir/manual.txt"
+ \\'
+ Matches the empty string at the end of a buffer.
- which works everywhere if a manual is installed.
+ 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.
- 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.
+2. Patterns
- For example, the statement
+ 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\bpa\bat\btt\bte\ber\brn\bns\bs in the Reference chapter.
- folder-hook . "set user_current_folder = $muttng_folder_name"
+ 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.
- will be already be translated to the following when reading the startup
- files:
+2.1. Complex Patterns
- folder-hook . "set user_current_folder = some_folder"
+ 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:
- with some_folder being the name of the first folder muttng opens. On the
- contrary,
+~s 'SPAM' ~U
- folder-hook . 'set user_current_folder = $muttng_folder_name'
+ The pattern above matches all messages that contain ``SPAM'' in the
+ subject and are unread.
- 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.
+ To logical OR patterns, simply use the | operator. This one especially
+ useful when using local groups:
- A more practical example is:
+~f ("nion@muttng\.org"|"ak@muttng\.org"|"pdmef@muttng\.org")
+(~b mutt-ng|~s Mutt-ng)
+!~x '@synflood\.at'
- folder-hook . 'source ~/.mutt/score-$muttng_folder_name'
+ 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.
- which can be used to source files containing score commands depending on
- the folder the user enters.
+2.2. Patterns and Dates
- 3.6. Type Conversions
+ 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 _\ba_\bf_\bt_\be_\br Juni
+ 1st, 2005.
- 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
+ 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).
-4. Defining/Using aliases
+ 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:
- Usage: aliaskey address [, address,...]
+~d >2w # messages older than two weeks
+~d <3d # messages newer than 3 days
+~d =1m # messages that are exactly one month old
- 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.
+3. Format Strings
- 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 (``,'').
+3.1. Introduction
- To remove an alias or aliases (``*'' means all aliases):
+ The so called _\bF_\bo_\br_\bm_\ba_\bt_\b _\bS_\bt_\br_\bi_\bn_\bg_\bs offer great flexibility when configuring
+ mutt-ng. In short, they describe what items to print out how in menus
+ and status messages.
- Usage: unalias[* | key ... ]
+ 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 _\be_\bx_\bp_\ba_\bn_\bd_\bo.
- alias muttdude me@cs.hmc.edu (Michael Elkins)
- alias theguys manny, moe, jack
+ 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:
- 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.
+ * the current hostname
+ * the current mutt-ng version number
- 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
+ The setting for the status bar of the index is controlled via the
+ $\b$s\bst\bta\bat\btu\bus\bs_\b_f\bfo\bor\brm\bma\bat\bt 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:
- 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.
+set status_format = "%v on %h: ..."
- 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.
+ 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:
- 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.
+Mutt-ng 1.5.9i on mailhost: ...
-5. Changing the default key bindings
+ In the index, there're more useful information one could want to see:
- Usage: bindmap key function
+ * which mailbox is open
+ * how man new, flagged or postponed messages
+ * ...
- This command allows you to change the default key bindings (operation
- invoked when pressing a key).
+ To include the mailbox' name is as easy as:
- 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:
+set status_format = "%v on %h: %B: ...
- generic
+ When the currently opened mailbox is Inbox, this will be expanded to:
- 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.
+Mutt-ng 1.5.9i on mailhost: Inbox: ...
- alias
+ 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.
- 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).
+3.2. Conditional Expansion
- attach
+ To only print the number of messages if there are new messages in the
+ current mailbox, further extend $status_format to:
- The attachment menu is used to access the attachments on received
- messages.
+set status_format = "%v on %h: %B %?n?%n new? ...
- browser
+ This feature is called _\bn_\bo_\bn_\bz_\be_\br_\bo_\b-_\bp_\br_\bi_\bn_\bt_\bi_\bn_\bg 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:
- The browser is used for both browsing the local directory
- structure, and for listing all of your incoming mailboxes.
+%?<item>?<string if nonzero>?
- editor
+ 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.
- The editor is the line-based editor the user enters text data.
+ 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:
- index
+%?<item>?<string if nonzero>&<string if zero>?
- The index is the list of messages contained in a mailbox.
+ Using this we can make mutt-ng to do the following:
- compose
+ * make it print ``_\bn new messages'' whereby _\bn is the count but only
+ if there new ones
+ * and make it print ``no new messages'' if there aren't any
- The compose menu is the screen used when sending a new message.
+ The corresponding configuration is:
- pager
+set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ...
- The pager is the mode used to display message/attachment data, and
- help listings.
+ This doubles the use of the ``new messages'' string because it'll get
+ always printed. Thus, it can be shortened to:
- pgp
+set status_format = "%v on %h: %B: %?n?%n&no? new messages ...
- The pgp menu is used to select the OpenPGP keys used for
- encrypting outgoing 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.
- postpone
+3.3. Modifications and Padding
- The postpone menu is similar to the index menu, except is used
- when recalling a message the user was composing, but saved until
- later.
+ Besides the information given so far, there're even more features of
+ format strings:
- 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?).
+ * 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 (_).
- In addition, key may consist of:
+ Also, there's a feature called _\bP_\ba_\bd_\bd_\bi_\bn_\bg supplied by the following two
+ expandos: %|X and %>X .
- Table 3.1. Alternative Key Names
+ %|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:
- 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
+set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-"
- key does not need to be enclosed in quotes unless it contains a space (``
- '').
+ %>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 %>):
- 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.
+set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)"
-6. Defining aliases for character sets
+4. Using Tags
- Usage: charset-hookaliascharset
+ 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\bpa\bat\btt\bte\ber\brn\bns\bs 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 _\bn_\be_\bx_\bt operation
+ will be applied to all tagged messages if that operation can be used
+ in that manner. If the $\b$a\bau\but\bto\bo_\b_t\bta\bag\bg variable is set, the next operation
+ applies to the tagged messages automatically, without requiring the
+ ``tag-prefix''.
+
+ In m\bma\bac\bcr\bro\bo or p\bpu\bus\bsh\bh 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.
- Usage: iconv-hookcharsetlocal-charset
+5. Using Hooks
- 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.
+ A _\bh_\bo_\bo_\bk 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 _\bh_\bo_\bo_\bk consists of a r\bre\beg\bge\bex\bxp\bp or p\bpa\bat\btt\bte\ber\brn\bns\bs along with a
+ configuration option/command. See
+ * f\bfo\bol\bld\bde\ber\br-\b-h\bho\boo\bok\bk
+ * s\bse\ben\bnd\bd-\b-h\bho\boo\bok\bk
+ * m\bme\bes\bss\bsa\bag\bge\be-\b-h\bho\boo\bok\bk
+ * s\bsa\bav\bve\be-\b-h\bho\boo\bok\bk
+ * m\bmb\bbo\box\bx-\b-h\bho\boo\bok\bk
+ * f\bfc\bcc\bc-\b-h\bho\boo\bok\bk
+ * f\bfc\bcc\bc-\b-s\bsa\bav\bve\be-\b-h\bho\boo\bok\bk
+
+ for specific details on each type of _\bh_\bo_\bo_\bk available.
+
+ _\bN_\bo_\bt_\be_\b: 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\bse\ben\bnd\bd-\b-h\bho\boo\bok\bk 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 ( \b s\bse\ben\bnd\bd-\b-h\bho\boo\bok\bk, s\bsa\bav\bve\be-\b-h\bho\boo\bok\bk, f\bfc\bcc\bc-\b-h\bho\boo\bok\bk,
+ m\bme\bes\bss\bsa\bag\bge\be-\b-h\bho\boo\bok\bk )are evaluated in a slightly different manner. For the
+ other types of hooks, a r\bre\beg\bge\bex\bxp\bp 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\bpa\bat\btt\bte\ber\brn\bns\bs language for matching messages
+ in hook commands. This works in exactly the same way as it would when
+ _\bl_\bi_\bm_\bi_\bt_\bi_\bn_\bg or_\bs_\be_\ba_\br_\bc_\bh_\bi_\bn_\bg 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
+ _\bm_\be_\b@_\bc_\bs_\b._\bh_\bm_\bc_\b._\be_\bd_\bu.
+
+ However, it is not required that you write the pattern to match using
+ the full searching language. You can still specify a simple _\br_\be_\bg_\bu_\bl_\ba_\br
+ _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn like the other hooks, in which case Mutt-ng will translate
+ your pattern into the full language, using the translation specified
+ by the d\bde\bef\bfa\bau\bul\blt\bt-\b-h\bho\boo\bok\bk variable. The pattern is translated at the time
+ the hook is declared, so the value of d\bde\bef\bfa\bau\bul\blt\bt-\b-h\bho\boo\bok\bk that is in effect
+ at that time will be used.
- 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.
+6. Using the sidebar
-7. Setting variables based upon mailbox
+ 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
- Usage: folder-hook [!]regexpcommand
+ If you want to specify the mailboxes you can do so with:
+set mbox='=INBOX'
+mailboxes INBOX \
+MBOX1 \
+MBOX2 \
+...
- 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.
+ You can also specify the colors for mailboxes with new mails by using:
+color sidebar_new red black
+color sidebar white black
- 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.
+ 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
- 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:
+macro index B ':toggle sidebar_visible^M'
+macro pager B ':toggle sidebar_visible^M'
- folder-hook mutt set sort=threads
+ 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'.
- However, the sorting method is not restored to its previous value when
- reading a different mailbox. To specify a default command, use the pattern
- ``.'':
+7. External Address Queries
- folder-hook . set sort=date-sent
+ 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 $\b$q\bqu\bue\ber\bry\by_\b_c\bco\bom\bmm\bma\ban\bnd\bd variable, you
+ specify the wrapper command to use. For example:
-8. Keyboard macros
+set query_command = "mutt_ldap_query.pl '%s'"
- Usage: macromenu key sequence [description]
+ 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.
- 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.
+ 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.
- 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.
+ 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.
- 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.
+8. Mailbox Formats
- 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).
+ 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
+ $\b$m\bmb\bbo\box\bx_\b_t\bty\byp\bpe\be variable.
- Optionally you can specify a descriptive text after sequence, which is
- shown in the help screens.
+ _\bm_\bb_\bo_\bx. 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:
- Note: Macro definitions (if any) listed in the help screen(s), are
- silently truncated at the screen width, and are not wrapped.
+From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
-9. Using color and mono video attributes
+ to denote the start of a new message (this is often referred to as the
+ ``From_'' line).
- Usage: colorobject foreground background [regexp]
+ _\bM_\bM_\bD_\bF. This is a variant of the _\bm_\bb_\bo_\bx format. Each message is surrounded
+ by lines containing ``^A^A^A^A'' (four control-A's).
- Usage: colorindex foreground pattern
+ _\bM_\bH. A radical departure from _\bm_\bb_\bo_\bx and _\bM_\bM_\bD_\bF, 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. _\bN_\bo_\bt_\be_\b: Mutt detects this type of
+ mailbox by looking for either .mh_sequences or .xmhcache (needed to
+ distinguish normal directories from MH mailboxes).
+
+ _\bM_\ba_\bi_\bl_\bd_\bi_\br. The newest of the mailbox formats, used by the Qmail MTA (a
+ replacement for sendmail). Similar to _\bM_\bH, except that it adds three
+ subdirectories of the mailbox: _\bt_\bm_\bp, _\bn_\be_\bw and _\bc_\bu_\br .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.
- Usage: uncolorindex pattern [pattern ...]
+9. Mailbox Shortcuts
- 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).
+ 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.
- object can be one of:
+ * ! -- refers to your $\b$s\bsp\bpo\boo\bol\blf\bfi\bil\ble\be (incoming) mailbox
+ * > -- refers to your $\b$m\bmb\bbo\box\bx file
+ * < -- refers to your $\b$r\bre\bec\bco\bor\brd\bd file
+ * ^ -- refers to the current mailbox
+ * - or !! -- refers to the file you've last visited
+ * ~ -- refers to your home directory
+ * = or + -- refers to your $\b$f\bfo\bol\bld\bde\ber\br directory
+ * @_\ba_\bl_\bi_\ba_\bs -- refers to the s\bsa\bav\bve\be-\b-h\bho\boo\bok\bk as determined by the address of
+ the alias
- o attachment
+10. Handling Mailing Lists
- o body (match regexp in the body of messages)
+ 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\bli\bis\bst\bts\bs commands in your muttrc.
- o bold (highlighting bold patterns in the body of messages)
+ 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 _\bi_\bn_\bd_\be_\bx menu display. This is useful to distinguish between personal
+ and list mail in the same mailbox. In the $\b$i\bin\bnd\bde\bex\bx_\b_f\bfo\bor\brm\bma\bat\bt 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 _\bi_\bn_\bd_\be_\bx menu and _\bp_\ba_\bg_\be_\br, 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 $\b$f\bfo\bol\bll\blo\bow\bwu\bup\bp_\b_t\bto\bo 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
+ $\b$h\bho\bon\bno\bor\br_\b_f\bfo\bol\bll\blo\bow\bwu\bup\bp_\b_t\bto\bo 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.
- o error (error messages printed by Mutt-ng)
+ 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.
- o header (match regexp in the message header)
+ 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 $\b$r\bre\bep\bpl\bly\by_\b_t\bto\bo variable to help decide
+ which address to use. If set to _\ba_\bs_\bk_\b-_\by_\be_\bs or _\ba_\bs_\bk_\b-_\bn_\bo, 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 _\by_\be_\bs, the ``Reply-To'' field will be
+ used when present.
- o hdrdefault (default color of the message header in the pager)
+ The ``X-Label:'' header field can be used to further identify mailing
+ lists or list subject matter (or just to annotate messages
+ individually). The $\b$i\bin\bnd\bde\bex\bx_\b_f\bfo\bor\brm\bma\bat\bt 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\bso\bor\brt\bt the mailbox into t\bth\bhr\bre\bea\bad\bds\bs. 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.
- o index (match pattern in the message index)
+11. Editing threads
- o indicator (arrow or bar used to indicate the current item in a menu)
+ 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.
- o markers (the ``+'' markers at the beginning of wrapped lines in the
- pager)
+11.1. Linking threads
- o message (informational messages)
+ 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.
- o normal
+ You can also connect multiple children at once, tagging them and using
+ the tag-prefix command (';') or the auto_tag option.
- o quoted (text matching $quote_regexp in the body of a message)
+11.2. Breaking threads
- o quoted1, quoted2, ..., quotedN (higher levels of quoting)
+ 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.
- o search (highlighting of words in the pager)
+12. Delivery Status Notification (DSN) Support
- o signature
+ R\bRf\bfC\bC \b 1\b18\b89\b94\b4 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.''
- o status (mode lines used to display info about the mailbox or message)
+ Users can make use of it in one of the following two ways:
- o tilde (the ``~'' used to pad blank lines in the pager)
+ * 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.
- o tree (thread tree drawn in the message index and attachment menu)
+ To support this, there are two variables:
- o underline (highlighting underlined patterns in the body of messages)
+ * $\b$d\bds\bsn\bn_\b_n\bno\bot\bti\bif\bfy\by is used to request receipts for different results
+ (such as failed message,message delivered, etc.).
+ * $\b$d\bds\bsn\bn_\b_r\bre\bet\btu\bur\brn\bn requests how much of your message should be returned
+ with the receipt (headers or full message).
- foreground and background can be one of the following:
+ Please see the reference chapter for possible values.
- o white
+13. POP3 Support (OPTIONAL)
- o black
+ If Mutt-ng was compiled with POP3 support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be
+ script with the _\b-_\b-_\be_\bn_\ba_\bb_\bl_\be_\b-_\bp_\bo_\bp flag), it has the ability to work with
+ mailboxes located on a remote POP3 server and fetch mail for local
+ browsing.
- o green
+ You can access the remote POP3 mailbox by selecting the folder
+ pop://popserver/.
- o magenta
+ You can select an alternative port by specifying it with the server,
+ i.e.: pop://popserver:port/.
- o blue
+ You can also specify different username for each folder, i.e.:
+ pop://username@popserver[:port]/.
- o cyan
+ 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 $\b$p\bpo\bop\bp_\b_m\bma\bai\bil\bl_\b_c\bch\bhe\bec\bck\bk variable, which
+ defaults to every 60 seconds.
- o yellow
+ If Mutt-ng was compiled with SSL support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be
+ script with the _\b-_\b-_\bw_\bi_\bt_\bh_\b-_\bs_\bs_\bl 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]/.
- o red
+ Another way to access your POP3 mail is the _\bf_\be_\bt_\bc_\bh_\b-_\bm_\ba_\bi_\bl function
+ (default: G). It allows to connect to p\bpo\bop\bp-\b-h\bho\bos\bst\bt ,fetch all your new
+ mail and place it in the local $\b$s\bsp\bpo\boo\bol\blf\bfi\bil\ble\be. After this point, Mutt-ng
+ runs exactly as if the mail had always been local.
- o default
+ _\bN_\bo_\bt_\be_\b: If you only need to fetch all messages to local mailbox you
+ should consider using a specialized program, such as fetchmail(1).
- o colorx
+14. IMAP Support (OPTIONAL)
- foreground can optionally be prefixed with the keyword bright to make the
- foreground color boldfaced (e.g., brightred).
+ If Mutt-ng was compiled with IMAP support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be
+ script with the _\b-_\b-_\be_\bn_\ba_\bb_\bl_\be_\b-_\bi_\bm_\ba_\bp flag), it has the ability to work with
+ folders located on a remote IMAP server.
- 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):
+ You can access the remote inbox by selecting the folder via its URL:
- set COLORFGBG="green;black"
- export COLORFGBG
+imap://imapserver/INBOX
- Note: The S-Lang library requires you to use the lightgray and brown
- keywords instead of white and yellow when setting this variable.
+ 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
- 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.
+imap://imapserver/path/to/folder
- 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.
+ 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.:
- If your terminal does not support color, it is still possible change the
- video attributes through the use of the ``mono'' command:
+imap://imapserver:port/INBOX
- Usage: monoobject attribute [regexp]
+ You can also specify different username for each folder by prenpending
+ your username and an @ symbol to the server's name.
- Usage: monoindex attribute pattern
+ If Mutt-ng was compiled with SSL support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be
+ script with the _\b-_\b-_\bw_\bi_\bt_\bh_\b-_\bs_\bs_\bl 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.
- Usage: unmonoindex pattern [pattern ...]
+ 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.
- where attribute is one of the following:
+ 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 _\bt_\bo_\bg_\bg_\bl_\be_\b-_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd command. See also the $\b$i\bim\bma\bap\bp_\b_l\bli\bis\bst\bt_\b_s\bsu\bub\bbs\bsc\bcr\bri\bib\bbe\bed\bd
+ variable.
- o none
+ Polling for new mail on an IMAP server can cause noticeable delays.
+ So, you'll want to carefully tune the $\b$i\bim\bma\bap\bp_\b_m\bma\bai\bil\bl_\b_c\bch\bhe\bec\bck\bk and $\b$t\bti\bim\bme\beo\bou\but\bt
+ variables.
- o bold
+ 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.
- o underline
+14.1. The Folder Browser
- o reverse
+ 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
- o standout
+ 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".
-10. Ignoring (weeding) unwanted message headers
+ 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 _\b-_\b-_\bw_\bi_\bt_\bh_\b-_\bs_\ba_\bs_\bl 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.
- Usage: ignorepattern [pattern ...]
+ There are a few variables which control authentication:
+ * $\b$i\bim\bma\bap\bp_\b_u\bus\bse\ber\br - 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}).
+ * $\b$i\bim\bma\bap\bp_\b_p\bpa\bas\bss\bs - a password which you may preset, used by all
+ authentication methods where a password is needed.
+ * $\b$i\bim\bma\bap\bp_\b_a\bau\but\bth\bhe\ben\bnt\bti\bic\bca\bat\bto\bor\brs\bs - 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).
- Usage: unignorepattern [pattern ...]
+15. NNTP Support (OPTIONAL)
- 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.
+ 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.
- 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.
+ 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 $\b$n\bnn\bnt\btp\bp_\b_n\bne\bew\bws\bsr\brc\bc
+ 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.
- 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''.
+15.1. Again: Scoring
- ``unignore *'' will remove all tokens from the ignore list.
+ 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\bMe\bes\bss\bsa\bag\bge\be
+ S\bSc\bco\bor\bri\bin\bng\bg.
- For example:
+ What has not been discusses in detail is mutt-ng's built-in realname
+ filter. For may newsreaders including those for ``advanced users''
+ like _\bs_\bl_\br_\bn or _\bt_\bi_\bn, there are frequent request for such functionality.
+ The solutions offered often are complicated regular expressions.
- # 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:
+ In mutt-ng this is as easy as
-11. Alternative addresses
+score ~* =42
- Usage: alternatesregexp [regexp ...]
+ 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
- Usage: unalternatesregexp [regexp ...]
+score !~* =42
- 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.)
+ on the contrary applies a score of 42 to all messages _\bn_\bo_\bt matching
+ those criteria which are very strict:
- 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.
+ * Email addresses must be valid according to R\bRf\bfC\bC \b 2\b28\b82\b22\b2
+ * 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.
- 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.
+16. SMTP Support (OPTIONAL)
- 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.
+ 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\bds\bsn\bn section) as well as handling the
+ 8BITMIME flag controlled via $\b$u\bus\bse\be_\b_8\b8b\bbi\bit\btm\bmi\bim\bme\be.
+
+ To enable sending mail directly via SMTP without an MTA such as
+ Postfix or SSMTP and the like, simply set the $\b$s\bsm\bmt\btp\bp_\b_h\bho\bos\bst\bt variable
+ pointing to your SMTP server.
+
+ Authentication mechanisms are available via the $\b$s\bsm\bmt\btp\bp_\b_u\bus\bse\ber\br and
+ $\b$s\bsm\bmt\btp\bp_\b_p\bpa\bas\bss\bs 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 $\b$s\bsm\bmt\btp\bp_\b_u\bus\bse\be_\b_t\btl\bls\bs 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
+ $\b$s\bsm\bmt\btp\bp_\b_e\ben\bnv\bve\bel\blo\bop\bpe\be may be used to set the envelope different from the
+ From: header.
-12. Format = Flowed
+17. Managing multiple IMAP/POP/NNTP accounts (OPTIONAL)
- 12.1. Introduction
+ 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\bac\bcc\bco\bou\bun\bnt\bt-\b-h\bho\boo\bok\bk command may help. This hook works like
+ f\bfo\bol\bld\bde\ber\br-\b-h\bho\boo\bok\bk but is invoked whenever you access a remote mailbox
+ (including inside the folder browser), not just when you open the
+ mailbox.
- 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.
+ Some examples:
- For introductory information on format=flowed messages, see
- <http://www.joeclark.org/ffaq.html>.
+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"'
- 12.2. Receiving: Display Setup
+18. Start a WWW Browser on URLs (EXTERNAL)
- 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:
+ If a message contains URLs (_\bu_\bn_\bi_\bf_\bi_\be_\bd_\b _\br_\be_\bs_\bo_\bu_\br_\bc_\be_\b _\bl_\bo_\bc_\ba_\bt_\bo_\br = address in the
+ WWW space like _\bh_\bt_\bt_\bp_\b:_\b/_\b/_\bw_\bw_\bw_\b._\bm_\bu_\bt_\bt_\b._\bo_\br_\bg_\b/), 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 <\b<f\bft\btp\bp:\b:/\b//\b/f\bft\btp\bp.\b.m\bmu\but\btt\bt.\b.o\bor\brg\bg/\b/m\bmu\but\btt\bt/\b/c\bco\bon\bnt\btr\bri\bib\bb/\b/>\b> and the configuration
+ commands:
+macro index \cb |urlview\n
+macro pager \cb |urlview\n
- set wrapmargin = 10
+19. Compressed folders Support (OPTIONAL)
- The code above makes the line break 10 columns before the right side of
- the terminal.
+ If Mutt-ng was compiled with compressed folders support (by running
+ the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be script with the _\b-_\b-_\be_\bn_\ba_\bb_\bl_\be_\b-_\bc_\bo_\bm_\bp_\br_\be_\bs_\bs_\be_\bd 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.
- If your terminal is so wide that the lines are embarrassingly long, you
- can also set a maximum line length:
+ The most common use is to open compressed archived folders e.g. with
+ gzip.
- set max_line_length = 120
+ 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.
- The example above will give you lines not longer than 120 characters.
+ There are three hooks defined (o\bop\bpe\ben\bn-\b-h\bho\boo\bok\bk, c\bcl\blo\bos\bse\be-\b-h\bho\boo\bok\bk and a\bap\bpp\bpe\ben\bnd\bd-\b-h\bho\boo\bok\bk
+ )which define commands to uncompress and compress a folder and to
+ append messages to an existing compressed folder respectively.
- When you view at format=flowed messages, you will often see the quoting
- hierarchy like in the following example:
+ For 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.
+open-hook \\.gz$ "gzip -cd %f > %t"
+close-hook \\.gz$ "gzip -c %t > %f"
+append-hook \\.gz$ "gzip -c %t >> %f"
- 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:
+ You do not have to specify all of the commands. If you omit
+ a\bap\bpp\bpe\ben\bnd\bd-\b-h\bho\boo\bok\bk ,the folder will be open and closed again each time you
+ will add to it. If you omit c\bcl\blo\bos\bse\be-\b-h\bho\boo\bok\bk (or give empty command) , the
+ folder will be open in the mode. If you specify a\bap\bpp\bpe\ben\bnd\bd-\b-h\bho\boo\bok\bk though
+ you'll be able to append to the folder.
- set stuff_quoted
+ 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 $\b$s\bsa\bav\bve\be_\b_e\bem\bmp\bpt\bty\by ,so that
+ the compressed file will be removed if you delete all of the messages.
- This will lead to a nicer result that is easier to read:
+19.1. Open a compressed mailbox for reading
- > 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.
+ Usage: o\bop\bpe\ben\bn-\b-h\bho\boo\bok\bk_\br_\be_\bg_\be_\bx_\bp "_\bc_\bo_\bm_\bm_\ba_\bn_\bd"
- 12.3. Sending
+ The _\bc_\bo_\bm_\bm_\ba_\bn_\bd is the command that can be used for opening the folders
+ whose names match _\br_\be_\bg_\be_\bx_\bp.
- If you want mutt-ng to send emails with format=flowed set, you need to
- explicitly set it:
+ The _\bc_\bo_\bm_\bm_\ba_\bn_\bd 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.
- set text_flowed
+ %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.
- 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
+ The _\bc_\bo_\bm_\bm_\ba_\bn_\bd should _\bn_\bo_\bt remove the original compressed file. The
+ _\bc_\bo_\bm_\bm_\ba_\bn_\bd should return non-zero exit status if it fails, so mutt knows
+ something's wrong.
- Please make sure that you manually prepend a space to each of them.
+ Example:
- 12.4. Additional Notes
+open-hook \\.gz$ "gzip -cd %f > %t"
- 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.
+ If the _\bc_\bo_\bm_\bm_\ba_\bn_\bd is empty, this operation is disabled for this file
+ type.
-13. Mailing lists
+19.2. Write a compressed mailbox
- Usage: listsregexp [regexp ...]
+ Usage: c\bcl\blo\bos\bse\be-\b-h\bho\boo\bok\bk_\br_\be_\bg_\be_\bx_\bp"_\bc_\bo_\bm_\bm_\ba_\bn_\bd"
- Usage: unlistsregexp [regexp ...]
+ This is used to close the folder that was open with the o\bop\bpe\ben\bn-\b-h\bho\boo\bok\bk
+ command after some changes were made to it.
- Usage: subscriberegexp [regexp ...]
+ The _\bc_\bo_\bm_\bm_\ba_\bn_\bd string is the command that can be used for closing the
+ folders whose names match _\br_\be_\bg_\be_\bx_\bp. It has the same format as in the
+ o\bop\bpe\ben\bn-\b-h\bho\boo\bok\bk command. Temporary folder in this case is the folder
+ previously produced by the o\bop\bpe\ben\bn-\b-h\bho\boo\bok\bk command.
- Usage: unsubscriberegexp [regexp ...]
+ The _\bc_\bo_\bm_\bm_\ba_\bn_\bd should _\bn_\bo_\bt remove the decompressed file. The _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ should return non-zero exit status if it fails, so mutt knows
+ something's wrong.
- 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.
+ Example:
- 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.
+close-hook \\.gz$ "gzip -c %t > %f"
- The ``unlists'' command is used to remove a token from the list of known
- and subscribed mailing-lists. Use ``unlists *'' to remove all tokens.
+ If the _\bc_\bo_\bm_\bm_\ba_\bn_\bd is empty, this operation is disabled for this file
+ type, and the file can only be open in the readonly mode.
- To remove a mailing list from the list of subscribed mailing lists, but
- keep it on the list of known mailing lists, use ``unsubscribe''.
+ c\bcl\blo\bos\bse\be-\b-h\bho\boo\bok\bk is not called when you exit from the folder if the folder
+ was not changed.
-14. Using Multiple spool mailboxes
+19.3. Append a message to a compressed mailbox
- Usage: mbox-hook [!]patternmailbox
+ Usage: a\bap\bpp\bpe\ben\bnd\bd-\b-h\bho\boo\bok\bk_\br_\be_\bg_\be_\bx_\bp"_\bc_\bo_\bm_\bm_\ba_\bn_\bd"
- 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.
+ This command is used for saving to an existing compressed folder. The
+ _\bc_\bo_\bm_\bm_\ba_\bn_\bd is the command that can be used for appending to the folders
+ whose names match _\br_\be_\bg_\be_\bx_\bp. It has the same format as in the o\bop\bpe\ben\bn-\b-h\bho\boo\bok\bk
+ command. The temporary folder in this case contains the messages that
+ are beingappended.
- 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).
+ The _\bc_\bo_\bm_\bm_\ba_\bn_\bd should _\bn_\bo_\bt remove the decompressed file. The _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ should return non-zero exit status if it fails, so mutt knows
+ something's wrong.
-15. Defining mailboxes which receive mail
+ Example:
- Usage: mailboxes[!]filename [filename ... ]
+append-hook \\.gz$ "gzip -c %t >> %f"
- Usage: unmailboxes[!]filename [filename ... ]
+ When a\bap\bpp\bpe\ben\bnd\bd-\b-h\bho\boo\bok\bk 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 ($\b$m\bmb\bbo\box\bx_\b_t\bty\byp\bpe\be )type is always supposed (i.e. this is the
+ format used for the temporary folder).
- 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.
+ If the file does not exist when you save to it, c\bcl\blo\bos\bse\be-\b-h\bho\boo\bok\bk is called,
+ and not a\bap\bpp\bpe\ben\bnd\bd-\b-h\bho\boo\bok\bk. a\bap\bpp\bpe\ben\bnd\bd-\b-h\bho\boo\bok\bk is only for appending to existing
+ folders.
- When changing folders, pressing space will cycle through folders with new
- mail.
+ If the _\bc_\bo_\bm_\bm_\ba_\bn_\bd is empty, this operation is disabled for this file
+ type. In this case, the folder will be open and closed again (using
+ o\bop\bpe\ben\bn-\b-h\bho\boo\bok\bk and c\bcl\blo\bos\bse\be-\b-h\bho\boo\bok\bk respectively) each time you will add to it.
- 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.
+19.4. Encrypted folders
- The ``unmailboxes'' command is used to remove a token from the list of
- folders which receive mail. Use ``unmailboxes *'' to remove all tokens.
+ 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:
- 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.
+open-hook \\.pgp$ "pgp -f < %f > %t"
+close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
- 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.
+ Please note, that PGP does not support appending to an encrypted
+ folder, so there is no a\bap\bpp\bpe\ben\bnd\bd-\b-h\bho\boo\bok\bk defined.
-16. User defined headers
+ _\bN_\bo_\bt_\be_\b: 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.
- Usage: my_hdrstring
+Chapter 5. Mutt-ng's MIME Support
- Usage: unmy_hdrfield [field ...]
+ _\bT_\ba_\bb_\bl_\be_\b _\bo_\bf_\b _\bC_\bo_\bn_\bt_\be_\bn_\bt_\bs
- The ``my_hdr'' command allows you to create your own header fields which
- will be added to every message you send.
+ 1\b1.\b. \b U\bUs\bsi\bin\bng\bg \b M\bMI\bIM\bME\bE \b i\bin\bn \b M\bMu\but\btt\bt
- For example, if you would like to add an ``Organization:'' header field to
- all of your outgoing messages, you can put the command
+ 1\b1.\b.1\b1.\b. \b V\bVi\bie\bew\bwi\bin\bng\bg \b M\bMI\bIM\bME\bE \b m\bme\bes\bss\bsa\bag\bge\bes\bs \b i\bin\bn \b t\bth\bhe\be \b p\bpa\bag\bge\ber\br
+ 1\b1.\b.2\b2.\b. \b T\bTh\bhe\be \b A\bAt\btt\bta\bac\bch\bhm\bme\ben\bnt\bt \b M\bMe\ben\bnu\bu
+ 1\b1.\b.3\b3.\b. \b T\bTh\bhe\be \b C\bCo\bom\bmp\bpo\bos\bse\be \b M\bMe\ben\bnu\bu
- my_hdr Organization: A Really Big Company, Anytown, USA
+ 2\b2.\b. \b M\bMI\bIM\bME\bE \b T\bTy\byp\bpe\be \b c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b w\bwi\bit\bth\bh \b m\bmi\bim\bme\be.\b.t\bty\byp\bpe\bes\bs
+ 3\b3.\b. \b M\bMI\bIM\bME\bE \b V\bVi\bie\bew\bwe\ber\br \b c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b w\bwi\bit\bth\bh \b m\bma\bai\bil\blc\bca\bap\bp
- in your .muttrc.
+ 3\b3.\b.1\b1.\b. \b T\bTh\bhe\be \b B\bBa\bas\bsi\bic\bcs\bs \b o\bof\bf \b t\bth\bhe\be \b m\bma\bai\bil\blc\bca\bap\bp \b f\bfi\bil\ble\be
+ 3\b3.\b.2\b2.\b. \b S\bSe\bec\bcu\bur\bre\be \b u\bus\bse\be \b o\bof\bf \b m\bma\bai\bil\blc\bca\bap\bp
+ 3\b3.\b.3\b3.\b. \b A\bAd\bdv\bva\ban\bnc\bce\bed\bd \b m\bma\bai\bil\blc\bca\bap\bp \b U\bUs\bsa\bag\bge\be
+ 3\b3.\b.4\b4.\b. \b E\bEx\bxa\bam\bmp\bpl\ble\be \b m\bma\bai\bil\blc\bca\bap\bp \b f\bfi\bil\ble\bes\bs
- 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.
+ 4\b4.\b. \b M\bMI\bIM\bME\bE \b A\bAu\but\bto\bov\bvi\bie\bew\bw
+ 5\b5.\b. \b M\bMI\bIM\bME\bE \b M\bMu\bul\blt\bti\bip\bpa\bar\brt\bt/\b/A\bAl\blt\bte\ber\brn\bna\bat\bti\biv\bve\be
+ 6\b6.\b. \b A\bAt\btt\bta\bac\bch\bhm\bme\ben\bnt\bt \b S\bSe\bea\bar\brc\bch\bhi\bin\bng\bg \b a\ban\bnd\bd \b C\bCo\bou\bun\bnt\bti\bin\bng\bg
+ 7\b7.\b. \b M\bMI\bIM\bME\bE \b L\bLo\boo\bok\bku\bup\bp
- 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.
+ 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.
- 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:
+1. Using MIME in Mutt
- unmy_hdr to cc
+ 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.
-17. Defining the order of headers when viewing messages
+1.1. Viewing MIME messages in the pager
- Usage: hdr_orderheader header [header ...]
+ 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.
- Usage: unhdr_order[ * | header header ...]
+ 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 --]
- With this command, you can specify an order in which mutt will attempt to
- present headers to you when viewing messages.
+ Where the Description is the description or filename given for the
+ attachment, and the Encoding is one of
+ 7bit/8bit/quoted-printable/base64/binary.
- ``unhdr_order *'' will clear all previous headers from the order list,
- thus removing the header order effects set by the system-wide startup
- file.
+ 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) --]
- hdr_order From Date: From: To: Cc: Subject:
+1.2. The Attachment Menu
-18. Specify default save filename
+ 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.
- Usage: save-hook [!]patternfilename
+ Finally, you can apply the usual message-related functions (like
+ <resend-message>, and the reply and forward functions) to attachments
+ of type message/rfc822.
- 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 the help on the attachment menu for more information.
- See pattern-hook for information on the exact format of pattern.
+1.3. The Compose Menu
- Examples:
+ 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.
- save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
- save-hook aol\\.com$ +spam
+ 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>
- Also see the fcc-save-hook command.
+ 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).
-19. Specify default Fcc: mailbox when composing
+2. MIME Type configuration with mime.types
- Usage: fcc-hook [!]patternmailbox
+ 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.
- 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.
+3. MIME Viewer configuration with mailcap
- See pattern-hook for information on the exact format of pattern.
+ Mutt-ng supports R\bRf\bfC\bC \b 1\b15\b52\b24\b4 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.
- Example:
+ 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
- fcc-hook [@.]aol\\.com$ +spammers
+ where $HOME is your home directory.
- 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.
+ In particular, the metamail distribution will install a mailcap file,
+ usually as /usr/local/etc/mailcap, which contains some baseline
+ entries.
-20. Specify default save filename and default Fcc: mailbox at once
+3.1. The Basics of the mailcap file
- Usage: fcc-save-hook [!]patternmailbox
+ A mailcap file consists of a series of lines which are comments,
+ blank, or definitions.
- This command is a shortcut, equivalent to doing both a fcc-hook and a
- save-hook with its arguments.
+ A comment line consists of a # character followed by anything you
+ want.
-21. Change settings based upon message recipients
+ A blank line is blank.
- Usage: reply-hook [!]patterncommand
+ 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.
- Usage: send-hook [!]patterncommand
+ So, in the simplest form, you can send a text/plain message to the
+ external pager more on stdin:
+text/plain; more
- Usage: send2-hook [!]patterncommand
+ Or, you could send the message as a file:
+text/plain; more %s
- 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.
+ Perhaps you would like to use lynx to interactively view a text/html
+ message:
+text/html; lynx %s
- 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.
+ In this case, lynx does not support viewing a file from stdin, so you
+ must use the %s syntax. _\bN_\bo_\bt_\be_\b:_\bS_\bo_\bm_\be_\b _\bo_\bl_\bd_\be_\br_\b _\bv_\be_\br_\bs_\bi_\bo_\bn_\bs_\b _\bo_\bf_\b _\bl_\by_\bn_\bx_\b _\bc_\bo_\bn_\bt_\ba_\bi_\bn_\b _\ba_\b _\bb_\bu_\bg
+ _\bw_\bh_\be_\br_\be_\b _\bt_\bh_\be_\by_\b _\bw_\bi_\bl_\bl_\b _\bc_\bh_\be_\bc_\bk_\b _\bt_\bh_\be_\b _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b _\bf_\bi_\bl_\be_\b _\bf_\bo_\br_\b _\ba_\b _\bv_\bi_\be_\bw_\be_\br_\b _\bf_\bo_\br_\b _\bt_\be_\bx_\bt_\b/_\bh_\bt_\bm_\bl_\b.
+ _\bT_\bh_\be_\by_\b _\bw_\bi_\bl_\bl_\b _\bf_\bi_\bn_\bd_\b _\bt_\bh_\be_\b _\bl_\bi_\bn_\be_\b _\bw_\bh_\bi_\bc_\bh_\b _\bc_\ba_\bl_\bl_\bs_\b _\bl_\by_\bn_\bx_\b,_\b _\ba_\bn_\bd_\b _\br_\bu_\bn_\b _\bi_\bt_\b._\b _\bT_\bh_\bi_\bs_\b _\bc_\ba_\bu_\bs_\be_\bs_\b _\bl_\by_\bn_\bx
+ _\bt_\bo_\b _\bc_\bo_\bn_\bt_\bi_\bn_\bu_\bo_\bu_\bs_\bl_\by_\b _\bs_\bp_\ba_\bw_\bn_\b _\bi_\bt_\bs_\be_\bl_\bf_\b _\bt_\bo_\b _\bv_\bi_\be_\bw_\b _\bt_\bh_\be_\b _\bo_\bb_\bj_\be_\bc_\bt_\b.
- 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.
+ 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
- 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).
+ 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
- See pattern-hook for information on the exact format of pattern.
+ This is the simplest form of a mailcap file.
- Example: send-hook mutt "set mime_forward signature=''"
+3.2. Secure use of mailcap
- 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.
+ 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 $\b$m\bma\bai\bil\blc\bca\bap\bp_\b_s\bsa\ban\bni\bit\bti\biz\bze\be
+ variable.
- 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.
+ 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:
-22. Change settings before formatting a message
+ _\bK_\be_\be_\bp_\b _\bt_\bh_\be_\b _\b%_\b-_\be_\bx_\bp_\ba_\bn_\bd_\bo_\bs_\b _\ba_\bw_\ba_\by_\b _\bf_\br_\bo_\bm_\b _\bs_\bh_\be_\bl_\bl_\b _\bq_\bu_\bo_\bt_\bi_\bn_\bg_\b. 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.
- Usage: message-hook [!]patterncommand
+ 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):
- 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.
+text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
+&& test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
- See pattern-hook for information on the exact format of pattern.
+3.3. Advanced mailcap Usage
- Example:
+3.3.1. Optional Fields
- message-hook ~A 'set pager=builtin'
- message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject:.*\""'
+ 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:
-23. Choosing the cryptographic key of the recipient
+ 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:
- Usage: crypt-hookpatternkeyid
+text/html; lynx -dump %s ; copiousoutput
- 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.
+ 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 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.
+ needsterminal
+ Mutt-ng uses this flag when viewing attachments with a\bau\but\bto\bo_\b_v\bvi\bie\bew\bw,
+ in order to decide whether it should honor the setting of the
+ $\b$w\bwa\bai\bit\bt_\b_k\bke\bey\by variable or not. When an attachment is viewed using
+ an interactive program, and the corresponding mailcap entry has
+ a _\bn_\be_\be_\bd_\bs_\bt_\be_\br_\bm_\bi_\bn_\ba_\bl flag, Mutt-ng will use $\b$w\bwa\bai\bit\bt_\b_k\bke\bey\by 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.
-24. Adding key sequences to the keyboard buffer
+ 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.
- Usage: pushstring
+ 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.
- 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:
+ 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.
- folder-hook . 'push <collapse-all>'
+ 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.
-25. Executing functions
+ 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:
- Usage: execfunction [function ... ]
+text/html; lynx %s; nametemplate=%s.html
- This command can be used to execute any function. Functions are listed in
- the functions. ``exec function'' is equivalent to ``push <function>''.
+ 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. _\bN_\bo_\bt_\be_\b:_\bt_\bh_\be
+ _\bc_\bo_\bn_\bt_\be_\bn_\bt_\b-_\bt_\by_\bp_\be_\b _\bm_\bu_\bs_\bt_\b _\bm_\ba_\bt_\bc_\bh_\b _\bb_\be_\bf_\bo_\br_\be_\b _\bM_\bu_\bt_\bt_\b-_\bn_\bg_\b _\bp_\be_\br_\bf_\bo_\br_\bm_\bs_\b _\bt_\bh_\be_\b _\bt_\be_\bs_\bt_\b. 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\bau\but\bto\bo_\b_v\bvi\bie\bew\bw 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\bau\but\bto\bo_\b_v\bvi\bie\bew\bw, 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.
-26. Message Scoring
+3.3.3. Command Expansion
- Usage: scorepattern value
+ 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:
- Usage: unscorepattern [pattern ... ]
+ %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.
- 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''.
+ %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.
- 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.
+ %{<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:
- score "~f nion@muttng\.org" 50
- score "~f @sco\.com" -100
+Content-Type: text/plain; charset=iso-8859-1
- 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:
+ 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.
- score "~f santaclaus@northpole\.int" =666
+ \%
+ This will be replaced by a %
- What is important to note is that negative score values will be rounded up
- to 0.
+ Mutt-ng does not currently support the %F and %n keywords specified in
+ R\bRf\bfC\bC \b 1\b15\b52\b24\b4. The main purpose of these parameters is for multipart
+ messages, which is handled internally by Mutt-ng.
- 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:
+3.4. Example mailcap files
- o flag threshold: when a message has a score value equal or higher than
- the flag threshold, it will be flagged.
+ This mailcap file is fairly simple and standard:
+>
+# I'm always running X :)
+video/*; xanim %s > /dev/null
+image/*; xv %s > /dev/null
- o read threshold: when a message has a score value equal or lower than
- the read threshold, it will be marked as read.
+# I'm always running netscape (if my computer had more memory, maybe)
+text/html; netscape -remote 'openURL(%s)'
- o delete threshold: when a message has a score value equal or lower than
- the delete threshold, it will be marked as deleted.
+ This mailcap file shows quite a number of examples:
- These three thresholds can be set via the variables $score_threshold_read,
- $score_threshold_flag and $score_threshold_delete.
+# 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
- 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.
+# 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
- Scoring gets especially interesting when combined with the color command
- and the ~n pattern:
+# Else use lynx to view it as text
+text/html; lynx %s
- color index black yellow "~n 10-"
- color index red yellow "~n 100-"
+# This version would convert the text/html to text/plain
+text/html; lynx -dump %s; copiousoutput
- 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.
+# I use enscript to print text in two columns to a page
+text/*; more %s; print=enscript -2Gr %s
-27. Spam detection
+# Netscape adds a flag to tell itself to view jpegs internally
+image/jpeg;xv %s; x-mozilla-flags=internal
- Usage: spampattern format
+# 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
- Usage: nospampattern
+# Convert images to text using the netpbm tools
+image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | \
+pgmtopbm | pbmtoascii -1x2 ) 2>&1 ; copiousoutput
- 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.)
+# Send excel spreadsheets to my NT box
+application/ms-excel; open.pl %s
- 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.
+4. MIME Autoview
- For example, suppose I use DCC, SpamAssassin, and PureMessage. I might
- define these spam settings:
+ Usage: auto_view_\bm_\bi_\bm_\be_\b-_\bt_\by_\bp_\be_\b _\b[_\bm_\bi_\bm_\be_\b-_\bt_\by_\bp_\be_\b _\b._\b._\b._\b]
- 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=", "
+ Usage: unauto_view_\bm_\bi_\bm_\be_\b-_\bt_\by_\bp_\be_\b _\b[_\bm_\bi_\bm_\be_\b-_\bt_\by_\bp_\be_\b _\b._\b._\b._\b]
- 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''.)
+ 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.
- 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.
+ 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.
- 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"
+ You then use the auto_view muttrc command to list the content-types
+ that you wish to view automatically.
-28. Setting variables
+ For instance, if you set auto_view to:
+auto_view text/html application/x-gunzip application/postscript
+image/gif application/x-tar-gz
- Usage: set[no|inv]variable [=value] [variable...]
+ 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\bme\bes\bss\bsa\bag\bge\be-\b-h\bho\boo\bok\bk to autoview messages
+ based on size, etc. ``unauto_view *'' will remove all previous
+ entries.
- Usage: togglevariable [variable ...]
+5. MIME Multipart/Alternative
- Usage: unsetvariable [variable ...]
+ Usage: alternative_order_\bm_\bi_\bm_\be_\b-_\bt_\by_\bp_\be_\b _\b[_\bm_\bi_\bm_\be_\b-_\bt_\by_\bp_\be_\b _\b._\b._\b._\b]
- Usage: resetvariable [variable ...]
+ Usage: unalternative_order_\bm_\bi_\bm_\be_\b-_\bt_\by_\bp_\be_\b _\b[_\bm_\bi_\bm_\be_\b-_\bt_\by_\bp_\be_\b _\b._\b._\b._\b]
- 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.
+ 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/*
- 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.
+ Next, mutt will check if any of the types have a defined a\bau\but\bto\bo_\b_v\bvi\bie\bew\bw,
+ 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.
- 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.''
+ To remove a MIME type from the alternative_order list, use the
+ unalternative_order command.
- Prefixing a variable with ``no'' will unset it. Example: set noaskbcc .
+6. Attachment Searching and Counting
- 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.
+ 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 toggle command automatically prepends the inv prefix to all specified
- variables.
+ The syntax is:
- The unset command automatically prepends the no prefix to all specified
- variables.
+ Usage: attachments_\b(_\b _\b{_\b+_\b|_\b-_\b}_\bd_\bi_\bs_\bp_\bo_\bs_\bi_\bt_\bi_\bo_\bn_\b _\bm_\bi_\bm_\be_\b-_\bt_\by_\bp_\be_\b _\b|_\b _\b?_\b _\b)
- 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:
+ Usage: unattachments_\b{_\b+_\b|_\b-_\b}_\bd_\bi_\bs_\bp_\bo_\bs_\bi_\bt_\bi_\bo_\bn_\b _\bm_\bi_\bm_\be_\b-_\bt_\by_\bp_\be
- set ?allow_8bit
+ Disposition is the attachment's Content-disposition type -- either
+ "inline" or "attachment". You can abbreviate this to I or A.
- The question mark is actually only required for boolean and quadoption
- variables.
+ 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.
- 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.
+ 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.)
- With the reset command there exists the special variable ``all'', which
- allows you to reset all variables to their system defaults.
+ 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.
-29. Reading initialization commands from another file
+ 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 $\b$c\bco\bou\bun\bnt\bt_\b_a\bat\btt\bta\bac\bch\bhm\bme\ben\bnt\bts\bs
+ variable may be used.
- Usage: sourcefilename [filename ...]
+7. MIME Lookup
- 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.
+ Usage: mime_lookup_\bm_\bi_\bm_\be_\b-_\bt_\by_\bp_\be_\b _\b[_\bm_\bi_\bm_\be_\b-_\bt_\by_\bp_\be_\b _\b._\b._\b._\b]
- If the filename begins with a tilde (``~''), it will be expanded to the
- path of your home directory.
+ Usage: unmime_lookup_\bm_\bi_\bm_\be_\b-_\bt_\by_\bp_\be_\b _\b[_\bm_\bi_\bm_\be_\b-_\bt_\by_\bp_\be_\b _\b._\b._\b._\b]
- 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|).
+ 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
-30. Removing hooks
+ 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.
- Usage: unhook[* | hook-type]
+Chapter 6. Security Considerations
- 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.
+ _\bT_\ba_\bb_\bl_\be_\b _\bo_\bf_\b _\bC_\bo_\bn_\bt_\be_\bn_\bt_\bs
-31. Sharing Setups
+ 1\b1.\b. \b P\bPa\bas\bss\bsw\bwo\bor\brd\bds\bs
+ 2\b2.\b. \b T\bTe\bem\bmp\bpo\bor\bra\bar\bry\by \b F\bFi\bil\ble\bes\bs
+ 3\b3.\b. \b I\bIn\bnf\bfo\bor\brm\bma\bat\bti\bio\bon\bn \b L\bLe\bea\bak\bks\bs
- 31.1. Character Sets
+ 3\b3.\b.1\b1.\b. \b M\bMe\bes\bss\bsa\bag\bge\be-\b-I\bID\bD:\b: \b h\bhe\bea\bad\bde\ber\brs\bs
+ 3\b3.\b.2\b2.\b. \b m\bma\bai\bil\blt\bto\bo:\b:-\b-s\bst\bty\byl\ble\be \b l\bli\bin\bnk\bks\bs
- 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.
+ 4\b4.\b. \b E\bEx\bxt\bte\ber\brn\bna\bal\bl \b a\bap\bpp\bpl\bli\bic\bca\bat\bti\bio\bon\bns\bs
- 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:
+ 4\b4.\b.1\b1.\b. \b m\bma\bai\bil\blc\bca\bap\bp
+ 4\b4.\b.2\b2.\b. \b O\bOt\bth\bhe\ber\br
- set config_charset = "..."
+ 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.
- 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:
+ Please do not run mutt-ng as the super user.
- # vim:fileencoding=...:
+ When configuring mutt-ng, there're some points to note about secure
+ setups.
- while, again, replacing the dots with the appropriate name. This tells
- vim(1) as which character set to read and save the file.
+ 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.
- 31.2. Modularization
+1. Passwords
- ``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.
+ 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.
- When using separation, setups may be, as a whole or in fractions, shared
- over different systems.
+2. Temporary Files
- 31.3. Conditional parts
+ Mutt-ng uses many temporary files for viewing messages, verifying
+ digital signatures, etc. The $\b$u\bum\bma\bas\bsk\bk 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 $\b$t\btm\bmp\bpd\bdi\bir\br variable.
- 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.
+3. Information Leaks
- To solve this, mutt-ng contain a feature based on the ``ifdef'' patch
- written for mutt. Its basic syntax is:
+3.1. Message-ID: headers
- ifdef <item> <command>
- ifndef <item> <command>
+ 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 $\b$m\bms\bsg\bgi\bid\bd_\b_f\bfo\bor\brm\bma\bat\bt
+ variable. Please make sure that you really know how local parts of
+ these Message-ID: headers are composed.
- ...whereby <item> can be one of:
+3.2. mailto:-style links
- o a function name
+ 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 $\b$e\bed\bdi\bit\bt_\b_h\bhe\bea\bad\bde\ber\brs\bs
+ variable is _\bu_\bn_\bs_\be_\bt, i.e. the user doesn't want to see header fields
+ while editing the message.
- o a variable name
+ For example, following a link like
- o a menu name
+mailto:joe@host?Attach=~/.gnupg/secring.gpg
- o a feature name
+ will send out the user's private gnupg keyring to joe@host if the user
+ doesn't follow the information on screen carefully enough.
- 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
+ When _\bu_\bn_\bs_\be_\bt_\bt_\bi_\bn_\bg the $\b$s\bst\btr\bri\bic\bct\bt_\b_m\bma\bai\bil\blt\bto\bo variable, mutt-ng will
- As an example, one can use the following in ~/.muttngrc:
+ * be less strict when interpreting these links by prepending a
+ X-Mailto- string to all header fields embedded in such a link _\ba_\bn_\bd
+ * turn on the $\b$e\bed\bdi\bit\bt_\b_h\bhe\bea\bad\bde\ber\brs\bs variable by force to let the user see
+ all the headers (because they still may leak information.)
- ifdef feature_imap 'source ~/.mutt-ng/setup-imap'
- ifdef feature_pop 'source ~/.mutt-ng/setup-pop'
- ifdef feature_nntp 'source ~/.mutt-ng/setup-nntp'
+4. External applications
- ...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.
+ Mutt-ng in many places has to rely on external applications or for
+ convenience supports mechanisms involving external applications.
- 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:
+4.1. mailcap
- ifdef imap_mail_check 'set imap_mail_check = 300'
+ One of these is the mailcap mechanism as defined by R\bRf\bfC\bC \b 1\b15\b52\b24\b4. Mutt-ng
+ can be set up to _\ba_\bu_\bt_\bo_\bm_\ba_\bt_\bi_\bc_\ba_\bl_\bl_\by execute any given utility as listed in
+ one of the mailcap files (see the $\b$m\bma\bai\bil\blc\bca\bap\bp_\b_p\bpa\bat\bth\bh variable for details.)
- Provided for completeness is the test for menu names. To set
- $pager_index_lines only if the pager menu is available, use:
+ 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...
- ifdef pager 'set pager_index_lines = 10'
+ * 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 $\b$m\bma\bai\bil\blc\bca\bap\bp_\b_s\bsa\ban\bni\bit\bti\biz\bze\be variable in its default state to
+ restrict mailcap expandos to a safe set of characters
- 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:
+4.2. Other
- ifdef feature_ncurses 'source ~/.mutt-ng/setup-ncurses'
- ifndef feature_ncurses 'source ~/.mutt-ng/setup-slang'
+ Besides the mailcap mechanism, mutt-ng uses a number of other external
+ utilities for operation.
- ...and...
+ 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.)
- ifdef feature_slang 'source ~/.mutt-ng/setup-slang'
- ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses'
+ As already noted, most of these problems are not built in but caused
+ by wrong configuration, so please check your configuration.
-32. Obsolete Variables
+Chapter 7. Reference
- 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.
+ _\bT_\ba_\bb_\bl_\be_\b _\bo_\bf_\b _\bC_\bo_\bn_\bt_\be_\bn_\bt_\bs
+
+ 1\b1.\b. \b C\bCo\bom\bmm\bma\ban\bnd\bd \b l\bli\bin\bne\be \b o\bop\bpt\bti\bio\bon\bns\bs
+ 2\b2.\b. \b P\bPa\bat\btt\bte\ber\brn\bns\bs
+ 3\b3.\b. \b C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ 4\b4.\b. \b C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ 5\b5.\b. \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs
+
+ 5\b5.\b.1\b1.\b. \b g\bge\ben\bne\ber\bri\bic\bc
+ 5\b5.\b.2\b2.\b. \b i\bin\bnd\bde\bex\bx
+ 5\b5.\b.3\b3.\b. \b p\bpa\bag\bge\ber\br
+ 5\b5.\b.4\b4.\b. \b a\bal\bli\bia\bas\bs
+ 5\b5.\b.5\b5.\b. \b q\bqu\bue\ber\bry\by
+ 5\b5.\b.6\b6.\b. \b a\bat\btt\bta\bac\bch\bh
+ 5\b5.\b.7\b7.\b. \b c\bco\bom\bmp\bpo\bos\bse\be
+ 5\b5.\b.8\b8.\b. \b p\bpo\bos\bst\btp\bpo\bon\bne\be
+ 5\b5.\b.9\b9.\b. \b b\bbr\bro\bow\bws\bse\ber\br
+ 5\b5.\b.1\b10\b0.\b. \b p\bpg\bgp\bp
+ 5\b5.\b.1\b11\b1.\b. \b e\bed\bdi\bit\bto\bor\br
+ 5\b5.\b.1\b12\b2.\b. \b s\bsi\bid\bde\beb\bba\bar\br
-Chapter 4. Advanced Usage
+1. Command line options
- Table of Contents
+ 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.
- 1. Regular Expressions
+ _\bT_\ba_\bb_\bl_\be_\b _\b7_\b._\b1_\b._\b _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\b:_\b _\bC_\bo_\bm_\bm_\ba_\bn_\bd_\b _\bL_\bi_\bn_\be_\b _\bO_\bp_\bt_\bi_\bo_\bn_\bs
+ 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
- 2. Patterns
+ To read messages in a mailbox
- 2.1. Complex Patterns
+ mutt ] -nz ] ] -F _\bm_\bu_\bt_\bt_\br_\bc ] ] -m _\bt_\by_\bp_\be ] ] -f _\bm_\ba_\bi_\bl_\bb_\bo_\bx ]
- 2.2. Patterns and Dates
+ To compose a new message
- 3. Format Strings
+ mutt ] -n ] ] -F _\bm_\bu_\bt_\bt_\br_\bc ] ] -a _\bf_\bi_\bl_\be ] ] -c _\ba_\bd_\bd_\br_\be_\bs_\bs ] ] -i _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be ] ]
+ -s _\bs_\bu_\bb_\bj_\be_\bc_\bt ] _\ba_\bd_\bd_\br_\be_\bs_\bs ] _\ba_\bd_\bd_\br_\be_\bs_\bs ... ]
- 3.1. Introduction
+ Mutt-ng also supports a ``batch'' mode to send prepared messages.
+ Simply redirect input from the file you wish to send. For example,
- 3.2. Conditional Expansion
+ mutt -s "data set for run #2" professor@bigschool.edu < ~/run2.dat
- 3.3. Modifications and Padding
+ 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''.
- 4. Using Tags
+2. Patterns
- 5. Using Hooks
+ _\bT_\ba_\bb_\bl_\be_\b _\b7_\b._\b2_\b._\b _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\b:_\b _\bP_\ba_\bt_\bt_\be_\br_\bn_\bs
+ 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\bre\beg\bge\bex\bxp\bp. 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 (\\).
- 5.1. Message Matching in Hooks
+ *) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too.
- 6. Using the sidebar
+3. Configuration Commands
- 7. External Address Queries
+ The following are the commands understood by mutt.
- 8. Mailbox Formats
+ * a\bac\bcc\bco\bou\bun\bnt\bt-\b-h\bho\boo\bok\bk _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ * a\bal\bli\bia\bas\bs_\bk_\be_\by_\ba_\bd_\bd_\br_\be_\bs_\bs [, _\ba_\bd_\bd_\br_\be_\bs_\bs, ... ]
+ * u\bun\bna\bal\bli\bia\bas\bs [ * | _\bk_\be_\by ... ]
+ * a\bal\blt\bte\ber\brn\bna\bat\bte\bes\bs_\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ * u\bun\bna\bal\blt\bte\ber\brn\bna\bat\bte\bes\bs [ * | _\br_\be_\bg_\be_\bx_\bp ... ]
+ * a\bal\blt\bte\ber\brn\bna\bat\bti\biv\bve\be_\b_o\bor\brd\bde\ber\br_\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ * u\bun\bna\bal\blt\bte\ber\brn\bna\bat\bti\biv\bve\be_\b_o\bor\brd\bde\ber\br_\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ * a\bap\bpp\bpe\ben\bnd\bd-\b-h\bho\boo\bok\bk _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ * a\bau\but\bto\bo_\b_v\bvi\bie\bew\bw_\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ * u\bun\bna\bau\but\bto\bo_\b_v\bvi\bie\bew\bw_\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ * b\bbi\bin\bnd\bd _\bm_\ba_\bp _\bk_\be_\by _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn
+ * c\bch\bha\bar\brs\bse\bet\bt-\b-h\bho\boo\bok\bk _\ba_\bl_\bi_\ba_\bs _\bc_\bh_\ba_\br_\bs_\be_\bt
+ * c\bcl\blo\bos\bse\be-\b-h\bho\boo\bok\bk _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ * c\bco\bol\blo\bor\br_\bo_\bb_\bj_\be_\bc_\bt_\bf_\bo_\br_\be_\bg_\br_\bo_\bu_\bn_\bd_\bb_\ba_\bc_\bk_\bg_\br_\bo_\bu_\bn_\bd [ _\br_\be_\bg_\be_\bx_\bp ]
+ * u\bun\bnc\bco\bol\blo\bor\br_\bi_\bn_\bd_\be_\bx_\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ * e\bex\bxe\bec\bc_\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn [ _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn ... ]
+ * f\bfc\bcc\bc-\b-h\bho\boo\bok\bk _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
+ * f\bfc\bcc\bc-\b-s\bsa\bav\bve\be-\b-h\bho\boo\bok\bk _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
+ * f\bfo\bol\bld\bde\ber\br-\b-h\bho\boo\bok\bk _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ * h\bhd\bdr\br_\b_o\bor\brd\bde\ber\br_\bh_\be_\ba_\bd_\be_\br [ _\bh_\be_\ba_\bd_\be_\br ... ]
+ * u\bun\bnh\bhd\bdr\br_\b_o\bor\brd\bde\ber\br_\bh_\be_\ba_\bd_\be_\br [ _\bh_\be_\ba_\bd_\be_\br ... ]
+ * c\bch\bha\bar\brs\bse\bet\bt-\b-h\bho\boo\bok\bk _\bc_\bh_\ba_\br_\bs_\be_\bt _\bl_\bo_\bc_\ba_\bl_\b-_\bc_\bh_\ba_\br_\bs_\be_\bt
+ * i\big\bgn\bno\bor\bre\be_\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ * u\bun\bni\big\bgn\bno\bor\bre\be_\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ * l\bli\bis\bst\bts\bs_\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ * u\bun\bnl\bli\bis\bst\bts\bs_\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ * m\bma\bac\bcr\bro\bo_\bm_\be_\bn_\bu_\bk_\be_\by_\bs_\be_\bq_\bu_\be_\bn_\bc_\be [ _\bd_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn ]
+ * m\bma\bai\bil\blb\bbo\box\bxe\bes\bs_\bf_\bi_\bl_\be_\bn_\ba_\bm_\be [ _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be ... ]
+ * m\bmb\bbo\box\bx-\b-h\bho\boo\bok\bk _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
+ * m\bme\bes\bss\bsa\bag\bge\be-\b-h\bho\boo\bok\bk _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ * m\bmi\bim\bme\be_\b_l\blo\boo\bok\bku\bup\bp_\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ * u\bun\bnm\bmi\bim\bme\be_\b_l\blo\boo\bok\bku\bup\bp_\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ * m\bmo\bon\bno\bo_\bo_\bb_\bj_\be_\bc_\bt_\b _\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\be [ _\br_\be_\bg_\be_\bx_\bp ]
+ * u\bun\bnm\bmo\bon\bno\bo_\bi_\bn_\bd_\be_\bx_\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ * m\bmy\by_\b_h\bhd\bdr\br _\bs_\bt_\br_\bi_\bn_\bg
+ * u\bun\bnm\bmy\by_\b_h\bhd\bdr\br_\bf_\bi_\be_\bl_\bd [ _\bf_\bi_\be_\bl_\bd ... ]
+ * o\bop\bpe\ben\bn-\b-h\bho\boo\bok\bk _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ * c\bcr\bry\byp\bpt\bt-\b-h\bho\boo\bok\bk _\bp_\ba_\bt_\bt_\be_\br_\bn _\bk_\be_\by_\b-_\bi_\bd
+ * p\bpu\bus\bsh\bh _\bs_\bt_\br_\bi_\bn_\bg
+ * r\bre\bes\bse\bet\bt_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [ _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
+ * s\bsa\bav\bve\be-\b-h\bho\boo\bok\bk _\br_\be_\bg_\be_\bx_\bp _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+ * s\bsc\bco\bor\bre\be _\bp_\ba_\bt_\bt_\be_\br_\bn _\bv_\ba_\bl_\bu_\be
+ * u\bun\bns\bsc\bco\bor\bre\be_\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ * s\bse\ben\bnd\bd-\b-h\bho\boo\bok\bk _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ * r\bre\bep\bpl\bly\by-\b-h\bho\boo\bok\bk _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ * s\bse\bet\bt [no|inv]_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be[ =_\bv_\ba_\bl_\bu_\be ] [ _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
+ * u\bun\bns\bse\bet\bt_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [ _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
+ * s\bso\bou\bur\brc\bce\be _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+ * s\bsp\bpa\bam\bm _\bp_\ba_\bt_\bt_\be_\br_\bn _\bf_\bo_\br_\bm_\ba_\bt
+ * n\bno\bos\bsp\bpa\bam\bm _\bp_\ba_\bt_\bt_\be_\br_\bn
+ * s\bsu\bub\bbs\bsc\bcr\bri\bib\bbe\be_\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ * u\bun\bns\bsu\bub\bbs\bsc\bcr\bri\bib\bbe\be_\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ * t\bto\bog\bgg\bgl\ble\be_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [ _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
+ * u\bun\bnh\bho\boo\bok\bk _\bh_\bo_\bo_\bk_\b-_\bt_\by_\bp_\be
- 9. Mailbox Shortcuts
+4. Configuration variables
- 10. Handling Mailing Lists
+ 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:
- 11. Editing threads
+ _\bT_\ba_\bb_\bl_\be_\b _\b7_\b._\b3_\b._\b _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\b:_\b _\bO_\bb_\bs_\bo_\bl_\be_\bt_\be_\b _\bV_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs
+ Old Name New Name
+ edit_hdrs $\b$e\bed\bdi\bit\bt_\b_h\bhe\bea\bad\bde\ber\brs\bs
+ forw_decode $\b$f\bfo\bor\brw\bwa\bar\brd\bd_\b_d\bde\bec\bco\bod\bde\be
+ forw_format $\b$f\bfo\bor\brw\bwa\bar\brd\bd_\b_f\bfo\bor\brm\bma\bat\bt
+ forw_quote $\b$f\bfo\bor\brw\bwa\bar\brd\bd_\b_q\bqu\buo\bot\bte\be
+ hdr_format $\b$i\bin\bnd\bde\bex\bx_\b_f\bfo\bor\brm\bma\bat\bt
+ indent_str $\b$i\bin\bnd\bde\ben\bnt\bt_\b_s\bst\btr\bri\bin\bng\bg
+ mime_fwd $\b$m\bmi\bim\bme\be_\b_f\bfo\bor\brw\bwa\bar\brd\bd
+ msg_format $\b$m\bme\bes\bss\bsa\bag\bge\be_\b_f\bfo\bor\brm\bma\bat\bt
+ pgp_autosign $\b$c\bcr\bry\byp\bpt\bt_\b_a\bau\but\bto\bos\bsi\big\bgn\bn
+ pgp_autoencrypt $\b$c\bcr\bry\byp\bpt\bt_\b_a\bau\but\bto\boe\ben\bnc\bcr\bry\byp\bpt\bt
+ pgp_replyencrypt $\b$c\bcr\bry\byp\bpt\bt_\b_r\bre\bep\bpl\bly\bye\ben\bnc\bcr\bry\byp\bpt\bt
+ pgp_replysign $\b$c\bcr\bry\byp\bpt\bt_\b_r\bre\bep\bpl\bly\bys\bsi\big\bgn\bn
+ pgp_replysignencrypted $\b$c\bcr\bry\byp\bpt\bt_\b_r\bre\bep\bpl\bly\bys\bsi\big\bgn\bne\ben\bnc\bcr\bry\byp\bpt\bte\bed\bd
+ pgp_verify_sig $\b$c\bcr\bry\byp\bpt\bt_\b_v\bve\ber\bri\bif\bfy\by_\b_s\bsi\big\bg
+ pgp_create_traditional $\b$p\bpg\bgp\bp_\b_a\bau\but\bto\boi\bin\bnl\bli\bin\bne\be
+ pgp_auto_traditional $\b$p\bpg\bgp\bp_\b_r\bre\bep\bpl\bly\byi\bin\bnl\bli\bin\bne\be
+ forw_decrypt $\b$f\bfo\bor\brw\bwa\bar\brd\bd_\b_d\bde\bec\bcr\bry\byp\bpt\bt
+ smime_sign_as $\b$s\bsm\bmi\bim\bme\be_\b_d\bde\bef\bfa\bau\bul\blt\bt_\b_k\bke\bey\by
+ post_indent_str $\b$p\bpo\bos\bst\bt_\b_i\bin\bnd\bde\ben\bnt\bt_\b_s\bst\btr\bri\bin\bng\bg
+ print_cmd $\b$p\bpr\bri\bin\bnt\bt_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ shorten_hierarchy $\b$s\bsi\bid\bde\beb\bba\bar\br_\b_s\bsh\bho\bor\brt\bte\ben\bn_\b_h\bhi\bie\ber\bra\bar\brc\bch\bhy\by
+ ask_followup_to $\b$n\bnn\bnt\btp\bp_\b_a\bas\bsk\bk_\b_f\bfo\bol\bll\blo\bow\bwu\bup\bp_\b_t\bto\bo
+ ask_x_comment_to $\b$n\bnn\bnt\btp\bp_\b_a\bas\bsk\bk_\b_x\bx_\b_c\bco\bom\bmm\bme\ben\bnt\bt_\b_t\bto\bo
+ catchup_newsgroup $\b$n\bnn\bnt\btp\bp_\b_c\bca\bat\btc\bch\bhu\bup\bp
+ followup_to_poster $\b$n\bnn\bnt\btp\bp_\b_f\bfo\bol\bll\blo\bow\bwu\bup\bp_\b_t\bto\bo_\b_p\bpo\bos\bst\bte\ber\br
+ group_index_format $\b$n\bnn\bnt\btp\bp_\b_g\bgr\bro\bou\bup\bp_\b_i\bin\bnd\bde\bex\bx_\b_f\bfo\bor\brm\bma\bat\bt
+ inews $\b$n\bnn\bnt\btp\bp_\b_i\bin\bne\bew\bws\bs
+ mime_subject $\b$n\bnn\bnt\btp\bp_\b_m\bmi\bim\bme\be_\b_s\bsu\bub\bbj\bje\bec\bct\bt
+ news_cache_dir $\b$n\bnn\bnt\btp\bp_\b_c\bca\bac\bch\bhe\be_\b_d\bdi\bir\br
+ news_server $\b$n\bnn\bnt\btp\bp_\b_h\bho\bos\bst\bt
+ newsrc $\b$n\bnn\bnt\btp\bp_\b_n\bne\bew\bws\bsr\brc\bc
+ nntp_poll $\b$n\bnn\bnt\btp\bp_\b_m\bma\bai\bil\bl_\b_c\bch\bhe\bec\bck\bk
+ pop_checkinterval $\b$p\bpo\bop\bp_\b_m\bma\bai\bil\bl_\b_c\bch\bhe\bec\bck\bk
+ post_moderated $\b$n\bnn\bnt\btp\bp_\b_p\bpo\bos\bst\bt_\b_m\bmo\bod\bde\ber\bra\bat\bte\bed\bd
+ save_unsubscribed $\b$n\bnn\bnt\btp\bp_\b_s\bsa\bav\bve\be_\b_u\bun\bns\bsu\bub\bbs\bsc\bcr\bri\bib\bbe\bed\bd
+ show_new_news $\b$n\bnn\bnt\btp\bp_\b_s\bsh\bho\bow\bw_\b_n\bne\bew\bw_\b_n\bne\bew\bws\bs
+ show_only_unread $\b$n\bnn\bnt\btp\bp_\b_s\bsh\bho\bow\bw_\b_o\bon\bnl\bly\by_\b_u\bun\bnr\bre\bea\bad\bd
+ x_comment_to $\b$n\bnn\bnt\btp\bp_\b_x\bx_\b_c\bco\bom\bmm\bme\ben\bnt\bt_\b_t\bto\bo
+ smtp_auth_username $\b$s\bsm\bmt\btp\bp_\b_u\bus\bse\ber\br
+ smtp_auth_password $\b$s\bsm\bmt\btp\bp_\b_p\bpa\bas\bss\bs
+ user_agent $\b$a\bag\bge\ben\bnt\bt_\b_s\bst\btr\bri\bin\bng\bg
+
+ The contrib subdirectory contains a script named update-config.pl
+ which eases migration.
- 11.1. Linking threads
+ A complete list of current variables follows.
- 11.2. Breaking threads
+1. $abort_noattach
- 12. Delivery Status Notification (DSN) Support
+ Type: quadoption
- 13. POP3 Support (OPTIONAL)
+ Default: no
- 14. IMAP Support (OPTIONAL)
+ 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 $\b$a\bat\btt\bta\bac\bch\bh_\b_r\bre\bem\bmi\bin\bnd\bd_\b_r\bre\beg\bge\bex\bxp\bp. If a match was
+ found and this variable is set to _\by_\be_\bs, message sending will be aborted
+ but the mail will be send nevertheless if set to _\bn_\bo.
- 14.1. The Folder Browser
+ This variable and $\b$a\bat\btt\bta\bac\bch\bh_\b_r\bre\bem\bmi\bin\bnd\bd_\b_r\bre\beg\bge\bex\bxp\bp are intended to remind the
+ user to attach files if the message's text references them.
- 14.2. Authentication
+ See also the $\b$a\bat\btt\bta\bac\bch\bh_\b_r\bre\bem\bmi\bin\bnd\bd_\b_r\bre\beg\bge\bex\bxp\bp variable.
- 15. NNTP Support (OPTIONAL)
+2. $abort_nosubject
- 15.1. Again: Scoring
+ Type: quadoption
- 16. SMTP Support (OPTIONAL)
+ Default: ask-yes
- 17. Managing multiple IMAP/POP/NNTP accounts (OPTIONAL)
+ If set to _\by_\be_\bs, when composing messages and no subject is given at the
+ subject prompt, composition will be aborted. If set to _\bn_\bo, composing
+ messages with no subject given at the subject prompt will never be
+ aborted.
- 18. Start a WWW Browser on URLs (EXTERNAL)
+3. $abort_unmodified
- 19. Compressed folders Support (OPTIONAL)
+ Type: quadoption
- 19.1. Open a compressed mailbox for reading
+ Default: yes
- 19.2. Write a compressed mailbox
+ If set to _\by_\be_\bs, composition will automatically abort after editing the
+ message body if no changes are made to the file (this check only
+ happens after the _\bf_\bi_\br_\bs_\bt edit of the file). When set to _\bn_\bo, composition
+ will never be aborted.
- 19.3. Append a message to a compressed mailbox
+4. $agent_string
- 19.4. Encrypted folders
+ Type: boolean
-1. Regular Expressions
+ Default: yes
- 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.
+ When _\bs_\be_\bt, Mutt-ng will add a ``User-Agent:'' header to outgoing
+ messages, indicating which version of Mutt-ng was used for composing
+ them.
- 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:
- ``\\''.
+5. $alias_file
- 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.
+ Type: path
- 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).
+ Default: "~/.muttngrc"
- 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 default file in which to save aliases created by the
+ ``c\bcr\bre\bea\bat\bte\be-\b-a\bal\bli\bia\bas\bs'' function.
- 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.
+ _\bN_\bo_\bt_\be_\b: Mutt-ng will not automatically source this file; you must
+ explicitly use the ``s\bso\bou\bur\brc\bce\be'' command for it to be executed.
- 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.
+6. $alias_format
- 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:
+ Type: string
- [:alnum:]
+ Default: "%4n %2f %t %-10a %r"
- Alphanumeric characters.
+ Specifies the format of the data displayed for the ``alias'' menu. The
+ following printf(3)-style sequences are available:
- [:alpha:]
+ %a
+ alias name
- Alphabetic characters.
+ %f
+ flags - currently, a "d" for an alias marked for deletion
- [:blank:]
+ %n
+ index number
- Space or tab characters.
+ %r
+ address which alias expands to
- [:cntrl:]
+ %t
+ character which indicates if the alias is tagged for inclusion
- Control characters.
+7. $allow_8bit
- [:digit:]
+ Type: boolean
- Numeric characters.
+ Default: yes
- [:graph:]
+ Controls whether 8-bit data is converted to 7-bit using either
+ quoted-printable or base64 encoding when sending mail.
- Characters that are both printable and visible. (A space is
- printable, but not visible, while an ``a'' is both.)
+8. $allow_ansi
- [:lower:]
+ Type: boolean
- Lower-case alphabetic characters.
+ Default: no
- [:print:]
+ 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.
- Printable characters (characters that are not control characters.)
+9. $arrow_cursor
- [:punct:]
+ Type: boolean
- Punctuation characters (characters that are not letter, digits,
- control characters, or space characters).
+ Default: no
- [:space:]
+ When _\bs_\be_\bt, 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.
- Space characters (such as space, tab and formfeed, to name a few).
+10. $ascii_chars
- [:upper:]
+ Type: boolean
- Upper-case alphabetic characters.
+ Default: no
- [:xdigit:]
+ If _\bs_\be_\bt, Mutt-ng will use plain ASCII characters when displaying thread
+ and attachment trees, instead of the default ACS characters.
- Characters that are hexadecimal digits.
+11. $askbcc
- 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].
+ Type: boolean
- 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:
+ Default: no
- Collating Symbols
+ If _\bs_\be_\bt, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients
+ before editing an outgoing message.
- 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''.
+12. $askcc
- Equivalence Classes
+ Type: boolean
- 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''.
+ Default: no
- A regular expression matching a single character may be followed by one of
- several repetition operators:
+ If _\bs_\be_\bt, Mutt-ng will prompt you for carbon-copy (Cc) recipients before
+ editing the body of an outgoing message.
- ?
+13. $assumed_charset
- The preceding item is optional and matched at most once.
+ Type: string
- *
+ Default: "us-ascii"
- The preceding item will be matched zero or more times.
+ 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:
- The preceding item will be matched one or more times.
+ set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
- {n}
+ However, only the first content is valid for the message body. This
+ variable is valid only if $\b$s\bst\btr\bri\bic\bct\bt_\b_m\bmi\bim\bme\be is unset.
- The preceding item is matched exactly n times.
+14. $attach_format
- {n,}
+ Type: string
- The preceding item is matched n or more times.
+ Default: "%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] "
- {,m}
+ This variable describes the format of the ``attachment'' menu. The
+ following printf(3)-style sequences are understood:
- The preceding item is matched at most m times.
+ %C
+ charset
- {n,m}
+ %c
+ requires charset conversion (n or c)
- The preceding item is matched at least n times, but no more than m
- times.
+ %D
+ deleted flag
- Two regular expressions may be concatenated; the resulting regular
- expression matches any string formed by concatenating two substrings that
- respectively match the concatenated subexpressions.
+ %d
+ description
- Two regular expressions may be joined by the infix operator ``|''; the
- resulting regular expression matches any string matching either
- subexpression.
+ %e
+ MIME Content-Transfer-Encoding: header field
- 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.
+ %f
+ filename
- Note: If you compile Mutt-ng with the GNU rx package, the following
- operators may also be used in regular expressions:
+ %I
+ MIME Content-Disposition: header field (I=inline, A=attachment)
- \\y
+ %m
+ major MIME type
- Matches the empty string at either the beginning or the end of a
- word.
+ %M
+ MIME subtype
- \\B
+ %n
+ attachment number
- Matches the empty string within a word.
+ %Q
+ "Q", if MIME part qualifies for attachment counting
- \\<
+ %s
+ size
- Matches the empty string at the beginning of a word.
+ %t
+ tagged flag
- \\>
+ %T
+ graphic tree characters
- Matches the empty string at the end of a word.
+ %u
+ unlink (=to delete) flag
- \\w
+ %X
+ number of qualifying MIME parts in this part and its children
- Matches any word-constituent character (letter, digit, or
- underscore).
+ %>X
+ right justify the rest of the string and pad with character "X"
- \\W
+ %|X
+ pad to the end of the line with character "X"
- Matches any character that is not word-constituent.
+15. $attach_remind_regexp
- \\`
+ Type: regular expression
- Matches the empty string at the beginning of a buffer (string).
+ 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 $\b$a\bab\bbo\bor\brt\bt_\b_n\bno\boa\bat\btt\bta\bac\bch\bh.
- Matches the empty string at the end of a buffer.
+ This variable and $\b$a\bab\bbo\bor\brt\bt_\b_n\bno\boa\bat\btt\bta\bac\bch\bh are intended to remind the user to
+ attach files if the message's text references them.
- 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.
+16. $attach_sep
-2. Patterns
+ Type: string
- 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.
+ Default: "\n"
- 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.
+ The separator to add between attachments when operating (saving,
+ printing, piping, etc) on a list of tagged attachments.
- 2.1. Complex Patterns
+17. $attach_split
- 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.
+ If this variable is _\bu_\bn_\bs_\be_\bt, 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
+ ``$\b$a\bat\btt\bta\bac\bch\bh_\b_s\bse\bep\bp'' separator is added after each attachment. When _\bs_\be_\bt,
+ Mutt-ng will operate on the attachments one by one.
- To logical OR patterns, simply use the | operator. This one especially
- useful when using local groups:
+18. $attribution
- ~f ("nion@muttng\.org"|"ak@muttng\.org"|"pdmef@muttng\.org")
- (~b mutt-ng|~s Mutt-ng)
- !~x '@synflood\.at'
+ Type: string
- 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.
+ Default: "On %d, %n wrote:"
- 2.2. Patterns and Dates
+ 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 ``$\b$i\bin\bnd\bde\bex\bx_\b_f\bfo\bor\brm\bma\bat\bt''.
- 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.
+19. $auto_tag
- 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).
+ Type: boolean
- 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:
+ Default: no
- ~d >2w # messages older than two weeks
- ~d <3d # messages newer than 3 days
- ~d =1m # messages that are exactly one month old
+ When _\bs_\be_\bt, functions in the _\bi_\bn_\bd_\be_\bx 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.
-3. Format Strings
+20. $autoedit
- 3.1. Introduction
+ Type: boolean
- 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.
+ Default: no
- 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.
+ When _\bs_\be_\bt along with ``$\b$e\bed\bdi\bit\bt_\b_h\bhe\bea\bad\bde\ber\brs\bs'', 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.
- 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:
+ Also see ``$\b$f\bfa\bas\bst\bt_\b_r\bre\bep\bpl\bly\by''.
- o the current hostname
+21. $beep
- o the current mutt-ng version number
+ Type: boolean
- 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:
+ Default: yes
- set status_format = "%v on %h: ..."
+ When this variable is _\bs_\be_\bt, Mutt-ng will beep when an error occurs.
- 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:
+22. $beep_new
- Mutt-ng 1.5.9i on mailhost: ...
+ Type: boolean
- In the index, there're more useful information one could want to see:
+ Default: no
- o which mailbox is open
+ When this variable is _\bs_\be_\bt, Mutt-ng will beep whenever it prints a
+ message notifying you of new mail. This is independent of the setting
+ of the ``$\b$b\bbe\bee\bep\bp'' variable.
- o how man new, flagged or postponed messages
+23. $bounce
- o ...
+ Type: quadoption
- To include the mailbox' name is as easy as:
+ Default: ask-yes
- set status_format = "%v on %h: %B: ...
+ Controls whether you will be asked to confirm bouncing messages. If
+ set to _\by_\be_\bs you don't get asked if you want to bounce a message.
+ Setting this variable to _\bn_\bo is not generally useful, and thus not
+ recommended, because you are unable to bounce messages.
- When the currently opened mailbox is Inbox, this will be expanded to:
+24. $bounce_delivered
- Mutt-ng 1.5.9i on mailhost: Inbox: ...
+ Type: boolean
- 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.
+ Default: yes
- 3.2. Conditional Expansion
+ When this variable is _\bs_\be_\bt, Mutt-ng will include Delivered-To: header
+ fields when bouncing messages. Postfix users may wish to _\bu_\bn_\bs_\be_\bt this
+ variable.
- To only print the number of messages if there are new messages in the
- current mailbox, further extend $status_format to:
+25. $braille_friendly
- set status_format = "%v on %h: %B %?n?%n new? ...
+ Type: boolean
- 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:
+ Default: no
- %?<item>?<string if nonzero>?
+ 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.
- 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.
+26. $certificate_file
- 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:
+ Type: path
- %?<item>?<string if nonzero>&<string if zero>?
+ Default: "~/.mutt_certificates"
- Using this we can make mutt-ng to do the following:
+ Availability: SSL or GNUTLS
- o make it print ``n new messages'' whereby n is the count but only if
- there new ones
+ 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.
- o and make it print ``no new messages'' if there aren't any
+ 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.
- The corresponding configuration is:
+ Example: set certificate_file=~/.muttng/certificates
- set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ...
+27. $charset
- This doubles the use of the ``new messages'' string because it'll get
- always printed. Thus, it can be shortened to:
+ Type: string
- set status_format = "%v on %h: %B: %?n?%n&no? new messages ...
+ Default: ""
- 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.
+ Character set your terminal uses to display and enter textual data.
- 3.3. Modifications and Padding
+28. $check_new
- Besides the information given so far, there're even more features of
- format strings:
+ Type: boolean
- o When specifying %_<item> instead of just %<item>, mutt-ng will convert
- all characters in the expansion of <item> to lowercase.
+ Default: yes
- o When specifying %:<item> instead of just %<item>, mutt-ng will convert
- all dots in the expansion of <item> to underscores (_).
+ _\bN_\bo_\bt_\be_\b: this option only affects _\bm_\ba_\bi_\bl_\bd_\bi_\br and _\bM_\bH style mailboxes.
- Also, there's a feature called Padding supplied by the following two
- expandos: %|X and %>X .
+ When _\bs_\be_\bt, 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 _\bu_\bn_\bs_\be_\bt, no check
+ for new mail is performed while the mailbox is open.
- %|X
+29. $collapse_unread
- 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:
+ Type: boolean
- set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-"
+ Default: yes
- %>X
+ When _\bu_\bn_\bs_\be_\bt, Mutt-ng will not collapse a thread if it contains any
+ unread messages.
- 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 %>):
+30. $compose_format
- set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)"
+ Type: string
-4. Using Tags
+ Default: "-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-"
- 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.
+ Controls the format of the status line displayed in the ``compose''
+ menu. This string is similar to ``$\b$s\bst\bta\bat\btu\bus\bs_\b_f\bfo\bor\brm\bma\bat\bt'', but has its own
+ set of printf(3)-like sequences:
-5. Using Hooks
+ %a
+ total number of attachments
- 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
+ %h
+ local hostname
- o folder-hook
+ %l
+ approximate size (in bytes) of the current message
- o send-hook
+ %v
+ Mutt-ng version string
- o message-hook
+ See the text describing the ``$\b$s\bst\bta\bat\btu\bus\bs_\b_f\bfo\bor\brm\bma\bat\bt'' option for more
+ information on how to set ``$\b$c\bco\bom\bmp\bpo\bos\bse\be_\b_f\bfo\bor\brm\bma\bat\bt''.
- o save-hook
+31. $config_charset
- o mbox-hook
+ Type: string
- o fcc-hook
+ Default: ""
- o fcc-save-hook
+ When defined, Mutt-ng will recode commands in rc files from this
+ encoding.
- for specific details on each type of hook available.
+32. $confirmappend
- 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:
+ Type: boolean
- send-hook . 'unmy_hdr From:'
- send-hook '~C ^b@b\.b$' my-hdr from: c@c.c
+ Default: yes
- 5.1. Message Matching in Hooks
+ When _\bs_\be_\bt, Mutt-ng will prompt for confirmation when appending messages
+ to an existing mailbox.
- 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.
+33. $confirmcreate
- 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.).
+ Type: boolean
- For example, if you wanted to set your return address based upon sending
- mail to a specific address, you could do something like:
+ Default: yes
- send-hook '~t ^me@cs\.hmc\.edu$' 'my-hdr From: Mutt-ng User <user@host>'
+ When _\bs_\be_\bt, Mutt-ng will prompt for confirmation when saving messages to
+ a mailbox which does not yet exist before creating it.
- which would execute the given command when sending mail to me@cs.hmc.edu.
+34. $connect_timeout
- 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.
+ Type: number
-6. Using the sidebar
+ Default: 30
- 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:
+ 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.
- set sidebar_visible="yes"
- set sidebar_width=25
+35. $content_type
- If you want to specify the mailboxes you can do so with:
+ Type: string
- set mbox='=INBOX'
- mailboxes INBOX \
- MBOX1 \
- MBOX2 \
- ...
+ Default: "text/plain"
- You can also specify the colors for mailboxes with new mails by using:
+ Sets the default Content-Type: header field for the body of newly
+ composed messages.
- color sidebar_new red black
- color sidebar white black
+36. $copy
- Reasonable key bindings look e.g. like this:
+ Type: quadoption
- 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
+ Default: yes
- macro index B ':toggle sidebar_visible^M'
- macro pager B ':toggle sidebar_visible^M'
+ This variable controls whether or not copies of your outgoing messages
+ will be saved for later references. Also see ``$\b$r\bre\bec\bco\bor\brd\bd'',
+ ``$\b$s\bsa\bav\bve\be_\b_n\bna\bam\bme\be'', ``$\b$f\bfo\bor\brc\bce\be_\b_n\bna\bam\bme\be'' and `` \b f\bfc\bcc\bc-\b-h\bho\boo\bok\bk''.
- 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'.
+37. $count_attachments
-7. External Address Queries
+ Type: boolean
- 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:
+ Default: yes
- set query_command = "mutt_ldap_query.pl '%s'"
+ 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.
- 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.
+ If it is _\bs_\be_\bt and rules were defined via the attachments and/or
+ unattachments commands, counting will be done. If it is _\bu_\bn_\bs_\be_\bt no
+ counting will be done regardless whether rules were defined or not.
- An example multiple response output:
+38. $crypt_autoencrypt
- 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
+ Type: boolean
- 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.
+ Default: no
- 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.
+ Setting this variable will cause Mutt-ng to always attempt to PGP
+ encrypt outgoing messages. This is probably only useful in connection
+ to the _\bs_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk command. It can be overridden by use of the _\bp_\bg_\bp_\b-_\bm_\be_\bn_\bu,
+ when encryption is not required or signing is requested as well. If
+ ``$\b$s\bsm\bmi\bim\bme\be_\b_i\bis\bs_\b_d\bde\bef\bfa\bau\bul\blt\bt'' is _\bs_\be_\bt, then OpenSSL is used instead to create
+ S/MIME messages and settings can be overridden by use of the
+ _\bs_\bm_\bi_\bm_\be_\b-_\bm_\be_\bn_\bu. (Crypto only)
-8. Mailbox Formats
+39. $crypt_autopgp
- 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.
+ Type: boolean
- 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:
+ Default: yes
- From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
+ This variable controls whether or not Mutt-ng may automatically enable
+ PGP encryption/signing for messages. See also ``$\b$c\bcr\bry\byp\bpt\bt_\b_a\bau\but\bto\boe\ben\bnc\bcr\bry\byp\bpt\bt'',
+ ``$\b$c\bcr\bry\byp\bpt\bt_\b_r\bre\bep\bpl\bly\bye\ben\bnc\bcr\bry\byp\bpt\bt'', ``$\b$c\bcr\bry\byp\bpt\bt_\b_a\bau\but\bto\bos\bsi\big\bgn\bn'', ``$\b$c\bcr\bry\byp\bpt\bt_\b_r\bre\bep\bpl\bly\bys\bsi\big\bgn\bn'' and
+ ``$\b$s\bsm\bmi\bim\bme\be_\b_i\bis\bs_\b_d\bde\bef\bfa\bau\bul\blt\bt''.
- to denote the start of a new message (this is often referred to as the
- ``From_'' line).
+40. $crypt_autosign
- MMDF. This is a variant of the mbox format. Each message is surrounded by
- lines containing ``^A^A^A^A'' (four control-A's).
+ Type: boolean
- 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.
+ Default: no
-9. Mailbox Shortcuts
+ Setting this variable will cause Mutt-ng to always attempt to
+ cryptographically sign outgoing messages. This can be overridden by
+ use of the _\bp_\bg_\bp_\b-_\bm_\be_\bn_\bu, when signing is not required or encryption is
+ requested as well. If ``$\b$s\bsm\bmi\bim\bme\be_\b_i\bis\bs_\b_d\bde\bef\bfa\bau\bul\blt\bt'' is _\bs_\be_\bt, then OpenSSL is
+ used instead to create S/MIME messages and settings can be overridden
+ by use of the _\bs_\bm_\bi_\bm_\be_\b-_\bm_\be_\bn_\bu. (Crypto only)
- 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.
+41. $crypt_autosmime
- o ! -- refers to your $spoolfile (incoming) mailbox
+ Type: boolean
- o > -- refers to your $mbox file
+ Default: yes
- o < -- refers to your $record file
+ This variable controls whether or not Mutt-ng may automatically enable
+ S/MIME encryption/signing for messages. See also
+ ``$\b$c\bcr\bry\byp\bpt\bt_\b_a\bau\but\bto\boe\ben\bnc\bcr\bry\byp\bpt\bt'', ``$\b$c\bcr\bry\byp\bpt\bt_\b_r\bre\bep\bpl\bly\bye\ben\bnc\bcr\bry\byp\bpt\bt'', ``$\b$c\bcr\bry\byp\bpt\bt_\b_a\bau\but\bto\bos\bsi\big\bgn\bn'',
+ ``$\b$c\bcr\bry\byp\bpt\bt_\b_r\bre\bep\bpl\bly\bys\bsi\big\bgn\bn'' and ``$\b$s\bsm\bmi\bim\bme\be_\b_i\bis\bs_\b_d\bde\bef\bfa\bau\bul\blt\bt''.
- o ^ -- refers to the current mailbox
+42. $crypt_replyencrypt
- o - or !! -- refers to the file you've last visited
+ Type: boolean
- o ~ -- refers to your home directory
+ Default: yes
- o = or + -- refers to your $folder directory
+ If _\bs_\be_\bt, automatically PGP or OpenSSL encrypt replies to messages which
+ are encrypted. (Crypto only)
- o @alias -- refers to the save-hook as determined by the address of the
- alias
+43. $crypt_replysign
-10. Handling Mailing Lists
+ Type: boolean
- 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.
+ Default: no
- 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.
+ If _\bs_\be_\bt, automatically PGP or OpenSSL sign replies to messages which
+ are signed.
- 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.
+ _\bN_\bo_\bt_\be_\b: this does not work on messages that are encrypted _\ba_\bn_\bd signed!
+ (Crypto only)
- 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.
+44. $crypt_replysignencrypted
- 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.
+ Type: boolean
-11. Editing threads
+ Default: no
- 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.
+ If _\bs_\be_\bt, automatically PGP or OpenSSL sign replies to messages which
+ are encrypted. This makes sense in combination with
+ ``$\b$c\bcr\bry\byp\bpt\bt_\b_r\bre\bep\bpl\bly\bye\ben\bnc\bcr\bry\byp\bpt\bt'', because it allows you to sign all messages
+ which are automatically encrypted. This works around the problem noted
+ in ``$\b$c\bcr\bry\byp\bpt\bt_\b_r\bre\bep\bpl\bly\bys\bsi\big\bgn\bn'', that Mutt-ng is not able to find out whether
+ an encrypted message is also signed. (Crypto only)
- 11.1. Linking threads
+45. $crypt_timestamp
- 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.
+ Type: boolean
- You can also connect multiple children at once, tagging them and using the
- tag-prefix command (';') or the auto_tag option.
+ Default: yes
- 11.2. Breaking threads
+ If _\bs_\be_\bt, 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 _\bu_\bn_\bs_\be_\bt
+ this setting. (Crypto only)
- 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.
+46. $crypt_use_gpgme
-12. Delivery Status Notification (DSN) Support
+ Type: boolean
- 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.''
+ Default: no
- Users can make use of it in one of the following two ways:
+ This variable controls the use the GPGME enabled crypto backends. If
+ it is _\bs_\be_\bt and Mutt-ng was build with gpgme support, the gpgme code for
+ S/MIME and PGP will be used instead of the classic code.
- 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.
+ _\bN_\bo_\bt_\be: You need to use this option in your .muttngrc configuration file
+ as it won't have any effect when used interactively.
- o The SMTP support via libESMTP supports it, too.
+47. $crypt_verify_sig
- To support this, there are two variables:
+ Type: quadoption
- o $dsn_notify is used to request receipts for different results (such as
- failed message,message delivered, etc.).
+ Default: yes
- o $dsn_return requests how much of your message should be returned with
- the receipt (headers or full message).
+ If ``_\by_\be_\bs'', always attempt to verify PGP or S/MIME signatures. If
+ ``_\ba_\bs_\bk'', ask whether or not to verify the signature. If ``_\bn_\bo'', never
+ attempt to verify cryptographic signatures. (Crypto only)
- Please see the reference chapter for possible values.
+48. $date_format
-13. POP3 Support (OPTIONAL)
+ Type: string
- 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.
+ Default: "!%a, %b %d, %Y at %I:%M:%S%p %Z"
- You can access the remote POP3 mailbox by selecting the folder
- pop://popserver/.
+ This variable controls the format of the date printed by the ``%d''
+ sequence in ``$\b$i\bin\bnd\bde\bex\bx_\b_f\bfo\bor\brm\bma\bat\bt''. This is passed to strftime(3) to
+ process the date.
- You can select an alternative port by specifying it with the server, i.e.:
- pop://popserver:port/.
+ 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 ``$\b$l\blo\boc\bca\bal\ble\be''. 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 _\bC locale (that is in US
+ English).
- You can also specify different username for each folder, i.e.:
- pop://username@popserver[:port]/.
+49. $debug_level
- 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.
+ Type: number
- 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]/.
+ Default: 1
- 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.
+ Availability: debug
- Note: If you only need to fetch all messages to local mailbox you should
- consider using a specialized program, such as fetchmail(1).
+ 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.
-14. IMAP Support (OPTIONAL)
+ 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.
- 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.
+50. $default_hook
- You can access the remote inbox by selecting the folder via its URL:
+ Type: string
- imap://imapserver/INBOX
+ Default: "~f %s !~P | (~P ~C %s)"
- 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
+ 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.
- imap://imapserver/path/to/folder
+51. $delete
- 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.:
+ Type: quadoption
- imap://imapserver:port/INBOX
+ Default: ask-yes
- You can also specify different username for each folder by prenpending
- your username and an @ symbol to the server's name.
+ Controls whether or not messages are really deleted when closing or
+ synchronizing a mailbox. If set to _\by_\be_\bs, messages marked for deleting
+ will automatically be purged without prompting. If set to _\bn_\bo, messages
+ marked for deletion will be kept in the mailbox.
- 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.
+52. $delete_space
- 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.
+ Type: boolean
- 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.
+ Default: no
- 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.
+ When sending messages with format=flowed by _\bs_\be_\bt_\bt_\bi_\bn_\bg the $\b$t\bte\bex\bxt\bt_\b_f\bfl\blo\bow\bwe\bed\bd
+ variable, this variable specifies whether to also set the DelSp
+ parameter to yes. If this is _\bu_\bn_\bs_\be_\bt, no additional parameter will be
+ send as a value of no already is the default behavior.
- 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.
+ _\bN_\bo_\bt_\be_\b: this variable only has an effect on _\bo_\bu_\bt_\bg_\bo_\bi_\bn_\bg messages (if
+ $\b$t\bte\bex\bxt\bt_\b_f\bfl\blo\bow\bwe\bed\bd is _\bs_\be_\bt) but not on incomming.
- 14.1. The Folder Browser
+53. $delete_untag
- 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:
+ Type: boolean
- 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.
+ Default: yes
- 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).
+ If this option is _\bs_\be_\bt, 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.
- 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).
+54. $digest_collapse
- 14.2. Authentication
+ Type: boolean
- 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".
+ Default: yes
- 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.
+ If this option is _\bs_\be_\bt, 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.
- Mutt-ng will try whichever methods are compiled in and available on the
- server, in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
+55. $display_filter
- There are a few variables which control authentication:
+ Type: path
- 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}).
+ Default: ""
- o $imap_pass - a password which you may preset, used by all
- authentication methods where a password is needed.
+ When _\bs_\be_\bt, specifies a command used to filter messages. When a message
+ is viewed it is passed as standard input to $\b$d\bdi\bis\bsp\bpl\bla\bay\by_\b_f\bfi\bil\blt\bte\ber\br, and the
+ filtered message is read from the standard output.
- 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).
+56. $dotlock_program
-15. NNTP Support (OPTIONAL)
+ Type: path
- 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.
+ Default: "$muttng_bindir/muttng_dotlock"
- 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.
+ Availability: Standalone and Dotlock
- 15.1. Again: Scoring
+ Contains the path of the muttng_dotlock(1) binary to be used by
+ Mutt-ng.
- 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.
+57. $dsn_notify
- 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.
+ Type: string
- In mutt-ng this is as easy as
+ Default: ""
- score ~* =42
+ _\bN_\bo_\bt_\be_\b: 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 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 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: _\bn_\be_\bv_\be_\br, to never request notification, _\bf_\ba_\bi_\bl_\bu_\br_\be, to
+ request notification on transmission failure, _\bd_\be_\bl_\ba_\by, to be notified of
+ message delays, _\bs_\bu_\bc_\bc_\be_\bs_\bs, to be notified of successful transmission.
- score !~* =42
+ Example: set dsn_notify="failure,delay"
- on the contrary applies a score of 42 to all messages not matching those
- criteria which are very strict:
+58. $dsn_return
- o Email addresses must be valid according to RfC 2822
+ Type: string
- 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.
+ Default: ""
- 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.
+ _\bN_\bo_\bt_\be_\b: you should not enable this unless you are using Sendmail 8.8.x
+ or greater or in connection with the SMTP support via libESMTP.
-16. SMTP Support (OPTIONAL)
+ This variable controls how much of your message is returned in DSN
+ messages. It may be set to either _\bh_\bd_\br_\bs to return just the message
+ header, or _\bf_\bu_\bl_\bl to return the full message.
- 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.
+ Example: set dsn_return=hdrs
- 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.
+59. $duplicate_threads
- Authentication mechanisms are available via the $smtp_user and $smtp_pass
- variables.
+ Type: boolean
- 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.
+ Default: yes
- 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.
+ This variable controls whether Mutt-ng, when sorting by threads,
+ threads messages with the same Message-ID: header field together. If
+ it is _\bs_\be_\bt, it will indicate that it thinks they are duplicates of each
+ other with an equals sign in the thread diagram.
-17. Managing multiple IMAP/POP/NNTP accounts (OPTIONAL)
+60. $edit_headers
- 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.
+ Type: boolean
- Some examples:
+ Default: no
- 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"'
+ This option allows you to edit the header of your outgoing messages
+ along with the body of your message.
-18. Start a WWW Browser on URLs (EXTERNAL)
+ Which empty header fields to show is controlled by the $\b$e\bed\bdi\bit\bto\bor\br_\b_h\bhe\bea\bad\bde\ber\brs\bs
+ option.
- 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:
+61. $editor
- macro index \cb |urlview\n
- macro pager \cb |urlview\n
+ Type: path
-19. Compressed folders Support (OPTIONAL)
+ Default: ""
- 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.
+ 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.
- The most common use is to open compressed archived folders e.g. with gzip.
+62. $editor_headers
- 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.
+ Type: string
- 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.
+ Default: "From: To: Cc: Bcc: Subject: Reply-To: Newsgroups:
+ Followup-To: X-Comment-To:"
- For example:
+ If $\b$e\bed\bdi\bit\bt_\b_h\bhe\bea\bad\bde\ber\brs\bs is _\bs_\be_\bt, this space-separated list specifies which
+ _\bn_\bo_\bn_\b-_\be_\bm_\bp_\bt_\by header fields to edit in addition to user-defined headers.
- open-hook \\.gz$ "gzip -cd %f > %t"
- close-hook \\.gz$ "gzip -c %t > %f"
- append-hook \\.gz$ "gzip -c %t >> %f"
+ Note: if $\b$e\bed\bdi\bit\bt_\b_h\bhe\bea\bad\bde\ber\brs\bs had to be turned on by force because
+ $\b$s\bst\btr\bri\bic\bct\bt_\b_m\bma\bai\bil\blt\bto\bo is _\bu_\bn_\bs_\be_\bt, this option has no effect.
- 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.
+63. $encode_from
- 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.
+ Type: boolean
- 19.1. Open a compressed mailbox for reading
+ Default: no
- Usage: open-hookregexp "command"
+ When _\bs_\be_\bt, 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.
- The command is the command that can be used for opening the folders whose
- names match regexp.
+ _\bN_\bo_\bt_\be_\b: as Mutt-ng currently violates RfC3676 defining format=flowed,
+ it's <em/strongly/ advised to _\bs_\be_\bt this option although discouraged by
+ the standard. Alternatively, you must take care of space-stuffing
+ <tt/From / lines (with a trailing space) yourself.
- 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.
+64. $entropy_file
- %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.
+ Type: path
- 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.
+ Default: ""
- Example:
+ Availability: SSL
- open-hook \\.gz$ "gzip -cd %f > %t"
+ The file which includes random data that is used to initialize SSL
+ library functions.
- If the command is empty, this operation is disabled for this file type.
+65. $envelope_from_address
- 19.2. Write a compressed mailbox
+ Type: e-mail address
- Usage: close-hookregexp"command"
+ Default: ""
- This is used to close the folder that was open with the open-hook command
- after some changes were made to it.
+ Manually sets the _\be_\bn_\bv_\be_\bl_\bo_\bp_\be sender for outgoing messages. This value is
+ ignored if ``$\b$u\bus\bse\be_\b_e\ben\bnv\bve\bel\blo\bop\bpe\be_\b_f\bfr\bro\bom\bm'' is unset.
- 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.
+66. $escape
- 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.
+ Type: string
- Example:
+ Default: "~"
- close-hook \\.gz$ "gzip -c %t > %f"
+ Escape character to use for functions in the builtin editor.
- If the command is empty, this operation is disabled for this file type,
- and the file can only be open in the readonly mode.
+67. $fast_reply
- close-hook is not called when you exit from the folder if the folder was
- not changed.
+ Type: boolean
- 19.3. Append a message to a compressed mailbox
+ Default: no
- Usage: append-hookregexp"command"
+ When _\bs_\be_\bt, the initial prompt for recipients and subject are skipped
+ when replying to messages, and the initial prompt for subject is
+ skipped when forwarding messages.
- 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.
+ _\bN_\bo_\bt_\be_\b: this variable has no effect when the ``$\b$a\bau\but\bto\boe\bed\bdi\bit\bt'' variable is
+ _\bs_\be_\bt.
- 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.
+68. $fcc_attach
- Example:
+ Type: boolean
- append-hook \\.gz$ "gzip -c %t >> %f"
+ Default: yes
- 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).
+ This variable controls whether or not attachments on outgoing messages
+ are saved along with the main body of your message.
- 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.
+69. $fcc_clear
- 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.
+ Type: boolean
- 19.4. Encrypted folders
+ Default: no
- 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:
+ When this variable is _\bs_\be_\bt, FCCs will be stored unencrypted and
+ unsigned, even when the actual message is encrypted and/or signed.
+ (PGP only)
- open-hook \\.pgp$ "pgp -f < %f > %t"
- close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
+70. $file_charset
- Please note, that PGP does not support appending to an encrypted folder,
- so there is no append-hook defined.
+ Type: string
- 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.
+ Default: ""
-Chapter 5. Mutt-ng's MIME Support
+ This variable is a colon-separated list of character encoding schemes
+ for text file attatchments. If _\bu_\bn_\bs_\be_\bt, $\b$c\bch\bha\bar\brs\bse\bet\bt value will be used
+ instead. For example, the following configuration would work for
+ Japanese text handling:
- Table of Contents
+ set file_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
- 1. Using MIME in Mutt
+ Note: ``iso-2022-*'' must be put at the head of the value as shown
+ above if included.
- 1.1. Viewing MIME messages in the pager
+71. $folder
- 1.2. The Attachment Menu
+ Type: path
- 1.3. The Compose Menu
+ Default: "~/Mail"
- 2. MIME Type configuration with mime.types
+ 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 _\bb_\be_\bf_\bo_\br_\be you use ``+''
+ or ``='' for any other variables since expansion takes place during
+ the ``set'' command.
- 3. MIME Viewer configuration with mailcap
+72. $folder_format
- 3.1. The Basics of the mailcap file
+ Type: string
- 3.2. Secure use of mailcap
+ Default: "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"
- 3.3. Advanced mailcap Usage
+ This variable allows you to customize the file browser display to your
+ personal taste. This string is similar to ``$\b$i\bin\bnd\bde\bex\bx_\b_f\bfo\bor\brm\bma\bat\bt'', but has
+ its own set of printf(3)-like sequences:
- 3.4. Example mailcap files
+ %C
+ current file number
- 4. MIME Autoview
+ %d
+ date/time folder was last modified
- 5. MIME Multipart/Alternative
+ %f
+ filename
- 6. Attachment Searching and Counting
+ %F
+ file permissions
- 7. MIME Lookup
+ %g
+ group name (or numeric gid, if missing)
- 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.
+ %l
+ number of hard links
-1. Using MIME in Mutt
+ %N
+ N if folder has new mail, blank otherwise
- 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.
+ %s
+ size in bytes
- 1.1. Viewing MIME messages in the pager
+ %t
+ * if the file is tagged, blank otherwise
- 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.
+ %u
+ owner name (or numeric uid, if missing)
- Mutt-ng will denote attachments with a couple lines describing them. These
- lines are of the form:
+ %>X
+ right justify the rest of the string and pad with character "X"
- [-- Attachment #1: Description --]
- [-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
+ %|X
+ pad to the end of the line with 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.
+73. $followup_to
- If Mutt-ng cannot deal with a MIME type, it will display a message like:
+ Type: boolean
- [-- image/gif is unsupported (use 'v' to view this part) --]
+ Default: yes
- 1.2. The Attachment Menu
+ Controls whether or not the Mail-Followup-To: header field is
+ generated when sending mail. When _\bs_\be_\bt, Mutt-ng will generate this
+ field when you are replying to a known mailing list, specified with
+ the ``subscribe'' or ``l\bli\bis\bst\bts\bs'' commands or detected by common mailing
+ list headers.
- 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.
+ 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.
- Finally, you can apply the usual message-related functions (like
- <resend-message>, and the reply and forward functions) to attachments of
- type message/rfc822.
+74. $force_buffy_check
- 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 _\bs_\be_\bt, it causes Mutt-ng to check for new mail when the _\bb_\bu_\bf_\bf_\by_\b-_\bl_\bi_\bs_\bt
+ command is invoked. When _\bu_\bn_\bs_\be_\bt, _\bb_\bu_\bf_\bf_\by_\b__\bl_\bi_\bs_\bt will just list all
+ mailboxes which are already known to have new mail.
- Attachments appear as follows:
+ Also see the following variables: ``$\b$t\bti\bim\bme\beo\bou\but\bt'', ``$\b$m\bma\bai\bil\bl_\b_c\bch\bhe\bec\bck\bk'' and
+ ``$\b$i\bim\bma\bap\bp_\b_m\bma\bai\bil\bl_\b_c\bch\bhe\bec\bck\bk''.
- 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>
+75. $force_list_reply
- 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: quadoption
-2. MIME Type configuration with mime.types
+ Default: ask-no
- 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.
+ This variable controls what effect ordinary replies have on mailing
+ list messages: if _\bs_\be_\bt, a normal reply will be interpreted as
+ list-reply while if it's _\bu_\bn_\bs_\be_\bt the reply functions work as usual.
-3. MIME Viewer configuration with mailcap
+76. $force_name
- 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.
+ Type: boolean
- 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
+ Default: no
- ${HOME}/.mailcap:/usr/local/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap
+ This variable is similar to ``$\b$s\bsa\bav\bve\be_\b_n\bna\bam\bme\be'', 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.
- where $HOME is your home directory.
+ Also see the ``$\b$r\bre\bec\bco\bor\brd\bd'' variable.
- In particular, the metamail distribution will install a mailcap file,
- usually as /usr/local/etc/mailcap, which contains some baseline entries.
+77. $forward_decode
- 3.1. The Basics of the mailcap file
+ Type: boolean
- A mailcap file consists of a series of lines which are comments, blank, or
- definitions.
+ Default: yes
- A comment line consists of a # character followed by anything you want.
+ 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 ``$\b$m\bmi\bim\bme\be_\b_f\bfo\bor\brw\bwa\bar\brd\bd'' is _\bu_\bn_\bs_\be_\bt, otherwise
+ ``$\b$m\bmi\bim\bme\be_\b_f\bfo\bor\brw\bwa\bar\brd\bd_\b_d\bde\bec\bco\bod\bde\be'' is used instead.
- A blank line is blank.
+78. $forward_decrypt
- 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: boolean
- So, in the simplest form, you can send a text/plain message to the
- external pager more on stdin:
+ Default: yes
- text/plain; more
+ Controls the handling of encrypted messages when forwarding a message.
+ When _\bs_\be_\bt, the outer layer of encryption is stripped off. This variable
+ is only used if ``$\b$m\bmi\bim\bme\be_\b_f\bfo\bor\brw\bwa\bar\brd\bd'' is _\bs_\be_\bt and ``$\b$m\bmi\bim\bme\be_\b_f\bfo\bor\brw\bwa\bar\brd\bd_\b_d\bde\bec\bco\bod\bde\be''
+ is _\bu_\bn_\bs_\be_\bt. (PGP only)
- Or, you could send the message as a file:
+79. $forward_edit
- text/plain; more %s
+ Type: quadoption
- Perhaps you would like to use lynx to interactively view a text/html
- message:
+ Default: yes
- text/html; lynx %s
+ 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 _\bn_\bo.
- 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.
+80. $forward_format
- 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:
+ Type: string
- text/html; lynx -dump %s | more
+ Default: "[%a: %s]"
- 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:
+ This variable controls the default subject when forwarding a message.
+ It uses the same format sequences as the ``$\b$i\bin\bnd\bde\bex\bx_\b_f\bfo\bor\brm\bma\bat\bt'' variable.
- text/html; lynx %s
- text/*; more
+81. $forward_quote
- This is the simplest form of a mailcap file.
+ Type: boolean
- 3.2. Secure use of mailcap
+ Default: no
- 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.
+ When _\bs_\be_\bt forwarded messages included in the main body of the message
+ (when ``$\b$m\bmi\bim\bme\be_\b_f\bfo\bor\brw\bwa\bar\brd\bd'' is _\bu_\bn_\bs_\be_\bt) will be quoted using
+ ``$\b$i\bin\bnd\bde\ben\bnt\bt_\b_s\bst\btr\bri\bin\bng\bg''.
- 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:
+82. $from
- 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.
+ Type: e-mail address
- 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):
+ Default: ""
- text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
- && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
+ This variable contains a default from address. It can be overridden
+ using my_hdr (including from send-hooks) and ``$\b$r\bre\bev\bve\ber\brs\bse\be_\b_n\bna\bam\bme\be''. This
+ variable is ignored if ``$\b$u\bus\bse\be_\b_f\bfr\bro\bom\bm'' is unset.
- 3.3. Advanced mailcap Usage
+ 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.
- 3.3.1. Optional Fields
+ Defaults to the contents of the environment variable $EMAIL.
- 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:
+83. $gecos_mask
- copiousoutput
+ Type: regular expression
- 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:
+ Default: "^[^,]*"
- text/html; lynx -dump %s ; copiousoutput
+ 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 will cause lynx to format the text/html output as text/plain
- and Mutt-ng will use your standard pager to display the results.
+ 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''.
- needsterminal
+84. $hdrs
- 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.
+ Type: boolean
- compose=<command>
+ Default: yes
- 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.
+ When _\bu_\bn_\bs_\be_\bt, the header fields normally added by the ``m\bmy\by_\b_h\bhd\bdr\br'' command
+ are not created. This variable _\bm_\bu_\bs_\bt be _\bu_\bn_\bs_\be_\bt before composing a new
+ message or replying in order to take effect. If _\bs_\be_\bt, the user defined
+ header fields are added to every new message.
- composetyped=<command>
+85. $header
- 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.
+ Type: boolean
- print=<command>
+ Default: no
- This flag specifies the command to use to print a specific MIME
- type. Mutt-ng supports this from the attachment and compose menus.
+ When _\bs_\be_\bt, this variable causes Mutt-ng to include the header of the
+ message you are replying to into the edit buffer. The ``$\b$w\bwe\bee\bed\bd''
+ setting applies.
- edit=<command>
+86. $header_cache
- 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.
+ Type: path
- nametemplate=<template>
+ Default: ""
- 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:
+ Availability: Header Cache
- text/html; lynx %s; nametemplate=%s.html
+ The $\b$h\bhe\bea\bad\bde\ber\br_\b_c\bca\bac\bch\bhe\be variable points to the header cache database.
- test=<command>
+ If $\b$h\bhe\bea\bad\bde\ber\br_\b_c\bca\bac\bch\bhe\be points to a directory it will contain a header cache
+ database per folder. If $\b$h\bhe\bea\bad\bde\ber\br_\b_c\bca\bac\bch\bhe\be points to a file that file will
+ be a single global header cache. By default it is _\bu_\bn_\bs_\be_\bt so no header
+ caching will be used.
- 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.
+87. $header_cache_compress
- 3.3.3. Command Expansion
+ Type: boolean
- 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:
+ Default: no
- %s
+ 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.
- 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.
+88. $help
- %t
+ Type: boolean
- 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.
+ Default: yes
- %{<parameter>}
+ When _\bs_\be_\bt, help lines describing the bindings for the major functions
+ provided by each menu are displayed on the first line of the screen.
- 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:
+ _\bN_\bo_\bt_\be_\b: 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.
- Content-Type: text/plain; charset=iso-8859-1
+89. $hidden_host
- 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.
+ Type: boolean
- \%
+ Default: no
- This will be replaced by a %
+ When _\bs_\be_\bt, Mutt-ng will skip the host name part of ``$\b$h\bho\bos\bst\btn\bna\bam\bme\be''
+ 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.
- 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.
+90. $hide_limited
- 3.4. Example mailcap files
+ Type: boolean
- This mailcap file is fairly simple and standard:
+ Default: no
- >
- # I'm always running X :)
- video/*; xanim %s > /dev/null
- image/*; xv %s > /dev/null
+ When _\bs_\be_\bt, Mutt-ng will not show the presence of messages that are
+ hidden by limiting, in the thread tree.
- # I'm always running netscape (if my computer had more memory, maybe)
- text/html; netscape -remote 'openURL(%s)'
+91. $hide_missing
- This mailcap file shows quite a number of examples:
+ Type: boolean
- # 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
+ Default: yes
- # 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
+ When _\bs_\be_\bt, Mutt-ng will not show the presence of missing messages in
+ the thread tree.
- # Else use lynx to view it as text
- text/html; lynx %s
+92. $hide_thread_subject
- # This version would convert the text/html to text/plain
- text/html; lynx -dump %s; copiousoutput
+ Type: boolean
- # I use enscript to print text in two columns to a page
- text/*; more %s; print=enscript -2Gr %s
+ Default: yes
- # Netscape adds a flag to tell itself to view jpegs internally
- image/jpeg;xv %s; x-mozilla-flags=internal
+ When _\bs_\be_\bt, 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.
- # 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
+93. $hide_top_limited
- # Convert images to text using the netpbm tools
- image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | \
- pgmtopbm | pbmtoascii -1x2 ) 2>&1 ; copiousoutput
+ Type: boolean
- # Send excel spreadsheets to my NT box
- application/ms-excel; open.pl %s
+ Default: no
-4. MIME Autoview
+ When _\bs_\be_\bt, 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 $\b$h\bhi\bid\bde\be_\b_m\bmi\bis\bss\bsi\bin\bng\bg is _\bs_\be_\bt, this option will have no effect.
- Usage: auto_viewmime-type [mime-type ...]
+94. $hide_top_missing
- Usage: unauto_viewmime-type [mime-type ...]
+ Type: boolean
- 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.
+ Default: yes
- 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.
+ When _\bs_\be_\bt, Mutt-ng will not show the presence of missing messages at
+ the top of threads in the thread tree. Note that when $\b$h\bhi\bid\bde\be_\b_l\bli\bim\bmi\bit\bte\bed\bd is
+ _\bs_\be_\bt, this option will have no effect.
- You then use the auto_view muttrc command to list the content-types that
- you wish to view automatically.
+95. $history
- For instance, if you set auto_view to:
+ Type: number
- auto_view text/html application/x-gunzip application/postscript
- image/gif application/x-tar-gz
+ Default: 10
- Mutt-ng could use the following mailcap entries to automatically view
- attachments of these types.
+ 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.
- 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
+96. $honor_followup_to
- ``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.
+ Type: quadoption
-5. MIME Multipart/Alternative
+ Default: yes
- Usage: alternative_ordermime-type [mime-type ...]
+ This variable controls whether or not a Mail-Followup-To: header field
+ is honored when group-replying to a message.
- Usage: unalternative_ordermime-type [mime-type ...]
+97. $hostname
- 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:
+ Type: string
- alternative_order text/enriched text/plain text
- application/postscript image/*
+ Default: ""
- 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.
+ Specifies the hostname to use after the ``@'' in local e-mail
+ addresses and during generation of Message-ID: headers.
- To remove a MIME type from the alternative_order list, use the
- unalternative_order command.
+ Please be sure to really know what you are doing when changing this
+ variable to configure a custom domain part of Message-IDs.
-6. Attachment Searching and Counting
+98. $ignore_list_reply_to
- 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.
+ Type: boolean
- The syntax is:
+ Default: no
- Usage: attachments( {+|-}disposition mime-type | ? )
+ Affects the behaviour of the _\br_\be_\bp_\bl_\by function when replying to messages
+ from mailing lists. When _\bs_\be_\bt, 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
+ _\bl_\bi_\bs_\bt_\b-_\br_\be_\bp_\bl_\by function; _\bg_\br_\bo_\bu_\bp_\b-_\br_\be_\bp_\bl_\by 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.
- Usage: unattachments{+|-}disposition mime-type
+99. $imap_authenticators
- Disposition is the attachment's Content-disposition type -- either
- "inline" or "attachment". You can abbreviate this to I or A.
+ Type: string
- 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.
+ Default: ""
- 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.)
+ Availability: IMAP
- 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.
+ 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.
- Some examples might help to illustrate. The examples that are not
- commented out define the default configuration of the lists.
+ If this parameter is _\bu_\bn_\bs_\be_\bt (the default) Mutt-ng will try all
+ available methods, in order from most-secure to least-secure.
- ## 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 $count_attachments variable may be used.
+ Example: set imap_authenticators="gssapi:cram-md5:login"
-7. MIME Lookup
+ _\bN_\bo_\bt_\be_\b: 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.
- Usage: mime_lookupmime-type [mime-type ...]
+100. $imap_check_subscribed
- Usage: unmime_lookupmime-type [mime-type ...]
+ Type: boolean
- 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:
+ Default: no
- mime_lookup application/octet-stream application/X-Lotus-Manuscript
+ When _\bs_\be_\bt, 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\bma\bai\bil\blb\bbo\box\bxe\bes\bs'' command.
- 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.
+101. $imap_delim_chars
-Chapter 6. Security Considerations
+ Type: string
- Table of Contents
+ Default: "/."
- 1. Passwords
+ Availability: IMAP
- 2. Temporary Files
+ 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 $\b$f\bfo\bol\bld\bde\ber\br variable.
- 3. Information Leaks
+102. $imap_headers
- 3.1. Message-ID: headers
+ Type: string
- 3.2. mailto:-style links
+ Default: ""
- 4. External applications
+ Availability: IMAP
- 4.1. mailcap
+ 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.
- 4.2. Other
+ _\bN_\bo_\bt_\be_\b: This is a space separated list.
- 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.
+103. $imap_home_namespace
- Please do not run mutt-ng as the super user.
+ Type: string
- When configuring mutt-ng, there're some points to note about secure
- setups.
+ Default: ""
- 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.
+ Availability: IMAP
-1. Passwords
+ 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.
- 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.
+104. $imap_keepalive
-2. Temporary Files
+ Type: number
- 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.
+ Default: 900
-3. Information Leaks
+ Availability: IMAP
- 3.1. Message-ID: headers
+ 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.
- 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.
+ 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.
- 3.2. mailto:-style links
+ Reduce this number if you find yourself getting disconnected from your
+ IMAP server due to inactivity.
- 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.
+105. $imap_list_subscribed
- For example, following a link like
+ Type: boolean
- mailto:joe@host?Attach=~/.gnupg/secring.gpg
+ Default: no
- will send out the user's private gnupg keyring to joe@host if the user
- doesn't follow the information on screen carefully enough.
+ Availability: IMAP
- When unsetting the $strict_mailto variable, mutt-ng will
+ 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 _\bt_\bo_\bg_\bg_\bl_\be_\b-_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd function.
- o be less strict when interpreting these links by prepending a X-Mailto-
- string to all header fields embedded in such a link and
+106. $imap_login
- o turn on the $edit_headers variable by force to let the user see all
- the headers (because they still may leak information.)
+ Type: string
-4. External applications
+ Default: ""
- Mutt-ng in many places has to rely on external applications or for
- convenience supports mechanisms involving external applications.
+ Availability: IMAP
- 4.1. mailcap
+ Your login name on the IMAP server.
- 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.)
+ This variable defaults to the value of ``$\b$i\bim\bma\bap\bp_\b_u\bus\bse\ber\br.''
- 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...
+107. $imap_mail_check
- o manually select trustworth applications with a reasonable calling
- sequence
+ Type: number
- o periodically check the contents of mailcap files, especially after
- software installations or upgrades
+ Default: 300
- o keep the software packages referenced in the mailcap file up to date
+ This variable configures how often (in seconds) Mutt-ng should look
+ for new mail in IMAP folders. This is split from the ``m\bma\bai\bil\bl_\b_c\bch\bhe\bec\bck\bk''
+ variable to generate less traffic and get more accurate information
+ for local folders.
- o leave the $mailcap_sanitize variable in its default state to restrict
- mailcap expandos to a safe set of characters
+108. $imap_pass
- 4.2. Other
+ Type: string
- Besides the mailcap mechanism, mutt-ng uses a number of other external
- utilities for operation.
+ Default: ""
- 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.)
+ Availability: IMAP
- As already noted, most of these problems are not built in but caused by
- wrong configuration, so please check your configuration.
+ Specifies the password for your IMAP account. If _\bu_\bn_\bs_\be_\bt, Mutt-ng will
+ prompt you for your password when you invoke the fetch-mail function.
-Chapter 7. Reference
+ _\bW_\ba_\br_\bn_\bi_\bn_\bg: 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.
- Table of Contents
+109. $imap_passive
- 1. Command line options
+ Type: boolean
- 2. Patterns
+ Default: yes
- 3. Configuration Commands
+ Availability: IMAP
- 4. Configuration variables
+ When _\bs_\be_\bt, 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.
- 5. Functions
+110. $imap_peek
- 5.1. generic
+ Type: boolean
- 5.2. index
+ Default: yes
- 5.3. pager
+ Availability: IMAP
- 5.4. alias
+ If _\bs_\be_\bt, 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.
- 5.5. query
+111. $imap_reconnect
- 5.6. attach
+ Type: quadoption
- 5.7. compose
+ Default: ask-yes
- 5.8. postpone
+ Availability: IMAP
- 5.9. browser
+ Controls whether or not Mutt-ng will try to reconnect to IMAP server
+ when the connection is lost.
- 5.10. pgp
+112. $imap_servernoise
- 5.11. editor
+ Type: boolean
- 5.12. sidebar
+ Default: yes
-1. Command line options
+ Availability: IMAP
- 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.
+ When _\bs_\be_\bt, 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.
- Table 7.1. Reference: Command Line Options
+113. $imap_user
- 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
+ Type: string
- To read messages in a mailbox
+ Default: ""
- mutt ] -nz ] ] -F muttrc ] ] -m type ] ] -f mailbox ]
+ Availability: IMAP
- To compose a new message
+ The name of the user whose mail you intend to access on the IMAP
+ server.
- mutt ] -n ] ] -F muttrc ] ] -a file ] ] -c address ] ] -i filename ] ] -s
- subject ] address ] address ... ]
+ This variable defaults to your user name on the local machine.
- Mutt-ng also supports a ``batch'' mode to send prepared messages. Simply
- redirect input from the file you wish to send. For example,
+114. $implicit_autoview
- mutt -s "data set for run #2" professor@bigschool.edu < ~/run2.dat
+ Type: boolean
- 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''.
+ Default: no
-2. Patterns
+ If _\bs_\be_\bt, Mutt-ng will look for a mailcap entry with the
+ ``copiousoutput'' flag set for _\be_\bv_\be_\br_\by 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.
- 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 (\\).
+115. $include
- *) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too.
+ Type: quadoption
-3. Configuration Commands
+ Default: ask-yes
- The following are the commands understood by mutt.
+ Controls whether or not a copy of the message(s) you are replying to
+ is included in your reply.
+
+116. $include_onlyfirst
- o account-hook pattern command
+ Type: boolean
- o aliaskeyaddress [, address, ... ]
+ Default: no
- o unalias [ * | key ... ]
+ Controls whether or not Mutt-ng includes only the first attachment of
+ the message you are replying.
- o alternatesregexp [ regexp ... ]
+117. $indent_string
- o unalternates [ * | regexp ... ]
+ Type: string
- o alternative_ordermimetype [ mimetype ... ]
+ Default: "> "
- o unalternative_ordermimetype [ mimetype ... ]
+ 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.
- o append-hook regexp command
+118. $index_format
- o auto_viewmimetype [ mimetype ... ]
+ Type: string
- o unauto_viewmimetype [ mimetype ... ]
+ Default: "%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s"
- o bind map key function
+ This variable allows you to customize the message index display to
+ your personal taste.
- o charset-hook alias charset
+ ``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:
- o close-hook regexp command
+ %a
+ address of the author
- o colorobjectforegroundbackground [ regexp ]
+ %A
+ reply-to address (if present; otherwise: address of author)
- o uncolorindexpattern [ pattern ... ]
+ %b
+ filename of the original message folder (think mailBox)
- o execfunction [ function ... ]
+ %B
+ the list to which the letter was sent, or else the folder name
+ (%b).
- o fcc-hook pattern mailbox
+ %c
+ number of characters (bytes) in the message
- o fcc-save-hook pattern mailbox
+ %C
+ current message number
- o folder-hook pattern command
+ %d
+ date and time of the message in the format specified by
+ ``date_format'' converted to sender's time zone
- o hdr_orderheader [ header ... ]
+ %D
+ date and time of the message in the format specified by
+ ``date_format'' converted to the local time zone
- o unhdr_orderheader [ header ... ]
+ %e
+ current message number in thread
- o charset-hook charset local-charset
+ %E
+ number of messages in current thread
- o ignorepattern [ pattern ... ]
+ %f
+ entire From: line (address + real name)
- o unignorepattern [ pattern ... ]
+ %F
+ author name, or recipient name if the message is from you
- o listsregexp [ regexp ... ]
+ %H
+ spam attribute(s) of this message
- o unlistsregexp [ regexp ... ]
+ %g
+ newsgroup name (if compiled with nntp support)
- o macromenukeysequence [ description ]
+ %i
+ message-id of the current message
- o mailboxesfilename [ filename ... ]
+ %l
+ number of lines in the message (does not work with maildir, mh,
+ and possibly IMAP folders)
- o mbox-hook pattern mailbox
+ %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.
- o message-hook pattern command
+ %m
+ total number of message in the mailbox
- o mime_lookupmimetype [ mimetype ... ]
+ %M
+ number of hidden messages if the thread is collapsed.
- o unmime_lookupmimetype [ mimetype ... ]
+ %N
+ message score
- o monoobject attribute [ regexp ]
+ %n
+ author's real name (or address if missing)
- o unmonoindexpattern [ pattern ... ]
+ %O
+ (_O_riginal save folder) Where Mutt-ng would formerly have
+ stashed the message: list name or recipient name if no list
- o my_hdr string
+ %s
+ subject of the message
- o unmy_hdrfield [ field ... ]
+ %S
+ status of the message (N/D/d/!/r/*)
- o open-hook regexp command
+ %t
+ `to:' field (recipients)
- o crypt-hook pattern key-id
+ %T
+ the appropriate character from the $\b$t\bto\bo_\b_c\bch\bha\bar\brs\bs string
- o push string
+ %u
+ user (login) name of the author
- o resetvariable [ variable ... ]
+ %v
+ first name of the author, or the recipient if the message is
+ from you
- o save-hook regexp filename
+ %W
+ name of organization of author (`organization:' field)
- o score pattern value
+ %X
+ number of attachments
- o unscorepattern [ pattern ... ]
+ %y
+ `x-label:' field, if present
- o send-hook regexp command
+ %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'.
- o reply-hook regexp command
+ %Z
+ message status flags
- o set [no|inv]variable[ =value ] [ variable ... ]
+ %{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
- o unsetvariable [ variable ... ]
+ %[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
- o source filename
+ %(fmt)
+ the local date and time when the message was received. ``fmt''
+ is expanded by the library function ``strftime''; a leading
+ bang disables locales
- o spam pattern format
+ %<fmt>
+ the current local time. ``fmt'' is expanded by the library
+ function ``strftime''; a leading bang disables locales.
- o nospam pattern
+ %>X
+ right justify the rest of the string and pad with character "X"
- o subscriberegexp [ regexp ... ]
+ %|X
+ pad to the end of the line with character "X"
- o unsubscriberegexp [ regexp ... ]
+ See also: ``$\b$t\bto\bo_\b_c\bch\bha\bar\brs\bs''.
- o togglevariable [ variable ... ]
+119. $ispell
- o unhook hook-type
+ Type: path
-4. Configuration variables
+ Default: "ispell"
- 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:
+ How to invoke ispell (GNU's spell-checking software).
- Table 7.3. Reference: Obsolete Variables
+120. $keep_flagged
- 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.
+ Type: boolean
- A complete list of current variables follows.
+ Default: no
-1. $abort_noattach
+ If _\bs_\be_\bt, read messages marked as flagged will not be moved from your
+ spool mailbox to your ``$\b$m\bmb\bbo\box\bx'' mailbox, or as a result of a
+ ``m\bmb\bbo\box\bx-\b-h\bho\boo\bok\bk'' command.
- Type: quadoption
+121. $locale
- Default: no
+ Type: string
- 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.
+ Default: "C"
- This variable and $attach_remind_regexp are intended to remind the user to
- attach files if the message's text references them.
+ The locale used by strftime(3) to format dates. Legal values are the
+ strings your system accepts for the locale variable LC_TIME.
- See also the $attach_remind_regexp variable.
+122. $mail_check
-2. $abort_nosubject
+ Type: number
- Type: quadoption
+ Default: 5
- Default: ask-yes
+ This variable configures how often (in seconds) Mutt-ng should look
+ for new mail.
- 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.
+ _\bN_\bo_\bt_\be_\b: This does not apply to IMAP mailboxes, see $\b$i\bim\bma\bap\bp_\b_m\bma\bai\bil\bl_\b_c\bch\bhe\bec\bck\bk.
-3. $abort_unmodified
+123. $mailcap_path
- Type: quadoption
+ Type: string
- Default: yes
+ Default: ""
- 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.
+ This variable specifies which files to consult when attempting to
+ display MIME bodies not directly supported by Mutt-ng.
-4. $agent_string
+124. $mailcap_sanitize
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.
+ If _\bs_\be_\bt, 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.
-5. $alias_file
-
- Type: path
-
- Default: "~/.muttngrc"
+ _\bD_\bO_\bN_\b'_\bT_\b _\bC_\bH_\bA_\bN_\bG_\bE_\b _\bT_\bH_\bI_\bS_\b _\bS_\bE_\bT_\bT_\bI_\bN_\bG_\b _\bU_\bN_\bL_\bE_\bS_\bS_\b _\bY_\bO_\bU_\b _\bA_\bR_\bE_\b _\bR_\bE_\bA_\bL_\bL_\bY_\b _\bS_\bU_\bR_\bE_\b _\bW_\bH_\bA_\bT_\b _\bY_\bO_\bU_\b _\bA_\bR_\bE
+ _\bD_\bO_\bI_\bN_\bG_\b!
- The default file in which to save aliases created by the ``create-alias''
- function.
+125. $maildir_header_cache_verify
- Note: Mutt-ng will not automatically source this file; you must explicitly
- use the ``source'' command for it to be executed.
+ Type: boolean
-6. $alias_format
+ Default: yes
- Type: string
+ Availability: Header Cache
- Default: "%4n %2f %t %-10a %r"
+ 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.
- Specifies the format of the data displayed for the ``alias'' menu. The
- following printf(3)-style sequences are available:
+126. $maildir_trash
- %a
+ Type: boolean
- alias name
+ Default: no
- %f
+ If _\bs_\be_\bt, messages marked as deleted will be saved with the maildir
+ (T)rashed flag instead of physically deleted.
- flags - currently, a "d" for an alias marked for deletion
+ _\bN_\bO_\bT_\bE_\b: this only applies to maildir-style mailboxes. Setting it will
+ have no effect on other mailbox types.
- %n
+ It is similiar to the trash option.
- index number
+127. $mark_old
- %r
+ Type: boolean
- address which alias expands to
+ Default: yes
- %t
+ Controls whether or not Mutt-ng marks _\bn_\be_\bw_\bu_\bn_\br_\be_\ba_\bd messages as _\bo_\bl_\bd if you
+ exit a mailbox without reading them.
- character which indicates if the alias is tagged for inclusion
+ With this option _\bs_\be_\bt, 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.
-7. $allow_8bit
+128. $markers
Type: boolean
Default: yes
- Controls whether 8-bit data is converted to 7-bit using either
- quoted-printable or base64 encoding when sending mail.
+ 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 ``$\b$s\bsm\bma\bar\brt\bt_\b_w\bwr\bra\bap\bp'' variable.
-8. $allow_ansi
+129. $mask
- Type: boolean
+ Type: regular expression
- Default: no
+ Default: "!^\.[^.]"
- 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.
+ A regular expression used in the file browser, optionally preceded by
+ the _\bn_\bo_\bt operator ``!''. Only files whose names match this mask will be
+ shown. The match is always case-sensitive.
-9. $arrow_cursor
+130. $max_display_recips
- Type: boolean
+ Type: number
- Default: no
+ Default: 0
- 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.
+ 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.
-10. $ascii_chars
+131. $max_line_length
- Type: boolean
+ Type: number
- Default: no
+ Default: 0
- If set, Mutt-ng will use plain ASCII characters when displaying thread and
- attachment trees, instead of the default ACS characters.
+ When _\bs_\be_\bt, 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 $\b$w\bwr\bra\bap\bpm\bma\bar\brg\bgi\bin\bn.
-11. $askbcc
+132. $mbox
- Type: boolean
+ Type: path
- Default: no
+ Default: "~/mbox"
- If set, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients
- before editing an outgoing message.
+ This specifies the folder into which read mail in your ``$\b$s\bsp\bpo\boo\bol\blf\bfi\bil\ble\be''
+ folder will be appended.
-12. $askcc
+133. $mbox_type
- Type: boolean
+ Type: folder magic
- Default: no
+ Default: mbox
- If set, Mutt-ng will prompt you for carbon-copy (Cc) recipients before
- editing the body of an outgoing message.
+ The default mailbox type used when creating new folders. May be any of
+ mbox, MMDF, MH and Maildir.
-13. $assumed_charset
+134. $menu_context
- Type: string
+ Type: number
- Default: "us-ascii"
+ Default: 0
- 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.
+ This variable controls the number of lines of context that are given
+ when scrolling through menus. (Similar to ``$\b$p\bpa\bag\bge\ber\br_\b_c\bco\bon\bnt\bte\bex\bxt\bt''.)
- For example, Japanese users might prefer this:
+135. $menu_move_off
- set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
+ Type: boolean
- However, only the first content is valid for the message body. This
- variable is valid only if $strict_mime is unset.
+ Default: yes
-14. $attach_format
+ When _\bu_\bn_\bs_\be_\bt, the bottom entry of menus will never scroll up past the
+ bottom of the screen, unless there are less entries than lines. When
+ _\bs_\be_\bt, the bottom entry may move off the bottom.
- Type: string
+136. $menu_scroll
- Default: "%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] "
+ Type: boolean
- This variable describes the format of the ``attachment'' menu. The
- following printf(3)-style sequences are understood:
+ Default: no
- %C
+ When _\bs_\be_\bt, menus will be scrolled up or down one line when you attempt
+ to move across a screen boundary. If _\bu_\bn_\bs_\be_\bt, the screen is cleared and
+ the next or previous page of the menu is displayed (useful for slow
+ links to avoid many redraws).
- charset
+137. $message_format
- %c
+ Type: string
- requires charset conversion (n or c)
+ Default: "%s"
- %D
+ 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 ``$\b$i\bin\bnd\bde\bex\bx_\b_f\bfo\bor\brm\bma\bat\bt''.
- deleted flag
+138. $meta_key
- %d
+ Type: boolean
- description
+ Default: no
- %e
+ If _\bs_\be_\bt, 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''.
- MIME Content-Transfer-Encoding: header field
+139. $metoo
- %f
+ Type: boolean
- filename
+ Default: no
- %I
+ If _\bu_\bn_\bs_\be_\bt, Mutt-ng will remove your address (see the ``alternates''
+ command) from the list of recipients when replying to a message.
- MIME Content-Disposition: header field (I=inline, A=attachment)
+140. $mh_purge
- %m
+ Type: boolean
+
+ Default: no
- major MIME type
+ When _\bu_\bn_\bs_\be_\bt, Mutt-ng will mimic mh's behaviour and rename deleted
+ messages to _\b,_\b<_\bo_\bl_\bd_\b _\bf_\bi_\bl_\be_\b _\bn_\ba_\bm_\be_\b> in mh folders instead of really deleting
+ them. If the variable is set, the message files will simply be
+ deleted.
- %M
+141. $mh_seq_flagged
- MIME subtype
+ Type: string
- %n
+ Default: "flagged"
- attachment number
+ The name of the MH sequence used for flagged messages.
- %Q
+142. $mh_seq_replied
- "Q", if MIME part qualifies for attachment counting
+ Type: string
- %s
+ Default: "replied"
- size
+ The name of the MH sequence used to tag replied messages.
- %t
+143. $mh_seq_unseen
- tagged flag
+ Type: string
- %T
+ Default: "unseen"
- graphic tree characters
+ The name of the MH sequence used for unseen messages.
- %u
+144. $mime_forward
- unlink (=to delete) flag
+ Type: quadoption
- %X
+ Default: no
- number of qualifying MIME parts in this part and its children
+ When _\bs_\be_\bt, the message you are forwarding will be attached as a
+ separate MIME part instead of included in the main body of the
+ message.
- %>X
+ 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.
- right justify the rest of the string and pad with character "X"
+ Also see ``$\b$f\bfo\bor\brw\bwa\bar\brd\bd_\b_d\bde\bec\bco\bod\bde\be'' and ``$\b$m\bmi\bim\bme\be_\b_f\bfo\bor\brw\bwa\bar\brd\bd_\b_d\bde\bec\bco\bod\bde\be''.
- %|X
+145. $mime_forward_decode
- pad to the end of the line with character "X"
+ Type: boolean
-15. $attach_remind_regexp
+ Default: no
- Type: regular expression
+ Controls the decoding of complex MIME messages into text/plain when
+ forwarding a message while ``$\b$m\bmi\bim\bme\be_\b_f\bfo\bor\brw\bwa\bar\brd\bd'' is _\bs_\be_\bt. Otherwise
+ ``$\b$f\bfo\bor\brw\bwa\bar\brd\bd_\b_d\bde\bec\bco\bod\bde\be'' is used instead.
- Default: "attach"
+146. $mime_forward_rest
- 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.
+ Type: quadoption
- This variable and $abort_noattach are intended to remind the user to
- attach files if the message's text references them.
+ Default: yes
-16. $attach_sep
+ 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.
+
+147. $mix_entry_format
Type: string
- Default: "\n"
+ Default: "%4n %c %-16s %a"
- The separator to add between attachments when operating (saving, printing,
- piping, etc) on a list of tagged attachments.
+ Availability: Mixmaster
-17. $attach_split
+ This variable describes the format of a remailer line on the mixmaster
+ chain selection screen. The following printf(3)-like sequences are
+ supported:
- Type: boolean
+ %n
+ The running number on the menu.
- Default: yes
+ %c
+ Remailer capabilities.
- 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.
+ %s
+ The remailer's short name.
-18. $attribution
+ %a
+ The remailer's e-mail address.
- Type: string
+148. $mixmaster
- Default: "On %d, %n wrote:"
+ Type: path
- 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''.
+ Default: "mixmaster"
-19. $auto_tag
+ Availability: Mixmaster
- Type: boolean
+ 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: no
+149. $move
- 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.
+ Type: quadoption
-20. $autoedit
+ Default: ask-no
- Type: boolean
+ Controls whether or not Mutt-ng will move read messages from your
+ spool mailbox to your ``$\b$m\bmb\bbo\box\bx'' mailbox, or as a result of a
+ ``m\bmb\bbo\box\bx-\b-h\bho\boo\bok\bk'' command.
- Default: no
+150. $msgid_format
- 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.
+ Type: string
- Also see ``$fast_reply''.
+ Default: "%Y%m%d%h%M%s.G%P%p"
-21. $beep
+ 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:
- Type: boolean
+ %d
+ the current day of month
- Default: yes
+ %h
+ the current hour
- When this variable is set, Mutt-ng will beep when an error occurs.
+ %m
+ the current month
-22. $beep_new
+ %M
+ the current minute
- Type: boolean
+ %O
+ the current UNIX timestamp (octal)
- Default: no
+ %p
+ the process ID
- 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.
+ %P
+ the current Message-ID prefix (a character rotating with every
+ Message-ID being generated)
-23. $bounce
+ %r
+ a random integer value (decimal)
- Type: quadoption
+ %R
+ a random integer value (hexadecimal)
- Default: ask-yes
+ %s
+ the current second
- 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.
+ %T
+ the current UNIX timestamp (decimal)
-24. $bounce_delivered
+ %X
+ the current UNIX timestamp (hexadecimal)
- Type: boolean
+ %Y
+ the current year (Y2K compliant)
- Default: yes
+ %%
+ the '%' character
- When this variable is set, Mutt-ng will include Delivered-To: header
- fields when bouncing messages. Postfix users may wish to unset this
- variable.
+ _\bN_\bo_\bt_\be_\b: Please only change this setting if you know what you are doing.
+ Also make sure to consult RFC2822 to produce technically _\bv_\ba_\bl_\bi_\bd
+ strings.
-25. $braille_friendly
+151. $muttng_bindir
- Type: boolean
+ Type: system property
- Default: no
+ Value: /opt/freebsd4/mutt-ng/bin
- 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.
+ _\bT_\bh_\bi_\bs_\b _\bi_\bs_\b _\ba_\b _\br_\be_\ba_\bd_\b-_\bo_\bn_\bl_\by_\b _\bs_\by_\bs_\bt_\be_\bm_\b _\bp_\br_\bo_\bp_\be_\br_\bt_\by_\b _\ba_\bn_\bd_\b _\bs_\bp_\be_\bc_\bi_\bf_\bi_\be_\bs_\b _\bt_\bh_\be_\b _\bd_\bi_\br_\be_\bc_\bt_\bo_\br_\by
+ _\bc_\bo_\bn_\bt_\ba_\bi_\bn_\bi_\bn_\bg_\b _\bt_\bh_\be_\b _\bm_\bu_\bt_\bt_\bn_\bg_\b _\bb_\bi_\bn_\ba_\br_\by_\b.
-26. $certificate_file
+152. $muttng_docdir
- Type: path
+ Type: system property
- Default: "~/.mutt_certificates"
+ Value: /opt/freebsd4/mutt-ng/doc/muttng
- Availability: SSL or GNUTLS
+ _\bT_\bh_\bi_\bs_\b _\bi_\bs_\b _\ba_\b _\br_\be_\ba_\bd_\b-_\bo_\bn_\bl_\by_\b _\bs_\by_\bs_\bt_\be_\bm_\b _\bp_\br_\bo_\bp_\be_\br_\bt_\by_\b _\ba_\bn_\bd_\b _\bs_\bp_\be_\bc_\bi_\bf_\bi_\be_\bs_\b _\bt_\bh_\be_\b _\bd_\bi_\br_\be_\bc_\bt_\bo_\br_\by
+ _\bc_\bo_\bn_\bt_\ba_\bi_\bn_\bi_\bn_\bg_\b _\bt_\bh_\be_\b _\bm_\bu_\bt_\bt_\bn_\bg_\b _\bd_\bo_\bc_\bu_\bm_\be_\bn_\bt_\ba_\bt_\bi_\bo_\bn_\b.
- 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.
+153. $muttng_folder_name
- 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.
+ Type: system property
- Example: set certificate_file=~/.muttng/certificates
+ Value:
-27. $charset
+ _\bT_\bh_\bi_\bs_\b _\bi_\bs_\b _\ba_\b _\br_\be_\ba_\bd_\b-_\bo_\bn_\bl_\by_\b _\bs_\by_\bs_\bt_\be_\bm_\b _\bp_\br_\bo_\bp_\be_\br_\bt_\by_\b _\ba_\bn_\bd_\b,_\b _\ba_\bt_\b _\br_\bu_\bn_\bt_\bi_\bm_\be_\b,_\b _\bs_\bp_\be_\bc_\bi_\bf_\bi_\be_\bs_\b _\bt_\bh_\be
+ _\bl_\ba_\bs_\bt_\b _\bp_\ba_\br_\bt_\b _\bo_\bf_\b _\bt_\bh_\be_\b _\bf_\bu_\bl_\bl_\b _\bp_\ba_\bt_\bh_\b _\bo_\br_\b _\bU_\bR_\bI_\b _\bo_\bf_\b _\bt_\bh_\be_\b _\bf_\bo_\bl_\bd_\be_\br_\b _\bc_\bu_\br_\br_\be_\bn_\bt_\bl_\by_\b _\bo_\bp_\be_\bn_\b _\b(_\bi_\bf
+ _\ba_\bn_\by_\b)_\b,_\b _\bi_\b._\be_\b._\b _\be_\bv_\be_\br_\by_\bt_\bh_\bi_\bn_\bg_\b _\ba_\bf_\bt_\be_\br_\b _\bt_\bh_\be_\b _\bl_\ba_\bs_\bt_\b _\b`_\b`_\b/_\b'_\b'_\b.
- Type: string
+154. $muttng_folder_path
- Default: ""
+ Type: system property
- Character set your terminal uses to display and enter textual data.
+ Value:
-28. $check_new
+ _\bT_\bh_\bi_\bs_\b _\bi_\bs_\b _\ba_\b _\br_\be_\ba_\bd_\b-_\bo_\bn_\bl_\by_\b _\bs_\by_\bs_\bt_\be_\bm_\b _\bp_\br_\bo_\bp_\be_\br_\bt_\by_\b _\ba_\bn_\bd_\b,_\b _\ba_\bt_\b _\br_\bu_\bn_\bt_\bi_\bm_\be_\b,_\b _\bs_\bp_\be_\bc_\bi_\bf_\bi_\be_\bs_\b _\bt_\bh_\be
+ _\bf_\bu_\bl_\bl_\b _\bp_\ba_\bt_\bh_\b _\bo_\br_\b _\bU_\bR_\bI_\b _\bo_\bf_\b _\bt_\bh_\be_\b _\bf_\bo_\bl_\bd_\be_\br_\b _\bc_\bu_\br_\br_\be_\bn_\bt_\bl_\by_\b _\bo_\bp_\be_\bn_\b _\b(_\bi_\bf_\b _\ba_\bn_\by_\b)_\b.
- Type: boolean
+155. $muttng_hcache_backend
- Default: yes
+ Type: system property
- Note: this option only affects maildir and MH style mailboxes.
+ Value: qdbm
- 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.
+ _\bT_\bh_\bi_\bs_\b _\bi_\bs_\b _\ba_\b _\br_\be_\ba_\bd_\b-_\bo_\bn_\bl_\by_\b _\bs_\by_\bs_\bt_\be_\bm_\b _\bp_\br_\bo_\bp_\be_\br_\bt_\by_\b _\ba_\bn_\bd_\b _\bs_\bp_\be_\bc_\bi_\bf_\bi_\be_\bs_\b _\bt_\bh_\be_\b _\bh_\be_\ba_\bd_\be_\br
+ _\bc_\bh_\ba_\bc_\bh_\bi_\bn_\bg_\b'_\bs_\b _\bd_\ba_\bt_\ba_\bb_\ba_\bs_\be_\b _\bb_\ba_\bc_\bk_\be_\bn_\bd_\b.
-29. $collapse_unread
+156. $muttng_pwd
- Type: boolean
+ Type: system property
- Default: yes
+ Value:
- When unset, Mutt-ng will not collapse a thread if it contains any unread
- messages.
+ _\bT_\bh_\bi_\bs_\b _\bi_\bs_\b _\ba_\b _\br_\be_\ba_\bd_\b-_\bo_\bn_\bl_\by_\b _\bs_\by_\bs_\bt_\be_\bm_\b _\bp_\br_\bo_\bp_\be_\br_\bt_\by_\b _\ba_\bn_\bd_\b,_\b _\ba_\bt_\b _\br_\bu_\bn_\bt_\bi_\bm_\be_\b,_\b _\bs_\bp_\be_\bc_\bi_\bf_\bi_\be_\bs_\b _\bt_\bh_\be
+ _\bc_\bu_\br_\br_\be_\bn_\bt_\b _\bw_\bo_\br_\bk_\bi_\bn_\bg_\b _\bd_\bi_\br_\be_\bc_\bt_\bo_\br_\by_\b _\bo_\bf_\b _\bt_\bh_\be_\b _\bm_\bu_\bt_\bt_\bn_\bg_\b _\bb_\bi_\bn_\ba_\br_\by_\b.
-30. $compose_format
+157. $muttng_revision
- Type: string
+ Type: system property
- Default: "-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-"
+ Value: 553
- 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:
+ _\bT_\bh_\bi_\bs_\b _\bi_\bs_\b _\ba_\b _\br_\be_\ba_\bd_\b-_\bo_\bn_\bl_\by_\b _\bs_\by_\bs_\bt_\be_\bm_\b _\bp_\br_\bo_\bp_\be_\br_\bt_\by_\b _\ba_\bn_\bd_\b _\bs_\bp_\be_\bc_\bi_\bf_\bi_\be_\bs_\b _\bm_\bu_\bt_\bt_\bn_\bg_\b'_\bs_\b _\bs_\bu_\bb_\bv_\be_\br_\bs_\bi_\bo_\bn
+ _\br_\be_\bv_\bi_\bs_\bi_\bo_\bn_\b _\bs_\bt_\br_\bi_\bn_\bg_\b.
- %a
+158. $muttng_sysconfdir
- total number of attachments
+ Type: system property
- %h
+ Value: /opt/freebsd4/mutt-ng/etc
- local hostname
+ _\bT_\bh_\bi_\bs_\b _\bi_\bs_\b _\ba_\b _\br_\be_\ba_\bd_\b-_\bo_\bn_\bl_\by_\b _\bs_\by_\bs_\bt_\be_\bm_\b _\bp_\br_\bo_\bp_\be_\br_\bt_\by_\b _\ba_\bn_\bd_\b _\bs_\bp_\be_\bc_\bi_\bf_\bi_\be_\bs_\b _\bt_\bh_\be_\b _\bd_\bi_\br_\be_\bc_\bt_\bo_\br_\by
+ _\bc_\bo_\bn_\bt_\ba_\bi_\bn_\bi_\bn_\bg_\b _\bt_\bh_\be_\b _\bm_\bu_\bt_\bt_\bn_\bg_\b _\bs_\by_\bs_\bt_\be_\bm_\b-_\bw_\bi_\bd_\be_\b _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn_\b.
- %l
+159. $muttng_version
- approximate size (in bytes) of the current message
+ Type: system property
- %v
+ Value: devel
- Mutt-ng version string
+ _\bT_\bh_\bi_\bs_\b _\bi_\bs_\b _\ba_\b _\br_\be_\ba_\bd_\b-_\bo_\bn_\bl_\by_\b _\bs_\by_\bs_\bt_\be_\bm_\b _\bp_\br_\bo_\bp_\be_\br_\bt_\by_\b _\ba_\bn_\bd_\b _\bs_\bp_\be_\bc_\bi_\bf_\bi_\be_\bs_\b _\bm_\bu_\bt_\bt_\bn_\bg_\b'_\bs_\b _\bv_\be_\br_\bs_\bi_\bo_\bn
+ _\bs_\bt_\br_\bi_\bn_\bg_\b.
- See the text describing the ``$status_format'' option for more information
- on how to set ``$compose_format''.
+160. $narrow_tree
-31. $config_charset
+ Type: boolean
- Type: string
+ Default: no
- Default: ""
+ This variable, when _\bs_\be_\bt, makes the thread tree narrower, allowing
+ deeper threads to fit on the screen.
- When defined, Mutt-ng will recode commands in rc files from this encoding.
+161. $net_inc
-32. $confirmappend
+ Type: number
- Type: boolean
+ Default: 10
- Default: yes
+ Operations that expect to transfer a large amount of data over the
+ network will update their progress every _\bn_\be_\bt_\b__\bi_\bn_\bc kilobytes. If set to
+ 0, no progress messages will be displayed.
- When set, Mutt-ng will prompt for confirmation when appending messages to
- an existing mailbox.
+ See also ``$\b$r\bre\bea\bad\bd_\b_i\bin\bnc\bc'' and ``$\b$w\bwr\bri\bit\bte\be_\b_i\bin\bnc\bc''.
-33. $confirmcreate
+162. $nntp_ask_followup_to
Type: boolean
- Default: yes
+ Default: no
- When set, Mutt-ng will prompt for confirmation when saving messages to a
- mailbox which does not yet exist before creating it.
+ Availability: NNTP
-34. $connect_timeout
+ If _\bs_\be_\bt, Mutt-ng will prompt you for the Followup-To: header field
+ before editing the body of an outgoing news article.
- Type: number
+163. $nntp_ask_x_comment_to
- Default: 30
+ Type: boolean
- 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.
+ Default: no
-35. $content_type
+ Availability: NNTP
- Type: string
+ If _\bs_\be_\bt, Mutt-ng will prompt you for the X-Comment-To: header field
+ before editing the body of an outgoing news article.
- Default: "text/plain"
+164. $nntp_cache_dir
- Sets the default Content-Type: header field for the body of newly composed
- messages.
+ Type: path
-36. $copy
+ Default: "~/.muttng"
- Type: quadoption
+ Availability: NNTP
- Default: yes
+ This variable points to directory where Mutt-ng will cache news
+ article headers. If _\bu_\bn_\bs_\be_\bt, headers will not be saved at all and will
+ be reloaded each time when you enter a newsgroup.
- 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''.
+ As for the header caching in connection with IMAP and/or Maildir, this
+ drastically increases speed and lowers traffic.
-37. $count_attachments
+165. $nntp_catchup
- Type: boolean
+ Type: quadoption
- Default: yes
+ Default: ask-yes
- 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.
+ Availability: NNTP
- If it is set and rules were defined via the attachments and/or
- unattachments commands, counting will be done. If it is unset no counting
- will be done regardless whether rules were defined or not.
+ If this variable is _\bs_\be_\bt, Mutt-ng will mark all articles in a newsgroup
+ as read when you leaving it.
-38. $crypt_autoencrypt
+166. $nntp_context
- Type: boolean
+ Type: number
- Default: no
+ Default: 1000
- 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)
+ Availability: NNTP
-39. $crypt_autopgp
+ This variable controls how many news articles to cache per newsgroup
+ (if caching is enabled, see $\b$n\bnn\bnt\btp\bp_\b_c\bca\bac\bch\bhe\be_\b_d\bdi\bir\br) and how many news
+ articles to show in the ``index'' menu.
- Type: boolean
+ If there're more articles than defined with $\b$n\bnn\bnt\btp\bp_\b_c\bco\bon\bnt\bte\bex\bxt\bt, all older
+ ones will be removed/not shown in the index.
- Default: yes
+167. $nntp_followup_to_poster
- 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''.
+ Type: quadoption
-40. $crypt_autosign
+ Default: ask-yes
- Type: boolean
+ Availability: NNTP
- Default: no
+ If this variable is _\bs_\be_\bt 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.
- 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)
+168. $nntp_group_index_format
-41. $crypt_autosmime
+ Type: string
- Type: boolean
+ Default: "%4C %M%N %5s %-45.45f %d"
- Default: yes
+ Availability: NNTP
- 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''.
+ This variable allows you to customize the newsgroup browser display to
+ your personal taste. This string is similar to ``i\bin\bnd\bde\bex\bx_\b_f\bfo\bor\brm\bma\bat\bt'', but
+ has its own set of printf(3)-like sequences:
+
+%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"
-42. $crypt_replyencrypt
+169. $nntp_host
- Type: boolean
+ Type: string
- Default: yes
+ Default: ""
- If set, automatically PGP or OpenSSL encrypt replies to messages which are
- encrypted. (Crypto only)
+ Availability: NNTP
-43. $crypt_replysign
+ This variable specifies the name (or address) of the NNTP server to be
+ used.
- Type: boolean
+ It defaults to the value specified via the environment variable
+ $NNTPSERVER or contained in the file /etc/nntpserver.
- Default: no
+ You can also specify a username and an alternative port for each
+ newsserver, e.g.
- If set, automatically PGP or OpenSSL sign replies to messages which are
- signed.
+ [nntp[s]://][username[:password]@]newsserver[:port]
- Note: this does not work on messages that are encrypted and signed!
- (Crypto only)
+ _\bN_\bo_\bt_\be_\b: 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.
-44. $crypt_replysignencrypted
+170. $nntp_inews
- Type: boolean
+ Type: path
- Default: no
+ Default: ""
+
+ Availability: NNTP
- 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)
+ If _\bs_\be_\bt, 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:
-45. $crypt_timestamp
+%s newsserver name
+
+ Example: set inews="/usr/local/bin/inews -hS"
+
+171. $nntp_load_description
Type: boolean
Default: yes
- 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)
+ Availability: NNTP
-46. $crypt_use_gpgme
+ This variable controls whether or not descriptions for newsgroups are
+ to be loaded when subscribing to a newsgroup.
- Type: boolean
+172. $nntp_mail_check
- Default: no
+ Type: number
- 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.
+ Default: 60
- Note: You need to use this option in your .muttngrc configuration file as
- it won't have any effect when used interactively.
+ Availability: NNTP
-47. $crypt_verify_sig
+ 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: quadoption
+173. $nntp_mime_subject
+
+ Type: boolean
Default: yes
- 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)
+ Availability: NNTP
-48. $date_format
+ If _\bu_\bn_\bs_\be_\bt, an 8-bit ``Subject:'' header field in a news article will
+ not be encoded according to RFC2047.
- Type: string
+ _\bN_\bo_\bt_\be_\b: Only change this setting if you know what you are doing.
- Default: "!%a, %b %d, %Y at %I:%M:%S%p %Z"
+174. $nntp_newsrc
- 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.
+ Type: path
- 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).
+ Default: "~/.newsrc"
-49. $debug_level
+ Availability: NNTP
- Type: number
+ This file contains information about subscribed newsgroup and articles
+ read so far.
- Default: 1
+ To ease the use of multiple news servers, the following
+ printf(3)-style sequence is understood:
- Availability: debug
+%s newsserver name
- 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.
+175. $nntp_pass
- 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.
+ Type: string
-50. $default_hook
+ Default: ""
- Type: string
+ Availability: NNTP
- Default: "~f %s !~P | (~P ~C %s)"
+ Your password for NNTP account.
- 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.
+ _\bN_\bo_\bt_\be_\b: 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.
-51. $delete
+176. $nntp_post_moderated
Type: quadoption
Default: ask-yes
- 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.
+ Availability: NNTP
-52. $delete_space
+ If set to _\by_\be_\bs, Mutt-ng will post articles to newsgroup that have not
+ permissions to post (e.g. moderated).
+
+ _\bN_\bo_\bt_\be_\b: if the newsserver does not support posting to that newsgroup or
+ a group is totally read-only, that posting will not have any effect.
+
+177. $nntp_reconnect
+
+ Type: quadoption
+
+ Default: ask-yes
+
+ Availability: NNTP
+
+ Controls whether or not Mutt-ng will try to reconnect to a newsserver
+ when the was connection lost.
+
+178. $nntp_save_unsubscribed
Type: boolean
Default: no
- 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.
+ Availability: NNTP
- Note: this variable only has an effect on outgoing messages (if
- $text_flowed is set) but not on incomming.
+ When _\bs_\be_\bt, info about unsubscribed newsgroups will be saved into the
+ ``newsrc'' file and into the news cache.
-53. $delete_untag
+179. $nntp_show_new_news
Type: boolean
Default: yes
- 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.
+ Availability: NNTP
-54. $digest_collapse
+ If _\bs_\be_\bt, 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.
+
+180. $nntp_show_only_unread
Type: boolean
- Default: yes
+ Default: no
- 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.
+ Availability: NNTP
-55. $display_filter
+ If _\bs_\be_\bt, only subscribed newsgroups that contain unread articles will
+ be displayed in the newsgroup browser.
- Type: path
+181. $nntp_user
+
+ Type: string
Default: ""
- 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.
+ Availability: NNTP
+
+ Your login name on the NNTP server. If _\bu_\bn_\bs_\be_\bt and the server requires
+ authentification, Mutt-ng will prompt you for your account name.
-56. $dotlock_program
+182. $nntp_x_comment_to
- Type: path
+ Type: boolean
- Default: "$muttng_bindir/muttng_dotlock"
+ Default: no
- Availability: Standalone and Dotlock
+ Availability: NNTP
- Contains the path of the muttng_dotlock(1) binary to be used by Mutt-ng.
+ If _\bs_\be_\bt, 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.
-57. $dsn_notify
+183. $operating_system
Type: string
Default: ""
- 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.
+ This specifies the operating system name for the User-Agent: header
+ field. If this is _\bu_\bn_\bs_\be_\bt, it will be set to the operating system name
+ that uname(2) returns. If uname(2) fails, ``UNIX'' will be used.
- 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.
+ It may, for example, look as: ``mutt-ng 1.5.9i (Linux)''.
- Example: set dsn_notify="failure,delay"
+184. $pager
-58. $dsn_return
+ Type: path
- Type: string
+ Default: "builtin"
- Default: ""
+ 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.
- 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.
+ 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.
- 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.
+185. $pager_context
- Example: set dsn_return=hdrs
+ Type: number
-59. $duplicate_threads
+ Default: 0
- Type: boolean
+ 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).
- Default: yes
+186. $pager_format
- 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.
+ Type: string
-60. $edit_headers
+ Default: "-%Z- %C/%m: %-20.20n %s"
- Type: boolean
+ 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 ``$\b$i\bin\bnd\bde\bex\bx_\b_f\bfo\bor\brm\bma\bat\bt''
+ section.
- Default: no
+187. $pager_index_lines
- This option allows you to edit the header of your outgoing messages along
- with the body of your message.
+ Type: number
- Which empty header fields to show is controlled by the $editor_headers
- option.
+ Default: 0
-61. $editor
+ 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 _\bp_\ba_\bg_\be_\br_\b__\bi_\bn_\bd_\be_\bx_\b__\bl_\bi_\bn_\be_\bs 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 _\bp_\ba_\bg_\be_\br_\b__\bi_\bn_\bd_\be_\bx_\b__\bl_\bi_\bn_\be_\bs, then the index will only use as many
+ lines as it needs.
- Type: path
+188. $pager_stop
- Default: ""
+ Type: boolean
- 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.
+ Default: no
-62. $editor_headers
+ When _\bs_\be_\bt, the internal-pager will _\bn_\bo_\bt move to the next message when
+ you are at the end of a message and invoke the _\bn_\be_\bx_\bt_\b-_\bp_\ba_\bg_\be function.
- Type: string
+189. $pgp_auto_decode
- Default: "From: To: Cc: Bcc: Subject: Reply-To: Newsgroups: Followup-To:
- X-Comment-To:"
+ Type: boolean
- If $edit_headers is set, this space-separated list specifies which
- non-empty header fields to edit in addition to user-defined headers.
+ Default: no
- Note: if $edit_headers had to be turned on by force because $strict_mailto
- is unset, this option has no effect.
+ If _\bs_\be_\bt, 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.
-63. $encode_from
+190. $pgp_autoinline
Type: boolean
Default: no
- 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.
+ 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 _\bp_\bg_\bp_\b-_\bm_\be_\bn_\bu, when
+ inline is not required.
- 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.
+ 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: ``$\b$p\bpg\bgp\bp_\b_m\bmi\bim\bme\be_\b_a\bau\but\bto\bo''.
-64. $entropy_file
+ Also note that using the old-style PGP message format is
+ _\bs_\bt_\br_\bo_\bn_\bg_\bl_\by_\bd_\be_\bp_\br_\be_\bc_\ba_\bt_\be_\bd. (PGP only)
- Type: path
+191. $pgp_check_exit
- Default: ""
+ Type: boolean
- Availability: SSL
+ Default: yes
- The file which includes random data that is used to initialize SSL library
- functions.
+ If _\bs_\be_\bt, 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)
-65. $envelope_from_address
+192. $pgp_clearsign_command
- Type: e-mail address
+ Type: string
Default: ""
- Manually sets the envelope sender for outgoing messages. This value is
- ignored if ``$use_envelope_from'' is unset.
-
-66. $escape
+ This format is used to create a old-style ``clearsigned'' PGP message.
- Type: string
+ Note that the use of this format is _\bs_\bt_\br_\bo_\bn_\bg_\bl_\by_\bd_\be_\bp_\br_\be_\bc_\ba_\bt_\be_\bd. (PGP only)
- Default: "~"
+193. $pgp_decode_command
- Escape character to use for functions in the builtin editor.
+ Type: string
-67. $fast_reply
+ Default: ""
- Type: boolean
+ This format strings specifies a command which is used to decode
+ application/pgp attachments.
- Default: no
+ The PGP command formats have their own set of printf(3)-like
+ sequences:
- 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.
+ %p
+ Expands to PGPPASSFD=0 when a pass phrase is needed, to an
+ empty string otherwise. Note: This may be used with a %?
+ construct.
- Note: this variable has no effect when the ``$autoedit'' variable is set.
+ %f
+ Expands to the name of a file containing a message.
-68. $fcc_attach
+ %s
+ Expands to the name of a file containing the signature part of
+ a multipart/signed attachment when verifying it.
- Type: boolean
+ %a
+ The value of $\b$p\bpg\bgp\bp_\b_s\bsi\big\bgn\bn_\b_a\bas\bs.
- Default: yes
+ %r
+ One or more key IDs.
- This variable controls whether or not attachments on outgoing messages are
- saved along with the main body of your message.
+ 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)
-69. $fcc_clear
+194. $pgp_decrypt_command
- Type: boolean
+ Type: string
- Default: no
+ Default: ""
- When this variable is set, FCCs will be stored unencrypted and unsigned,
- even when the actual message is encrypted and/or signed. (PGP only)
+ This command is used to decrypt a PGP encrypted message. (PGP only)
-70. $file_charset
+195. $pgp_encrypt_only_command
Type: string
Default: ""
- 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:
-
- set file_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-
- Note: ``iso-2022-*'' must be put at the head of the value as shown above
- if included.
+ This command is used to encrypt a body part without signing it. (PGP
+ only)
-71. $folder
+196. $pgp_encrypt_sign_command
- Type: path
+ Type: string
- Default: "~/Mail"
+ Default: ""
- 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.
+ This command is used to both sign and encrypt a body part. (PGP only)
-72. $folder_format
+197. $pgp_entry_format
Type: string
- Default: "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"
+ Default: "%4n %t%f %4l/0x%k %-4a %2c %u"
- 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:
+ This variable allows you to customize the PGP key selection menu to
+ your personal taste. This string is similar to ``$\b$i\bin\bnd\bde\bex\bx_\b_f\bfo\bor\brm\bma\bat\bt'', but
+ has its own set of printf(3)-like sequences:
- %C
+ %n
+ number
- current file number
+ %k
+ key id
- %d
+ %u
+ user id
- date/time folder was last modified
+ %a
+ algorithm
+
+ %l
+ key length
%f
+ flags
- filename
+ %c
+ capabilities
- %F
+ %t
+ trust/validity of the key-uid association
- file permissions
+ %[<s>]
+ date of the key where <s> is an strftime(3) expression
- %g
+ (PGP only)
- group name (or numeric gid, if missing)
+198. $pgp_export_command
- %l
+ Type: string
- number of hard links
+ Default: ""
- %N
+ This command is used to export a public key from the user's key ring.
+ (PGP only)
- N if folder has new mail, blank otherwise
+199. $pgp_getkeys_command
- %s
+ Type: string
- size in bytes
+ Default: ""
- %t
+ 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)
- * if the file is tagged, blank otherwise
-
- %u
-
- owner name (or numeric uid, if missing)
-
- %>X
-
- right justify the rest of the string and pad with character "X"
-
- %|X
-
- pad to the end of the line with character "X"
-
-73. $followup_to
-
- Type: boolean
-
- Default: yes
-
- 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.
-
- 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.
-
-74. $force_buffy_check
-
- Type: boolean
-
- Default: no
-
- 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.
-
- Also see the following variables: ``$timeout'', ``$mail_check'' and
- ``$imap_mail_check''.
-
-75. $force_list_reply
-
- Type: quadoption
-
- Default: ask-no
-
- This variable controls what effect ordinary replies have on mailing list
- messages: if set, a normal reply will be interpreted as list-reply while
- if it's unset the reply functions work as usual.
-
-76. $force_name
-
- Type: boolean
-
- Default: no
-
- 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.
-
- Also see the ``$record'' variable.
-
-77. $forward_decode
+200. $pgp_good_sign
- Type: boolean
+ Type: regular expression
- Default: yes
+ Default: ""
- 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.
+ If you assign a text to this variable, then a PGP signature is only
+ considered verified if the output from $\b$p\bpg\bgp\bp_\b_v\bve\ber\bri\bif\bfy\by_\b_c\bco\bom\bmm\bma\ban\bnd\bd contains
+ the text. Use this variable if the exit code from the command is 0
+ even for bad signatures. (PGP only)
-78. $forward_decrypt
+201. $pgp_ignore_subkeys
Type: boolean
Default: yes
- 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)
-
-79. $forward_edit
-
- Type: quadoption
-
- Default: yes
-
- 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.
+ Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys.
+ Instead, the principal key will inherit the subkeys' capabilities.
+ _\bU_\bn_\bs_\be_\bt this if you want to play interesting key selection games. (PGP
+ only)
-80. $forward_format
+202. $pgp_import_command
Type: string
- Default: "[%a: %s]"
-
- This variable controls the default subject when forwarding a message. It
- uses the same format sequences as the ``$index_format'' variable.
-
-81. $forward_quote
-
- Type: boolean
-
- Default: no
-
- When set forwarded messages included in the main body of the message (when
- ``$mime_forward'' is unset) will be quoted using ``$indent_string''.
-
-82. $from
-
- Type: e-mail address
-
Default: ""
- 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.
-
- 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.
-
- Defaults to the contents of the environment variable $EMAIL.
-
-83. $gecos_mask
-
- Type: regular expression
-
- 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''.
-
-84. $hdrs
-
- Type: boolean
-
- Default: yes
-
- 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.
-
-85. $header
-
- Type: boolean
-
- Default: no
+ This command is used to import a key from a message into the user's
+ public key ring. (PGP only)
- 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.
-
-86. $header_cache
+203. $pgp_list_pubring_command
- Type: path
+ Type: string
Default: ""
- Availability: Header Cache
-
- The $header_cache variable points to the header cache database.
-
- 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.
-
-87. $header_cache_compress
-
- Type: boolean
-
- Default: no
-
- 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.
-
-88. $help
-
- Type: boolean
-
- Default: yes
-
- When set, help lines describing the bindings for the major functions
- provided by each menu are displayed on the first line of the screen.
-
- 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.
+ 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.
-89. $hidden_host
-
- Type: boolean
-
- Default: no
-
- 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.
-
-90. $hide_limited
-
- Type: boolean
-
- Default: no
-
- When set, Mutt-ng will not show the presence of messages that are hidden
- by limiting, in the thread tree.
-
-91. $hide_missing
-
- Type: boolean
-
- Default: yes
+ This format is also generated by the pgpring utility which comes with
+ Mutt-ng. (PGP only)
- When set, Mutt-ng will not show the presence of missing messages in the
- thread tree.
+204. $pgp_list_secring_command
-92. $hide_thread_subject
+ Type: string
- Type: boolean
+ Default: ""
- Default: yes
+ 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.
- 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.
+ This format is also generated by the pgpring utility which comes with
+ Mutt-ng. (PGP only)
-93. $hide_top_limited
+205. $pgp_long_ids
Type: boolean
Default: no
- 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.
-
-94. $hide_top_missing
-
- Type: boolean
-
- Default: yes
-
- 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.
-
-95. $history
-
- Type: number
-
- Default: 10
-
- 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.
+ If _\bs_\be_\bt, use 64 bit PGP key IDs. _\bU_\bn_\bs_\be_\bt uses the normal 32 bit Key IDs.
+ (PGP only)
-96. $honor_followup_to
+206. $pgp_mime_auto
Type: quadoption
- Default: yes
-
- This variable controls whether or not a Mail-Followup-To: header field is
- honored when group-replying to a message.
-
-97. $hostname
-
- Type: string
-
- Default: ""
+ Default: ask-yes
- Specifies the hostname to use after the ``@'' in local e-mail addresses
- and during generation of Message-ID: headers.
+ 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).
- Please be sure to really know what you are doing when changing this
- variable to configure a custom domain part of Message-IDs.
+ Also note that using the old-style PGP message format is
+ _\bs_\bt_\br_\bo_\bn_\bg_\bl_\by_\bd_\be_\bp_\br_\be_\bc_\ba_\bt_\be_\bd. (PGP only)
-98. $ignore_list_reply_to
+207. $pgp_replyinline
Type: boolean
Default: no
- 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.
-
-99. $imap_authenticators
-
- Type: string
-
- Default: ""
-
- Availability: IMAP
-
- 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.
-
- If this parameter is unset (the default) Mutt-ng will try all available
- methods, in order from most-secure to least-secure.
+ 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
+ _\bp_\bg_\bp_\b-_\bm_\be_\bn_\bu, 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.
- Example: set imap_authenticators="gssapi:cram-md5:login"
+ 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: ``$\b$p\bpg\bgp\bp_\b_m\bmi\bim\bme\be_\b_a\bau\but\bto\bo''.
- 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.
+ Also note that using the old-style PGP message format is
+ _\bs_\bt_\br_\bo_\bn_\bg_\bl_\by_\bd_\be_\bp_\br_\be_\bc_\ba_\bt_\be_\bd. (PGP only)
-100. $imap_check_subscribed
+208. $pgp_retainable_sigs
Type: boolean
Default: no
- 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.
-
-101. $imap_delim_chars
-
- Type: string
-
- Default: "/."
-
- Availability: IMAP
-
- 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.
-
-102. $imap_headers
+ If _\bs_\be_\bt, signed and encrypted messages will consist of nested
+ multipart/signed and multipart/encrypted body parts.
- Type: string
+ 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)
- Default: ""
+209. $pgp_show_unusable
- Availability: IMAP
+ Type: boolean
- 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.
+ Default: yes
- Note: This is a space separated list.
+ If _\bs_\be_\bt, 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)
-103. $imap_home_namespace
+210. $pgp_sign_as
Type: string
Default: ""
- Availability: IMAP
-
- 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.
-
-104. $imap_keepalive
-
- Type: number
-
- Default: 900
-
- Availability: IMAP
-
- 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.
-
- 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.
-
- Reduce this number if you find yourself getting disconnected from your
- IMAP server due to inactivity.
-
-105. $imap_list_subscribed
+ 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)
- Type: boolean
-
- Default: no
-
- Availability: IMAP
-
- 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.
-
-106. $imap_login
-
- Type: string
-
- Default: ""
-
- Availability: IMAP
-
- Your login name on the IMAP server.
-
- This variable defaults to the value of ``$imap_user.''
-
-107. $imap_mail_check
-
- Type: number
-
- Default: 300
-
- 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.
-
-108. $imap_pass
-
- Type: string
-
- Default: ""
-
- Availability: IMAP
-
- Specifies the password for your IMAP account. If unset, Mutt-ng will
- prompt you for your password when you invoke the fetch-mail function.
-
- 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.
-
-109. $imap_passive
-
- Type: boolean
-
- Default: yes
-
- Availability: IMAP
-
- 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.
-
-110. $imap_peek
-
- Type: boolean
-
- Default: yes
-
- Availability: IMAP
-
- 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.
-
-111. $imap_reconnect
-
- Type: quadoption
-
- Default: ask-yes
-
- Availability: IMAP
-
- Controls whether or not Mutt-ng will try to reconnect to IMAP server when
- the connection is lost.
-
-112. $imap_servernoise
-
- Type: boolean
-
- Default: yes
-
- Availability: IMAP
-
- 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.
-
-113. $imap_user
-
- Type: string
-
- Default: ""
-
- Availability: IMAP
-
- The name of the user whose mail you intend to access on the IMAP server.
-
- This variable defaults to your user name on the local machine.
-
-114. $implicit_autoview
-
- Type: boolean
-
- Default: no
-
- 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.
-
-115. $include
-
- Type: quadoption
-
- Default: ask-yes
-
- 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
-
- Controls whether or not Mutt-ng includes only the first attachment of the
- message you are replying.
-
-117. $indent_string
-
- Type: string
-
- Default: "> "
-
- 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.
-
-118. $index_format
-
- Type: string
-
- Default: "%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s"
-
- This variable allows you to customize the message index display to your
- personal taste.
-
- ``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
-
- %A
-
- reply-to address (if present; otherwise: address of author)
-
- %b
-
- filename of the original message folder (think mailBox)
-
- %B
-
- the list to which the letter was sent, or else the folder name
- (%b).
-
- %c
-
- number of characters (bytes) in the message
-
- %C
-
- current message number
-
- %d
-
- date and time of the message in the format specified by
- ``date_format'' converted to sender's time zone
-
- %D
-
- date and time of the message in the format specified by
- ``date_format'' converted to the local time zone
-
- %e
-
- current message number in thread
-
- %E
-
- number of messages in current thread
-
- %f
-
- entire From: line (address + real name)
-
- %F
-
- author name, or recipient name if the message is from you
-
- %H
-
- spam attribute(s) of this message
-
- %g
-
- newsgroup name (if compiled with nntp support)
-
- %i
-
- message-id of the current message
-
- %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
-
- %n
-
- author's real name (or address if missing)
-
- %O
-
- (_O_riginal save folder) Where Mutt-ng would formerly have stashed
- the message: list name or recipient name if no list
-
- %s
-
- subject of the message
-
- %S
-
- status of the message (N/D/d/!/r/*)
-
- %t
-
- `to:' field (recipients)
-
- %T
-
- the appropriate character from the $to_chars string
-
- %u
-
- user (login) name of the author
-
- %v
-
- first name of the author, or the recipient if the message is from
- you
-
- %W
-
- name of organization of author (`organization:' field)
-
- %X
-
- number of attachments
-
- %y
-
- `x-label:' field, if present
-
- %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'.
-
- %Z
-
- message status flags
-
- %{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
-
- %[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
-
- %(fmt)
-
- the local date and time when the message was received. ``fmt'' is
- expanded by the library function ``strftime''; a leading bang
- disables locales
-
- %<fmt>
-
- the current local time. ``fmt'' is expanded by the library
- function ``strftime''; a leading bang disables locales.
-
- %>X
-
- right justify the rest of the string and pad with character "X"
-
- %|X
-
- pad to the end of the line with character "X"
-
- See also: ``$to_chars''.
-
-119. $ispell
-
- Type: path
-
- Default: "ispell"
-
- How to invoke ispell (GNU's spell-checking software).
-
-120. $keep_flagged
-
- Type: boolean
-
- Default: no
-
- 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.
-
-121. $locale
-
- Type: string
-
- Default: "C"
-
- The locale used by strftime(3) to format dates. Legal values are the
- strings your system accepts for the locale variable LC_TIME.
-
-122. $mail_check
-
- Type: number
-
- Default: 5
-
- This variable configures how often (in seconds) Mutt-ng should look for
- new mail.
-
- Note: This does not apply to IMAP mailboxes, see $imap_mail_check.
-
-123. $mailcap_path
-
- Type: string
-
- Default: ""
-
- This variable specifies which files to consult when attempting to display
- MIME bodies not directly supported by Mutt-ng.
-
-124. $mailcap_sanitize
-
- Type: boolean
-
- Default: yes
-
- 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.
-
- DON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE DOING!
-
-125. $maildir_header_cache_verify
-
- Type: boolean
-
- Default: yes
-
- Availability: Header Cache
-
- 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.
-
-126. $maildir_trash
-
- Type: boolean
-
- Default: no
-
- If set, messages marked as deleted will be saved with the maildir
- (T)rashed flag instead of physically deleted.
-
- NOTE: this only applies to maildir-style mailboxes. Setting it will have
- no effect on other mailbox types.
-
- It is similiar to the trash option.
-
-127. $mark_old
-
- Type: boolean
-
- Default: yes
-
- Controls whether or not Mutt-ng marks newunread messages as old if you
- exit a mailbox without reading them.
-
- 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.
-
-128. $markers
-
- Type: boolean
-
- Default: yes
-
- 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.
-
-129. $mask
-
- Type: regular expression
-
- Default: "!^\.[^.]"
-
- 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.
-
-130. $max_display_recips
-
- Type: number
-
- Default: 0
-
- 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.
-
-131. $max_line_length
-
- Type: number
-
- Default: 0
-
- 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.
-
-132. $mbox
-
- Type: path
-
- Default: "~/mbox"
-
- This specifies the folder into which read mail in your ``$spoolfile''
- folder will be appended.
-
-133. $mbox_type
-
- Type: folder magic
-
- Default: mbox
-
- The default mailbox type used when creating new folders. May be any of
- mbox, MMDF, MH and Maildir.
-
-134. $menu_context
-
- Type: number
-
- Default: 0
-
- This variable controls the number of lines of context that are given when
- scrolling through menus. (Similar to ``$pager_context''.)
-
-135. $menu_move_off
-
- Type: boolean
-
- Default: yes
-
- 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.
-
-136. $menu_scroll
-
- Type: boolean
-
- Default: no
-
- 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).
-
-137. $message_format
-
- Type: string
-
- Default: "%s"
-
- 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''.
-
-138. $meta_key
-
- Type: boolean
-
- Default: no
-
- 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''.
-
-139. $metoo
-
- Type: boolean
-
- Default: no
-
- If unset, Mutt-ng will remove your address (see the ``alternates''
- command) from the list of recipients when replying to a message.
-
-140. $mh_purge
-
- Type: boolean
-
- Default: no
-
- 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.
-
-141. $mh_seq_flagged
-
- Type: string
-
- Default: "flagged"
-
- The name of the MH sequence used for flagged messages.
-
-142. $mh_seq_replied
-
- Type: string
-
- Default: "replied"
-
- The name of the MH sequence used to tag replied messages.
-
-143. $mh_seq_unseen
-
- Type: string
-
- Default: "unseen"
-
- The name of the MH sequence used for unseen messages.
-
-144. $mime_forward
-
- Type: quadoption
-
- Default: no
-
- 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.
-
- 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.
-
- Also see ``$forward_decode'' and ``$mime_forward_decode''.
-
-145. $mime_forward_decode
-
- Type: boolean
-
- Default: no
-
- 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.
-
-146. $mime_forward_rest
-
- Type: quadoption
-
- Default: yes
-
- 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.
-
-147. $mix_entry_format
-
- Type: string
-
- Default: "%4n %c %-16s %a"
-
- 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:
-
- %n
-
- The running number on the menu.
-
- %c
-
- Remailer capabilities.
-
- %s
-
- The remailer's short name.
-
- %a
-
- The remailer's e-mail address.
-
-148. $mixmaster
-
- Type: path
-
- Default: "mixmaster"
-
- Availability: Mixmaster
-
- 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.
-
-149. $move
-
- Type: quadoption
-
- Default: ask-no
-
- 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.
-
-150. $msgid_format
-
- Type: string
-
- Default: "%Y%m%d%h%M%s.G%P%p"
-
- 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:
-
- %d
-
- the current day of month
-
- %h
-
- the current hour
-
- %m
-
- the current month
-
- %M
-
- the current minute
-
- %O
-
- the current UNIX timestamp (octal)
-
- %p
-
- the process ID
-
- %P
-
- the current Message-ID prefix (a character rotating with every
- Message-ID being generated)
-
- %r
-
- a random integer value (decimal)
-
- %R
-
- a random integer value (hexadecimal)
-
- %s
-
- the current second
-
- %T
-
- the current UNIX timestamp (decimal)
-
- %X
-
- the current UNIX timestamp (hexadecimal)
-
- %Y
-
- the current year (Y2K compliant)
-
- %%
-
- the '%' character
-
- Note: Please only change this setting if you know what you are doing. Also
- make sure to consult RFC2822 to produce technically valid strings.
-
-151. $muttng_bindir
-
- Type: system property
-
- Value: /opt/freebsd4/mutt-ng/bin
-
- This is a read-only system property and specifies the directory containing
- the muttng binary.
-
-152. $muttng_docdir
-
- Type: system property
-
- Value: /opt/freebsd4/mutt-ng/doc/muttng
-
- This is a read-only system property and specifies the directory containing
- the muttng documentation.
-
-153. $muttng_folder_name
-
- Type: system property
-
- Value:
-
- 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 ``/''.
-
-154. $muttng_folder_path
-
- Type: system property
-
- Value:
-
- This is a read-only system property and, at runtime, specifies the full
- path or URI of the folder currently open (if any).
-
-155. $muttng_hcache_backend
-
- Type: system property
-
- Value: qdbm
-
- This is a read-only system property and specifies the header chaching's
- database backend.
-
-156. $muttng_pwd
-
- Type: system property
-
- Value:
-
- This is a read-only system property and, at runtime, specifies the current
- working directory of the muttng binary.
-
-157. $muttng_revision
-
- Type: system property
-
- Value: 545
-
- This is a read-only system property and specifies muttng's subversion
- revision string.
-
-158. $muttng_sysconfdir
-
- Type: system property
-
- Value: /opt/freebsd4/mutt-ng/etc
-
- This is a read-only system property and specifies the directory containing
- the muttng system-wide configuration.
-
-159. $muttng_version
-
- Type: system property
-
- Value: devel
-
- This is a read-only system property and specifies muttng's version string.
-
-160. $narrow_tree
-
- Type: boolean
-
- Default: no
-
- This variable, when set, makes the thread tree narrower, allowing deeper
- threads to fit on the screen.
-
-161. $net_inc
-
- Type: number
-
- Default: 10
-
- Operations that expect to transfer a large amount of data over the network
- will update their progress every net_inc kilobytes. If set to 0, no
- progress messages will be displayed.
-
- See also ``$read_inc'' and ``$write_inc''.
-
-162. $nntp_ask_followup_to
-
- Type: boolean
-
- Default: no
-
- Availability: NNTP
-
- If set, Mutt-ng will prompt you for the Followup-To: header field before
- editing the body of an outgoing news article.
-
-163. $nntp_ask_x_comment_to
-
- Type: boolean
-
- Default: no
-
- Availability: NNTP
-
- If set, Mutt-ng will prompt you for the X-Comment-To: header field before
- editing the body of an outgoing news article.
-
-164. $nntp_cache_dir
-
- Type: path
-
- Default: "~/.muttng"
-
- Availability: NNTP
-
- 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.
-
- As for the header caching in connection with IMAP and/or Maildir, this
- drastically increases speed and lowers traffic.
-
-165. $nntp_catchup
-
- Type: quadoption
-
- Default: ask-yes
-
- Availability: NNTP
-
- If this variable is set, Mutt-ng will mark all articles in a newsgroup as
- read when you leaving it.
-
-166. $nntp_context
-
- Type: number
-
- Default: 1000
-
- Availability: NNTP
-
- 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.
-
- If there're more articles than defined with $nntp_context, all older ones
- will be removed/not shown in the index.
-
-167. $nntp_followup_to_poster
-
- 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.
-
-168. $nntp_group_index_format
-
- Type: string
-
- Default: "%4C %M%N %5s %-45.45f %d"
-
- Availability: NNTP
-
- 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:
-
- %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"
-
-
-169. $nntp_host
-
- Type: string
-
- Default: ""
-
- Availability: NNTP
-
- This variable specifies the name (or address) of the NNTP server to be
- used.
-
- It defaults to the value specified via the environment variable
- $NNTPSERVER or contained in the file /etc/nntpserver.
-
- You can also specify a username and an alternative port for each
- newsserver, e.g.
-
- [nntp[s]://][username[:password]@]newsserver[:port]
-
- 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.
-
-170. $nntp_inews
-
- Type: path
-
- Default: ""
-
- Availability: NNTP
-
- 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:
-
- %s newsserver name
-
-
- Example: set inews="/usr/local/bin/inews -hS"
-
-171. $nntp_load_description
-
- Type: boolean
-
- Default: yes
-
- Availability: NNTP
-
- This variable controls whether or not descriptions for newsgroups are to
- be loaded when subscribing to a newsgroup.
-
-172. $nntp_mail_check
-
- Type: number
-
- Default: 60
-
- Availability: NNTP
-
- 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.).
-
-173. $nntp_mime_subject
-
- Type: boolean
-
- Default: yes
-
- Availability: NNTP
-
- If unset, an 8-bit ``Subject:'' header field in a news article will not be
- encoded according to RFC2047.
-
- Note: Only change this setting if you know what you are doing.
-
-174. $nntp_newsrc
-
- Type: path
-
- Default: "~/.newsrc"
-
- Availability: NNTP
-
- This file contains information about subscribed newsgroup and articles
- read so far.
-
- To ease the use of multiple news servers, the following printf(3)-style
- sequence is understood:
-
- %s newsserver name
-
-
-175. $nntp_pass
-
- Type: string
-
- Default: ""
-
- Availability: NNTP
-
- Your password for NNTP account.
-
- 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.
-
-176. $nntp_post_moderated
-
- Type: quadoption
-
- Default: ask-yes
-
- Availability: NNTP
-
- If set to yes, Mutt-ng will post articles to newsgroup that have not
- permissions to post (e.g. moderated).
-
- 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.
-
-177. $nntp_reconnect
-
- Type: quadoption
-
- Default: ask-yes
-
- Availability: NNTP
-
- Controls whether or not Mutt-ng will try to reconnect to a newsserver when
- the was connection lost.
-
-178. $nntp_save_unsubscribed
-
- Type: boolean
-
- Default: no
-
- Availability: NNTP
-
- When set, info about unsubscribed newsgroups will be saved into the
- ``newsrc'' file and into the news cache.
-
-179. $nntp_show_new_news
-
- Type: boolean
-
- Default: yes
-
- Availability: NNTP
-
- 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.
-
-180. $nntp_show_only_unread
-
- Type: boolean
-
- Default: no
-
- Availability: NNTP
-
- If set, only subscribed newsgroups that contain unread articles will be
- displayed in the newsgroup browser.
-
-181. $nntp_user
-
- Type: string
-
- Default: ""
-
- Availability: NNTP
-
- Your login name on the NNTP server. If unset and the server requires
- authentification, Mutt-ng will prompt you for your account name.
-
-182. $nntp_x_comment_to
-
- Type: boolean
-
- Default: no
-
- Availability: NNTP
-
- 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.
-
-183. $operating_system
-
- 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)''.
-
-184. $pager
-
- Type: path
-
- Default: "builtin"
-
- 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.
-
- 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.
-
-185. $pager_context
-
- Type: number
-
- Default: 0
-
- 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).
-
-186. $pager_format
-
- Type: string
-
- Default: "-%Z- %C/%m: %-20.20n %s"
-
- 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.
-
-187. $pager_index_lines
-
- Type: number
-
- Default: 0
-
- 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.
-
-188. $pager_stop
-
- 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.
-
-189. $pgp_auto_decode
-
- Type: boolean
-
- Default: no
-
- 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.
-
-190. $pgp_autoinline
-
- Type: boolean
-
- Default: no
-
- 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.
-
- 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''.
-
- Also note that using the old-style PGP message format is
- stronglydeprecated. (PGP only)
-
-191. $pgp_check_exit
-
- Type: boolean
-
- Default: yes
-
- 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)
-
-192. $pgp_clearsign_command
-
- Type: string
-
- Default: ""
-
- This format is used to create a old-style ``clearsigned'' PGP message.
-
- Note that the use of this format is stronglydeprecated. (PGP only)
-
-193. $pgp_decode_command
-
- 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.
-
- %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.
-
- %a
-
- The value of $pgp_sign_as.
-
- %r
-
- One or more key IDs.
-
- 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)
-
-194. $pgp_decrypt_command
-
- Type: string
-
- Default: ""
-
- This command is used to decrypt a PGP encrypted message. (PGP only)
-
-195. $pgp_encrypt_only_command
-
- Type: string
-
- Default: ""
-
- This command is used to encrypt a body part without signing it. (PGP only)
-
-196. $pgp_encrypt_sign_command
-
- Type: string
-
- Default: ""
-
- This command is used to both sign and encrypt a body part. (PGP only)
-
-197. $pgp_entry_format
-
- Type: string
-
- Default: "%4n %t%f %4l/0x%k %-4a %2c %u"
-
- 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:
-
- %n
-
- number
-
- %k
-
- key id
-
- %u
-
- user id
-
- %a
-
- algorithm
-
- %l
-
- key length
-
- %f
-
- flags
-
- %c
-
- capabilities
-
- %t
-
- trust/validity of the key-uid association
-
- %[<s>]
-
- date of the key where <s> is an strftime(3) expression
-
- (PGP only)
-
-198. $pgp_export_command
-
- Type: string
-
- Default: ""
-
- This command is used to export a public key from the user's key ring. (PGP
- only)
-
-199. $pgp_getkeys_command
-
- Type: string
-
- Default: ""
-
- 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)
-
-200. $pgp_good_sign
-
- Type: regular expression
-
- Default: ""
-
- 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)
-
-201. $pgp_ignore_subkeys
-
- 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)
-
-202. $pgp_import_command
-
- Type: string
-
- Default: ""
-
- This command is used to import a key from a message into the user's public
- key ring. (PGP only)
-
-203. $pgp_list_pubring_command
-
- Type: string
-
- Default: ""
-
- 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.
-
- This format is also generated by the pgpring utility which comes with
- Mutt-ng. (PGP only)
-
-204. $pgp_list_secring_command
-
- Type: string
-
- Default: ""
-
- 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.
-
- This format is also generated by the pgpring utility which comes with
- Mutt-ng. (PGP only)
-
-205. $pgp_long_ids
-
- Type: boolean
-
- Default: no
-
- If set, use 64 bit PGP key IDs. Unset uses the normal 32 bit Key IDs. (PGP
- only)
-
-206. $pgp_mime_auto
-
- Type: quadoption
-
- Default: ask-yes
-
- 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).
-
- Also note that using the old-style PGP message format is
- stronglydeprecated. (PGP only)
-
-207. $pgp_replyinline
-
- 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.
-
- 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''.
-
- Also note that using the old-style PGP message format is
- stronglydeprecated. (PGP only)
-
-208. $pgp_retainable_sigs
-
- Type: boolean
-
- Default: no
-
- If set, signed and encrypted messages will consist of nested
- multipart/signed and multipart/encrypted body parts.
-
- 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)
-
-209. $pgp_show_unusable
-
- Type: boolean
-
- Default: yes
-
- 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)
-
-210. $pgp_sign_as
-
- Type: string
-
- Default: ""
-
- 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)
-
-211. $pgp_sign_command
-
- Type: string
-
- Default: ""
-
- This command is used to create the detached PGP signature for a
- multipart/signed PGP/MIME body part. (PGP only)
-
-212. $pgp_sort_keys
-
- Type: sort order
-
- Default: address
-
- Specifies how the entries in the ``pgp keys'' menu are sorted. The
- following are legal values:
-
- address
-
- sort alphabetically by user id
-
- keyid
-
- sort alphabetically by key id
-
- date
-
- sort by key creation date
-
- trust
-
- sort by the trust of the key
-
- If you prefer reverse order of the above values, prefix it with
- ``reverse-''. (PGP only)
-
-213. $pgp_strict_enc
-
- 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)
-
-214. $pgp_timeout
-
- Type: number
-
- Default: 300
-
- The number of seconds after which a cached passphrase will expire if not
- used. Default: 300. (PGP only)
-
-215. $pgp_use_gpg_agent
-
- Type: boolean
-
- Default: no
-
- If set, Mutt-ng will use a possibly-running gpg-agent process. (PGP only)
-
-216. $pgp_verify_command
-
- Type: string
-
- Default: ""
-
- This command is used to verify PGP signatures. (PGP only)
-
-217. $pgp_verify_key_command
-
- Type: string
-
- Default: ""
-
- This command is used to verify key information from the key selection
- menu. (PGP only)
-
-218. $pipe_decode
-
- Type: boolean
-
- Default: no
-
- 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.
-
-219. $pipe_sep
-
- Type: string
-
- Default: "\n"
-
- The separator to add between messages when piping a list of tagged
- messages to an external Unix command.
-
-220. $pipe_split
-
- 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.
-
-221. $pop_auth_try_all
-
- Type: boolean
-
- Default: yes
-
- Availability: POP
-
- 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.
-
-222. $pop_authenticators
-
- Type: string
-
- Default: ""
-
- Availability: POP
-
- 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''.
-
- 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.
-
- Example: set pop_authenticators="digest-md5:apop:user"
-
-223. $pop_delete
-
- Type: quadoption
-
- Default: ask-no
-
- Availability: POP
-
- 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.
-
-224. $pop_host
-
- Type: string
-
- Default: ""
-
- Availability: POP
-
- The name of your POP server for the ``fetch-mail'' function. You can also
- specify an alternative port, username and password, i.e.:
-
- [pop[s]://][username[:password]@]popserver[:port]
-
- 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.
-
-225. $pop_last
-
- Type: boolean
-
- Default: no
-
- Availability: POP
-
- 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.
-
-226. $pop_mail_check
-
- Type: number
-
- Default: 60
-
- Availability: POP
-
- This variable configures how often (in seconds) Mutt-ng should look for
- new mail.
-
-227. $pop_pass
-
- Type: string
-
- Default: ""
-
- Availability: POP
-
- Specifies the password for your POP account. If unset, Mutt-ng will prompt
- you for your password when you open POP mailbox.
-
- 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.
-
-228. $pop_reconnect
-
- Type: quadoption
-
- Default: ask-yes
-
- Availability: POP
-
- Controls whether or not Mutt-ng will try to reconnect to a POP server if
- the connection is lost.
-
-229. $pop_user
-
- Type: string
-
- Default: ""
-
- Availability: POP
-
- Your login name on the POP server.
-
- This variable defaults to your user name on the local machine.
-
-230. $post_indent_string
-
- 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.
-
-231. $postpone
-
- Type: quadoption
-
- Default: ask-yes
-
- Controls whether or not messages are saved in the ``$postponed'' mailbox
- when you elect not to send immediately.
-
-232. $postponed
-
- Type: path
-
- Default: "~/postponed"
-
- 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.
-
-233. $preconnect
-
- Type: string
-
- Default: ""
-
- 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:
-
- preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net sleep 20 <
- /dev/null > /dev/null"
-
- Mailbox ``foo'' on mailhost.net can now be reached as
- ``{localhost:1234}foo''.
-
- Note: For this example to work, you must be able to log in to the remote
- machine without having to enter a password.
-
-234. $print
-
- Type: quadoption
-
- Default: ask-no
-
- Controls whether or not Mutt-ng really prints messages. This is set to
- ask-no by default, because some people accidentally hit ``p'' often.
-
-235. $print_command
-
- Type: path
-
- Default: "lpr"
-
- This specifies the command pipe that should be used to print messages.
-
-236. $print_decode
-
- Type: boolean
-
- Default: yes
-
- 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.
-
-237. $print_split
-
- 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.
-
- Those who use the enscript(1) program's mail-printing mode will most
- likely want to set this option.
-
-238. $prompt_after
-
- 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.
-
-239. $query_command
-
- Type: path
-
- Default: ""
-
- 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.
-
-240. $quit
-
- 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.
-
-241. $quote_empty
-
- Type: boolean
-
- Default: yes
-
- Controls whether or not empty lines will be quoted using
- ``indent_string''.
-
-242. $quote_quoted
-
- 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''.
-
-243. $quote_regexp
-
- Type: regular expression
-
- Default: "^([ \t]*[|>:}#])+"
-
- A regular expression used in the internal-pager to determine quoted
- sections of text in the body of a message.
-
- 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.
-
-244. $read_inc
-
- Type: number
-
- Default: 10
-
- 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.
-
- Also see the ``$write_inc'' variable.
-
-245. $read_only
-
- Type: boolean
-
- Default: no
-
- If set, all folders are opened in read-only mode.
-
-246. $realname
-
- Type: string
-
- 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.
-
- Note: This variable will not be used when the user has set a real name in
- the $from variable.
-
-247. $recall
-
- Type: quadoption
-
- Default: ask-yes
-
- Controls whether or not Mutt-ng recalls postponed messages when composing
- a new message. Also see ``$postponed''.
-
- Setting this variable to yes is not generally useful, and thus not
- recommended.
-
-248. $record
-
- Type: path
-
- Default: ""
-
- 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.)
-
- The value of $record is overridden by the ``$force_name'' and
- ``$save_name'' variables, and the ``fcc-hook'' command.
-
-249. $reply_regexp
-
- Type: regular expression
-
- Default: "^(re([\[0-9\]+])*|aw):[ \t]*"
-
- A regular expression used to recognize reply messages when threading and
- replying. The default value corresponds to the English ``Re:'' and the
- German ``Aw:''.
-
-250. $reply_self
-
- 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.
-
-251. $reply_to
-
- Type: quadoption
-
- Default: ask-yes
-
- 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.
-
- 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.
-
-252. $resolve
-
- 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.
-
-253. $reverse_alias
-
- 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:
-
- alias juser abd30425@somewhere.net (Joe User)
-
- and then you receive mail which contains the following header:
-
- From: abd30425@somewhere.net
-
- 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).
-
-254. $reverse_name
-
- Type: boolean
-
- Default: no
-
- 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.
-
-255. $reverse_realname
-
- Type: boolean
-
- 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.
-
-256. $rfc2047_parameters
-
- Type: boolean
-
- Default: no
-
- 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:
-
- =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
-
- When this variable is set interactively, the change doesn't have the
- desired effect before you have changed folders.
-
- Note that this use of RFC 2047's encoding is explicitly, prohibited by the
- standard, but nevertheless encountered in the wild.
-
- 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.
-
-257. $save_address
-
- Type: boolean
-
- Default: no
-
- 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.
-
-258. $save_empty
-
- Type: boolean
-
- Default: yes
-
- 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.
-
- Note: This only applies to mbox and MMDF folders, Mutt-ng does not delete
- MH and Maildir directories.
-
-259. $save_name
-
- 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.
-
- Also see the ``$force_name'' variable.
-
-260. $score
-
- Type: boolean
-
- Default: yes
-
- 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.
-
-261. $score_threshold_delete
-
- Type: number
-
- Default: -1
-
- 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.
-
-262. $score_threshold_flag
-
- Type: number
-
- Default: 9999
-
- Messages which have been assigned a score greater than or equal to this
- variable's value are automatically marked ``flagged''.
-
-263. $score_threshold_read
-
- Type: number
-
- Default: -1
-
- 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.
-
-264. $send_charset
-
- Type: string
-
- Default: "us-ascii:iso-8859-1:utf-8"
-
- 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.
-
-265. $sendmail
-
- Type: path
-
- Default: "/usr/sbin/sendmail -oem -oi"
-
- 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.
-
-266. $sendmail_wait
-
- Type: number
-
- Default: 0
-
- Specifies the number of seconds to wait for the ``$sendmail'' process to
- finish before giving up and putting delivery in the background.
-
- Mutt-ng interprets the value of this variable as follows:
-
- >0
-
- number of seconds to wait for sendmail to finish before continuing
-
- 0
-
- wait forever for sendmail to finish
-
- <0
-
- always put sendmail in the background without waiting
-
- 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.
-
-267. $shell
-
- Type: path
-
- Default: ""
-
- Command to use when spawning a subshell. By default, the user's login
- shell from /etc/passwd is used.
-
-268. $sidebar_boundary
-
- Type: string
-
- Default: "."
-
- 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.''
-
-269. $sidebar_delim
-
- Type: string
-
- Default: "|"
-
- This specifies the delimiter between the sidebar (if visible) and other
- screens.
-
-270. $sidebar_newmail_only
-
- Type: boolean
-
- Default: no
-
- If set, only folders with new mail will be shown in the sidebar.
-
-271. $sidebar_number_format
-
- Type: string
-
- Default: "%m%?n?(%n)?%?f?[%f]?"
-
- 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.)
-
- The following printf(3)-like sequences are supported all of which may be
- printed non-zero:
-
- %d
-
- Number of deleted messages. 1)
-
- %F
-
- Number of flagged messages.
-
- %m
-
- Total number of messages.
-
- %M
-
- Total number of messages shown, i.e. not hidden by a limit. 1)
-
- %n
-
- Number of new messages.
-
- %t
-
- Number of tagged messages. 1)
-
- 1) These expandos only have a non-zero value for the current mailbox and
- will always be zero otherwise.
-
-272. $sidebar_shorten_hierarchy
-
- 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.
-
- At which characters this compression is done is controled via the
- $sidebar_boundary variable.
-
-273. $sidebar_visible
-
- Type: boolean
-
- Default: no
-
- This specifies whether or not to show the sidebar (a list of folders
- specified with the ``mailboxes'' command).
-
-274. $sidebar_width
-
- Type: number
-
- Default: 0
-
- The width of the sidebar.
-
-275. $sig_dashes
-
- Type: boolean
-
- Default: yes
-
- 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.
-
- For example, Mutt-ng has the ability to highlight the signature in a
- different color in the builtin pager.
-
-276. $sig_on_top
-
- Type: boolean
-
- Default: no
-
- 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.
-
-277. $signature
-
- Type: path
-
- Default: "~/.signature"
-
- 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.
-
-278. $signoff_string
-
- Type: string
-
- Default: ""
-
- 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.
-
- 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.
-
-279. $simple_search
-
- Type: string
-
- Default: "~f %s | ~s %s"
-
- 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.
-
- 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:
-
- ~f joe | ~s joe
-
-280. $sleep_time
-
- Type: number
-
- Default: 1
-
- 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.
-
-281. $smart_wrap
-
- Type: boolean
-
- Default: yes
-
- 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.
-
-282. $smileys
-
- Type: regular expression
-
- Default: "(>From )|(:[-^]?[][)(><}{|/DP])"
-
- The pager uses this variable to catch some common false positives of
- ``$quote_regexp'', most notably smileys in the beginning of a line
-
-283. $smime_ask_cert_label
-
- Type: boolean
-
- Default: yes
-
- 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)
-
-284. $smime_ca_location
-
- Type: path
-
- Default: ""
-
- This variable contains the name of either a directory, or a file which
- contains trusted certificates for use with OpenSSL. (S/MIME only)
-
-285. $smime_certificates
-
- Type: path
-
- Default: ""
-
- 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)
-
-286. $smime_decrypt_command
-
- Type: string
-
- Default: ""
-
- This format string specifies a command which is used to decrypt
- application/x-pkcs7-mime attachments.
-
- The OpenSSL command formats have their own set of printf(3)-like sequences
- similar to PGP's:
-
- %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.
-
- %k
-
- The key-pair specified with $smime_default_key
-
- %c
-
- One or more certificate IDs.
-
- %a
-
- The algorithm used for encryption.
-
- %C
-
- 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".
-
- 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)
-
-287. $smime_decrypt_use_default_key
-
- 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)
-
-288. $smime_default_key
-
- Type: string
-
- Default: ""
-
- 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)
-
-289. $smime_encrypt_command
-
- Type: string
-
- Default: ""
-
- This command is used to create encrypted S/MIME messages. (S/MIME only)
-
-290. $smime_encrypt_with
-
- Type: string
-
- Default: ""
-
- This sets the algorithm that should be used for encryption. Valid choices
- are ``des'', ``des3'', ``rc2-40'', ``rc2-64'', ``\frc2-128''.
-
- If unset ``3des'' (TripleDES) is used. (S/MIME only)
-
-291. $smime_get_cert_command
-
- Type: string
-
- Default: ""
-
- This command is used to extract X509 certificates from a PKCS7 structure.
- (S/MIME only)
-
-292. $smime_get_cert_email_command
-
- Type: string
-
- Default: ""
-
- 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)
-
-293. $smime_get_signer_cert_command
-
- Type: string
-
- Default: ""
-
- 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)
-
-294. $smime_import_cert_command
-
- Type: string
-
- Default: ""
-
- This command is used to import a certificate via smime_keysng. (S/MIME
- only)
-
-295. $smime_is_default
-
- Type: boolean
-
- Default: no
-
- 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.
-
- 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.
-
- (Note that this variable can be overridden by unsetting $crypt_autosmime.)
- (S/MIME only)
-
-296. $smime_keys
-
- Type: path
-
- Default: ""
-
- 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)
-
-297. $smime_pk7out_command
-
- Type: string
-
- Default: ""
-
- This command is used to extract PKCS7 structures of S/MIME signatures, in
- order to extract the public X509 certificate(s). (S/MIME only)
-
-298. $smime_sign_command
-
- Type: string
-
- Default: ""
-
- This command is used to created S/MIME signatures of type
- multipart/signed, which can be read by all mail clients. (S/MIME only)
-
-299. $smime_sign_opaque_command
-
- Type: string
-
- Default: ""
-
- 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)
-
-300. $smime_timeout
-
- Type: number
-
- Default: 300
-
- The number of seconds after which a cached passphrase will expire if not
- used. (S/MIME only)
-
-301. $smime_verify_command
-
- Type: string
-
- Default: ""
-
- This command is used to verify S/MIME signatures of type multipart/signed.
- (S/MIME only)
-
-302. $smime_verify_opaque_command
-
- Type: string
-
- Default: ""
-
- This command is used to verify S/MIME signatures of type
- application/x-pkcs7-mime. (S/MIME only)
-
-303. $smtp_host
-
- Type: string
-
- Default: ""
-
- Availability: SMTP
-
- 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.
-
-304. $smtp_pass
-
- Type: string
-
- Default: ""
-
- Availability: SMTP
-
- 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.
-
- 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.
-
-305. $smtp_port
-
- Type: number
-
- Default: 25
-
- Availability: SMTP
-
- Defines the port that the SMTP host is listening on for mail delivery.
- Must be specified as a number.
-
- Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP
- servers will probably desire 587, the mail submission port.
-
-306. $smtp_use_tls
-
- Type: string
-
- Default: ""
-
- Availability: SMTP (and SSL)
-
- 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.
-
-307. $smtp_user
-
- Type: string
-
- Default: ""
-
- Availability: SMTP
-
- Defines the username to use with SMTP AUTH. Setting this variable will
- cause Mutt-ng to attempt to use SMTP AUTH when sending.
-
-308. $sort
-
- Type: sort order
-
- Default: date
-
- Specifies how to sort messages in the index menu. Valid values are:
-
- date or date-sent
- date-received
- from
- mailbox-order (unsorted)
- score
- size
- spam
- subject
- threads
- to
-
-
- You may optionally use the ``reverse-'' prefix to specify reverse sorting
- order (example: set sort=reverse-date-sent).
-
-309. $sort_alias
-
- Type: sort order
-
- Default: alias
-
- Specifies how the entries in the ``alias'' menu are sorted. The following
- are legal values:
-
- address (sort alphabetically by email address)
- alias (sort alphabetically by alias name)
- unsorted (leave in order specified in .muttrc)
-
-
-310. $sort_aux
-
- Type: sort order
-
- Default: date
-
- 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.
-
- 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.)
-
- 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).
-
-311. $sort_browser
-
- Type: sort order
-
- Default: alpha
-
- Specifies how to sort entries in the file browser. By default, the entries
- are sorted alphabetically. Valid values:
-
- alpha (alphabetically)
- date
- size
- unsorted
-
-
- You may optionally use the ``reverse-'' prefix to specify reverse sorting
- order (example: set sort_browser=reverse-date).
-
-312. $sort_re
-
- Type: boolean
-
- Default: yes
-
- 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.
-
-313. $spam_separator
-
- Type: string
-
- Default: ","
-
- ``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.
-
-314. $spoolfile
-
- Type: path
-
- Default: ""
-
- 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.
-
-315. $ssl_ca_certificates_file
-
- Type: path
-
- Default: ""
-
- 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.
-
- Example: set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
-
-316. $ssl_client_cert
-
- Type: path
-
- Default: ""
-
- Availability: SSL
-
- The file containing a client certificate and its associated private key.
-
-317. $ssl_force_tls
-
- Type: boolean
-
- Default: no
-
- 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''.
-
-318. $ssl_min_dh_prime_bits
-
- Type: number
-
- Default: 0
-
- Availability: GNUTLS
-
- 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.
-
-319. $ssl_starttls
-
- Type: quadoption
-
- Default: yes
-
- Availability: SSL or GNUTLS
-
- 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.
-
-320. $ssl_use_sslv2
-
- Type: boolean
-
- Default: yes
-
- Availability: SSL
-
- This variables specifies whether to attempt to use SSLv2 in the SSL
- authentication process.
-
-321. $ssl_use_sslv3
-
- Type: boolean
-
- Default: yes
-
- Availability: SSL or GNUTLS
-
- This variables specifies whether to attempt to use SSLv3 in the SSL
- authentication process.
-
-322. $ssl_use_tlsv1
-
- Type: boolean
-
- Default: yes
-
- Availability: SSL or GNUTLS
-
- This variables specifies whether to attempt to use TLSv1 in the SSL
- authentication process.
-
-323. $ssl_usesystemcerts
-
- Type: boolean
-
- Default: yes
-
- Availability: SSL
-
- 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.
-
-324. $status_chars
-
- Type: string
-
- Default: "-*%A"
-
- 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).
-
-325. $status_format
-
- Type: string
-
- 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)---"
-
- 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:
-
- %b
-
- number of mailboxes with new mail *
-
- %B
-
- the short pathname of the current mailbox
-
- %d
-
- number of deleted messages *
-
- %f
-
- the full pathname of the current mailbox
-
- %F
-
- number of flagged messages *
-
- %h
-
- local hostname
-
- %l
-
- size (in bytes) of the current mailbox *
-
- %L
-
- size (in bytes) of the messages shown (i.e., which match the
- current limit) *
-
- %m
-
- the number of messages in the mailbox *
-
- %M
-
- the number of messages shown (i.e., which match the current limit)
- *
-
- %n
-
- number of new messages in the mailbox *
-
- %o
-
- number of old unread messages *
-
- %p
-
- number of postponed messages *
-
- %P
-
- percentage of the way through the index
-
- %r
-
- modified/read-only/won't-write/attach-message indicator, according
- to $status_chars
-
- %s
-
- current sorting mode ($sort)
-
- %S
-
- current aux sorting method ($sort_aux)
-
- %t
-
- number of tagged messages *
-
- %u
-
- number of unread messages *
-
- %v
-
- Mutt-ng version string
-
- %V
-
- currently active limit pattern, if any *
-
- %>X
-
- right justify the rest of the string and pad with "X"
-
- %|X
-
- pad to the end of the line with "X"
-
- * = can be optionally printed if nonzero
-
- 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
-
- %?<sequence_char>?<optional_string>?
-
- 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.
-
- Here is an example illustrating how to optionally print the number of new
- messages in a mailbox:
-
- %?n?%n new messages.?
-
- 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:
-
- %?<sequence_char>?<if_string>&<else_string>?
-
- 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:
-
- %_h
-
- 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.
-
-326. $status_on_top
-
- Type: boolean
-
- Default: no
-
- Setting this variable causes the ``status bar'' to be displayed on the
- first line of the screen rather than near the bottom.
-
-327. $strict_mailto
-
- 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.
-
- 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.
-
-328. $strict_mime
-
- Type: boolean
-
- Default: yes
-
- 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.
-
- 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.
-
-329. $strict_threads
-
- Type: boolean
-
- Default: no
-
- 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.
-
-330. $strip_was
-
- Type: boolean
-
- Default: no
-
- 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)
-
-331. $strip_was_regex
-
- Type: regular expression
-
- Default: "\([Ww][Aa][RrSs]: .*\)[ ]*$"
-
- 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.
-
-332. $stuff_quoted
-
- Type: boolean
-
- Default: no
-
- 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.
-
-333. $suspend
-
- Type: boolean
-
- Default: yes
-
- 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.''
-
-334. $text_flowed
-
- 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.
-
- Note that $indent_string is ignored when this option is set.
-
-335. $thorough_search
-
- Type: boolean
-
- Default: no
-
- 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.
-
-336. $thread_received
-
- Type: boolean
-
- Default: no
-
- When set, Mutt-ng uses the date received rather than the date sent to
- thread messages by subject.
-
-337. $tilde
-
- Type: boolean
-
- Default: no
-
- When set, the internal-pager will pad blank lines to the bottom of the
- screen with a tilde (~).
-
-338. $timeout
-
- Type: number
-
- Default: 600
-
- 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.
-
-339. $tmpdir
-
- Type: path
-
- Default: ""
-
- 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.
-
-340. $to_chars
-
- 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).
-
-341. $trash
-
- Type: path
-
- Default: ""
-
- 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.
-
- Note: When you delete a message in the trash folder, it is really deleted,
- so that there is no way to recover mail.
-
-342. $tunnel
-
- Type: string
-
- Default: ""
-
- 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:
-
- tunnel="ssh -q mailhost.net /usr/local/libexec/imapd"
-
- Note: For this example to work you must be able to log in to the remote
- machine without having to enter a password.
-
-343. $umask
-
- Type: number
-
- Default: 0077
-
- This sets the umask that will be used by Mutt-ng when creating all kinds
- of files. If unset, the default value is 077.
-
-344. $uncollapse_jump
-
- Type: boolean
-
- Default: no
-
- When set, Mutt-ng will jump to the next unread message, if any, when the
- current thread is uncollapsed.
-
-345. $use_8bitmime
-
- 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.
-
-346. $use_domain
-
- Type: boolean
-
- Default: yes
-
- 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.
-
-347. $use_envelope_from
-
- 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).
-
-348. $use_from
-
- Type: boolean
-
- Default: yes
-
- 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.
-
-349. $use_idn
-
- Type: boolean
-
- Default: yes
-
- Availability: IDN
-
- When set, Mutt-ng will show you international domain names decoded.
-
- Note: You can use IDNs for addresses even if this is unset. This variable
- only affects decoding.
-
-350. $use_ipv6
-
- Type: boolean
-
- Default: yes
-
- 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.
-
-351. $visual
-
- Type: path
-
- Default: ""
-
- Specifies the visual editor to invoke when the ~v command is given in the
- builtin editor.
-
-352. $wait_key
-
- Type: boolean
-
- Default: yes
-
- Controls whether Mutt-ng will ask you to press a key after shell- escape,
- pipe-message, pipe-entry, print-message, and print-entry commands.
-
- 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.
-
- 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.
-
-353. $weed
-
- Type: boolean
-
- Default: yes
-
- When set, Mutt-ng will weed headers when displaying, forwarding, printing,
- or replying to messages.
-
-354. $wrap_search
-
- Type: boolean
-
- Default: yes
-
- Controls whether searches wrap around the end of the mailbox.
-
- When set, searches will wrap around the first (or last) message. When
- unset, searches will not wrap.
-
-355. $wrapmargin
-
- Type: number
-
- Default: 0
-
- Controls the size of the margin remaining at the right side of the
- terminal when Mutt-ng's pager does smart wrapping.
-
-356. $write_bcc
-
- Type: boolean
-
- Default: yes
-
- Controls whether Mutt-ng writes out the Bcc header when preparing messages
- to be sent. Exim users may wish to unset this.
-
-357. $write_inc
-
- Type: number
-
- Default: 10
-
- 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.
-
- Also see the ``$read_inc'' variable.
-
-358. $xterm_icon
-
- Type: string
-
- Default: "M%?n?AIL&ail?"
-
- 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''.
-
-359. $xterm_leave
-
- 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`"
-
-360. $xterm_set_titles
-
- Type: boolean
-
- Default: no
-
- 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.
-
-361. $xterm_title
-
- Type: string
-
- Default: "Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?"
-
- 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''.
-
-5. Functions
-
- 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.
-
- 5.1. generic
-
- 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).
-
- Table 7.4. Reference: Default Generic Function Bindings
-
- 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
-
- 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
-
- 5.5. query
-
- Table 7.8. Reference: Default Query Menu Function Bindings
-
- 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
-
- 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
-
- Function Default Key Description
- <delete-entry> d delete the current entry
- <undelete-entry> u undelete the current entry
-
- 5.9. browser
-
- Table 7.12. Reference: Default Browser Menu Function Bindings
-
- 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
-
- Table 7.13. Reference: Default PGP Menu Function Bindings
-
- Function Default Key Description
- <view-name> % view the key's user id
- <verify-key> c verify a PGP public key
-
- 5.11. editor
-
- Table 7.14. Reference: Default Editor Function Bindings
-
- 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
-
- 5.12. sidebar
-
- Table 7.15. Referene: Default Sidebar Function Bindings
-
- 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
-
-Appendix A. Acknowledgments
-
- Kari Hurtta <kari.hurtta@fmi.fi> co-developed the original MIME >parsing
- code back in the ELM-ME days.
-
- The following people have been very helpful to the development of Mutt
- (sorted by surnames):
-
- 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>
-
- Mutt-ng is developed by the following people:
-
- o Andreas Krennmair <ak@synflood.at>
- o Nico Golde <nico@ngolde.de>
- o Rocco Rutte <pdmef@cs.tu-berlin.de>
-
- The following people have been very helpful to the development of Mutt-ng
- (sorted by surnames):
-
- 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>
-
-Appendix B. Hacking Documentation
-
- 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.
-
- This two pass processing is required to keep the file size low and to
- sanitize use, i.e. drastically lower the typing overhead.
-
- 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).
-
- <muttng-doc:man name="" [sect=""]/>
-
- References to manual pages. If the sect parameter is omitted,
- it'll be 1 for the commands section. There's no auto-indexing yet.
-
- <muttng-doc:envvar name=""/>
-
- 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.
-
- <muttng-doc:hook name=""/>
-
- References to hooks. The string -hook will be added automatically
- to the value given in the name parameter. All entries will be
- auto-indexed.
-
- <muttng-doc:pattern name="" [full="1"]/>
-
- 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.
-
- <muttng-doc:key [mod="C|E"]>key</muttng-doc:key>
-
- 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.
-
- <muttng-doc:funcdef name=""/>
-
- 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.
-
- <muttng-doc:funcref name=""/>
+211. $pgp_sign_command
- References to functions.. This is practically the same as the
- above except that there's no anchor defined.
+ Type: string
- <muttng-doc:vardef name=""/>
+ Default: ""
- 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.
+ This command is used to create the detached PGP signature for a
+ multipart/signed PGP/MIME body part. (PGP only)
- <muttng-doc:varref name=""/>
+212. $pgp_sort_keys
- 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.
+ Type: sort order
- <muttng-doc:web url""/>
+ Default: address
- 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).
+ Specifies how the entries in the ``pgp keys'' menu are sorted. The
+ following are legal values:
- <muttng-doc:rfc num=""/>
+ address
+ sort alphabetically by user id
- 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.
+ keyid
+ sort alphabetically by key id
- <muttng-doc:cmddef name="" [noanchor="1"]/>
+ date
+ sort by key creation date
- 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.
+ trust
+ sort by the trust of the key
- <muttng-doc:cmdref name=""/>
+ If you prefer reverse order of the above values, prefix it with
+ ``reverse-''. (PGP only)
- References to configuration commands. Use this to refer to
- commands as it builds the proper internal reference name.
- Auto-indexing is done.
+213. $pgp_strict_enc
- <muttng-doc:lstconf/>, <muttng-doc:lstmail/>, <muttng-doc:lstshell/>
+ Type: boolean
- 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.
+ Default: yes
- <muttng-doc:special [docbook=""] [latex=""]/>
+ If _\bs_\be_\bt, 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)
- This is intended for specifying special strings for either
- DocBook/XML or LaTeX.
+214. $pgp_timeout
- Additional notes follow.
+ Type: number
- 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.
+ Default: 300
-Index
+ The number of seconds after which a cached passphrase will expire if
+ not used. Default: 300. (PGP only)
- Symbols
+215. $pgp_use_gpg_agent
- ~$/ =$, Patterns
+ Type: boolean
- ~*/ =*, Patterns
+ Default: no
- ~=/ ==, Patterns
+ If _\bs_\be_\bt, Mutt-ng will use a possibly-running gpg-agent process. (PGP
+ only)
- ~A/ =A, Patterns
+216. $pgp_verify_command
- ~b/ =b, Complex Patterns, Patterns
+ Type: string
- ~B/ =B, Patterns
+ Default: ""
- ~c/ =c, Patterns
+ This command is used to verify PGP signatures. (PGP only)
- ~C/ =C, Patterns
+217. $pgp_verify_key_command
- ~d/ =d, Patterns and Dates, Patterns
+ Type: string
- ~D/ =D, Patterns
+ Default: ""
- ~E/ =E, Patterns
+ This command is used to verify key information from the key selection
+ menu. (PGP only)
- ~e/ =e, Patterns
+218. $pipe_decode
- ~f/ =f, Complex Patterns, Patterns
+ Type: boolean
- ~F/ =F, Patterns
+ Default: no
- ~g/ =g, Patterns
+ Used in connection with the _\bp_\bi_\bp_\be_\b-_\bm_\be_\bs_\bs_\ba_\bg_\be command. When _\bu_\bn_\bs_\be_\bt, Mutt-ng
+ will pipe the messages without any preprocessing. When _\bs_\be_\bt, Mutt-ng
+ will weed headers and will attempt to PGP/MIME decode the messages
+ first.
- ~G/ =G, Patterns
+219. $pipe_sep
- ~H/ =H, Spam detection, Patterns
+ Type: string
- ~h/ =h, Patterns
+ Default: "\n"
- ~i/ =i, Patterns
+ The separator to add between messages when piping a list of tagged
+ messages to an external Unix command.
- ~k/ =k, Patterns
+220. $pipe_split
- ~L/ =L, Patterns
+ Type: boolean
- ~l/ =l, Patterns
+ Default: no
- ~m/ =m, Patterns
+ Used in connection with the _\bp_\bi_\bp_\be_\b-_\bm_\be_\bs_\bs_\ba_\bg_\be command and the ``tag-
+ prefix'' or ``tag-prefix-cond'' operators. If this variable is _\bu_\bn_\bs_\be_\bt,
+ when piping a list of tagged messages Mutt-ng will concatenate the
+ messages and will pipe them as a single folder. When _\bs_\be_\bt, Mutt-ng will
+ pipe the messages one by one. In both cases the messages are piped in
+ the current sorted order, and the ``$\b$p\bpi\bip\bpe\be_\b_s\bse\bep\bp'' separator is added
+ after each message.
- ~M/ =M, Patterns
+221. $pop_auth_try_all
- ~n/ =n, Message Scoring, Patterns
+ Type: boolean
- ~N/ =N, Patterns
+ Default: yes
- ~O/ =O, Patterns
+ Availability: POP
- ~p/ =p, Patterns
+ If _\bs_\be_\bt, Mutt-ng will try all available methods. When _\bu_\bn_\bs_\be_\bt, 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.
- ~P/ =P, Patterns
+222. $pop_authenticators
- ~Q/ =Q, Patterns
+ Type: string
- ~R/ =R, Patterns
+ Default: ""
- ~r/ =r, Patterns
+ Availability: POP
- ~s/ =s, Complex Patterns, 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''.
- ~S/ =S, Patterns
+ This parameter is case-insensitive. If this parameter is _\bu_\bn_\bs_\be_\bt (the
+ default) Mutt-ng will try all available methods, in order from
+ most-secure to least-secure.
- ~T/ =T, Patterns
+ Example: set pop_authenticators="digest-md5:apop:user"
- ~t/ =t, Patterns
+223. $pop_delete
- ~U/ =U, Complex Patterns, Patterns
+ Type: quadoption
- ~u/ =u, Patterns
+ Default: ask-no
- ~v/ =v, Patterns
+ Availability: POP
- ~V/ =V, Patterns
+ If _\bs_\be_\bt, Mutt-ng will delete successfully downloaded messages from the
+ POP server when using the ``fetch-mail'' function. When _\bu_\bn_\bs_\be_\bt, Mutt-ng
+ will download messages but also leave them on the POP server.
- ~w/ =w, Patterns
+224. $pop_host
- ~x/ =x, Complex Patterns, Patterns
+ Type: string
- ~X/ =X, Patterns
+ Default: ""
- ~y/ =y, Handling Mailing Lists, Patterns
+ Availability: POP
- ~z/ =z, Patterns
+ The name of your POP server for the ``fetch-mail'' function. You can
+ also specify an alternative port, username and password, i.e.:
- A
+ [pop[s]://][username[:password]@]popserver[:port]
- $abort_noattach , $abort_noattach
+ _\bN_\bo_\bt_\be_\b: 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.
- $abort_nosubject , $abort_nosubject
+225. $pop_last
- $abort_unmodified , $abort_unmodified
+ Type: boolean
- account-hook, Managing multiple IMAP/POP/NNTP accounts (OPTIONAL),
- Configuration Commands
+ Default: no
- $agent_string , Configuration variables
+ Availability: POP
- $agent_string , $agent_string
+ If this variable is _\bs_\be_\bt, 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.
- alias, Miscellaneous Functions, Defining/Using aliases, Configuration
- Commands
+226. $pop_mail_check
- $alias_file, Miscellaneous Functions, Defining/Using aliases
+ Type: number
- $alias_file , $alias_file
+ Default: 60
- $alias_format , $alias_format
+ Availability: POP
- $allow_8bit , $allow_8bit
+ This variable configures how often (in seconds) Mutt-ng should look
+ for new mail.
- $allow_ansi , $allow_ansi
+227. $pop_pass
- alternates, Alternative addresses, Configuration Commands
+ Type: string
- alternative_order, MIME Multipart/Alternative, Configuration Commands
+ Default: ""
- append-hook, Compressed folders Support (OPTIONAL), Append a message to a
- compressed mailbox, Encrypted folders, Configuration Commands
+ Availability: POP
- $arrow_cursor , $arrow_cursor
+ Specifies the password for your POP account. If _\bu_\bn_\bs_\be_\bt, Mutt-ng will
+ prompt you for your password when you open POP mailbox.
- $ascii_chars , $ascii_chars
+ _\bN_\bo_\bt_\be_\b: 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.
- $askbcc , $askbcc
+228. $pop_reconnect
- $askcc , $askcc
+ Type: quadoption
- $assumed_charset , $assumed_charset
+ Default: ask-yes
- <attach-file>, Composing new messages, compose
+ Availability: POP
- <attach-key>, Composing new messages, compose
+ Controls whether or not Mutt-ng will try to reconnect to a POP server
+ if the connection is lost.
- <attach-message>, Composing new messages, compose
+229. $pop_user
- attachments, Attachment Searching and Counting
+ Type: string
- $attach_format , $attach_format
+ Default: ""
- $attach_remind_regexp , $attach_remind_regexp
+ Availability: POP
- $attach_sep , $attach_sep
+ Your login name on the POP server.
- $attach_split , $attach_split
+ This variable defaults to your user name on the local machine.
- $attribution, Change settings based upon message recipients, $attribution
+230. $post_indent_string
- $auto_tag, Using Tags
+ Type: string
- $autoedit , $autoedit
+ Default: ""
- $auto_tag , $auto_tag
+ Similar to the ``$\b$a\bat\btt\btr\bri\bib\bbu\but\bti\bio\bon\bn'' variable, Mutt-ng will append this
+ string after the inclusion of a message which is being replied to.
- auto_view, The Pager, Optional Fields, Search Order, MIME Autoview, MIME
- Multipart/Alternative, Configuration Commands
+231. $postpone
- B
+ Type: quadoption
- <backspace>, Editing Input Fields, editor
+ Default: ask-yes
- <backward-char>, Editing Input Fields, editor
+ Controls whether or not messages are saved in the ``$\b$p\bpo\bos\bst\btp\bpo\bon\bne\bed\bd''
+ mailbox when you elect not to send immediately.
- <backward-word>, Editing Input Fields, editor
+232. $postponed
- $beep , $beep
+ Type: path
- $beep_new , $beep_new
+ Default: "~/postponed"
- bind, Editing Input Fields, Changing the default key bindings, Keyboard
- macros, Configuration Commands
+ Mutt-ng allows you to indefinitely ``p\bpo\bos\bst\btp\bpo\bon\bne\be 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
+ ``$\b$p\bpo\bos\bst\btp\bpo\bon\bne\be'' variable.
- <bol>, Editing Input Fields, editor
+233. $preconnect
- <bottom>, pager
+ Type: string
- <bottom-page>, generic
+ Default: ""
- <bounce>, Sending Mail, $bounce
+ If _\bs_\be_\bt, 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:
- <bounce-message>, index, pager, attach
+ preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net sleep 20 <
+ /dev/null > /dev/null"
- $bounce_delivered , $bounce_delivered
+ Mailbox ``foo'' on mailhost.net can now be reached as
+ ``{localhost:1234}foo''.
- $braille_friendly , $braille_friendly
+ _\bN_\bo_\bt_\be_\b: For this example to work, you must be able to log in to the
+ remote machine without having to enter a password.
- <buffy-cycle>, editor
+234. $print
- C
+ Type: quadoption
- <capitalize-word>, Editing Input Fields, editor
+ Default: ask-no
- $certificate_file , $certificate_file
+ Controls whether or not Mutt-ng really prints messages. This is set to
+ _\ba_\bs_\bk_\b-_\bn_\bo by default, because some people accidentally hit ``p'' often.
- <change-dir>, browser
+235. $print_command
- <change-folder>, index, pager
+ Type: path
- <change-folder-readonly>, index, pager
+ Default: "lpr"
- $charset , $charset
+ This specifies the command pipe that should be used to print messages.
- charset-hook, Defining aliases for character sets, Configuration Commands
+236. $print_decode
- <check-new>, browser
+ Type: boolean
- <check-traditional-pgp>, Miscellaneous Functions, index, pager
+ Default: yes
- $check_new , $check_new
+ Used in connection with the print-message command. If this option is
+ _\bs_\be_\bt, the message is decoded before it is passed to the external
+ command specified by $\b$p\bpr\bri\bin\bnt\bt_\b_c\bco\bom\bmm\bma\ban\bnd\bd. If this option is _\bu_\bn_\bs_\be_\bt, 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.
- <clear-flag>, index
+237. $print_split
- close-hook, Compressed folders Support (OPTIONAL), Write a compressed
- mailbox, Append a message to a compressed mailbox, Configuration Commands
+ Type: boolean
- <collapse-all>, Threaded Mode
+ Default: no
- <collapse-parts>, attach
+ Used in connection with the print-message command. If this option is
+ _\bs_\be_\bt, the command specified by $\b$p\bpr\bri\bin\bnt\bt_\b_c\bco\bom\bmm\bma\ban\bnd\bd is executed once for each
+ message which is to be printed. If this option is _\bu_\bn_\bs_\be_\bt, the command
+ specified by $\b$p\bpr\bri\bin\bnt\bt_\b_c\bco\bom\bmm\bma\ban\bnd\bd is executed only once, and all the
+ messages are concatenated, with a form feed as the message separator.
- <collapse-thread>, Threaded Mode
+ Those who use the enscript(1) program's mail-printing mode will most
+ likely want to set this option.
- $collapse_unread , $collapse_unread
+238. $prompt_after
- color, The Pager, Using color and mono video attributes, Configuration
- Commands
+ Type: boolean
- $COLORFGBG, Using color and mono video attributes
+ Default: yes
- <complete>, Editing Input Fields, editor
+ If you use an _\be_\bx_\bt_\be_\br_\bn_\ba_\bl ``$\b$p\bpa\bag\bge\ber\br'', 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 _\bu_\bn_\bs_\be_\bt, Mutt-ng will return to the
+ index menu when the external pager exits.
- <complete-query>, Editing Input Fields, editor
+239. $query_command
- <compose>, Sending Mail
+ Type: path
- $compose_format , $compose_format
+ Default: ""
- $config_charset , $config_charset
+ 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\bqu\bue\ber\bry\by'' for
+ more information.
- $confirmappend , $confirmappend
+240. $quit
- $confirmcreate , $confirmcreate
+ Type: quadoption
- $connect_timeout , $connect_timeout
+ Default: yes
- $content_type , $content_type
+ This variable controls whether ``quit'' and ``exit'' actually quit
+ from Mutt-ng. If it set to _\by_\be_\bs, they do quit, if it is set to _\bn_\bo, they
+ have no effect, and if it is set to _\ba_\bs_\bk_\b-_\by_\be_\bs or _\ba_\bs_\bk_\b-_\bn_\bo, you are
+ prompted for confirmation when you try to quit.
- $copy , $copy
+241. $quote_empty
- <copy-file>, compose
+ Type: boolean
- <copy-message>, index, pager
+ Default: yes
- $count_attachments, Attachment Searching and Counting
+ Controls whether or not empty lines will be quoted using
+ ``i\bin\bnd\bde\ben\bnt\bt_\b_s\bst\btr\bri\bin\bng\bg''.
- $count_attachments , $count_attachments
+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 _\bs_\be_\bt, one quote character
+ will be added to the end of existing prefix. Otherwise, quoted lines
+ will be prepended by ``i\bin\bnd\bde\ben\bnt\bt_\b_s\bst\btr\bri\bin\bng\bg''.
- 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
+ _\bN_\bo_\bt_\be_\b: In order to use the _\bq_\bu_\bo_\bt_\be_\bd_\bx patterns in the internal pager, you
+ need to set this to a regular expression that matches _\be_\bx_\ba_\bc_\bt_\bl_\by 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 _\br_\be_\ba_\bd_\b__\bi_\bn_\bc 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 ``$\b$w\bwr\bri\bit\bte\be_\b_i\bin\bnc\bc'' 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
+ _\bN_\bo_\bt_\be_\b: This variable will _\bn_\bo_\bt be used when the user has set a real name
+ in the $\b$f\bfr\bro\bom\bm 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 ``$\b$p\bpo\bos\bst\btp\bpo\bon\bne\bed\bd''.
- $default_hook , $default_hook
+ Setting this variable to _\by_\be_\bs 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\bmy\by_\b_h\bhd\bdr\br''
+ command to create a Bcc: header field with your email address in it.)
- <delete-pattern>, index
+ The value of $\b$r\bre\bec\bco\bor\brd\bd is overridden by the ``$\b$f\bfo\bor\brc\bce\be_\b_n\bna\bam\bme\be'' and
+ ``$\b$s\bsa\bav\bve\be_\b_n\bna\bam\bme\be'' variables, and the `` \b f\bfc\bcc\bc-\b-h\bho\boo\bok\bk'' 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 _\bu_\bn_\bs_\be_\bt 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 _\bs_\be_\bt, 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 _\bu_\bn_\bs_\be_\bt, 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 _\bs_\be_\bt, the default From: line of the
+ reply messages is built using the address where you received the
+ messages you are replying to _\bi_\bf that address matches your alternates.
+ If the variable is _\bu_\bn_\bs_\be_\bt, 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\bre\bev\bve\ber\brs\bse\be_\b_n\bna\bam\bme\be feature.
+ When it is _\bs_\be_\bt, Mutt-ng will use the address from incoming messages
+ as-is, possibly including eventual real names. When it is _\bu_\bn_\bs_\be_\bt,
+ Mutt-ng will override any such real names with the setting of the
+ r\bre\bea\bal\bln\bna\bam\bme\be 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 _\bs_\be_\bt, 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 _\bs_\be_\bt 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 _\bn_\bo_\bt have the effect that
+ Mutt-ng _\bg_\be_\bn_\be_\br_\ba_\bt_\be_\bs 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 _\bs_\be_\bt, Mutt-ng will take the sender's full address when choosing a
+ default folder for saving a mail. If ``$\b$s\bsa\bav\bve\be_\b_n\bna\bam\bme\be'' or ``$\b$f\bfo\bor\brc\bce\be_\b_n\bna\bam\bme\be''
+ is _\bs_\be_\bt 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 _\bu_\bn_\bs_\be_\bt, mailboxes which contain no saved messages will be removed
+ when closed (the exception is ``$\b$s\bsp\bpo\boo\bol\blf\bfi\bil\ble\be'' which is never removed).
+ If _\bs_\be_\bt, mailboxes are never removed.
- $fast_reply , $fast_reply
+ _\bN_\bo_\bt_\be_\b: 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
+ ``$\b$f\bfo\bol\bld\bde\ber\br'' directory with the _\bu_\bs_\be_\br_\bn_\ba_\bm_\be 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 ``$\b$r\bre\bec\bco\bor\brd\bd''
+ mailbox.
- <fetch-mail>, index
+ Also see the ``$\b$f\bfo\bor\brc\bce\be_\b_n\bna\bam\bme\be'' 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 _\bu_\bn_\bs_\be_\bt, scoring is turned off. This can be useful
+ to selectively disable scoring for certain folders when the
+ ``$\b$s\bsc\bco\bor\bre\be_\b_t\bth\bhr\bre\bes\bsh\bho\bol\bld\bd_\b_d\bde\bel\ble\bet\bte\be'' 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_list_reply , $force_list_reply
+ Default: 9999
- $force_name , $force_name
+ Messages which have been assigned a score greater than or equal to
+ this variable's value are automatically marked ``flagged''.
- <forget-passphrase>, Miscellaneous Functions, Composing new messages,
- index, pager, compose
+263. $score_threshold_read
- <forward>, Sending Mail
+ Type: number
- <forward-char>, Editing Input Fields, editor
+ Default: -1
- $forward_decode , 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_decrypt , Configuration variables
+264. $send_charset
- $forward_format , Configuration variables
+ Type: string
- <forward-message>, index, pager, attach
+ Default: "us-ascii:iso-8859-1:utf-8"
- $forward_quote , Configuration variables
+ 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 ``$\b$c\bch\bha\bar\brs\bse\bet\bt'' 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-word>, Editing Input Fields, editor
+265. $sendmail
- $forward_decode , $forward_decode
+ Type: path
- $forward_decrypt , $forward_decrypt
+ Default: "/usr/sbin/sendmail -oem -oi"
- $forward_edit , $forward_edit
+ 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_format , $forward_format
+266. $sendmail_wait
- $forward_quote , $forward_quote
+ Type: number
- $from , $from
+ Default: 0
- G
+ Specifies the number of seconds to wait for the ``$\b$s\bse\ben\bnd\bdm\bma\bai\bil\bl'' process
+ to finish before giving up and putting delivery in the background.
- $gecos_mask , $gecos_mask
+ Mutt-ng interprets the value of this variable as follows:
- <group-reply>, Sending Mail, index, pager, attach
+ >0
+ number of seconds to wait for sendmail to finish before
+ continuing
- H
+ 0
+ wait forever for sendmail to finish
- <half-down>, generic, pager
+ <0
+ always put sendmail in the background without waiting
- <half-up>, generic, pager
+ 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.
- $hdrs , $hdrs
+267. $shell
- hdr_order, Defining the order of headers when viewing messages,
- Configuration Commands
+ Type: path
- $header , $header
+ Default: ""
- $header_cache , $header_cache
+ Command to use when spawning a subshell. By default, the user's login
+ shell from /etc/passwd is used.
- $header_cache_compress , $header_cache_compress
+268. $sidebar_boundary
- <help>, Moving Around in Menus, $help, generic, pager
+ Type: string
- $hidden_host , $hidden_host
+ Default: "."
- $hide_limited , $hide_limited
+ When the sidebar is displayed and $\b$s\bsi\bid\bde\beb\bba\bar\br_\b_s\bsh\bho\bor\brt\bte\ben\bn_\b_h\bhi\bie\ber\bra\bar\brc\bch\bhy\by is _\bs_\be_\bt,
+ this variable specifies the characters at which to split a folder name
+ into ``hierarchy items.''
- $hide_missing , $hide_missing
+269. $sidebar_delim
- $hide_thread_subject , $hide_thread_subject
+ Type: string
- $hide_top_limited , $hide_top_limited
+ Default: "|"
- $hide_top_missing , $hide_top_missing
+ This specifies the delimiter between the sidebar (if visible) and
+ other screens.
- $history , $history
+270. $sidebar_newmail_only
- <history-down>, Editing Input Fields, editor
+ Type: boolean
- <history-up>, Editing Input Fields, editor
+ Default: no
- $HOME, MIME Type configuration with mime.types, MIME Viewer configuration
- with mailcap
+ If _\bs_\be_\bt, only folders with new mail will be shown in the sidebar.
- $honor_followup_to, Miscellaneous Functions, Handling Mailing Lists
+271. $sidebar_number_format
- $honor_followup_to , $honor_followup_to
+ Type: string
- $HOSTNAME, Environment Variables
+ Default: "%m%?n?(%n)?%?f?[%f]?"
- $hostname , $hostname
+ This variable controls how message counts are printed when the sidebar
+ is enabled. If this variable is _\be_\bm_\bp_\bt_\by (_\ba_\bn_\bd_\b _\bo_\bn_\bl_\by_\b _\bi_\bf), no numbers will
+ be printed _\ba_\bn_\bd Mutt-ng won't frequently count mail (which may be a
+ great speedup esp. with mbox-style mailboxes.)
- I
+ The following printf(3)-like sequences are supported all of which may
+ be printed non-zero:
- iconv-hook, Defining aliases for character sets
+ %d
+ Number of deleted messages. 1)
- ignore, Miscellaneous Functions, Ignoring (weeding) unwanted message
- headers, Configuration Commands
+ %F
+ Number of flagged messages.
- $ignore_list_reply_to , $ignore_list_reply_to
+ %m
+ Total number of messages.
- $imap_authenticators, Authentication
+ %M
+ Total number of messages shown, i.e. not hidden by a limit. 1)
- $imap_home_namespace, Configuration Variables
+ %n
+ Number of new messages.
- $imap_list_subscribed, IMAP Support (OPTIONAL)
+ %t
+ Number of tagged messages. 1)
- $imap_mail_check, Manual Conventions, Conditional parts, IMAP Support
- (OPTIONAL)
+ 1) These expandos only have a non-zero value for the current mailbox
+ and will always be zero otherwise.
- $imap_pass, Authentication
+272. $sidebar_shorten_hierarchy
- $imap_user, Authentication
+ Type: boolean
- $imap_authenticators , $imap_authenticators
+ Default: no
- $imap_check_subscribed , $imap_check_subscribed
+ When _\bs_\be_\bt, the ``hierarchy'' of the sidebar entries will be shortened
+ only if they cannot be printed in full length (because
+ ``$\b$s\bsi\bid\bde\beb\bba\bar\br_\b_w\bwi\bid\bdt\bth\bh'' 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_delim_chars , $imap_delim_chars
+ At which characters this compression is done is controled via the
+ $\b$s\bsi\bid\bde\beb\bba\bar\br_\b_b\bbo\bou\bun\bnd\bda\bar\bry\by variable.
- $imap_headers , $imap_headers
+273. $sidebar_visible
- $imap_home_namespace , $imap_home_namespace
+ Type: boolean
- $imap_keepalive , $imap_keepalive
+ Default: no
- $imap_list_subscribed , $imap_list_subscribed
+ This specifies whether or not to show the sidebar (a list of folders
+ specified with the ``mailboxes'' command).
- $imap_login , $imap_login
+274. $sidebar_width
- $imap_mail_check , $imap_mail_check
+ Type: number
- $imap_pass , $imap_pass
+ Default: 0
- $imap_passive , $imap_passive
+ The width of the sidebar.
- $imap_peek , $imap_peek
+275. $sig_dashes
- $imap_reconnect , $imap_reconnect
+ Type: boolean
- $imap_servernoise , $imap_servernoise
+ Default: yes
- $imap_user , $imap_user
+ If set, a line containing ``-- '' (dash, dash, space) will be inserted
+ before your ``$\b$s\bsi\big\bgn\bna\bat\btu\bur\bre\be''. It is _\bs_\bt_\br_\bo_\bn_\bg_\bl_\by 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.
- $implicit_autoview , $implicit_autoview
+ For example, Mutt-ng has the ability to highlight the signature in a
+ different color in the builtin pager.
- $include , $include
+276. $sig_on_top
- $include_onlyfirst , $include_onlyfirst
+ Type: boolean
- $indent_string , Configuration variables
+ Default: no
- $indent_string , $indent_string
+ If _\bs_\be_\bt, the signature will be included before any quoted or forwarded
+ text. It is _\bs_\bt_\br_\bo_\bn_\bg_\bl_\by 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.
- $index_format, Threaded Mode, Spam detection, Handling Mailing Lists,
- Configuration variables
+277. $signature
- $index_format , $index_format
+ Type: path
- <ispell>, Composing new messages, $ispell, compose
+ Default: "~/.signature"
- J
+ 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.
- <jump>, generic
+278. $signoff_string
- K
+ Type: string
- $keep_flagged , $keep_flagged
+ Default: ""
- <kill-eol>, Editing Input Fields, editor
+ If _\bs_\be_\bt, 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-eow>, 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.
- <kill-line>, Editing Input Fields, editor
+279. $simple_search
- <kill-word>, Editing Input Fields, editor
+ Type: string
- L
+ Default: "~f %s | ~s %s"
- <last-entry>, Moving Around in Menus, generic
+ 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\bpa\bat\btt\bte\ber\brn\bns\bs'' for more information on search patterns.
- <limit>, index
+ 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>, Miscellaneous Functions, Sending Mail, index, pager, attach
+ ~f joe | ~s joe
- lists, Miscellaneous Functions, Mailing lists, Handling Mailing Lists,
- Configuration Commands
+280. $sleep_time
- $locale, Change settings based upon message recipients, $locale
+ Type: number
- M
+ Default: 1
- macro, Miscellaneous Functions, Keyboard macros, Adding key sequences to
- the keyboard buffer, Using Tags, Configuration Commands
+ 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>, index, pager, query
+281. $smart_wrap
- <mail-key>, Sending Mail, index, pager
+ Type: boolean
- mailboxes, Defining mailboxes which receive mail, Configuration Commands
+ Default: yes
- $mailcap_path, mailcap
+ Controls the display of lines longer than the screen width in the
+ internal pager. If _\bs_\be_\bt, long lines are wrapped at a word boundary. If
+ _\bu_\bn_\bs_\be_\bt, lines are simply wrapped at the screen edge. Also see the
+ ``$\b$m\bma\bar\brk\bke\ber\brs\bs'' variable.
- $mailcap_sanitize, Secure use of mailcap, mailcap
+282. $smileys
- $mailcap_path , $mailcap_path
+ Type: regular expression
- $mailcap_sanitize , $mailcap_sanitize
+ Default: "(>From )|(:[-^]?[][)(><}{|/DP])"
- $maildir_header_cache_verify , $maildir_header_cache_verify
+ The _\bp_\ba_\bg_\be_\br uses this variable to catch some common false positives of
+ ``$\b$q\bqu\buo\bot\bte\be_\b_r\bre\beg\bge\bex\bxp\bp'', most notably smileys in the beginning of a line
- $maildir_trash , $maildir_trash
+283. $smime_ask_cert_label
- $mail_check , $mail_check
+ Type: boolean
- <mark-as-new>, pager
+ Default: yes
- $markers , $markers
+ 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 _\bs_\be_\bt by
+ default. (S/MIME only)
- $mark_old , $mark_old
+284. $smime_ca_location
- $mask , $mask
+ Type: path
- $max_display_recips , $max_display_recips
+ Default: ""
- $max_line_length , $max_line_length
+ This variable contains the name of either a directory, or a file which
+ contains trusted certificates for use with OpenSSL. (S/MIME only)
- $mbox, Mailbox Shortcuts, $mbox
+285. $smime_certificates
- mbox-hook, Using Multiple spool mailboxes, Using Hooks, Configuration
- Commands
+ Type: path
- $mbox_type, Mailbox Formats, Append a message to a compressed mailbox
+ Default: ""
- $mbox_type , $mbox_type
+ 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_context , $menu_context
+286. $smime_decrypt_command
- $menu_move_off , $menu_move_off
+ Type: string
- $menu_scroll , $menu_scroll
+ Default: ""
- $message_format , Configuration variables
+ This format string specifies a command which is used to decrypt
+ application/x-pkcs7-mime attachments.
- message-hook, Change settings before formatting a message, Using Hooks,
- Message Matching in Hooks, MIME Autoview, Configuration Commands
+ The OpenSSL command formats have their own set of printf(3)-like
+ sequences similar to PGP's:
- $message_format , $message_format
+ %f
+ Expands to the name of a file containing a message.
- $meta_key , $meta_key
+ %s
+ Expands to the name of a file containing the signature part of
+ a multipart/signed attachment when verifying it.
- $metoo , $metoo
+ %k
+ The key-pair specified with $\b$s\bsm\bmi\bim\bme\be_\b_d\bde\bef\bfa\bau\bul\blt\bt_\b_k\bke\bey\by
- $mh_purge , $mh_purge
+ %c
+ One or more certificate IDs.
- $mh_seq_flagged , $mh_seq_flagged
+ %a
+ The algorithm used for encryption.
- $mh_seq_replied , $mh_seq_replied
+ %C
+ CA location: Depending on whether $\b$s\bsm\bmi\bim\bme\be_\b_c\bca\ba_\b_l\blo\boc\bca\bat\bti\bio\bon\bn points to
+ a directory or file, this expands to "-CApath
+ $\b$s\bsm\bmi\bim\bme\be_\b_c\bca\ba_\b_l\blo\boc\bca\bat\bti\bio\bon\bn" or "-CAfile $\b$s\bsm\bmi\bim\bme\be_\b_c\bca\ba_\b_l\blo\boc\bca\bat\bti\bio\bon\bn".
- $mh_seq_unseen , $mh_seq_unseen
+ 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)
- <middle-page>, generic
+287. $smime_decrypt_use_default_key
- $mime_forward , Configuration variables
+ Type: boolean
- $mime_forward , $mime_forward
+ Default: yes
- $mime_forward_decode , $mime_forward_decode
+ If _\bs_\be_\bt (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_forward_rest , $mime_forward_rest
+288. $smime_default_key
- mime_lookup, MIME Lookup, Configuration Commands
+ Type: string
- $mix_entry_format, Sending anonymous messages via mixmaster
+ Default: ""
- $mixmaster , $mixmaster
+ 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)
- $mix_entry_format , $mix_entry_format
+289. $smime_encrypt_command
- mono, Using color and mono video attributes, Configuration Commands
+ Type: string
- $move , $move
+ Default: ""
- $msgid_format, Message-ID: headers
+ This command is used to create encrypted S/MIME messages. (S/MIME
+ only)
- $msgid_format , $msgid_format
+290. $smime_encrypt_with
- $muttng_bindir , $muttng_bindir
+ Type: string
- $muttng_docdir , $muttng_docdir
+ Default: ""
- $muttng_folder_name , $muttng_folder_name
+ This sets the algorithm that should be used for encryption. Valid
+ choices are ``des'', ``des3'', ``rc2-40'', ``rc2-64'', ``\frc2-128''.
- $muttng_folder_path , $muttng_folder_path
+ If _\bu_\bn_\bs_\be_\bt ``_\b3_\bd_\be_\bs'' (TripleDES) is used. (S/MIME only)
- $muttng_hcache_backend , $muttng_hcache_backend
+291. $smime_get_cert_command
- $muttng_pwd , $muttng_pwd
+ Type: string
- $muttng_revision , $muttng_revision
+ Default: ""
- $muttng_sysconfdir , $muttng_sysconfdir
+ This command is used to extract X509 certificates from a PKCS7
+ structure. (S/MIME only)
- $muttng_version , $muttng_version
+292. $smime_get_cert_email_command
- my_hdr, User defined headers, Configuration Commands
+ Type: string
- N
+ Default: ""
- $narrow_tree , $narrow_tree
+ 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)
- $net_inc , $net_inc
+293. $smime_get_signer_cert_command
- <new-mime>, compose
+ Type: string
- <next-entry>, Moving Around in Menus, generic, pager
+ Default: ""
- <next-line>, generic, 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>, index, pager
+294. $smime_import_cert_command
- <next-new-then-unread>, index, pager
+ Type: string
- <next-page>, generic, pager
+ Default: ""
- <next-subthread>, Threaded Mode, index, pager
+ This command is used to import a certificate via smime_keysng. (S/MIME
+ only)
- <next-thread>, Threaded Mode, index, pager
+295. $smime_is_default
- <next-undeleted>, index, pager
+ Type: boolean
- <next-unread>, index, pager
+ Default: no
- $nntp_ask_followup_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 _\bs_\be_\bt.
- $nntp_ask_x_comment_to , 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_cache_dir , Configuration variables
+ (Note that this variable can be overridden by unsetting
+ $\b$c\bcr\bry\byp\bpt\bt_\b_a\bau\but\bto\bos\bsm\bmi\bim\bme\be.) (S/MIME only)
- $nntp_catchup , Configuration variables
+296. $smime_keys
- $nntp_followup_to_poster , Configuration variables
+ Type: path
- $nntp_group_index_format , Configuration variables
+ Default: ""
- $nntp_host , 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_inews , Configuration variables
+297. $smime_pk7out_command
- $nntp_mail_check , Configuration variables
+ Type: string
- $nntp_mime_subject , Configuration variables
+ Default: ""
- $nntp_newsrc, NNTP Support (OPTIONAL), 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_post_moderated , Configuration variables
+298. $smime_sign_command
- $nntp_save_unsubscribed , Configuration variables
+ Type: string
- $nntp_show_new_news , Configuration variables
+ Default: ""
- $nntp_show_only_unread , 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)
- $nntp_x_comment_to , Configuration variables
+299. $smime_sign_opaque_command
- $NNTPSERVER, NNTP Support (OPTIONAL)
+ Type: string
- $nntp_ask_followup_to , $nntp_ask_followup_to
+ Default: ""
- $nntp_ask_x_comment_to , $nntp_ask_x_comment_to
+ 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_cache_dir , $nntp_cache_dir
+300. $smime_timeout
- $nntp_catchup , $nntp_catchup
+ Type: number
- $nntp_context , $nntp_context
+ Default: 300
- $nntp_followup_to_poster , $nntp_followup_to_poster
+ The number of seconds after which a cached passphrase will expire if
+ not used. (S/MIME only)
- $nntp_group_index_format , $nntp_group_index_format
+301. $smime_verify_command
- $nntp_host , $nntp_host
+ Type: string
- $nntp_inews , $nntp_inews
+ Default: ""
- $nntp_load_description , $nntp_load_description
+ This command is used to verify S/MIME signatures of type
+ multipart/signed. (S/MIME only)
- $nntp_mail_check , $nntp_mail_check
+302. $smime_verify_opaque_command
- $nntp_mime_subject , $nntp_mime_subject
+ Type: string
- $nntp_newsrc , $nntp_newsrc
+ Default: ""
- $nntp_pass , $nntp_pass
+ This command is used to verify S/MIME signatures of type
+ application/x-pkcs7-mime. (S/MIME only)
- $nntp_post_moderated , $nntp_post_moderated
+303. $smtp_host
- $nntp_reconnect , $nntp_reconnect
+ Type: string
- $nntp_save_unsubscribed , $nntp_save_unsubscribed
+ Default: ""
- $nntp_show_new_news , $nntp_show_new_news
+ Availability: SMTP
- $nntp_show_only_unread , $nntp_show_only_unread
+ 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 ``$\b$s\bse\ben\bnd\bdm\bma\bai\bil\bl'', and any associated variables.
- $nntp_user , $nntp_user
+304. $smtp_pass
- $nntp_x_comment_to , $nntp_x_comment_to
+ Type: string
- nospam, Spam detection, Configuration Commands
+ Default: ""
- O
+ Availability: SMTP
- 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
+ Defines the password to use with SMTP AUTH. If ``$\b$s\bsm\bmt\btp\bp_\b_u\bus\bse\ber\br'' is set,
+ but this variable is not, you will be prompted for a password when
+ sending.
- $operating_system , $operating_system
+ _\bN_\bo_\bt_\be_\b: 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.
- P
+305. $smtp_port
- <page-down>, Moving Around in Menus
+ Type: number
- <page-up>, Moving Around in Menus
+ Default: 25
- $pager , $pager
+ Availability: SMTP
- $pager_index_lines, Conditional parts
+ Defines the port that the SMTP host is listening on for mail delivery.
+ Must be specified as a number.
- $pager_context , $pager_context
+ Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP
+ servers will probably desire 587, the mail submission port.
- $pager_format , $pager_format
+306. $smtp_use_tls
- $pager_index_lines , $pager_index_lines
+ Type: string
- $pager_stop , $pager_stop
+ Default: ""
- <parent-message>, Threaded Mode, index, pager
+ Availability: SMTP (and SSL)
- pattern-hook, Specify default save filename, Specify default Fcc: mailbox
- when composing, Change settings based upon message recipients, Change
- settings before formatting a message
+ Defines wether to use STARTTLS. If this option is set to ``_\br_\be_\bq_\bu_\bi_\br_\be_\bd''
+ and the server does not support STARTTLS or there is an error in the
+ TLS Handshake, the connection will fail. Setting this to ``_\be_\bn_\ba_\bb_\bl_\be_\bd''
+ 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_autoinline , Configuration variables
+307. $smtp_user
- $pgp_entry_format, Using Mutt-ng with PGP
+ Type: string
- <pgp-menu>, Composing new messages, compose
+ Default: ""
- $pgp_replyinline , Configuration variables
+ Availability: SMTP
- $pgp_sign_as, Using Mutt-ng with PGP
+ Defines the username to use with SMTP AUTH. Setting this variable will
+ cause Mutt-ng to attempt to use SMTP AUTH when sending.
- $pgp_autoinline , $pgp_autoinline
+308. $sort
- $pgp_auto_decode , $pgp_auto_decode
+ Type: sort order
- $pgp_check_exit , $pgp_check_exit
+ Default: date
- $pgp_clearsign_command , $pgp_clearsign_command
+ Specifies how to sort messages in the _\bi_\bn_\bd_\be_\bx menu. Valid values are:
- $pgp_decode_command , $pgp_decode_command
+ date or date-sent
+ date-received
+ from
+ mailbox-order (unsorted)
+ score
+ size
+ spam
+ subject
+ threads
+ to
- $pgp_decrypt_command , $pgp_decrypt_command
+ You may optionally use the ``reverse-'' prefix to specify reverse
+ sorting order (example: set sort=reverse-date-sent).
- $pgp_encrypt_only_command , $pgp_encrypt_only_command
+309. $sort_alias
- $pgp_encrypt_sign_command , $pgp_encrypt_sign_command
+ Type: sort order
- $pgp_entry_format , $pgp_entry_format
+ Default: alias
- $pgp_export_command , $pgp_export_command
+ Specifies how the entries in the ``alias'' menu are sorted. The
+ following are legal values:
- $pgp_getkeys_command , $pgp_getkeys_command
+ address (sort alphabetically by email address)
+ alias (sort alphabetically by alias name)
+ unsorted (leave in order specified in .muttrc)
- $pgp_good_sign , $pgp_good_sign
+310. $sort_aux
- $pgp_ignore_subkeys , $pgp_ignore_subkeys
+ Type: sort order
- $pgp_import_command , $pgp_import_command
+ Default: date
- $pgp_list_pubring_command , $pgp_list_pubring_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 ``$\b$s\bso\bor\brt\bt'' 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_list_secring_command , $pgp_list_secring_command
+ 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_long_ids , $pgp_long_ids
+ _\bN_\bo_\bt_\be_\b: For reversed ``$\b$s\bso\bor\brt\bt'' order $\b$s\bso\bor\brt\bt_\b_a\bau\bux\bx is reversed again (which
+ is not the right thing to do, but kept to not break any existing
+ configuration setting).
- $pgp_mime_auto , $pgp_mime_auto
+311. $sort_browser
- $pgp_replyinline , $pgp_replyinline
+ Type: sort order
- $pgp_retainable_sigs , $pgp_retainable_sigs
+ Default: alpha
- $pgp_show_unusable , $pgp_show_unusable
+ Specifies how to sort entries in the file browser. By default, the
+ entries are sorted alphabetically. Valid values:
- $pgp_sign_as , $pgp_sign_as
+ alpha (alphabetically)
+ date
+ size
+ unsorted
- $pgp_sign_command , $pgp_sign_command
+ You may optionally use the ``reverse-'' prefix to specify reverse
+ sorting order (example: set sort_browser=reverse-date).
- $pgp_sort_keys , $pgp_sort_keys
+312. $sort_re
- $pgp_strict_enc , $pgp_strict_enc
+ Type: boolean
- $pgp_timeout , $pgp_timeout
+ Default: yes
- $pgp_use_gpg_agent , $pgp_use_gpg_agent
+ This variable is only useful when sorting by threads with
+ ``$\b$s\bst\btr\bri\bic\bct\bt_\b_t\bth\bhr\bre\bea\bad\bds\bs'' _\bu_\bn_\bs_\be_\bt. In that case, it changes the heuristic
+ Mutt-ng uses to thread messages by subject. With $\b$s\bso\bor\brt\bt_\b_r\bre\be_\bs_\be_\bt, 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 ``$\b$r\bre\bep\bpl\bly\by_\b_r\bre\beg\bge\bex\bxp\bp''. With $\b$s\bso\bor\brt\bt_\b_r\bre\be_\bu_\bn_\bs_\be_\bt, Mutt-ng will
+ attach the message whether or not this is the case, as long as the
+ non-``$\b$r\bre\bep\bpl\bly\by_\b_r\bre\beg\bge\bex\bxp\bp'' parts of both messages are identical.
- $pgp_verify_command , $pgp_verify_command
+313. $spam_separator
- $pgp_verify_key_command , $pgp_verify_key_command
+ Type: string
- $pipe_decode, Miscellaneous Functions
+ Default: ","
- <pipe-entry>, attach, compose
+ ``s\bsp\bpa\bam\bm_\b_s\bse\bep\bpa\bar\bra\bat\bto\bor\br'' controls what happens when multiple spam headers
+ are matched: if _\bu_\bn_\bs_\be_\bt, each successive header will overwrite any
+ previous matches value for the spam label. If _\bs_\be_\bt, each successive
+ match will append to the previous, using ``s\bsp\bpa\bam\bm_\b_s\bse\bep\bpa\bar\bra\bat\bto\bor\br'' as a
+ separator.
- <pipe-message>, Miscellaneous Functions, index, pager
+314. $spoolfile
- $pipe_split, Miscellaneous Functions
+ Type: path
- $pipe_decode , $pipe_decode
+ Default: ""
- $pipe_sep , $pipe_sep
+ 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.
- $pipe_split , $pipe_split
+315. $ssl_ca_certificates_file
- $pop_mail_check, POP3 Support (OPTIONAL), Configuration variables
+ Type: path
- $pop_authenticators , $pop_authenticators
+ Default: ""
- $pop_auth_try_all , $pop_auth_try_all
+ 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_delete , $pop_delete
+ Example: set
+ ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
- $pop_host , $pop_host
+316. $ssl_client_cert
- $pop_last , $pop_last
+ Type: path
- $pop_mail_check , $pop_mail_check
+ Default: ""
- $pop_pass , $pop_pass
+ Availability: SSL
- $pop_reconnect , $pop_reconnect
+ The file containing a client certificate and its associated private
+ key.
- $pop_user , $pop_user
+317. $ssl_force_tls
- $post_indent_string , Configuration variables
+ Type: boolean
- $postpone, Postponing Mail, $postpone
+ Default: no
- <postpone-message>, Composing new messages, compose
+ If this variable is _\bs_\be_\bt, 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 ``$\b$s\bss\bsl\bl_\b_s\bst\bta\bar\brt\btt\btl\bls\bs''.
- $postponed, Postponing Mail, $postponed
+318. $ssl_min_dh_prime_bits
- $post_indent_string , $post_indent_string
+ Type: number
- $preconnect , $preconnect
+ Default: 0
- <previous-entry>, Moving Around in Menus, generic, pager
+ Availability: GNUTLS
- <previous-line>, generic, 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>, index, pager
+319. $ssl_starttls
- <previous-new-then-unread>, index, pager
+ Type: quadoption
- <previous-page>, generic, index, pager
+ Default: yes
- <previous-subthread>, Threaded Mode, index, pager
+ Availability: SSL or GNUTLS
- <previous-thread>, Threaded Mode, index, pager
+ If _\bs_\be_\bt (the default), Mutt-ng will attempt to use STARTTLS on servers
+ advertising the capability. When _\bu_\bn_\bs_\be_\bt, Mutt-ng will not attempt to
+ use STARTTLS regardless of the server's capabilities.
- <previous-undeleted>, index, pager
+320. $ssl_use_sslv2
- <previous-unread>, index, pager
+ Type: boolean
- $print , $print
+ Default: yes
- $print_command , Configuration variables
+ Availability: SSL
- <print-entry>, attach, compose
+ This variables specifies whether to attempt to use SSLv2 in the SSL
+ authentication process.
- <print-message>, index, pager
+321. $ssl_use_sslv3
- $print_command , $print_command
+ Type: boolean
- $print_decode , $print_decode
+ Default: yes
- $print_split , $print_split
+ Availability: SSL or GNUTLS
- $prompt_after , $prompt_after
+ This variables specifies whether to attempt to use SSLv3 in the SSL
+ authentication process.
- push, Adding key sequences to the keyboard buffer, Using Tags,
- Configuration Commands
+322. $ssl_use_tlsv1
- Q
+ Type: boolean
- <query>, index, query
+ Default: yes
- <query-append>, query
+ Availability: SSL or GNUTLS
- $query_command, External Address Queries
+ This variables specifies whether to attempt to use TLSv1 in the SSL
+ authentication process.
- $query_command , $query_command
+323. $ssl_usesystemcerts
- <quit>, Moving Around in Menus, Composing new messages, $quit, index,
- pager
+ Type: boolean
- <quote-char>, Editing Input Fields, editor
+ Default: yes
- $quote_regexp, Miscellaneous Functions, Using color and mono video
- attributes
+ Availability: SSL
- $quote_empty , $quote_empty
+ If set to _\by_\be_\bs, Mutt-ng will use CA certificates in the system-wide
+ certificate store when checking if server certificate is signed by a
+ trusted CA.
- $quote_quoted , $quote_quoted
+324. $status_chars
- $quote_regexp , $quote_regexp
+ Type: string
- R
+ Default: "-*%A"
- <read-subthread>, Threaded Mode, index, pager
+ Controls the characters used by the ``%r'' indicator in
+ ``$\b$s\bst\bta\bat\btu\bus\bs_\b_f\bfo\bor\brm\bma\bat\bt''. 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).
- <read-thread>, Threaded Mode, index, pager
+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 _\bi_\bn_\bd_\be_\bx menu.
+ This string is similar to ``$\b$i\bin\bnd\bde\bex\bx_\b_f\bfo\bor\brm\bma\bat\bt'', 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 $\b$s\bst\bta\bat\btu\bus\bs_\b_c\bch\bha\bar\brs\bs
- $reverse_alias , $reverse_alias
+ %s
+ current sorting mode ($\b$s\bso\bor\brt\bt)
- $reverse_name , $reverse_name
+ %S
+ current aux sorting method ($\b$s\bso\bor\brt\bt_\b_a\bau\bux\bx)
- $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 _\bs_\be_\bq_\bu_\be_\bn_\bc_\be_\b__\bc_\bh_\ba_\br is a character from the table above, and
+ _\bo_\bp_\bt_\bi_\bo_\bn_\ba_\bl_\b__\bs_\bt_\br_\bi_\bn_\bg is the string you would like printed if _\bs_\be_\bq_\bu_\be_\bn_\bc_\be_\b__\bc_\bh_\ba_\br
+ is nonzero. _\bo_\bp_\bt_\bi_\bo_\bn_\ba_\bl_\b__\bs_\bt_\br_\bi_\bn_\bg_\bm_\ba_\by contain other sequences as well as
+ normal text, but you may _\bn_\bo_\bt 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 ``$\b$e\bed\bdi\bit\bt_\b_h\bhe\bea\bad\bde\ber\brs\bs'' is unset.
- <search-opposite>, generic, pager, query
+ If this variable is _\bs_\be_\bt, Mutt-ng is strict and allows anything to be
+ changed. If it's _\bu_\bn_\bs_\be_\bt, all headers given will be prefixed with
+ ``X-Mailto-'' and the message including headers will be shown in the
+ editor regardless of what ``$\b$e\bed\bdi\bit\bt_\b_h\bhe\bea\bad\bde\ber\brs\bs'' 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 _\bu_\bn_\bs_\be_\bt, 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 $\b$a\bas\bss\bsu\bum\bme\bed\bd_\b_c\bch\bha\bar\brs\bse\bet\bt.
- 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 _\bs_\be_\bt, threading will only make use of the ``In-Reply-To:'' and
+ ``References:'' header fields when you ``$\b$s\bso\bor\brt\bt'' 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
+ ``$\b$s\bso\bor\brt\bt_\b_r\bre\be'' 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 _\bs_\be_\bt, Mutt-ng will remove the trailing part of the ``Subject:''
+ line which matches $\b$s\bst\btr\bri\bip\bp_\b_w\bwa\bas\bs_\b_r\bre\beg\bge\bex\bx 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 $\b$s\bst\btr\bri\bip\bp_\b_w\bwa\bas\bs is _\bs_\be_\bt, 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 _\bs_\be_\bt, 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 _\bu_\bn_\bs_\be_\bt, Mutt-ng won't stop when the user presses the terminal's
+ _\bs_\bu_\bs_\bp 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 _\bs_\be_\bt, 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 $\b$i\bin\bnd\bde\ben\bnt\bt_\b_s\bst\btr\bri\bin\bng\bg 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\bpa\bat\btt\bte\ber\brn\bns\bs'' above. If _\bs_\be_\bt, the headers and attachments of messages to
+ be searched are decoded before searching. If _\bu_\bn_\bs_\be_\bt, 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 _\bs_\be_\bt, 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 _\bs_\be_\bt, 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 _\bn_\bu_\bm_\bb_\be_\br_\b _\bo_\bf_\b _\bs_\be_\bc_\bo_\bn_\bd_\bs 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 _\by_\bo_\bu. 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 _\bs_\be_\bt, 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
+ _\bN_\bo_\bt_\be: 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
+ _\bN_\bo_\bt_\be_\b: 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 _\bu_\bn_\bs_\be_\bt, 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 _\bs_\be_\bt, Mutt-ng will jump to the next unread message, if any, when
+ the current thread is _\bu_\bncollapsed.
- <sort-mailbox>, index
+345. $use_8bitmime
- <sort-reverse>, index, browser
+ Type: boolean
- $sort_alias , $sort_alias
+ Default: no
- $sort_aux , $sort_aux
+ _\bW_\ba_\br_\bn_\bi_\bn_\bg_\b: 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 _\bs_\be_\bt, Mutt-ng will either invoke ``$\b$s\bse\ben\bnd\bdm\bma\bai\bil\bl'' 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 _\bs_\be_\bt, Mutt-ng will qualify all local addresses (ones without the
+ @host portion) with the value of ``$\b$h\bho\bos\bst\btn\bna\bam\bme\be''. If _\bu_\bn_\bs_\be_\bt, 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 _\bs_\be_\bt, Mutt-ng will use ``$\b$e\ben\bnv\bve\bel\blo\bop\bpe\be_\b_f\bfr\bro\bom\bm_\b_a\bad\bdd\bdr\bre\bes\bss\bs'' as the _\be_\bn_\bv_\be_\bl_\bo_\bp_\be
+ 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
+ _\bN_\bo_\bt_\be_\b: 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 _\bs_\be_\bt, Mutt-ng will generate the ``From:'' header field when
+ sending messages. If _\bu_\bn_\bs_\be_\bt, no ``From:'' header field will be
+ generated unless the user explicitly sets one using the ``m\bmy\by_\b_h\bhd\bdr\br''
+ 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 _\bs_\be_\bt, Mutt-ng will show you international domain names decoded.
- $strict_mailto, mailto:-style links
+ _\bN_\bo_\bt_\be_\b: You can use IDNs for addresses even if this is _\bu_\bn_\bs_\be_\bt. 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 _\bs_\be_\bt, Mutt-ng will look for IPv6 addresses of hosts it tries to
+ contact. If this option is _\bu_\bn_\bs_\be_\bt, 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 _\b~_\bv 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 _\bs_\bh_\be_\bl_\bl_\b-
+ _\be_\bs_\bc_\ba_\bp_\be, _\bp_\bi_\bp_\be_\b-_\bm_\be_\bs_\bs_\ba_\bg_\be, _\bp_\bi_\bp_\be_\b-_\be_\bn_\bt_\br_\by, _\bp_\br_\bi_\bn_\bt_\b-_\bm_\be_\bs_\bs_\ba_\bg_\be, and _\bp_\br_\bi_\bn_\bt_\b-_\be_\bn_\bt_\br_\by
+ commands.
- <tag-message>, pager
+ It is also used when viewing attachments with ``a\bau\but\bto\bo_\b_v\bvi\bie\bew\bw'', provided
+ that the corresponding mailcap entry has a needsterminal flag, and the
+ external program is interactive.
- <tag-pattern>, index
+ When _\bs_\be_\bt, Mutt-ng will always ask for a key. When _\bu_\bn_\bs_\be_\bt, 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 _\bs_\be_\bt, 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 _\bs_\be_\bt, searches will wrap around the first (or last) message. When
+ _\bu_\bn_\bs_\be_\bt, 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 _\bu_\bn_\bs_\be_\bt 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 _\bw_\br_\bi_\bt_\be_\b__\bi_\bn_\bc
+ messages to indicate progress. If set to 0, only a single message will
+ be displayed before writing a mailbox.
- $trash , $trash
+ Also see the ``$\b$r\bre\bea\bad\bd_\b_i\bin\bnc\bc'' 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
+ $\b$x\bxt\bte\ber\brm\bm_\b_s\bse\bet\bt_\b_t\bti\bit\btl\ble\bes\bs is _\bs_\be_\bt. This string is identical in formatting to
+ the one used by ``$\b$s\bst\bta\bat\btu\bus\bs_\b_f\bfo\bor\brm\bma\bat\bt''.
- 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 $\b$x\bxt\bte\ber\brm\bm_\b_s\bse\bet\bt_\b_t\bti\bit\btl\ble\bes\bs is _\bs_\be_\bt, 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 _\bu_\bn_\bs_\be_\bt
+ 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
+ $\b$x\bxt\bte\ber\brm\bm_\b_s\bse\bet\bt_\b_t\bti\bit\btl\ble\bes\bs has been _\bs_\be_\bt. This string is identical in formatting
+ to the one used by ``$\b$s\bst\bta\bat\btu\bus\bs_\b_f\bfo\bor\brm\bma\bat\bt''.
- 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\bbi\bin\bnd\bd command.
+
+5.1. generic
+
+ The _\bg_\be_\bn_\be_\br_\bi_\bc menu is not a real menu, but specifies common functions
+ (such as movement) available in all menus except for _\bp_\ba_\bg_\be_\br and _\be_\bd_\bi_\bt_\bo_\br.
+ Changing settings for this menu will affect the default bindings for
+ all menus (except as noted).
+
+ _\bT_\ba_\bb_\bl_\be_\b _\b7_\b._\b4_\b._\b _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\b:_\b _\bD_\be_\bf_\ba_\bu_\bl_\bt_\b _\bG_\be_\bn_\be_\br_\bi_\bc_\b _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\b _\bB_\bi_\bn_\bd_\bi_\bn_\bg_\bs
+ 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
+
+ _\bT_\ba_\bb_\bl_\be_\b _\b7_\b._\b5_\b._\b _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\b:_\b _\bD_\be_\bf_\ba_\bu_\bl_\bt_\b _\bI_\bn_\bd_\be_\bx_\b _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\b _\bB_\bi_\bn_\bd_\bi_\bn_\bg_\bs
+ 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
+
+ _\bT_\ba_\bb_\bl_\be_\b _\b7_\b._\b6_\b._\b _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\b:_\b _\bD_\be_\bf_\ba_\bu_\bl_\bt_\b _\bP_\ba_\bg_\be_\br_\b _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\b _\bB_\bi_\bn_\bd_\bi_\bn_\bg_\bs
+ 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
+
+ _\bT_\ba_\bb_\bl_\be_\b _\b7_\b._\b7_\b._\b _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\b:_\b _\bD_\be_\bf_\ba_\bu_\bl_\bt_\b _\bA_\bl_\bi_\ba_\bs_\b _\bM_\be_\bn_\bu_\b _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\b _\bB_\bi_\bn_\bd_\bi_\bn_\bg_\bs
+ 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
+ _\bT_\ba_\bb_\bl_\be_\b _\b7_\b._\b8_\b._\b _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\b:_\b _\bD_\be_\bf_\ba_\bu_\bl_\bt_\b _\bQ_\bu_\be_\br_\by_\b _\bM_\be_\bn_\bu_\b _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\b _\bB_\bi_\bn_\bd_\bi_\bn_\bg_\bs
+ 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
+
+ _\bT_\ba_\bb_\bl_\be_\b _\b7_\b._\b9_\b._\b _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\b:_\b _\bD_\be_\bf_\ba_\bu_\bl_\bt_\b _\bA_\bt_\bt_\ba_\bc_\bh_\bm_\be_\bn_\bt_\b _\bM_\be_\bn_\bu_\b _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\b _\bB_\bi_\bn_\bd_\bi_\bn_\bg_\bs
+ 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
+
+ _\bT_\ba_\bb_\bl_\be_\b _\b7_\b._\b1_\b0_\b._\b _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\b:_\b _\bD_\be_\bf_\ba_\bu_\bl_\bt_\b _\bC_\bo_\bm_\bp_\bo_\bs_\be_\b _\bM_\be_\bn_\bu_\b _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\b _\bB_\bi_\bn_\bd_\bi_\bn_\bg_\bs
+ 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
+
+ _\bT_\ba_\bb_\bl_\be_\b _\b7_\b._\b1_\b1_\b._\b _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\b:_\b _\bD_\be_\bf_\ba_\bu_\bl_\bt_\b _\bP_\bo_\bs_\bt_\bp_\bo_\bn_\be_\b _\bM_\be_\bn_\bu_\b _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\b _\bB_\bi_\bn_\bd_\bi_\bn_\bg_\bs
+ 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
+
+ _\bT_\ba_\bb_\bl_\be_\b _\b7_\b._\b1_\b2_\b._\b _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\b:_\b _\bD_\be_\bf_\ba_\bu_\bl_\bt_\b _\bB_\br_\bo_\bw_\bs_\be_\br_\b _\bM_\be_\bn_\bu_\b _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\b _\bB_\bi_\bn_\bd_\bi_\bn_\bg_\bs
+ 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
+
+ _\bT_\ba_\bb_\bl_\be_\b _\b7_\b._\b1_\b3_\b._\b _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\b:_\b _\bD_\be_\bf_\ba_\bu_\bl_\bt_\b _\bP_\bG_\bP_\b _\bM_\be_\bn_\bu_\b _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\b _\bB_\bi_\bn_\bd_\bi_\bn_\bg_\bs
+ 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
+ _\bT_\ba_\bb_\bl_\be_\b _\b7_\b._\b1_\b4_\b._\b _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\b:_\b _\bD_\be_\bf_\ba_\bu_\bl_\bt_\b _\bE_\bd_\bi_\bt_\bo_\br_\b _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\b _\bB_\bi_\bn_\bd_\bi_\bn_\bg_\bs
+ 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
+ _\bT_\ba_\bb_\bl_\be_\b _\b7_\b._\b1_\b5_\b._\b _\bR_\be_\bf_\be_\br_\be_\bn_\be_\b:_\b _\bD_\be_\bf_\ba_\bu_\bl_\bt_\b _\bS_\bi_\bd_\be_\bb_\ba_\br_\b _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\b _\bB_\bi_\bn_\bd_\bi_\bn_\bg_\bs
+ 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\bka\bar\bri\bi.\b.h\bhu\bur\brt\btt\bta\ba@\b@f\bfm\bmi\bi.\b.f\bfi\bi> 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\bvi\bik\bka\bas\bsa\ba@\b@w\bwr\bri\bit\bte\bem\bme\be.\b.c\bco\bom\bm>
+ * Francois Berjon < F\bFr\bra\ban\bnc\bco\boi\bis\bs.\b.B\bBe\ber\brj\bjo\bon\bn@\b@a\baa\bar\br.\b.a\bal\blc\bca\bat\bte\bel\bl-\b-a\bal\bls\bst\bth\bho\bom\bm.\b.f\bfr\br>
+ * Aric Blumer <a\bar\bri\bic\bc@\b@f\bfo\bor\bre\be.\b.c\bco\bom\bm>
+ * John Capo <j\bjc\bc@\b@i\bir\brb\bbs\bs.\b.c\bco\bom\bm>
+ * David Champion <d\bdg\bgc\bc@\b@u\buc\bch\bhi\bic\bca\bag\bgo\bo.\b.e\bed\bdu\bu>
+ * Brendan Cully <b\bbr\bre\ben\bnd\bda\ban\bn@\b@k\bku\bub\bbl\bla\bai\bi.\b.c\bco\bom\bm>
+ * Liviu Daia <d\bda\bai\bia\ba@\b@s\bst\bto\boi\bil\blo\bow\bw.\b.i\bim\bma\bar\br.\b.r\bro\bo>
+ * Thomas E. Dickey <d\bdi\bic\bck\bke\bey\by@\b@h\bhe\ber\brn\bnd\bdo\bon\bn4\b4.\b.h\bhi\bis\bs.\b.c\bco\bom\bm>
+ * David DeSimone <f\bfo\box\bx@\b@c\bco\bon\bnv\bve\bex\bx.\b.h\bhp\bp.\b.c\bco\bom\bm>
+ * Nickolay N. Dudorov <n\bnn\bnd\bd@\b@w\bwi\bin\bnt\bt.\b.i\bit\btf\bfs\bs.\b.n\bns\bsk\bk.\b.s\bsu\bu>
+ * Ruslan Ermilov <r\bru\bu@\b@f\bfr\bre\bee\beb\bbs\bsd\bd.\b.o\bor\brg\bg>
+ * Edmund Grimley Evans <e\bed\bdm\bmu\bun\bnd\bdo\bo@\b@r\bra\ban\bno\bo.\b.o\bor\brg\bg>
+ * Michael Finken <f\bfi\bin\bnk\bke\ben\bn@\b@c\bco\bon\bnw\bwa\bar\bre\be.\b.d\bde\be>
+ * Sven Guckes <g\bgu\buc\bck\bke\bes\bs@\b@m\bma\bat\bth\bh.\b.f\bfu\bu-\b-b\bbe\ber\brl\bli\bin\bn.\b.d\bde\be>
+ * Lars Hecking <l\blh\bhe\bec\bck\bki\bin\bng\bg@\b@n\bnm\bmr\brc\bc.\b.i\bie\be>
+ * Mark Holloman <h\bho\bol\bll\blo\bom\bma\ban\bn@\b@n\bna\ban\bnd\bdo\bo.\b.n\bne\bet\bt>
+ * Andreas Holzmann <h\bho\bol\blz\bzm\bma\ban\bnn\bn@\b@f\bfm\bmi\bi.\b.u\bun\bni\bi-\b-p\bpa\bas\bss\bsa\bau\bu.\b.d\bde\be>
+ * Marco d'Itri <m\bmd\bd@\b@l\bli\bin\bnu\bux\bx.\b.i\bit\bt>
+ * Björn Jacke <b\bbj\bja\bac\bck\bke\be@\b@s\bsu\bus\bse\be.\b.c\bco\bom\bm>
+ * Byrial Jensen <b\bby\byr\bri\bia\bal\bl@\b@i\bim\bma\bag\bge\be.\b.d\bdk\bk>
+ * David Jeske <j\bje\bes\bsk\bke\be@\b@i\big\bgc\bco\bom\bm.\b.n\bne\bet\bt>
+ * Christophe Kalt <k\bka\bal\blt\bt@\b@h\bhu\bug\bgo\bo.\b.i\bin\bnt\bt-\b-e\bev\bvr\bry\by.\b.f\bfr\br>
+ * Tommi Komulainen <T\bTo\bom\bmm\bmi\bi.\b.K\bKo\bom\bmu\bul\bla\bai\bin\bne\ben\bn@\b@i\bik\bki\bi.\b.f\bfi\bi>
+ * Felix von Leitner (a.k.a ``Fefe'') < l\ble\bei\bit\btn\bne\ber\br@\b@m\bma\bat\bth\bh.\b.f\bfu\bu-\b-b\bbe\ber\brl\bli\bin\bn.\b.d\bde\be >
+ * Brandon Long <b\bbl\blo\bon\bng\bg@\b@f\bfi\bic\bct\bti\bio\bon\bn.\b.n\bne\bet\bt>
+ * Jimmy Mäkeä <j\bjm\bmy\by@\b@f\bfl\bla\bas\bsh\bhb\bba\bac\bck\bk.\b.n\bne\bet\bt>
+ * Lars Marowsky-Bree <l\blm\bmb\bb@\b@p\bpo\boi\bin\bnt\bte\ber\br.\b.i\bin\bn-\b-m\bmi\bin\bnd\bde\ben\bn.\b.d\bde\be>
+ * Thomas ``Mike'' Michlmayr <m\bmi\bik\bke\be@\b@c\bco\bos\bsy\by.\b.s\bsb\bbg\bg.\b.a\bac\bc.\b.a\bat\bt>
+ * Andrew W. Nosenko <a\baw\bwn\bn@\b@b\bbc\bcs\bs.\b.z\bzp\bp.\b.u\bua\ba>
+ * David O'Brien <o\bob\bbr\bri\bie\ben\bn@\b@N\bNu\bux\bxi\bi.\b.c\bcs\bs.\b.u\buc\bcd\bda\bav\bvi\bis\bs.\b.e\bed\bdu\bu>
+ * Clint Olsen <o\bol\bls\bse\ben\bnc\bc@\b@i\bic\bch\bhi\bip\bps\bs.\b.i\bin\bnt\bte\bel\bl.\b.c\bco\bom\bm>
+ * Park Myeong Seok <p\bpm\bms\bs@\b@r\bro\bom\bma\ban\bnc\bce\be.\b.k\bka\bai\bis\bst\bt.\b.a\bac\bc.\b.k\bkr\br>
+ * Thomas Parmelan <t\bto\bom\bm@\b@a\ban\bnk\bkh\bh.\b.f\bfr\br.\b.e\beu\bu.\b.o\bor\brg\bg>
+ * Ollivier Robert <r\bro\bob\bbe\ber\brt\bto\bo@\b@k\bke\bel\blt\bti\bia\ba.\b.f\bfr\bre\bee\ben\bni\bix\bx.\b.f\bfr\br>
+ * Thomas Roessler <r\bro\boe\bes\bss\bsl\ble\ber\br@\b@d\bdo\boe\bes\bs-\b-n\bno\bot\bt-\b-e\bex\bxi\bis\bst\bt.\b.o\bor\brg\bg>
+ * Roland Rosenfeld <r\bro\bol\bla\ban\bnd\bd@\b@s\bsp\bpi\bin\bnn\bna\bak\bke\ber\br.\b.d\bde\be>
+ * TAKIZAWA Takashi <t\bta\bak\bki\bi@\b@l\blu\bun\bna\ba.\b.e\bem\bma\bai\bil\bl.\b.n\bne\be.\b.j\bjp\bp>
+ * Allain Thivillon <A\bAl\bll\bla\bai\bin\bn.\b.T\bTh\bhi\biv\bvi\bil\bll\blo\bon\bn@\b@a\bal\blm\bma\ba.\b.f\bfr\br>
+ * Gero Treuner <g\bge\ber\bro\bo@\b@7\b70\b0t\bt.\b.d\bde\be>
+ * Vsevolod Volkov <v\bvv\bvv\bv@\b@l\blu\buc\bck\bky\by.\b.n\bne\bet\bt>
+ * Ken Weinert <k\bke\ben\bnw\bw@\b@i\bih\bhs\bs.\b.c\bco\bom\bm>
- $use_from , $use_from
+ Mutt-ng is developed by the following people:
- $use_idn , $use_idn
+ * Andreas Krennmair <a\bak\bk@\b@s\bsy\byn\bnf\bfl\blo\boo\bod\bd.\b.a\bat\bt>
+ * Nico Golde <n\bni\bic\bco\bo@\b@n\bng\bgo\bol\bld\bde\be.\b.d\bde\be>
+ * Rocco Rutte <p\bpd\bdm\bme\bef\bf@\b@c\bcs\bs.\b.t\btu\bu-\b-b\bbe\ber\brl\bli\bin\bn.\b.d\bde\be>
- $use_ipv6 , $use_ipv6
+ The following people have been very helpful to the development of
+ Mutt-ng (sorted by surnames):
- V
+ * Christian Gall <c\bcg\bg@\b@c\bcg\bga\bal\bll\bl.\b.d\bde\be>
+ * Iain Lea <i\bia\bai\bin\bn@\b@b\bbr\bri\bic\bcb\bbr\bra\bac\bc.\b.d\bde\be>
+ * Andreas Kneib <a\bak\bkn\bne\bei\bib\bb@\b@g\bgm\bmx\bx.\b.n\bne\bet\bt>
+ * Felix Meinhold <f\bfe\bel\bli\bix\bx.\b.m\bme\bei\bin\bnh\bho\bol\bld\bd@\b@g\bgm\bmx\bx.\b.n\bne\bet\bt>
+ * Carsten Schoelzki <c\bcj\bjs\bs@\b@w\bwe\bei\bis\bss\bsh\bhu\buh\bhn\bn.\b.d\bde\be>
+ * Elimar Riesebieter <r\bri\bie\bes\bse\beb\bbi\bie\be@\b@l\blx\bxt\bte\bec\bc.\b.d\bde\be>
- <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 (_\bn_\bo_\bt_\be_\b:_\b _\bt_\bh_\bi_\bs_\b _\bi_\bs_\b _\bf_\ba_\br_\b _\bf_\br_\bo_\bm_\b _\bb_\be_\bi_\bn_\bg_\b _\bc_\bo_\bm_\bp_\bl_\be_\bt_\be_\b,
+ _\ba_\bn_\by_\b _\bh_\be_\bl_\bp_\b _\bt_\bo_\bw_\ba_\br_\bd_\bs_\b _\bc_\bo_\bn_\bs_\bi_\bs_\bt_\be_\bn_\bc_\by_\b _\bi_\bs_\b _\bh_\bi_\bg_\bh_\bl_\by_\b _\ba_\bp_\bp_\br_\be_\bc_\bi_\ba_\bt_\be_\bd).
- <view-mailcap>, attach
+ <muttng-doc:man name="" [sect=""]/>
+ _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\bs_\b _\bt_\bo_\b _\bm_\ba_\bn_\bu_\ba_\bl_\b _\bp_\ba_\bg_\be_\bs_\b. 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=""/>
+ _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\bs_\b _\bt_\bo_\b _\be_\bn_\bv_\bi_\br_\bo_\bn_\bm_\be_\bn_\bt_\b _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs_\b. 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=""/>
+ _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\bs_\b _\bt_\bo_\b _\bh_\bo_\bo_\bk_\bs_\b. 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"]/>
+ _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\bs_\b _\bt_\bo_\b _\bp_\ba_\bt_\bt_\be_\br_\bn_\bs_\b. 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>
+ _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\bi_\bn_\bg_\b _\ba_\b _\bk_\be_\by_\b.. 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=""/>
+ _\bD_\be_\bf_\bi_\bn_\bi_\bn_\bg_\b _\ba_\b _\bc_\bo_\bm_\bm_\ba_\bn_\bd_\b.. 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=""/>
+ _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\bs_\b _\bt_\bo_\b _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\bs_\b.. This is practically the same as the
+ above except that there's no anchor defined.
- $wait_key , $wait_key
+ <muttng-doc:vardef name=""/>
+ _\bD_\be_\bf_\bi_\bn_\bi_\bn_\bg_\b _\ba_\b _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\b. 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=""/>
+ _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\bs_\b _\bt_\bo_\b _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs_\b. 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""/>
+ _\bP_\br_\be_\bt_\bt_\by_\b _\bp_\br_\bi_\bn_\bt_\b _\ba_\b _\bl_\bi_\bn_\bk_\be_\bd_\b _\bU_\bR_\bL. 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=""/>
+ _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\bs_\b _\bt_\bo_\b _\bR_\bf_\bC_\b _\bd_\bo_\bc_\bu_\bm_\be_\bn_\bt_\bs_\b. Use this to produce links to RfC
+ document with number given as the num parameter. A link to
+ <\b<h\bht\btt\btp\bp:\b:/\b//\b/w\bww\bww\bw.\b.f\bfa\baq\bqs\bs.\b.o\bor\brg\bg/\b/>\b> will be made. Auto-indexing is done
+ under _\bR_\bf_\bC.
- $wrap_search , $wrap_search
+ <muttng-doc:cmddef name="" [noanchor="1"]/>
+ _\bD_\be_\bf_\bi_\bn_\bi_\bn_\bg_\b _\ba_\b _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn_\b _\bc_\bo_\bm_\bm_\ba_\bn_\bd_\b. 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=""/>
+ _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\bs_\b _\bt_\bo_\b _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn_\b _\bc_\bo_\bm_\bm_\ba_\bn_\bd_\bs_\b. 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/>
+ _\bS_\bc_\br_\be_\be_\bn_\b _\bl_\ba_\by_\bo_\bu_\bt_\b _\bb_\by_\b _\bc_\bo_\bn_\bt_\be_\bx_\bt_\b. 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 _\bm_\bu_\bs_\bt have an attribute called texstr which is directly
+ passed to longtable.
- $xterm_leave , $xterm_leave
+Index
- $xterm_set_titles , $xterm_set_titles
+Symbols
+
+ ~$/ =$, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~*/ =*, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~=/ ==, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~A/ =A, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~b/ =b, C\bCo\bom\bmp\bpl\ble\bex\bx \b P\bPa\bat\btt\bte\ber\brn\bns\bs, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~B/ =B, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~c/ =c, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~C/ =C, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~d/ =d, P\bPa\bat\btt\bte\ber\brn\bns\bs \b a\ban\bnd\bd \b D\bDa\bat\bte\bes\bs, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~D/ =D, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~E/ =E, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~e/ =e, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~f/ =f, C\bCo\bom\bmp\bpl\ble\bex\bx \b P\bPa\bat\btt\bte\ber\brn\bns\bs, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~F/ =F, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~g/ =g, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~G/ =G, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~H/ =H, S\bSp\bpa\bam\bm \b d\bde\bet\bte\bec\bct\bti\bio\bon\bn, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~h/ =h, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~i/ =i, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~k/ =k, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~L/ =L, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~l/ =l, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~m/ =m, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~M/ =M, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~n/ =n, M\bMe\bes\bss\bsa\bag\bge\be \b S\bSc\bco\bor\bri\bin\bng\bg, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~N/ =N, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~O/ =O, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~p/ =p, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~P/ =P, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~Q/ =Q, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~R/ =R, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~r/ =r, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~s/ =s, C\bCo\bom\bmp\bpl\ble\bex\bx \b P\bPa\bat\btt\bte\ber\brn\bns\bs, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~S/ =S, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~T/ =T, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~t/ =t, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~U/ =U, C\bCo\bom\bmp\bpl\ble\bex\bx \b P\bPa\bat\btt\bte\ber\brn\bns\bs, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~u/ =u, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~v/ =v, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~V/ =V, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~w/ =w, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~x/ =x, C\bCo\bom\bmp\bpl\ble\bex\bx \b P\bPa\bat\btt\bte\ber\brn\bns\bs, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~X/ =X, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~y/ =y, H\bHa\ban\bnd\bdl\bli\bin\bng\bg \b M\bMa\bai\bil\bli\bin\bng\bg \b L\bLi\bis\bst\bts\bs, P\bPa\bat\btt\bte\ber\brn\bns\bs
+ ~z/ =z, P\bPa\bat\btt\bte\ber\brn\bns\bs
+
+A
+
+ $abort_noattach , $\b$a\bab\bbo\bor\brt\bt_\b_n\bno\boa\bat\btt\bta\bac\bch\bh
+ $abort_nosubject , $\b$a\bab\bbo\bor\brt\bt_\b_n\bno\bos\bsu\bub\bbj\bje\bec\bct\bt
+ $abort_unmodified , $\b$a\bab\bbo\bor\brt\bt_\b_u\bun\bnm\bmo\bod\bdi\bif\bfi\bie\bed\bd
+ account-hook, M\bMa\ban\bna\bag\bgi\bin\bng\bg \b m\bmu\bul\blt\bti\bip\bpl\ble\be \b I\bIM\bMA\bAP\bP/\b/P\bPO\bOP\bP/\b/N\bNN\bNT\bTP\bP \b a\bac\bcc\bco\bou\bun\bnt\bts\bs \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b),
+ C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ $agent_string , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $agent_string , $\b$a\bag\bge\ben\bnt\bt_\b_s\bst\btr\bri\bin\bng\bg
+ alias, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, D\bDe\bef\bfi\bin\bni\bin\bng\bg/\b/U\bUs\bsi\bin\bng\bg \b a\bal\bli\bia\bas\bse\bes\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn
+ C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ $alias_file, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, D\bDe\bef\bfi\bin\bni\bin\bng\bg/\b/U\bUs\bsi\bin\bng\bg \b a\bal\bli\bia\bas\bse\bes\bs
+ $alias_file , $\b$a\bal\bli\bia\bas\bs_\b_f\bfi\bil\ble\be
+ $alias_format , $\b$a\bal\bli\bia\bas\bs_\b_f\bfo\bor\brm\bma\bat\bt
+ $allow_8bit , $\b$a\bal\bll\blo\bow\bw_\b_8\b8b\bbi\bit\bt
+ $allow_ansi , $\b$a\bal\bll\blo\bow\bw_\b_a\ban\bns\bsi\bi
+ alternates, A\bAl\blt\bte\ber\brn\bna\bat\bti\biv\bve\be \b a\bad\bdd\bdr\bre\bes\bss\bse\bes\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ alternative_order, M\bMI\bIM\bME\bE \b M\bMu\bul\blt\bti\bip\bpa\bar\brt\bt/\b/A\bAl\blt\bte\ber\brn\bna\bat\bti\biv\bve\be, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ append-hook, C\bCo\bom\bmp\bpr\bre\bes\bss\bse\bed\bd \b f\bfo\bol\bld\bde\ber\brs\bs \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b), A\bAp\bpp\bpe\ben\bnd\bd \b a\ba \b m\bme\bes\bss\bsa\bag\bge\be
+ t\bto\bo \b a\ba \b c\bco\bom\bmp\bpr\bre\bes\bss\bse\bed\bd \b m\bma\bai\bil\blb\bbo\box\bx, E\bEn\bnc\bcr\bry\byp\bpt\bte\bed\bd \b f\bfo\bol\bld\bde\ber\brs\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn
+ C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ $arrow_cursor , $\b$a\bar\brr\bro\bow\bw_\b_c\bcu\bur\brs\bso\bor\br
+ $ascii_chars , $\b$a\bas\bsc\bci\bii\bi_\b_c\bch\bha\bar\brs\bs
+ $askbcc , $\b$a\bas\bsk\bkb\bbc\bcc\bc
+ $askcc , $\b$a\bas\bsk\bkc\bcc\bc
+ $assumed_charset , $\b$a\bas\bss\bsu\bum\bme\bed\bd_\b_c\bch\bha\bar\brs\bse\bet\bt
+ <attach-file>, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs, c\bco\bom\bmp\bpo\bos\bse\be
+ <attach-key>, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs, c\bco\bom\bmp\bpo\bos\bse\be
+ <attach-message>, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs, c\bco\bom\bmp\bpo\bos\bse\be
+ attachments, A\bAt\btt\bta\bac\bch\bhm\bme\ben\bnt\bt \b S\bSe\bea\bar\brc\bch\bhi\bin\bng\bg \b a\ban\bnd\bd \b C\bCo\bou\bun\bnt\bti\bin\bng\bg
+ $attach_format , $\b$a\bat\btt\bta\bac\bch\bh_\b_f\bfo\bor\brm\bma\bat\bt
+ $attach_remind_regexp , $\b$a\bat\btt\bta\bac\bch\bh_\b_r\bre\bem\bmi\bin\bnd\bd_\b_r\bre\beg\bge\bex\bxp\bp
+ $attach_sep , $\b$a\bat\btt\bta\bac\bch\bh_\b_s\bse\bep\bp
+ $attach_split , $\b$a\bat\btt\bta\bac\bch\bh_\b_s\bsp\bpl\bli\bit\bt
+ $attribution, C\bCh\bha\ban\bng\bge\be \b s\bse\bet\btt\bti\bin\bng\bgs\bs \b b\bba\bas\bse\bed\bd \b u\bup\bpo\bon\bn \b m\bme\bes\bss\bsa\bag\bge\be \b r\bre\bec\bci\bip\bpi\bie\ben\bnt\bts\bs,
+ $\b$a\bat\btt\btr\bri\bib\bbu\but\bti\bio\bon\bn
+
+ $auto_tag, U\bUs\bsi\bin\bng\bg \b T\bTa\bag\bgs\bs
+ $autoedit , $\b$a\bau\but\bto\boe\bed\bdi\bit\bt
+ $auto_tag , $\b$a\bau\but\bto\bo_\b_t\bta\bag\bg
+ auto_view, T\bTh\bhe\be \b P\bPa\bag\bge\ber\br, O\bOp\bpt\bti\bio\bon\bna\bal\bl \b F\bFi\bie\bel\bld\bds\bs, S\bSe\bea\bar\brc\bch\bh \b O\bOr\brd\bde\ber\br, M\bMI\bIM\bME\bE \b A\bAu\but\bto\bov\bvi\bie\bew\bw,
+ M\bMI\bIM\bME\bE \b M\bMu\bul\blt\bti\bip\bpa\bar\brt\bt/\b/A\bAl\blt\bte\ber\brn\bna\bat\bti\biv\bve\be, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+B
+
+ <backspace>, E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs, e\bed\bdi\bit\bto\bor\br
+ <backward-char>, E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs, e\bed\bdi\bit\bto\bor\br
+ <backward-word>, E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs, e\bed\bdi\bit\bto\bor\br
+ $beep , $\b$b\bbe\bee\bep\bp
+ $beep_new , $\b$b\bbe\bee\bep\bp_\b_n\bne\bew\bw
+ bind, E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs, C\bCh\bha\ban\bng\bgi\bin\bng\bg \b t\bth\bhe\be \b d\bde\bef\bfa\bau\bul\blt\bt \b k\bke\bey\by \b b\bbi\bin\bnd\bdi\bin\bng\bgs\bs,
+ K\bKe\bey\byb\bbo\boa\bar\brd\bd \b m\bma\bac\bcr\bro\bos\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ <bol>, E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs, e\bed\bdi\bit\bto\bor\br
+ <bottom>, p\bpa\bag\bge\ber\br
+ <bottom-page>, g\bge\ben\bne\ber\bri\bic\bc
+ <bounce>, S\bSe\ben\bnd\bdi\bin\bng\bg \b M\bMa\bai\bil\bl, $\b$b\bbo\bou\bun\bnc\bce\be
+ <bounce-message>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br, a\bat\btt\bta\bac\bch\bh
+ $bounce_delivered , $\b$b\bbo\bou\bun\bnc\bce\be_\b_d\bde\bel\bli\biv\bve\ber\bre\bed\bd
+ $braille_friendly , $\b$b\bbr\bra\bai\bil\bll\ble\be_\b_f\bfr\bri\bie\ben\bnd\bdl\bly\by
+ <buffy-cycle>, e\bed\bdi\bit\bto\bor\br
+
+C
+
+ <capitalize-word>, E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs, e\bed\bdi\bit\bto\bor\br
+ $certificate_file , $\b$c\bce\ber\brt\bti\bif\bfi\bic\bca\bat\bte\be_\b_f\bfi\bil\ble\be
+ <change-dir>, b\bbr\bro\bow\bws\bse\ber\br
+ <change-folder>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ <change-folder-readonly>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ $charset , $\b$c\bch\bha\bar\brs\bse\bet\bt
+ charset-hook, D\bDe\bef\bfi\bin\bni\bin\bng\bg \b a\bal\bli\bia\bas\bse\bes\bs \b f\bfo\bor\br \b c\bch\bha\bar\bra\bac\bct\bte\ber\br \b s\bse\bet\bts\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn
+ C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ <check-new>, b\bbr\bro\bow\bws\bse\ber\br
+ <check-traditional-pgp>, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ $check_new , $\b$c\bch\bhe\bec\bck\bk_\b_n\bne\bew\bw
+ <clear-flag>, i\bin\bnd\bde\bex\bx
+ close-hook, C\bCo\bom\bmp\bpr\bre\bes\bss\bse\bed\bd \b f\bfo\bol\bld\bde\ber\brs\bs \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b), W\bWr\bri\bit\bte\be \b a\ba \b c\bco\bom\bmp\bpr\bre\bes\bss\bse\bed\bd
+ m\bma\bai\bil\blb\bbo\box\bx, A\bAp\bpp\bpe\ben\bnd\bd \b a\ba \b m\bme\bes\bss\bsa\bag\bge\be \b t\bto\bo \b a\ba \b c\bco\bom\bmp\bpr\bre\bes\bss\bse\bed\bd \b m\bma\bai\bil\blb\bbo\box\bx,
+ C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ <collapse-all>, T\bTh\bhr\bre\bea\bad\bde\bed\bd \b M\bMo\bod\bde\be
+ <collapse-parts>, a\bat\btt\bta\bac\bch\bh
+ <collapse-thread>, T\bTh\bhr\bre\bea\bad\bde\bed\bd \b M\bMo\bod\bde\be
+ $collapse_unread , $\b$c\bco\bol\bll\bla\bap\bps\bse\be_\b_u\bun\bnr\bre\bea\bad\bd
+ color, T\bTh\bhe\be \b P\bPa\bag\bge\ber\br, U\bUs\bsi\bin\bng\bg \b c\bco\bol\blo\bor\br \b a\ban\bnd\bd \b m\bmo\bon\bno\bo \b v\bvi\bid\bde\beo\bo \b a\bat\btt\btr\bri\bib\bbu\but\bte\bes\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn
+ C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ $COLORFGBG, U\bUs\bsi\bin\bng\bg \b c\bco\bol\blo\bor\br \b a\ban\bnd\bd \b m\bmo\bon\bno\bo \b v\bvi\bid\bde\beo\bo \b a\bat\btt\btr\bri\bib\bbu\but\bte\bes\bs
+ <complete>, E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs, e\bed\bdi\bit\bto\bor\br
+ <complete-query>, E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs, e\bed\bdi\bit\bto\bor\br
+ <compose>, S\bSe\ben\bnd\bdi\bin\bng\bg \b M\bMa\bai\bil\bl
+ $compose_format , $\b$c\bco\bom\bmp\bpo\bos\bse\be_\b_f\bfo\bor\brm\bma\bat\bt
+ $config_charset , $\b$c\bco\bon\bnf\bfi\big\bg_\b_c\bch\bha\bar\brs\bse\bet\bt
+ $confirmappend , $\b$c\bco\bon\bnf\bfi\bir\brm\bma\bap\bpp\bpe\ben\bnd\bd
+ $confirmcreate , $\b$c\bco\bon\bnf\bfi\bir\brm\bmc\bcr\bre\bea\bat\bte\be
+ $connect_timeout , $\b$c\bco\bon\bnn\bne\bec\bct\bt_\b_t\bti\bim\bme\beo\bou\but\bt
+ $content_type , $\b$c\bco\bon\bnt\bte\ben\bnt\bt_\b_t\bty\byp\bpe\be
+ $copy , $\b$c\bco\bop\bpy\by
+ <copy-file>, c\bco\bom\bmp\bpo\bos\bse\be
+ <copy-message>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ $count_attachments, A\bAt\btt\bta\bac\bch\bhm\bme\ben\bnt\bt \b S\bSe\bea\bar\brc\bch\bhi\bin\bng\bg \b a\ban\bnd\bd \b C\bCo\bou\bun\bnt\bti\bin\bng\bg
+ $count_attachments , $\b$c\bco\bou\bun\bnt\bt_\b_a\bat\btt\bta\bac\bch\bhm\bme\ben\bnt\bts\bs
+ <create-alias>, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, D\bDe\bef\bfi\bin\bni\bin\bng\bg/\b/U\bUs\bsi\bin\bng\bg \b a\bal\bli\bia\bas\bse\bes\bs,
+ i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br, q\bqu\bue\ber\bry\by
+
+ $crypt_autoencrypt , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $crypt_autosign , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ crypt-hook, C\bCh\bho\boo\bos\bsi\bin\bng\bg \b t\bth\bhe\be \b c\bcr\bry\byp\bpt\bto\bog\bgr\bra\bap\bph\bhi\bic\bc \b k\bke\bey\by \b o\bof\bf \b t\bth\bhe\be \b r\bre\bec\bci\bip\bpi\bie\ben\bnt\bt,
+ C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ $crypt_replyencrypt , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $crypt_replysign , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $crypt_replysignencrypted , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $crypt_verify_sig , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $crypt_autoencrypt , $\b$c\bcr\bry\byp\bpt\bt_\b_a\bau\but\bto\boe\ben\bnc\bcr\bry\byp\bpt\bt
+ $crypt_autopgp , $\b$c\bcr\bry\byp\bpt\bt_\b_a\bau\but\bto\bop\bpg\bgp\bp
+ $crypt_autosign , $\b$c\bcr\bry\byp\bpt\bt_\b_a\bau\but\bto\bos\bsi\big\bgn\bn
+ $crypt_autosmime , $\b$c\bcr\bry\byp\bpt\bt_\b_a\bau\but\bto\bos\bsm\bmi\bim\bme\be
+ $crypt_replyencrypt , $\b$c\bcr\bry\byp\bpt\bt_\b_r\bre\bep\bpl\bly\bye\ben\bnc\bcr\bry\byp\bpt\bt
+ $crypt_replysign , $\b$c\bcr\bry\byp\bpt\bt_\b_r\bre\bep\bpl\bly\bys\bsi\big\bgn\bn
+ $crypt_replysignencrypted , $\b$c\bcr\bry\byp\bpt\bt_\b_r\bre\bep\bpl\bly\bys\bsi\big\bgn\bne\ben\bnc\bcr\bry\byp\bpt\bte\bed\bd
+ $crypt_timestamp , $\b$c\bcr\bry\byp\bpt\bt_\b_t\bti\bim\bme\bes\bst\bta\bam\bmp\bp
+ $crypt_use_gpgme , $\b$c\bcr\bry\byp\bpt\bt_\b_u\bus\bse\be_\b_g\bgp\bpg\bgm\bme\be
+ $crypt_verify_sig , $\b$c\bcr\bry\byp\bpt\bt_\b_v\bve\ber\bri\bif\bfy\by_\b_s\bsi\big\bg
+ <current-bottom>, g\bge\ben\bne\ber\bri\bic\bc
+ <current-middle>, g\bge\ben\bne\ber\bri\bic\bc
+ <current-top>, g\bge\ben\bne\ber\bri\bic\bc
+
+D
+
+ $date_format , $\b$d\bda\bat\bte\be_\b_f\bfo\bor\brm\bma\bat\bt
+ $debug_level , $\b$d\bde\beb\bbu\bug\bg_\b_l\ble\bev\bve\bel\bl
+ <decode-copy>, i\bin\bnd\bde\bex\bx
+ <decode-save>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ default-hook, M\bMe\bes\bss\bsa\bag\bge\be \b M\bMa\bat\btc\bch\bhi\bin\bng\bg \b i\bin\bn \b H\bHo\boo\bok\bks\bs
+ $default_hook , $\b$d\bde\bef\bfa\bau\bul\blt\bt_\b_h\bho\boo\bok\bk
+ $delete , $\b$d\bde\bel\ble\bet\bte\be
+ <delete-char>, E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs, e\bed\bdi\bit\bto\bor\br
+ <delete-entry>, a\bat\btt\bta\bac\bch\bh, p\bpo\bos\bst\btp\bpo\bon\bne\be
+ <delete-message>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ <delete-pattern>, i\bin\bnd\bde\bex\bx
+ $delete_space, A\bAd\bdd\bdi\bit\bti\bio\bon\bna\bal\bl \b N\bNo\bot\bte\bes\bs
+ <delete-subthread>, T\bTh\bhr\bre\bea\bad\bde\bed\bd \b M\bMo\bod\bde\be, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ <delete-thread>, T\bTh\bhr\bre\bea\bad\bde\bed\bd \b M\bMo\bod\bde\be, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ $delete_space , $\b$d\bde\bel\ble\bet\bte\be_\b_s\bsp\bpa\bac\bce\be
+ $delete_untag , $\b$d\bde\bel\ble\bet\bte\be_\b_u\bun\bnt\bta\bag\bg
+ <detach-file>, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs, c\bco\bom\bmp\bpo\bos\bse\be
+ $digest_collapse , $\b$d\bdi\big\bge\bes\bst\bt_\b_c\bco\bol\bll\bla\bap\bps\bse\be
+ <display-address>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ <display-message>, i\bin\bnd\bde\bex\bx
+ <display-toggle-weed>, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br, a\bat\btt\bta\bac\bch\bh,
+ c\bco\bom\bmp\bpo\bos\bse\be
+
+ $display_filter , $\b$d\bdi\bis\bsp\bpl\bla\bay\by_\b_f\bfi\bil\blt\bte\ber\br
+ $dotlock_program , $\b$d\bdo\bot\btl\blo\boc\bck\bk_\b_p\bpr\bro\bog\bgr\bra\bam\bm
+ <downcase-word>, E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs, e\bed\bdi\bit\bto\bor\br
+ $dsn_notify, D\bDe\bel\bli\biv\bve\ber\bry\by \b S\bSt\bta\bat\btu\bus\bs \b N\bNo\bot\bti\bif\bfi\bic\bca\bat\bti\bio\bon\bn \b (\b(D\bDS\bSN\bN)\b) \b S\bSu\bup\bpp\bpo\bor\brt\bt
+ $dsn_return, D\bDe\bel\bli\biv\bve\ber\bry\by \b S\bSt\bta\bat\btu\bus\bs \b N\bNo\bot\bti\bif\bfi\bic\bca\bat\bti\bio\bon\bn \b (\b(D\bDS\bSN\bN)\b) \b S\bSu\bup\bpp\bpo\bor\brt\bt
+ $dsn_notify , $\b$d\bds\bsn\bn_\b_n\bno\bot\bti\bif\bfy\by
+ $dsn_return , $\b$d\bds\bsn\bn_\b_r\bre\bet\btu\bur\brn\bn
+ $duplicate_threads , $\b$d\bdu\bup\bpl\bli\bic\bca\bat\bte\be_\b_t\bth\bhr\bre\bea\bad\bds\bs
+
+E
+
+ <edit>, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br, c\bco\bom\bmp\bpo\bos\bse\be
+ <edit-bcc>, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs, c\bco\bom\bmp\bpo\bos\bse\be
+ <edit-cc>, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs, c\bco\bom\bmp\bpo\bos\bse\be
+ <edit-description>, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs, c\bco\bom\bmp\bpo\bos\bse\be
+ <edit-encoding>, c\bco\bom\bmp\bpo\bos\bse\be
+ <edit-fcc>, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs, c\bco\bom\bmp\bpo\bos\bse\be
+ <edit-file>, c\bco\bom\bmp\bpo\bos\bse\be
+ <edit-from>, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs, c\bco\bom\bmp\bpo\bos\bse\be
+ $edit_headers, E\bEd\bdi\bit\bti\bin\bng\bg \b t\bth\bhe\be \b m\bme\bes\bss\bsa\bag\bge\be \b h\bhe\bea\bad\bde\ber\br, U\bUs\bse\ber\br \b d\bde\bef\bfi\bin\bne\bed\bd \b h\bhe\bea\bad\bde\ber\brs\bs,
+ m\bma\bai\bil\blt\bto\bo:\b:-\b-s\bst\bty\byl\ble\be \b l\bli\bin\bnk\bks\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs, c\bco\bom\bmp\bpo\bos\bse\be
+
+ <edit-mime>, c\bco\bom\bmp\bpo\bos\bse\be
+ <edit-reply-to>, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs, c\bco\bom\bmp\bpo\bos\bse\be
+ <edit-subject>, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs, c\bco\bom\bmp\bpo\bos\bse\be
+ <edit-to>, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs, c\bco\bom\bmp\bpo\bos\bse\be
+ <edit-type>, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br, a\bat\btt\bta\bac\bch\bh, c\bco\bom\bmp\bpo\bos\bse\be
+ $EDITOR, M\bMa\ban\bnu\bua\bal\bl \b C\bCo\bon\bnv\bve\ben\bnt\bti\bio\bon\bns\bs, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs
+ $editor , $\b$e\bed\bdi\bit\bto\bor\br
+ $editor_headers, E\bEd\bdi\bit\bti\bin\bng\bg \b t\bth\bhe\be \b m\bme\bes\bss\bsa\bag\bge\be \b h\bhe\bea\bad\bde\ber\br, D\bDe\bef\bfi\bin\bni\bin\bng\bg/\b/U\bUs\bsi\bin\bng\bg \b a\bal\bli\bia\bas\bse\bes\bs
+ $editor_headers , $\b$e\bed\bdi\bit\bto\bor\br_\b_h\bhe\bea\bad\bde\ber\brs\bs
+ $edit_headers , $\b$e\bed\bdi\bit\bt_\b_h\bhe\bea\bad\bde\ber\brs\bs
+ $encode_from , $\b$e\ben\bnc\bco\bod\bde\be_\b_f\bfr\bro\bom\bm
+ <enter-command>, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, g\bge\ben\bne\ber\bri\bic\bc, p\bpa\bag\bge\ber\br
+ <enter-mask>, b\bbr\bro\bow\bws\bse\ber\br
+ $entropy_file , $\b$e\ben\bnt\btr\bro\bop\bpy\by_\b_f\bfi\bil\ble\be
+ $envelope_from_address , $\b$e\ben\bnv\bve\bel\blo\bop\bpe\be_\b_f\bfr\bro\bom\bm_\b_a\bad\bdd\bdr\bre\bes\bss\bs
+ <eol>, E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs, e\bed\bdi\bit\bto\bor\br
+ $escape , $\b$e\bes\bsc\bca\bap\bpe\be
+ exec, E\bEx\bxe\bec\bcu\but\bti\bin\bng\bg \b f\bfu\bun\bnc\bct\bti\bio\bon\bns\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ <exit>, g\bge\ben\bne\ber\bri\bic\bc, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ <extract-keys>, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br, a\bat\btt\bta\bac\bch\bh
+
+F
+
+ $fast_reply , $\b$f\bfa\bas\bst\bt_\b_r\bre\bep\bpl\bly\by
+ fcc-hook, S\bSp\bpe\bec\bci\bif\bfy\by \b d\bde\bef\bfa\bau\bul\blt\bt \b F\bFc\bcc\bc:\b: \b m\bma\bai\bil\blb\bbo\box\bx \b w\bwh\bhe\ben\bn \b c\bco\bom\bmp\bpo\bos\bsi\bin\bng\bg, S\bSp\bpe\bec\bci\bif\bfy\by \b d\bde\bef\bfa\bau\bul\blt\bt
+ s\bsa\bav\bve\be \b f\bfi\bil\ble\ben\bna\bam\bme\be \b a\ban\bnd\bd \b d\bde\bef\bfa\bau\bul\blt\bt \b F\bFc\bcc\bc:\b: \b m\bma\bai\bil\blb\bbo\box\bx \b a\bat\bt \b o\bon\bnc\bce\be, U\bUs\bsi\bin\bng\bg \b H\bHo\boo\bok\bks\bs,
+ M\bMe\bes\bss\bsa\bag\bge\be \b M\bMa\bat\btc\bch\bhi\bin\bng\bg \b i\bin\bn \b H\bHo\boo\bok\bks\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ fcc-save-hook, S\bSp\bpe\bec\bci\bif\bfy\by \b d\bde\bef\bfa\bau\bul\blt\bt \b s\bsa\bav\bve\be \b f\bfi\bil\ble\ben\bna\bam\bme\be, S\bSp\bpe\bec\bci\bif\bfy\by \b d\bde\bef\bfa\bau\bul\blt\bt \b F\bFc\bcc\bc:\b:
+ m\bma\bai\bil\blb\bbo\box\bx \b w\bwh\bhe\ben\bn \b c\bco\bom\bmp\bpo\bos\bsi\bin\bng\bg, S\bSp\bpe\bec\bci\bif\bfy\by \b d\bde\bef\bfa\bau\bul\blt\bt \b s\bsa\bav\bve\be \b f\bfi\bil\ble\ben\bna\bam\bme\be \b a\ban\bnd\bd
+ d\bde\bef\bfa\bau\bul\blt\bt \b F\bFc\bcc\bc:\b: \b m\bma\bai\bil\blb\bbo\box\bx \b a\bat\bt \b o\bon\bnc\bce\be, U\bUs\bsi\bin\bng\bg \b H\bHo\boo\bok\bks\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn
+ C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ $fcc_attach , $\b$f\bfc\bcc\bc_\b_a\bat\btt\bta\bac\bch\bh
+ $fcc_clear , $\b$f\bfc\bcc\bc_\b_c\bcl\ble\bea\bar\br
+ <fetch-mail>, i\bin\bnd\bde\bex\bx
+ $file_charset , $\b$f\bfi\bil\ble\be_\b_c\bch\bha\bar\brs\bse\bet\bt
+ <filter-entry>, c\bco\bom\bmp\bpo\bos\bse\be
+ <first-entry>, M\bMo\bov\bvi\bin\bng\bg \b A\bAr\bro\bou\bun\bnd\bd \b i\bin\bn \b M\bMe\ben\bnu\bus\bs, g\bge\ben\bne\ber\bri\bic\bc
+ <flag-message>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ $folder, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b V\bVa\bar\bri\bia\bab\bbl\ble\bes\bs, D\bDe\bef\bfi\bin\bni\bin\bng\bg \b m\bma\bai\bil\blb\bbo\box\bxe\bes\bs \b w\bwh\bhi\bic\bch\bh \b r\bre\bec\bce\bei\biv\bve\be
+ m\bma\bai\bil\bl, M\bMa\bai\bil\blb\bbo\box\bx \b S\bSh\bho\bor\brt\btc\bcu\but\bts\bs, $\b$f\bfo\bol\bld\bde\ber\br
+
+ folder-hook, S\bSe\bet\btt\bti\bin\bng\bg \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs \b b\bba\bas\bse\bed\bd \b u\bup\bpo\bon\bn \b m\bma\bai\bil\blb\bbo\box\bx, S\bSp\bpa\bam\bm \b d\bde\bet\bte\bec\bct\bti\bio\bon\bn,
+ U\bUs\bsi\bin\bng\bg \b H\bHo\boo\bok\bks\bs, M\bMa\ban\bna\bag\bgi\bin\bng\bg \b m\bmu\bul\blt\bti\bip\bpl\ble\be \b I\bIM\bMA\bAP\bP/\b/P\bPO\bOP\bP/\b/N\bNN\bNT\bTP\bP \b a\bac\bcc\bco\bou\bun\bnt\bts\bs
+ (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b), C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ $folder_format , $\b$f\bfo\bol\bld\bde\ber\br_\b_f\bfo\bor\brm\bma\bat\bt
+ $followup_to, M\bMa\bai\bil\bli\bin\bng\bg \b l\bli\bis\bst\bts\bs, H\bHa\ban\bnd\bdl\bli\bin\bng\bg \b M\bMa\bai\bil\bli\bin\bng\bg \b L\bLi\bis\bst\bts\bs
+ $followup_to , $\b$f\bfo\bol\bll\blo\bow\bwu\bup\bp_\b_t\bto\bo
+ $force_buffy_check , $\b$f\bfo\bor\brc\bce\be_\b_b\bbu\buf\bff\bfy\by_\b_c\bch\bhe\bec\bck\bk
+ $force_list_reply , $\b$f\bfo\bor\brc\bce\be_\b_l\bli\bis\bst\bt_\b_r\bre\bep\bpl\bly\by
+ $force_name , $\b$f\bfo\bor\brc\bce\be_\b_n\bna\bam\bme\be
+ <forget-passphrase>, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs,
+ i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br, c\bco\bom\bmp\bpo\bos\bse\be
+
+ <forward>, S\bSe\ben\bnd\bdi\bin\bng\bg \b M\bMa\bai\bil\bl
+ <forward-char>, E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs, e\bed\bdi\bit\bto\bor\br
+ $forward_decode , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $forward_decrypt , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $forward_format , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ <forward-message>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br, a\bat\btt\bta\bac\bch\bh
+ $forward_quote , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ <forward-word>, E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs, e\bed\bdi\bit\bto\bor\br
+ $forward_decode , $\b$f\bfo\bor\brw\bwa\bar\brd\bd_\b_d\bde\bec\bco\bod\bde\be
+ $forward_decrypt , $\b$f\bfo\bor\brw\bwa\bar\brd\bd_\b_d\bde\bec\bcr\bry\byp\bpt\bt
+ $forward_edit , $\b$f\bfo\bor\brw\bwa\bar\brd\bd_\b_e\bed\bdi\bit\bt
+ $forward_format , $\b$f\bfo\bor\brw\bwa\bar\brd\bd_\b_f\bfo\bor\brm\bma\bat\bt
+ $forward_quote , $\b$f\bfo\bor\brw\bwa\bar\brd\bd_\b_q\bqu\buo\bot\bte\be
+ $from , $\b$f\bfr\bro\bom\bm
+
+G
+
+ $gecos_mask , $\b$g\bge\bec\bco\bos\bs_\b_m\bma\bas\bsk\bk
+ <group-reply>, S\bSe\ben\bnd\bdi\bin\bng\bg \b M\bMa\bai\bil\bl, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br, a\bat\btt\bta\bac\bch\bh
+
+H
+
+ <half-down>, g\bge\ben\bne\ber\bri\bic\bc, p\bpa\bag\bge\ber\br
+ <half-up>, g\bge\ben\bne\ber\bri\bic\bc, p\bpa\bag\bge\ber\br
+ $hdrs , $\b$h\bhd\bdr\brs\bs
+ hdr_order, D\bDe\bef\bfi\bin\bni\bin\bng\bg \b t\bth\bhe\be \b o\bor\brd\bde\ber\br \b o\bof\bf \b h\bhe\bea\bad\bde\ber\brs\bs \b w\bwh\bhe\ben\bn \b v\bvi\bie\bew\bwi\bin\bng\bg \b m\bme\bes\bss\bsa\bag\bge\bes\bs,
+ C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ $header , $\b$h\bhe\bea\bad\bde\ber\br
+ $header_cache , $\b$h\bhe\bea\bad\bde\ber\br_\b_c\bca\bac\bch\bhe\be
+ $header_cache_compress , $\b$h\bhe\bea\bad\bde\ber\br_\b_c\bca\bac\bch\bhe\be_\b_c\bco\bom\bmp\bpr\bre\bes\bss\bs
+ <help>, M\bMo\bov\bvi\bin\bng\bg \b A\bAr\bro\bou\bun\bnd\bd \b i\bin\bn \b M\bMe\ben\bnu\bus\bs, $\b$h\bhe\bel\blp\bp, g\bge\ben\bne\ber\bri\bic\bc, p\bpa\bag\bge\ber\br
+ $hidden_host , $\b$h\bhi\bid\bdd\bde\ben\bn_\b_h\bho\bos\bst\bt
+ $hide_limited , $\b$h\bhi\bid\bde\be_\b_l\bli\bim\bmi\bit\bte\bed\bd
+ $hide_missing , $\b$h\bhi\bid\bde\be_\b_m\bmi\bis\bss\bsi\bin\bng\bg
+ $hide_thread_subject , $\b$h\bhi\bid\bde\be_\b_t\bth\bhr\bre\bea\bad\bd_\b_s\bsu\bub\bbj\bje\bec\bct\bt
+ $hide_top_limited , $\b$h\bhi\bid\bde\be_\b_t\bto\bop\bp_\b_l\bli\bim\bmi\bit\bte\bed\bd
+ $hide_top_missing , $\b$h\bhi\bid\bde\be_\b_t\bto\bop\bp_\b_m\bmi\bis\bss\bsi\bin\bng\bg
+ $history , $\b$h\bhi\bis\bst\bto\bor\bry\by
+ <history-down>, E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs, e\bed\bdi\bit\bto\bor\br
+ <history-up>, E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs, e\bed\bdi\bit\bto\bor\br
+ $HOME, M\bMI\bIM\bME\bE \b T\bTy\byp\bpe\be \b c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b w\bwi\bit\bth\bh \b m\bmi\bim\bme\be.\b.t\bty\byp\bpe\bes\bs, M\bMI\bIM\bME\bE \b V\bVi\bie\bew\bwe\ber\br
+ c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b w\bwi\bit\bth\bh \b m\bma\bai\bil\blc\bca\bap\bp
+
+ $honor_followup_to, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, H\bHa\ban\bnd\bdl\bli\bin\bng\bg \b M\bMa\bai\bil\bli\bin\bng\bg \b L\bLi\bis\bst\bts\bs
+ $honor_followup_to , $\b$h\bho\bon\bno\bor\br_\b_f\bfo\bol\bll\blo\bow\bwu\bup\bp_\b_t\bto\bo
+ $HOSTNAME, E\bEn\bnv\bvi\bir\bro\bon\bnm\bme\ben\bnt\bt \b V\bVa\bar\bri\bia\bab\bbl\ble\bes\bs
+ $hostname , $\b$h\bho\bos\bst\btn\bna\bam\bme\be
+
+I
+
+ iconv-hook, D\bDe\bef\bfi\bin\bni\bin\bng\bg \b a\bal\bli\bia\bas\bse\bes\bs \b f\bfo\bor\br \b c\bch\bha\bar\bra\bac\bct\bte\ber\br \b s\bse\bet\bts\bs
+ ignore, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, I\bIg\bgn\bno\bor\bri\bin\bng\bg \b (\b(w\bwe\bee\bed\bdi\bin\bng\bg)\b) \b u\bun\bnw\bwa\ban\bnt\bte\bed\bd \b m\bme\bes\bss\bsa\bag\bge\be
+ h\bhe\bea\bad\bde\ber\brs\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ $ignore_list_reply_to , $\b$i\big\bgn\bno\bor\bre\be_\b_l\bli\bis\bst\bt_\b_r\bre\bep\bpl\bly\by_\b_t\bto\bo
+ $imap_authenticators, A\bAu\but\bth\bhe\ben\bnt\bti\bic\bca\bat\bti\bio\bon\bn
+ $imap_home_namespace, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b V\bVa\bar\bri\bia\bab\bbl\ble\bes\bs
+ $imap_list_subscribed, I\bIM\bMA\bAP\bP \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
+ $imap_mail_check, M\bMa\ban\bnu\bua\bal\bl \b C\bCo\bon\bnv\bve\ben\bnt\bti\bio\bon\bns\bs, C\bCo\bon\bnd\bdi\bit\bti\bio\bon\bna\bal\bl \b p\bpa\bar\brt\bts\bs, I\bIM\bMA\bAP\bP \b S\bSu\bup\bpp\bpo\bor\brt\bt
+ (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
+
+ $imap_pass, A\bAu\but\bth\bhe\ben\bnt\bti\bic\bca\bat\bti\bio\bon\bn
+ $imap_user, A\bAu\but\bth\bhe\ben\bnt\bti\bic\bca\bat\bti\bio\bon\bn
+ $imap_authenticators , $\b$i\bim\bma\bap\bp_\b_a\bau\but\bth\bhe\ben\bnt\bti\bic\bca\bat\bto\bor\brs\bs
+ $imap_check_subscribed , $\b$i\bim\bma\bap\bp_\b_c\bch\bhe\bec\bck\bk_\b_s\bsu\bub\bbs\bsc\bcr\bri\bib\bbe\bed\bd
+ $imap_delim_chars , $\b$i\bim\bma\bap\bp_\b_d\bde\bel\bli\bim\bm_\b_c\bch\bha\bar\brs\bs
+ $imap_headers , $\b$i\bim\bma\bap\bp_\b_h\bhe\bea\bad\bde\ber\brs\bs
+ $imap_home_namespace , $\b$i\bim\bma\bap\bp_\b_h\bho\bom\bme\be_\b_n\bna\bam\bme\bes\bsp\bpa\bac\bce\be
+ $imap_keepalive , $\b$i\bim\bma\bap\bp_\b_k\bke\bee\bep\bpa\bal\bli\biv\bve\be
+ $imap_list_subscribed , $\b$i\bim\bma\bap\bp_\b_l\bli\bis\bst\bt_\b_s\bsu\bub\bbs\bsc\bcr\bri\bib\bbe\bed\bd
+ $imap_login , $\b$i\bim\bma\bap\bp_\b_l\blo\bog\bgi\bin\bn
+ $imap_mail_check , $\b$i\bim\bma\bap\bp_\b_m\bma\bai\bil\bl_\b_c\bch\bhe\bec\bck\bk
+ $imap_pass , $\b$i\bim\bma\bap\bp_\b_p\bpa\bas\bss\bs
+ $imap_passive , $\b$i\bim\bma\bap\bp_\b_p\bpa\bas\bss\bsi\biv\bve\be
+ $imap_peek , $\b$i\bim\bma\bap\bp_\b_p\bpe\bee\bek\bk
+ $imap_reconnect , $\b$i\bim\bma\bap\bp_\b_r\bre\bec\bco\bon\bnn\bne\bec\bct\bt
+ $imap_servernoise , $\b$i\bim\bma\bap\bp_\b_s\bse\ber\brv\bve\ber\brn\bno\boi\bis\bse\be
+ $imap_user , $\b$i\bim\bma\bap\bp_\b_u\bus\bse\ber\br
+ $implicit_autoview , $\b$i\bim\bmp\bpl\bli\bic\bci\bit\bt_\b_a\bau\but\bto\bov\bvi\bie\bew\bw
+ $include , $\b$i\bin\bnc\bcl\blu\bud\bde\be
+ $include_onlyfirst , $\b$i\bin\bnc\bcl\blu\bud\bde\be_\b_o\bon\bnl\bly\byf\bfi\bir\brs\bst\bt
+ $indent_string , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $indent_string , $\b$i\bin\bnd\bde\ben\bnt\bt_\b_s\bst\btr\bri\bin\bng\bg
+ $index_format, T\bTh\bhr\bre\bea\bad\bde\bed\bd \b M\bMo\bod\bde\be, S\bSp\bpa\bam\bm \b d\bde\bet\bte\bec\bct\bti\bio\bon\bn, H\bHa\ban\bnd\bdl\bli\bin\bng\bg \b M\bMa\bai\bil\bli\bin\bng\bg \b L\bLi\bis\bst\bts\bs,
+ C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+
+ $index_format , $\b$i\bin\bnd\bde\bex\bx_\b_f\bfo\bor\brm\bma\bat\bt
+ <ispell>, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs, $\b$i\bis\bsp\bpe\bel\bll\bl, c\bco\bom\bmp\bpo\bos\bse\be
+
+J
+
+ <jump>, g\bge\ben\bne\ber\bri\bic\bc
+
+K
+
+ $keep_flagged , $\b$k\bke\bee\bep\bp_\b_f\bfl\bla\bag\bgg\bge\bed\bd
+ <kill-eol>, E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs, e\bed\bdi\bit\bto\bor\br
+ <kill-eow>, E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs, e\bed\bdi\bit\bto\bor\br
+ <kill-line>, E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs, e\bed\bdi\bit\bto\bor\br
+ <kill-word>, E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs, e\bed\bdi\bit\bto\bor\br
+
+L
+
+ <last-entry>, M\bMo\bov\bvi\bin\bng\bg \b A\bAr\bro\bou\bun\bnd\bd \b i\bin\bn \b M\bMe\ben\bnu\bus\bs, g\bge\ben\bne\ber\bri\bic\bc
+ <limit>, i\bin\bnd\bde\bex\bx
+ <list-reply>, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, S\bSe\ben\bnd\bdi\bin\bng\bg \b M\bMa\bai\bil\bl, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br,
+ a\bat\btt\bta\bac\bch\bh
+
+ lists, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, M\bMa\bai\bil\bli\bin\bng\bg \b l\bli\bis\bst\bts\bs, H\bHa\ban\bnd\bdl\bli\bin\bng\bg \b M\bMa\bai\bil\bli\bin\bng\bg \b L\bLi\bis\bst\bts\bs,
+ C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ $locale, C\bCh\bha\ban\bng\bge\be \b s\bse\bet\btt\bti\bin\bng\bgs\bs \b b\bba\bas\bse\bed\bd \b u\bup\bpo\bon\bn \b m\bme\bes\bss\bsa\bag\bge\be \b r\bre\bec\bci\bip\bpi\bie\ben\bnt\bts\bs, $\b$l\blo\boc\bca\bal\ble\be
+
+M
+
+ macro, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, K\bKe\bey\byb\bbo\boa\bar\brd\bd \b m\bma\bac\bcr\bro\bos\bs, A\bAd\bdd\bdi\bin\bng\bg \b k\bke\bey\by \b s\bse\beq\bqu\bue\ben\bnc\bce\bes\bs
+ t\bto\bo \b t\bth\bhe\be \b k\bke\bey\byb\bbo\boa\bar\brd\bd \b b\bbu\buf\bff\bfe\ber\br, U\bUs\bsi\bin\bng\bg \b T\bTa\bag\bgs\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ <mail>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br, q\bqu\bue\ber\bry\by
+ <mail-key>, S\bSe\ben\bnd\bdi\bin\bng\bg \b M\bMa\bai\bil\bl, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ mailboxes, D\bDe\bef\bfi\bin\bni\bin\bng\bg \b m\bma\bai\bil\blb\bbo\box\bxe\bes\bs \b w\bwh\bhi\bic\bch\bh \b r\bre\bec\bce\bei\biv\bve\be \b m\bma\bai\bil\bl, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn
+ C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ $mailcap_path, m\bma\bai\bil\blc\bca\bap\bp
+ $mailcap_sanitize, S\bSe\bec\bcu\bur\bre\be \b u\bus\bse\be \b o\bof\bf \b m\bma\bai\bil\blc\bca\bap\bp, m\bma\bai\bil\blc\bca\bap\bp
+ $mailcap_path , $\b$m\bma\bai\bil\blc\bca\bap\bp_\b_p\bpa\bat\bth\bh
+ $mailcap_sanitize , $\b$m\bma\bai\bil\blc\bca\bap\bp_\b_s\bsa\ban\bni\bit\bti\biz\bze\be
+ $maildir_header_cache_verify , $\b$m\bma\bai\bil\bld\bdi\bir\br_\b_h\bhe\bea\bad\bde\ber\br_\b_c\bca\bac\bch\bhe\be_\b_v\bve\ber\bri\bif\bfy\by
+ $maildir_trash , $\b$m\bma\bai\bil\bld\bdi\bir\br_\b_t\btr\bra\bas\bsh\bh
+ $mail_check , $\b$m\bma\bai\bil\bl_\b_c\bch\bhe\bec\bck\bk
+ <mark-as-new>, p\bpa\bag\bge\ber\br
+ $markers , $\b$m\bma\bar\brk\bke\ber\brs\bs
+ $mark_old , $\b$m\bma\bar\brk\bk_\b_o\bol\bld\bd
+ $mask , $\b$m\bma\bas\bsk\bk
+ $max_display_recips , $\b$m\bma\bax\bx_\b_d\bdi\bis\bsp\bpl\bla\bay\by_\b_r\bre\bec\bci\bip\bps\bs
+ $max_line_length , $\b$m\bma\bax\bx_\b_l\bli\bin\bne\be_\b_l\ble\ben\bng\bgt\bth\bh
+ $mbox, M\bMa\bai\bil\blb\bbo\box\bx \b S\bSh\bho\bor\brt\btc\bcu\but\bts\bs, $\b$m\bmb\bbo\box\bx
+ mbox-hook, U\bUs\bsi\bin\bng\bg \b M\bMu\bul\blt\bti\bip\bpl\ble\be \b s\bsp\bpo\boo\bol\bl \b m\bma\bai\bil\blb\bbo\box\bxe\bes\bs, U\bUs\bsi\bin\bng\bg \b H\bHo\boo\bok\bks\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn
+ C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ $mbox_type, M\bMa\bai\bil\blb\bbo\box\bx \b F\bFo\bor\brm\bma\bat\bts\bs, A\bAp\bpp\bpe\ben\bnd\bd \b a\ba \b m\bme\bes\bss\bsa\bag\bge\be \b t\bto\bo \b a\ba \b c\bco\bom\bmp\bpr\bre\bes\bss\bse\bed\bd \b m\bma\bai\bil\blb\bbo\box\bx
+ $mbox_type , $\b$m\bmb\bbo\box\bx_\b_t\bty\byp\bpe\be
+ $menu_context , $\b$m\bme\ben\bnu\bu_\b_c\bco\bon\bnt\bte\bex\bxt\bt
+ $menu_move_off , $\b$m\bme\ben\bnu\bu_\b_m\bmo\bov\bve\be_\b_o\bof\bff\bf
+ $menu_scroll , $\b$m\bme\ben\bnu\bu_\b_s\bsc\bcr\bro\bol\bll\bl
+ $message_format , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ message-hook, C\bCh\bha\ban\bng\bge\be \b s\bse\bet\btt\bti\bin\bng\bgs\bs \b b\bbe\bef\bfo\bor\bre\be \b f\bfo\bor\brm\bma\bat\btt\bti\bin\bng\bg \b a\ba \b m\bme\bes\bss\bsa\bag\bge\be, U\bUs\bsi\bin\bng\bg
+ H\bHo\boo\bok\bks\bs, M\bMe\bes\bss\bsa\bag\bge\be \b M\bMa\bat\btc\bch\bhi\bin\bng\bg \b i\bin\bn \b H\bHo\boo\bok\bks\bs, M\bMI\bIM\bME\bE \b A\bAu\but\bto\bov\bvi\bie\bew\bw, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn
+ C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ $message_format , $\b$m\bme\bes\bss\bsa\bag\bge\be_\b_f\bfo\bor\brm\bma\bat\bt
+ $meta_key , $\b$m\bme\bet\bta\ba_\b_k\bke\bey\by
+ $metoo , $\b$m\bme\bet\bto\boo\bo
+ $mh_purge , $\b$m\bmh\bh_\b_p\bpu\bur\brg\bge\be
+ $mh_seq_flagged , $\b$m\bmh\bh_\b_s\bse\beq\bq_\b_f\bfl\bla\bag\bgg\bge\bed\bd
+ $mh_seq_replied , $\b$m\bmh\bh_\b_s\bse\beq\bq_\b_r\bre\bep\bpl\bli\bie\bed\bd
+ $mh_seq_unseen , $\b$m\bmh\bh_\b_s\bse\beq\bq_\b_u\bun\bns\bse\bee\ben\bn
+ <middle-page>, g\bge\ben\bne\ber\bri\bic\bc
+ $mime_forward , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $mime_forward , $\b$m\bmi\bim\bme\be_\b_f\bfo\bor\brw\bwa\bar\brd\bd
+ $mime_forward_decode , $\b$m\bmi\bim\bme\be_\b_f\bfo\bor\brw\bwa\bar\brd\bd_\b_d\bde\bec\bco\bod\bde\be
+ $mime_forward_rest , $\b$m\bmi\bim\bme\be_\b_f\bfo\bor\brw\bwa\bar\brd\bd_\b_r\bre\bes\bst\bt
+ mime_lookup, M\bMI\bIM\bME\bE \b L\bLo\boo\bok\bku\bup\bp, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ $mix_entry_format, S\bSe\ben\bnd\bdi\bin\bng\bg \b a\ban\bno\bon\bny\bym\bmo\bou\bus\bs \b m\bme\bes\bss\bsa\bag\bge\bes\bs \b v\bvi\bia\ba \b m\bmi\bix\bxm\bma\bas\bst\bte\ber\br
+ $mixmaster , $\b$m\bmi\bix\bxm\bma\bas\bst\bte\ber\br
+ $mix_entry_format , $\b$m\bmi\bix\bx_\b_e\ben\bnt\btr\bry\by_\b_f\bfo\bor\brm\bma\bat\bt
+ mono, U\bUs\bsi\bin\bng\bg \b c\bco\bol\blo\bor\br \b a\ban\bnd\bd \b m\bmo\bon\bno\bo \b v\bvi\bid\bde\beo\bo \b a\bat\btt\btr\bri\bib\bbu\but\bte\bes\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ $move , $\b$m\bmo\bov\bve\be
+ $msgid_format, M\bMe\bes\bss\bsa\bag\bge\be-\b-I\bID\bD:\b: \b h\bhe\bea\bad\bde\ber\brs\bs
+ $msgid_format , $\b$m\bms\bsg\bgi\bid\bd_\b_f\bfo\bor\brm\bma\bat\bt
+ $muttng_bindir , $\b$m\bmu\but\btt\btn\bng\bg_\b_b\bbi\bin\bnd\bdi\bir\br
+ $muttng_docdir , $\b$m\bmu\but\btt\btn\bng\bg_\b_d\bdo\boc\bcd\bdi\bir\br
+ $muttng_folder_name , $\b$m\bmu\but\btt\btn\bng\bg_\b_f\bfo\bol\bld\bde\ber\br_\b_n\bna\bam\bme\be
+ $muttng_folder_path , $\b$m\bmu\but\btt\btn\bng\bg_\b_f\bfo\bol\bld\bde\ber\br_\b_p\bpa\bat\bth\bh
+ $muttng_hcache_backend , $\b$m\bmu\but\btt\btn\bng\bg_\b_h\bhc\bca\bac\bch\bhe\be_\b_b\bba\bac\bck\bke\ben\bnd\bd
+ $muttng_pwd , $\b$m\bmu\but\btt\btn\bng\bg_\b_p\bpw\bwd\bd
+ $muttng_revision , $\b$m\bmu\but\btt\btn\bng\bg_\b_r\bre\bev\bvi\bis\bsi\bio\bon\bn
+ $muttng_sysconfdir , $\b$m\bmu\but\btt\btn\bng\bg_\b_s\bsy\bys\bsc\bco\bon\bnf\bfd\bdi\bir\br
+ $muttng_version , $\b$m\bmu\but\btt\btn\bng\bg_\b_v\bve\ber\brs\bsi\bio\bon\bn
+ my_hdr, U\bUs\bse\ber\br \b d\bde\bef\bfi\bin\bne\bed\bd \b h\bhe\bea\bad\bde\ber\brs\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+N
+
+ $narrow_tree , $\b$n\bna\bar\brr\bro\bow\bw_\b_t\btr\bre\bee\be
+ $net_inc , $\b$n\bne\bet\bt_\b_i\bin\bnc\bc
+ <new-mime>, c\bco\bom\bmp\bpo\bos\bse\be
+ <next-entry>, M\bMo\bov\bvi\bin\bng\bg \b A\bAr\bro\bou\bun\bnd\bd \b i\bin\bn \b M\bMe\ben\bnu\bus\bs, g\bge\ben\bne\ber\bri\bic\bc, p\bpa\bag\bge\ber\br
+ <next-line>, g\bge\ben\bne\ber\bri\bic\bc, p\bpa\bag\bge\ber\br
+ <next-new>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ <next-new-then-unread>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ <next-page>, g\bge\ben\bne\ber\bri\bic\bc, p\bpa\bag\bge\ber\br
+ <next-subthread>, T\bTh\bhr\bre\bea\bad\bde\bed\bd \b M\bMo\bod\bde\be, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ <next-thread>, T\bTh\bhr\bre\bea\bad\bde\bed\bd \b M\bMo\bod\bde\be, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ <next-undeleted>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ <next-unread>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ $nntp_ask_followup_to , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $nntp_ask_x_comment_to , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $nntp_cache_dir , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $nntp_catchup , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $nntp_followup_to_poster , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $nntp_group_index_format , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $nntp_host , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $nntp_inews , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $nntp_mail_check , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $nntp_mime_subject , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $nntp_newsrc, N\bNN\bNT\bTP\bP \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b), C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $nntp_post_moderated , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $nntp_save_unsubscribed , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $nntp_show_new_news , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $nntp_show_only_unread , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $nntp_x_comment_to , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $NNTPSERVER, N\bNN\bNT\bTP\bP \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
+ $nntp_ask_followup_to , $\b$n\bnn\bnt\btp\bp_\b_a\bas\bsk\bk_\b_f\bfo\bol\bll\blo\bow\bwu\bup\bp_\b_t\bto\bo
+ $nntp_ask_x_comment_to , $\b$n\bnn\bnt\btp\bp_\b_a\bas\bsk\bk_\b_x\bx_\b_c\bco\bom\bmm\bme\ben\bnt\bt_\b_t\bto\bo
+ $nntp_cache_dir , $\b$n\bnn\bnt\btp\bp_\b_c\bca\bac\bch\bhe\be_\b_d\bdi\bir\br
+ $nntp_catchup , $\b$n\bnn\bnt\btp\bp_\b_c\bca\bat\btc\bch\bhu\bup\bp
+ $nntp_context , $\b$n\bnn\bnt\btp\bp_\b_c\bco\bon\bnt\bte\bex\bxt\bt
+ $nntp_followup_to_poster , $\b$n\bnn\bnt\btp\bp_\b_f\bfo\bol\bll\blo\bow\bwu\bup\bp_\b_t\bto\bo_\b_p\bpo\bos\bst\bte\ber\br
+ $nntp_group_index_format , $\b$n\bnn\bnt\btp\bp_\b_g\bgr\bro\bou\bup\bp_\b_i\bin\bnd\bde\bex\bx_\b_f\bfo\bor\brm\bma\bat\bt
+ $nntp_host , $\b$n\bnn\bnt\btp\bp_\b_h\bho\bos\bst\bt
+ $nntp_inews , $\b$n\bnn\bnt\btp\bp_\b_i\bin\bne\bew\bws\bs
+ $nntp_load_description , $\b$n\bnn\bnt\btp\bp_\b_l\blo\boa\bad\bd_\b_d\bde\bes\bsc\bcr\bri\bip\bpt\bti\bio\bon\bn
+ $nntp_mail_check , $\b$n\bnn\bnt\btp\bp_\b_m\bma\bai\bil\bl_\b_c\bch\bhe\bec\bck\bk
+ $nntp_mime_subject , $\b$n\bnn\bnt\btp\bp_\b_m\bmi\bim\bme\be_\b_s\bsu\bub\bbj\bje\bec\bct\bt
+ $nntp_newsrc , $\b$n\bnn\bnt\btp\bp_\b_n\bne\bew\bws\bsr\brc\bc
+ $nntp_pass , $\b$n\bnn\bnt\btp\bp_\b_p\bpa\bas\bss\bs
+ $nntp_post_moderated , $\b$n\bnn\bnt\btp\bp_\b_p\bpo\bos\bst\bt_\b_m\bmo\bod\bde\ber\bra\bat\bte\bed\bd
+ $nntp_reconnect , $\b$n\bnn\bnt\btp\bp_\b_r\bre\bec\bco\bon\bnn\bne\bec\bct\bt
+ $nntp_save_unsubscribed , $\b$n\bnn\bnt\btp\bp_\b_s\bsa\bav\bve\be_\b_u\bun\bns\bsu\bub\bbs\bsc\bcr\bri\bib\bbe\bed\bd
+ $nntp_show_new_news , $\b$n\bnn\bnt\btp\bp_\b_s\bsh\bho\bow\bw_\b_n\bne\bew\bw_\b_n\bne\bew\bws\bs
+ $nntp_show_only_unread , $\b$n\bnn\bnt\btp\bp_\b_s\bsh\bho\bow\bw_\b_o\bon\bnl\bly\by_\b_u\bun\bnr\bre\bea\bad\bd
+ $nntp_user , $\b$n\bnn\bnt\btp\bp_\b_u\bus\bse\ber\br
+ $nntp_x_comment_to , $\b$n\bnn\bnt\btp\bp_\b_x\bx_\b_c\bco\bom\bmm\bme\ben\bnt\bt_\b_t\bto\bo
+ nospam, S\bSp\bpa\bam\bm \b d\bde\bet\bte\bec\bct\bti\bio\bon\bn, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+O
+
+ open-hook, C\bCo\bom\bmp\bpr\bre\bes\bss\bse\bed\bd \b f\bfo\bol\bld\bde\ber\brs\bs \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b), O\bOp\bpe\ben\bn \b a\ba \b c\bco\bom\bmp\bpr\bre\bes\bss\bse\bed\bd
+ m\bma\bai\bil\blb\bbo\box\bx \b f\bfo\bor\br \b r\bre\bea\bad\bdi\bin\bng\bg, W\bWr\bri\bit\bte\be \b a\ba \b c\bco\bom\bmp\bpr\bre\bes\bss\bse\bed\bd \b m\bma\bai\bil\blb\bbo\box\bx, A\bAp\bpp\bpe\ben\bnd\bd \b a\ba
+ m\bme\bes\bss\bsa\bag\bge\be \b t\bto\bo \b a\ba \b c\bco\bom\bmp\bpr\bre\bes\bss\bse\bed\bd \b m\bma\bai\bil\blb\bbo\box\bx, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ $operating_system , $\b$o\bop\bpe\ber\bra\bat\bti\bin\bng\bg_\b_s\bsy\bys\bst\bte\bem\bm
+
+P
+
+ <page-down>, M\bMo\bov\bvi\bin\bng\bg \b A\bAr\bro\bou\bun\bnd\bd \b i\bin\bn \b M\bMe\ben\bnu\bus\bs
+ <page-up>, M\bMo\bov\bvi\bin\bng\bg \b A\bAr\bro\bou\bun\bnd\bd \b i\bin\bn \b M\bMe\ben\bnu\bus\bs
+ $pager , $\b$p\bpa\bag\bge\ber\br
+ $pager_index_lines, C\bCo\bon\bnd\bdi\bit\bti\bio\bon\bna\bal\bl \b p\bpa\bar\brt\bts\bs
+ $pager_context , $\b$p\bpa\bag\bge\ber\br_\b_c\bco\bon\bnt\bte\bex\bxt\bt
+ $pager_format , $\b$p\bpa\bag\bge\ber\br_\b_f\bfo\bor\brm\bma\bat\bt
+ $pager_index_lines , $\b$p\bpa\bag\bge\ber\br_\b_i\bin\bnd\bde\bex\bx_\b_l\bli\bin\bne\bes\bs
+ $pager_stop , $\b$p\bpa\bag\bge\ber\br_\b_s\bst\bto\bop\bp
+ <parent-message>, T\bTh\bhr\bre\bea\bad\bde\bed\bd \b M\bMo\bod\bde\be, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ pattern-hook, S\bSp\bpe\bec\bci\bif\bfy\by \b d\bde\bef\bfa\bau\bul\blt\bt \b s\bsa\bav\bve\be \b f\bfi\bil\ble\ben\bna\bam\bme\be, S\bSp\bpe\bec\bci\bif\bfy\by \b d\bde\bef\bfa\bau\bul\blt\bt \b F\bFc\bcc\bc:\b:
+ m\bma\bai\bil\blb\bbo\box\bx \b w\bwh\bhe\ben\bn \b c\bco\bom\bmp\bpo\bos\bsi\bin\bng\bg, C\bCh\bha\ban\bng\bge\be \b s\bse\bet\btt\bti\bin\bng\bgs\bs \b b\bba\bas\bse\bed\bd \b u\bup\bpo\bon\bn \b m\bme\bes\bss\bsa\bag\bge\be
+ r\bre\bec\bci\bip\bpi\bie\ben\bnt\bts\bs, C\bCh\bha\ban\bng\bge\be \b s\bse\bet\btt\bti\bin\bng\bgs\bs \b b\bbe\bef\bfo\bor\bre\be \b f\bfo\bor\brm\bma\bat\btt\bti\bin\bng\bg \b a\ba \b m\bme\bes\bss\bsa\bag\bge\be
+
+ $pgp_autoinline , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $pgp_entry_format, U\bUs\bsi\bin\bng\bg \b M\bMu\but\btt\bt-\b-n\bng\bg \b w\bwi\bit\bth\bh \b P\bPG\bGP\bP
+ <pgp-menu>, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs, c\bco\bom\bmp\bpo\bos\bse\be
+ $pgp_replyinline , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $pgp_sign_as, U\bUs\bsi\bin\bng\bg \b M\bMu\but\btt\bt-\b-n\bng\bg \b w\bwi\bit\bth\bh \b P\bPG\bGP\bP
+ $pgp_autoinline , $\b$p\bpg\bgp\bp_\b_a\bau\but\bto\boi\bin\bnl\bli\bin\bne\be
+ $pgp_auto_decode , $\b$p\bpg\bgp\bp_\b_a\bau\but\bto\bo_\b_d\bde\bec\bco\bod\bde\be
+ $pgp_check_exit , $\b$p\bpg\bgp\bp_\b_c\bch\bhe\bec\bck\bk_\b_e\bex\bxi\bit\bt
+ $pgp_clearsign_command , $\b$p\bpg\bgp\bp_\b_c\bcl\ble\bea\bar\brs\bsi\big\bgn\bn_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $pgp_decode_command , $\b$p\bpg\bgp\bp_\b_d\bde\bec\bco\bod\bde\be_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $pgp_decrypt_command , $\b$p\bpg\bgp\bp_\b_d\bde\bec\bcr\bry\byp\bpt\bt_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $pgp_encrypt_only_command , $\b$p\bpg\bgp\bp_\b_e\ben\bnc\bcr\bry\byp\bpt\bt_\b_o\bon\bnl\bly\by_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $pgp_encrypt_sign_command , $\b$p\bpg\bgp\bp_\b_e\ben\bnc\bcr\bry\byp\bpt\bt_\b_s\bsi\big\bgn\bn_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $pgp_entry_format , $\b$p\bpg\bgp\bp_\b_e\ben\bnt\btr\bry\by_\b_f\bfo\bor\brm\bma\bat\bt
+ $pgp_export_command , $\b$p\bpg\bgp\bp_\b_e\bex\bxp\bpo\bor\brt\bt_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $pgp_getkeys_command , $\b$p\bpg\bgp\bp_\b_g\bge\bet\btk\bke\bey\bys\bs_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $pgp_good_sign , $\b$p\bpg\bgp\bp_\b_g\bgo\boo\bod\bd_\b_s\bsi\big\bgn\bn
+ $pgp_ignore_subkeys , $\b$p\bpg\bgp\bp_\b_i\big\bgn\bno\bor\bre\be_\b_s\bsu\bub\bbk\bke\bey\bys\bs
+ $pgp_import_command , $\b$p\bpg\bgp\bp_\b_i\bim\bmp\bpo\bor\brt\bt_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $pgp_list_pubring_command , $\b$p\bpg\bgp\bp_\b_l\bli\bis\bst\bt_\b_p\bpu\bub\bbr\bri\bin\bng\bg_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $pgp_list_secring_command , $\b$p\bpg\bgp\bp_\b_l\bli\bis\bst\bt_\b_s\bse\bec\bcr\bri\bin\bng\bg_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $pgp_long_ids , $\b$p\bpg\bgp\bp_\b_l\blo\bon\bng\bg_\b_i\bid\bds\bs
+ $pgp_mime_auto , $\b$p\bpg\bgp\bp_\b_m\bmi\bim\bme\be_\b_a\bau\but\bto\bo
+ $pgp_replyinline , $\b$p\bpg\bgp\bp_\b_r\bre\bep\bpl\bly\byi\bin\bnl\bli\bin\bne\be
+ $pgp_retainable_sigs , $\b$p\bpg\bgp\bp_\b_r\bre\bet\bta\bai\bin\bna\bab\bbl\ble\be_\b_s\bsi\big\bgs\bs
+ $pgp_show_unusable , $\b$p\bpg\bgp\bp_\b_s\bsh\bho\bow\bw_\b_u\bun\bnu\bus\bsa\bab\bbl\ble\be
+ $pgp_sign_as , $\b$p\bpg\bgp\bp_\b_s\bsi\big\bgn\bn_\b_a\bas\bs
+ $pgp_sign_command , $\b$p\bpg\bgp\bp_\b_s\bsi\big\bgn\bn_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $pgp_sort_keys , $\b$p\bpg\bgp\bp_\b_s\bso\bor\brt\bt_\b_k\bke\bey\bys\bs
+ $pgp_strict_enc , $\b$p\bpg\bgp\bp_\b_s\bst\btr\bri\bic\bct\bt_\b_e\ben\bnc\bc
+ $pgp_timeout , $\b$p\bpg\bgp\bp_\b_t\bti\bim\bme\beo\bou\but\bt
+ $pgp_use_gpg_agent , $\b$p\bpg\bgp\bp_\b_u\bus\bse\be_\b_g\bgp\bpg\bg_\b_a\bag\bge\ben\bnt\bt
+ $pgp_verify_command , $\b$p\bpg\bgp\bp_\b_v\bve\ber\bri\bif\bfy\by_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $pgp_verify_key_command , $\b$p\bpg\bgp\bp_\b_v\bve\ber\bri\bif\bfy\by_\b_k\bke\bey\by_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $pipe_decode, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs
+ <pipe-entry>, a\bat\btt\bta\bac\bch\bh, c\bco\bom\bmp\bpo\bos\bse\be
+ <pipe-message>, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ $pipe_split, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs
+ $pipe_decode , $\b$p\bpi\bip\bpe\be_\b_d\bde\bec\bco\bod\bde\be
+ $pipe_sep , $\b$p\bpi\bip\bpe\be_\b_s\bse\bep\bp
+ $pipe_split , $\b$p\bpi\bip\bpe\be_\b_s\bsp\bpl\bli\bit\bt
+ $pop_mail_check, P\bPO\bOP\bP3\b3 \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b), C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $pop_authenticators , $\b$p\bpo\bop\bp_\b_a\bau\but\bth\bhe\ben\bnt\bti\bic\bca\bat\bto\bor\brs\bs
+ $pop_auth_try_all , $\b$p\bpo\bop\bp_\b_a\bau\but\bth\bh_\b_t\btr\bry\by_\b_a\bal\bll\bl
+ $pop_delete , $\b$p\bpo\bop\bp_\b_d\bde\bel\ble\bet\bte\be
+ $pop_host , $\b$p\bpo\bop\bp_\b_h\bho\bos\bst\bt
+ $pop_last , $\b$p\bpo\bop\bp_\b_l\bla\bas\bst\bt
+ $pop_mail_check , $\b$p\bpo\bop\bp_\b_m\bma\bai\bil\bl_\b_c\bch\bhe\bec\bck\bk
+ $pop_pass , $\b$p\bpo\bop\bp_\b_p\bpa\bas\bss\bs
+ $pop_reconnect , $\b$p\bpo\bop\bp_\b_r\bre\bec\bco\bon\bnn\bne\bec\bct\bt
+ $pop_user , $\b$p\bpo\bop\bp_\b_u\bus\bse\ber\br
+ $post_indent_string , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $postpone, P\bPo\bos\bst\btp\bpo\bon\bni\bin\bng\bg \b M\bMa\bai\bil\bl, $\b$p\bpo\bos\bst\btp\bpo\bon\bne\be
+ <postpone-message>, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs, c\bco\bom\bmp\bpo\bos\bse\be
+ $postponed, P\bPo\bos\bst\btp\bpo\bon\bni\bin\bng\bg \b M\bMa\bai\bil\bl, $\b$p\bpo\bos\bst\btp\bpo\bon\bne\bed\bd
+ $post_indent_string , $\b$p\bpo\bos\bst\bt_\b_i\bin\bnd\bde\ben\bnt\bt_\b_s\bst\btr\bri\bin\bng\bg
+ $preconnect , $\b$p\bpr\bre\bec\bco\bon\bnn\bne\bec\bct\bt
+ <previous-entry>, M\bMo\bov\bvi\bin\bng\bg \b A\bAr\bro\bou\bun\bnd\bd \b i\bin\bn \b M\bMe\ben\bnu\bus\bs, g\bge\ben\bne\ber\bri\bic\bc, p\bpa\bag\bge\ber\br
+ <previous-line>, g\bge\ben\bne\ber\bri\bic\bc, p\bpa\bag\bge\ber\br
+ <previous-new>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ <previous-new-then-unread>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ <previous-page>, g\bge\ben\bne\ber\bri\bic\bc, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ <previous-subthread>, T\bTh\bhr\bre\bea\bad\bde\bed\bd \b M\bMo\bod\bde\be, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ <previous-thread>, T\bTh\bhr\bre\bea\bad\bde\bed\bd \b M\bMo\bod\bde\be, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ <previous-undeleted>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ <previous-unread>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ $print , $\b$p\bpr\bri\bin\bnt\bt
+ $print_command , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ <print-entry>, a\bat\btt\bta\bac\bch\bh, c\bco\bom\bmp\bpo\bos\bse\be
+ <print-message>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ $print_command , $\b$p\bpr\bri\bin\bnt\bt_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $print_decode , $\b$p\bpr\bri\bin\bnt\bt_\b_d\bde\bec\bco\bod\bde\be
+ $print_split , $\b$p\bpr\bri\bin\bnt\bt_\b_s\bsp\bpl\bli\bit\bt
+ $prompt_after , $\b$p\bpr\bro\bom\bmp\bpt\bt_\b_a\baf\bft\bte\ber\br
+ push, A\bAd\bdd\bdi\bin\bng\bg \b k\bke\bey\by \b s\bse\beq\bqu\bue\ben\bnc\bce\bes\bs \b t\bto\bo \b t\bth\bhe\be \b k\bke\bey\byb\bbo\boa\bar\brd\bd \b b\bbu\buf\bff\bfe\ber\br, U\bUs\bsi\bin\bng\bg \b T\bTa\bag\bgs\bs,
+ C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+Q
+
+ <query>, i\bin\bnd\bde\bex\bx, q\bqu\bue\ber\bry\by
+ <query-append>, q\bqu\bue\ber\bry\by
+ $query_command, E\bEx\bxt\bte\ber\brn\bna\bal\bl \b A\bAd\bdd\bdr\bre\bes\bss\bs \b Q\bQu\bue\ber\bri\bie\bes\bs
+ $query_command , $\b$q\bqu\bue\ber\bry\by_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ <quit>, M\bMo\bov\bvi\bin\bng\bg \b A\bAr\bro\bou\bun\bnd\bd \b i\bin\bn \b M\bMe\ben\bnu\bus\bs, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs, $\b$q\bqu\bui\bit\bt, i\bin\bnd\bde\bex\bx,
+ p\bpa\bag\bge\ber\br
+
+ <quote-char>, E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs, e\bed\bdi\bit\bto\bor\br
+ $quote_regexp, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, U\bUs\bsi\bin\bng\bg \b c\bco\bol\blo\bor\br \b a\ban\bnd\bd \b m\bmo\bon\bno\bo \b v\bvi\bid\bde\beo\bo
+ a\bat\btt\btr\bri\bib\bbu\but\bte\bes\bs
+
+ $quote_empty , $\b$q\bqu\buo\bot\bte\be_\b_e\bem\bmp\bpt\bty\by
+ $quote_quoted , $\b$q\bqu\buo\bot\bte\be_\b_q\bqu\buo\bot\bte\bed\bd
+ $quote_regexp , $\b$q\bqu\buo\bot\bte\be_\b_r\bre\beg\bge\bex\bxp\bp
+
+R
+
+ <read-subthread>, T\bTh\bhr\bre\bea\bad\bde\bed\bd \b M\bMo\bod\bde\be, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ <read-thread>, T\bTh\bhr\bre\bea\bad\bde\bed\bd \b M\bMo\bod\bde\be, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ $read_inc , $\b$r\bre\bea\bad\bd_\b_i\bin\bnc\bc
+ $read_only , $\b$r\bre\bea\bad\bd_\b_o\bon\bnl\bly\by
+ $realname , $\b$r\bre\bea\bal\bln\bna\bam\bme\be
+ <rebuild-cache>, g\bge\ben\bne\ber\bri\bic\bc
+ $recall , $\b$r\bre\bec\bca\bal\bll\bl
+ <recall-message>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ $record, E\bEn\bnv\bvi\bir\bro\bon\bnm\bme\ben\bnt\bt \b V\bVa\bar\bri\bia\bab\bbl\ble\bes\bs, S\bSp\bpe\bec\bci\bif\bfy\by \b d\bde\bef\bfa\bau\bul\blt\bt \b F\bFc\bcc\bc:\b: \b m\bma\bai\bil\blb\bbo\box\bx \b w\bwh\bhe\ben\bn
+ c\bco\bom\bmp\bpo\bos\bsi\bin\bng\bg, M\bMa\bai\bil\blb\bbo\box\bx \b S\bSh\bho\bor\brt\btc\bcu\but\bts\bs, $\b$r\bre\bec\bco\bor\brd\bd
+
+ <redraw-screen>, p\bpa\bag\bge\ber\br
+ <refresh>, g\bge\ben\bne\ber\bri\bic\bc
+ <rename-file>, c\bco\bom\bmp\bpo\bos\bse\be
+ <reply>, S\bSe\ben\bnd\bdi\bin\bng\bg \b M\bMa\bai\bil\bl, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br, a\bat\btt\bta\bac\bch\bh
+ reply-hook, C\bCh\bha\ban\bng\bge\be \b s\bse\bet\btt\bti\bin\bng\bgs\bs \b b\bba\bas\bse\bed\bd \b u\bup\bpo\bon\bn \b m\bme\bes\bss\bsa\bag\bge\be \b r\bre\bec\bci\bip\bpi\bie\ben\bnt\bts\bs,
+ C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ $reply_to, A\bAl\blt\bte\ber\brn\bna\bat\bti\biv\bve\be \b a\bad\bdd\bdr\bre\bes\bss\bse\bes\bs, H\bHa\ban\bnd\bdl\bli\bin\bng\bg \b M\bMa\bai\bil\bli\bin\bng\bg \b L\bLi\bis\bst\bts\bs
+ $reply_regexp , $\b$r\bre\bep\bpl\bly\by_\b_r\bre\beg\bge\bex\bxp\bp
+ $reply_self , $\b$r\bre\bep\bpl\bly\by_\b_s\bse\bel\blf\bf
+ $reply_to , $\b$r\bre\bep\bpl\bly\by_\b_t\bto\bo
+ <resend-message>, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, T\bTh\bhe\be \b A\bAt\btt\bta\bac\bch\bhm\bme\ben\bnt\bt \b M\bMe\ben\bnu\bu, i\bin\bnd\bde\bex\bx,
+ a\bat\btt\bta\bac\bch\bh
+
+ reset, S\bSe\bet\btt\bti\bin\bng\bg \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ $resolve , $\b$r\bre\bes\bso\bol\blv\bve\be
+ $reverse_alias , $\b$r\bre\bev\bve\ber\brs\bse\be_\b_a\bal\bli\bia\bas\bs
+ $reverse_name , $\b$r\bre\bev\bve\ber\brs\bse\be_\b_n\bna\bam\bme\be
+ $reverse_realname , $\b$r\bre\bev\bve\ber\brs\bse\be_\b_r\bre\bea\bal\bln\bna\bam\bme\be
+ RfC
- $xterm_title , $xterm_title
+ 1524, M\bMI\bIM\bME\bE \b V\bVi\bie\bew\bwe\ber\br \b c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b w\bwi\bit\bth\bh \b m\bma\bai\bil\blc\bca\bap\bp, C\bCo\bom\bmm\bma\ban\bnd\bd \b E\bEx\bxp\bpa\ban\bns\bsi\bio\bon\bn,
+ m\bma\bai\bil\blc\bca\bap\bp
+
+ 1894, D\bDe\bel\bli\biv\bve\ber\bry\by \b S\bSt\bta\bat\btu\bus\bs \b N\bNo\bot\bti\bif\bfi\bic\bca\bat\bti\bio\bon\bn \b (\b(D\bDS\bSN\bN)\b) \b S\bSu\bup\bpp\bpo\bor\brt\bt
+ 2822, A\bAg\bga\bai\bin\bn:\b: \b S\bSc\bco\bor\bri\bin\bng\bg
+ 3676, S\bSe\ben\bnd\bdi\bin\bng\bg
+ 822, U\bUs\bse\ber\br \b d\bde\bef\bfi\bin\bne\bed\bd \b h\bhe\bea\bad\bde\ber\brs\bs
+
+ $rfc2047_parameters , $\b$r\brf\bfc\bc2\b20\b04\b47\b7_\b_p\bpa\bar\bra\bam\bme\bet\bte\ber\brs\bs
+
+S
+
+ $save_empty, C\bCo\bom\bmp\bpr\bre\bes\bss\bse\bed\bd \b f\bfo\bol\bld\bde\ber\brs\bs \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
+ <save-entry>, a\bat\btt\bta\bac\bch\bh
+ save-hook, S\bSp\bpe\bec\bci\bif\bfy\by \b d\bde\bef\bfa\bau\bul\blt\bt \b s\bsa\bav\bve\be \b f\bfi\bil\ble\ben\bna\bam\bme\be, S\bSp\bpe\bec\bci\bif\bfy\by \b d\bde\bef\bfa\bau\bul\blt\bt \b s\bsa\bav\bve\be
+ f\bfi\bil\ble\ben\bna\bam\bme\be \b a\ban\bnd\bd \b d\bde\bef\bfa\bau\bul\blt\bt \b F\bFc\bcc\bc:\b: \b m\bma\bai\bil\blb\bbo\box\bx \b a\bat\bt \b o\bon\bnc\bce\be, U\bUs\bsi\bin\bng\bg \b H\bHo\boo\bok\bks\bs, M\bMe\bes\bss\bsa\bag\bge\be
+ M\bMa\bat\btc\bch\bhi\bin\bng\bg \b i\bin\bn \b H\bHo\boo\bok\bks\bs, M\bMa\bai\bil\blb\bbo\box\bx \b S\bSh\bho\bor\brt\btc\bcu\but\bts\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ <save-message>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ $save_address , $\b$s\bsa\bav\bve\be_\b_a\bad\bdd\bdr\bre\bes\bss\bs
+ $save_empty , $\b$s\bsa\bav\bve\be_\b_e\bem\bmp\bpt\bty\by
+ $save_name , $\b$s\bsa\bav\bve\be_\b_n\bna\bam\bme\be
+ score, M\bMe\bes\bss\bsa\bag\bge\be \b S\bSc\bco\bor\bri\bin\bng\bg, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs, $\b$s\bsc\bco\bor\bre\be
+ $score_threshold_delete, M\bMe\bes\bss\bsa\bag\bge\be \b S\bSc\bco\bor\bri\bin\bng\bg
+ $score_threshold_flag, M\bMe\bes\bss\bsa\bag\bge\be \b S\bSc\bco\bor\bri\bin\bng\bg
+ $score_threshold_read, M\bMe\bes\bss\bsa\bag\bge\be \b S\bSc\bco\bor\bri\bin\bng\bg
+ $score_threshold_delete , $\b$s\bsc\bco\bor\bre\be_\b_t\bth\bhr\bre\bes\bsh\bho\bol\bld\bd_\b_d\bde\bel\ble\bet\bte\be
+ $score_threshold_flag , $\b$s\bsc\bco\bor\bre\be_\b_t\bth\bhr\bre\bes\bsh\bho\bol\bld\bd_\b_f\bfl\bla\bag\bg
+ $score_threshold_read , $\b$s\bsc\bco\bor\bre\be_\b_t\bth\bhr\bre\bes\bsh\bho\bol\bld\bd_\b_r\bre\bea\bad\bd
+ <search>, g\bge\ben\bne\ber\bri\bic\bc, p\bpa\bag\bge\ber\br, a\bal\bli\bia\bas\bs, q\bqu\bue\ber\bry\by, b\bbr\bro\bow\bws\bse\ber\br
+ <search-next>, g\bge\ben\bne\ber\bri\bic\bc, p\bpa\bag\bge\ber\br, a\bal\bli\bia\bas\bs, q\bqu\bue\ber\bry\by, b\bbr\bro\bow\bws\bse\ber\br
+ <search-opposite>, g\bge\ben\bne\ber\bri\bic\bc, p\bpa\bag\bge\ber\br, q\bqu\bue\ber\bry\by
+ <search-reverse>, g\bge\ben\bne\ber\bri\bic\bc, p\bpa\bag\bge\ber\br, a\bal\bli\bia\bas\bs, q\bqu\bue\ber\bry\by, b\bbr\bro\bow\bws\bse\ber\br
+ <search-toggle>, p\bpa\bag\bge\ber\br
+ <select-entry>, g\bge\ben\bne\ber\bri\bic\bc
+ <select-new>, b\bbr\bro\bow\bws\bse\ber\br
+ send-hook, C\bCh\bha\ban\bng\bge\be \b s\bse\bet\btt\bti\bin\bng\bgs\bs \b b\bba\bas\bse\bed\bd \b u\bup\bpo\bon\bn \b m\bme\bes\bss\bsa\bag\bge\be \b r\bre\bec\bci\bip\bpi\bie\ben\bnt\bts\bs, U\bUs\bsi\bin\bng\bg \b H\bHo\boo\bok\bks\bs,
+ M\bMe\bes\bss\bsa\bag\bge\be \b M\bMa\bat\btc\bch\bhi\bin\bng\bg \b i\bin\bn \b H\bHo\boo\bok\bks\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ <send-message>, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs, c\bco\bom\bmp\bpo\bos\bse\be
+ send2-hook, C\bCh\bha\ban\bng\bge\be \b s\bse\bet\btt\bti\bin\bng\bgs\bs \b b\bba\bas\bse\bed\bd \b u\bup\bpo\bon\bn \b m\bme\bes\bss\bsa\bag\bge\be \b r\bre\bec\bci\bip\bpi\bie\ben\bnt\bts\bs
+ <senderdecode-copy>, p\bpa\bag\bge\ber\br
+ $sendmail, C\bCh\bha\ban\bng\bge\be \b s\bse\bet\btt\bti\bin\bng\bgs\bs \b b\bba\bas\bse\bed\bd \b u\bup\bpo\bon\bn \b m\bme\bes\bss\bsa\bag\bge\be \b r\bre\bec\bci\bip\bpi\bie\ben\bnt\bts\bs, $\b$s\bse\ben\bnd\bdm\bma\bai\bil\bl
+ $sendmail_wait , $\b$s\bse\ben\bnd\bdm\bma\bai\bil\bl_\b_w\bwa\bai\bit\bt
+ $send_charset , $\b$s\bse\ben\bnd\bd_\b_c\bch\bha\bar\brs\bse\bet\bt
+ set, S\bSe\bet\btt\bti\bin\bng\bg \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ <set-flag>, i\bin\bnd\bde\bex\bx
+ $shell , $\b$s\bsh\bhe\bel\bll\bl
+ <shell-escape>, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, g\bge\ben\bne\ber\bri\bic\bc, p\bpa\bag\bge\ber\br
+ <show-limit>, i\bin\bnd\bde\bex\bx
+ <show-version>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ <sidebar-next>, s\bsi\bid\bde\beb\bba\bar\br
+ <sidebar-next-new>, s\bsi\bid\bde\beb\bba\bar\br
+ <sidebar-open>, s\bsi\bid\bde\beb\bba\bar\br
+ <sidebar-previous>, s\bsi\bid\bde\beb\bba\bar\br
+ <sidebar-scroll-down>, s\bsi\bid\bde\beb\bba\bar\br
+ <sidebar-scroll-up>, s\bsi\bid\bde\beb\bba\bar\br
+ $sidebar_shorten_hierarchy , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $sidebar_boundary , $\b$s\bsi\bid\bde\beb\bba\bar\br_\b_b\bbo\bou\bun\bnd\bda\bar\bry\by
+ $sidebar_delim , $\b$s\bsi\bid\bde\beb\bba\bar\br_\b_d\bde\bel\bli\bim\bm
+ $sidebar_newmail_only , $\b$s\bsi\bid\bde\beb\bba\bar\br_\b_n\bne\bew\bwm\bma\bai\bil\bl_\b_o\bon\bnl\bly\by
+ $sidebar_number_format , $\b$s\bsi\bid\bde\beb\bba\bar\br_\b_n\bnu\bum\bmb\bbe\ber\br_\b_f\bfo\bor\brm\bma\bat\bt
+ $sidebar_shorten_hierarchy , $\b$s\bsi\bid\bde\beb\bba\bar\br_\b_s\bsh\bho\bor\brt\bte\ben\bn_\b_h\bhi\bie\ber\bra\bar\brc\bch\bhy\by
+ $sidebar_visible , $\b$s\bsi\bid\bde\beb\bba\bar\br_\b_v\bvi\bis\bsi\bib\bbl\ble\be
+ $sidebar_width , $\b$s\bsi\bid\bde\beb\bba\bar\br_\b_w\bwi\bid\bdt\bth\bh
+ $signature, C\bCh\bha\ban\bng\bge\be \b s\bse\bet\btt\bti\bin\bng\bgs\bs \b b\bba\bas\bse\bed\bd \b u\bup\bpo\bon\bn \b m\bme\bes\bss\bsa\bag\bge\be \b r\bre\bec\bci\bip\bpi\bie\ben\bnt\bts\bs, $\b$s\bsi\big\bgn\bna\bat\btu\bur\bre\be
+ $signoff_string , $\b$s\bsi\big\bgn\bno\bof\bff\bf_\b_s\bst\btr\bri\bin\bng\bg
+ $sig_dashes , $\b$s\bsi\big\bg_\b_d\bda\bas\bsh\bhe\bes\bs
+ $sig_on_top , $\b$s\bsi\big\bg_\b_o\bon\bn_\b_t\bto\bop\bp
+ $simple_search , $\b$s\bsi\bim\bmp\bpl\ble\be_\b_s\bse\bea\bar\brc\bch\bh
+ <skip-quoted>, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, p\bpa\bag\bge\ber\br
+ $sleep_time , $\b$s\bsl\ble\bee\bep\bp_\b_t\bti\bim\bme\be
+ $smart_wrap , $\b$s\bsm\bma\bar\brt\bt_\b_w\bwr\bra\bap\bp
+ $smileys , $\b$s\bsm\bmi\bil\ble\bey\bys\bs
+ $smime_default_key , C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ <smime-menu>, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs
+ $smime_ask_cert_label , $\b$s\bsm\bmi\bim\bme\be_\b_a\bas\bsk\bk_\b_c\bce\ber\brt\bt_\b_l\bla\bab\bbe\bel\bl
+ $smime_ca_location , $\b$s\bsm\bmi\bim\bme\be_\b_c\bca\ba_\b_l\blo\boc\bca\bat\bti\bio\bon\bn
+ $smime_certificates , $\b$s\bsm\bmi\bim\bme\be_\b_c\bce\ber\brt\bti\bif\bfi\bic\bca\bat\bte\bes\bs
+ $smime_decrypt_command , $\b$s\bsm\bmi\bim\bme\be_\b_d\bde\bec\bcr\bry\byp\bpt\bt_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $smime_decrypt_use_default_key , $\b$s\bsm\bmi\bim\bme\be_\b_d\bde\bec\bcr\bry\byp\bpt\bt_\b_u\bus\bse\be_\b_d\bde\bef\bfa\bau\bul\blt\bt_\b_k\bke\bey\by
+ $smime_default_key , $\b$s\bsm\bmi\bim\bme\be_\b_d\bde\bef\bfa\bau\bul\blt\bt_\b_k\bke\bey\by
+ $smime_encrypt_command , $\b$s\bsm\bmi\bim\bme\be_\b_e\ben\bnc\bcr\bry\byp\bpt\bt_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $smime_encrypt_with , $\b$s\bsm\bmi\bim\bme\be_\b_e\ben\bnc\bcr\bry\byp\bpt\bt_\b_w\bwi\bit\bth\bh
+ $smime_get_cert_command , $\b$s\bsm\bmi\bim\bme\be_\b_g\bge\bet\bt_\b_c\bce\ber\brt\bt_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $smime_get_cert_email_command , $\b$s\bsm\bmi\bim\bme\be_\b_g\bge\bet\bt_\b_c\bce\ber\brt\bt_\b_e\bem\bma\bai\bil\bl_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $smime_get_signer_cert_command , $\b$s\bsm\bmi\bim\bme\be_\b_g\bge\bet\bt_\b_s\bsi\big\bgn\bne\ber\br_\b_c\bce\ber\brt\bt_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $smime_import_cert_command , $\b$s\bsm\bmi\bim\bme\be_\b_i\bim\bmp\bpo\bor\brt\bt_\b_c\bce\ber\brt\bt_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $smime_is_default , $\b$s\bsm\bmi\bim\bme\be_\b_i\bis\bs_\b_d\bde\bef\bfa\bau\bul\blt\bt
+ $smime_keys , $\b$s\bsm\bmi\bim\bme\be_\b_k\bke\bey\bys\bs
+ $smime_pk7out_command , $\b$s\bsm\bmi\bim\bme\be_\b_p\bpk\bk7\b7o\bou\but\bt_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $smime_sign_command , $\b$s\bsm\bmi\bim\bme\be_\b_s\bsi\big\bgn\bn_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $smime_sign_opaque_command , $\b$s\bsm\bmi\bim\bme\be_\b_s\bsi\big\bgn\bn_\b_o\bop\bpa\baq\bqu\bue\be_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $smime_timeout , $\b$s\bsm\bmi\bim\bme\be_\b_t\bti\bim\bme\beo\bou\but\bt
+ $smime_verify_command , $\b$s\bsm\bmi\bim\bme\be_\b_v\bve\ber\bri\bif\bfy\by_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $smime_verify_opaque_command , $\b$s\bsm\bmi\bim\bme\be_\b_v\bve\ber\bri\bif\bfy\by_\b_o\bop\bpa\baq\bqu\bue\be_\b_c\bco\bom\bmm\bma\ban\bnd\bd
+ $smtp_envelope, S\bSM\bMT\bTP\bP \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
+ $smtp_host, S\bSM\bMT\bTP\bP \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
+ $smtp_pass, S\bSM\bMT\bTP\bP \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b), C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $smtp_use_tls, S\bSM\bMT\bTP\bP \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
+ $smtp_user, S\bSM\bMT\bTP\bP \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b), C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ $smtp_host , $\b$s\bsm\bmt\btp\bp_\b_h\bho\bos\bst\bt
+ $smtp_pass , $\b$s\bsm\bmt\btp\bp_\b_p\bpa\bas\bss\bs
+ $smtp_port , $\b$s\bsm\bmt\btp\bp_\b_p\bpo\bor\brt\bt
+ $smtp_user , $\b$s\bsm\bmt\btp\bp_\b_u\bus\bse\ber\br
+ $smtp_use_tls , $\b$s\bsm\bmt\btp\bp_\b_u\bus\bse\be_\b_t\btl\bls\bs
+ $sort , $\b$s\bso\bor\brt\bt, b\bbr\bro\bow\bws\bse\ber\br
+ <sort-mailbox>, i\bin\bnd\bde\bex\bx
+ <sort-reverse>, i\bin\bnd\bde\bex\bx, b\bbr\bro\bow\bws\bse\ber\br
+ $sort_alias , $\b$s\bso\bor\brt\bt_\b_a\bal\bli\bia\bas\bs
+ $sort_aux , $\b$s\bso\bor\brt\bt_\b_a\bau\bux\bx
+ $sort_browser , $\b$s\bso\bor\brt\bt_\b_b\bbr\bro\bow\bws\bse\ber\br
+ $sort_re , $\b$s\bso\bor\brt\bt_\b_r\bre\be
+ source, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, D\bDe\bef\bfi\bin\bni\bin\bng\bg/\b/U\bUs\bsi\bin\bng\bg \b a\bal\bli\bia\bas\bse\bes\bs, R\bRe\bea\bad\bdi\bin\bng\bg
+ i\bin\bni\bit\bti\bia\bal\bli\biz\bza\bat\bti\bio\bon\bn \b c\bco\bom\bmm\bma\ban\bnd\bds\bs \b f\bfr\bro\bom\bm \b a\ban\bno\bot\bth\bhe\ber\br \b f\bfi\bil\ble\be, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn
+ C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ spam, S\bSp\bpa\bam\bm \b d\bde\bet\bte\bec\bct\bti\bio\bon\bn, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ $spam_separator , $\b$s\bsp\bpa\bam\bm_\b_s\bse\bep\bpa\bar\bra\bat\bto\bor\br
+ $spoolfile, S\bSe\bet\btt\bti\bin\bng\bg \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs \b b\bba\bas\bse\bed\bd \b u\bup\bpo\bon\bn \b m\bma\bai\bil\blb\bbo\box\bx, D\bDe\bef\bfi\bin\bni\bin\bng\bg \b m\bma\bai\bil\blb\bbo\box\bxe\bes\bs
+ w\bwh\bhi\bic\bch\bh \b r\bre\bec\bce\bei\biv\bve\be \b m\bma\bai\bil\bl, M\bMa\bai\bil\blb\bbo\box\bx \b S\bSh\bho\bor\brt\btc\bcu\but\bts\bs, P\bPO\bOP\bP3\b3 \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b),
+ $\b$s\bsp\bpo\boo\bol\blf\bfi\bil\ble\be
+
+ $ssl_ca_certificates_file , $\b$s\bss\bsl\bl_\b_c\bca\ba_\b_c\bce\ber\brt\bti\bif\bfi\bic\bca\bat\bte\bes\bs_\b_f\bfi\bil\ble\be
+ $ssl_client_cert , $\b$s\bss\bsl\bl_\b_c\bcl\bli\bie\ben\bnt\bt_\b_c\bce\ber\brt\bt
+ $ssl_force_tls , $\b$s\bss\bsl\bl_\b_f\bfo\bor\brc\bce\be_\b_t\btl\bls\bs
+ $ssl_min_dh_prime_bits , $\b$s\bss\bsl\bl_\b_m\bmi\bin\bn_\b_d\bdh\bh_\b_p\bpr\bri\bim\bme\be_\b_b\bbi\bit\bts\bs
+ $ssl_starttls , $\b$s\bss\bsl\bl_\b_s\bst\bta\bar\brt\btt\btl\bls\bs
+ $ssl_usesystemcerts , $\b$s\bss\bsl\bl_\b_u\bus\bse\bes\bsy\bys\bst\bte\bem\bmc\bce\ber\brt\bts\bs
+ $ssl_use_sslv2 , $\b$s\bss\bsl\bl_\b_u\bus\bse\be_\b_s\bss\bsl\blv\bv2\b2
+ $ssl_use_sslv3 , $\b$s\bss\bsl\bl_\b_u\bus\bse\be_\b_s\bss\bsl\blv\bv3\b3
+ $ssl_use_tlsv1 , $\b$s\bss\bsl\bl_\b_u\bus\bse\be_\b_t\btl\bls\bsv\bv1\b1
+ $status_format, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs, I\bIn\bnt\btr\bro\bod\bdu\buc\bct\bti\bio\bon\bn
+ $status_chars , $\b$s\bst\bta\bat\btu\bus\bs_\b_c\bch\bha\bar\brs\bs
+ $status_format , $\b$s\bst\bta\bat\btu\bus\bs_\b_f\bfo\bor\brm\bma\bat\bt
+ $status_on_top , $\b$s\bst\bta\bat\btu\bus\bs_\b_o\bon\bn_\b_t\bto\bop\bp
+ $strict_mailto, m\bma\bai\bil\blt\bto\bo:\b:-\b-s\bst\bty\byl\ble\be \b l\bli\bin\bnk\bks\bs
+ $strict_threads, T\bTh\bhr\bre\bea\bad\bde\bed\bd \b M\bMo\bod\bde\be
+ $strict_mailto , $\b$s\bst\btr\bri\bic\bct\bt_\b_m\bma\bai\bil\blt\bto\bo
+ $strict_mime , $\b$s\bst\btr\bri\bic\bct\bt_\b_m\bmi\bim\bme\be
+ $strict_threads , $\b$s\bst\btr\bri\bic\bct\bt_\b_t\bth\bhr\bre\bea\bad\bds\bs
+ $strip_was , $\b$s\bst\btr\bri\bip\bp_\b_w\bwa\bas\bs
+ $strip_was_regex , $\b$s\bst\btr\bri\bip\bp_\b_w\bwa\bas\bs_\b_r\bre\beg\bge\bex\bx
+ $stuff_quoted , $\b$s\bst\btu\buf\bff\bf_\b_q\bqu\buo\bot\bte\bed\bd
+ subscribe, M\bMa\bai\bil\bli\bin\bng\bg \b l\bli\bis\bst\bts\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs, b\bbr\bro\bow\bws\bse\ber\br
+ $suspend , $\b$s\bsu\bus\bsp\bpe\ben\bnd\bd
+ <sync-mailbox>, M\bMa\ban\bnu\bua\bal\bl \b C\bCo\bon\bnv\bve\ben\bnt\bti\bio\bon\bns\bs, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+
+T
+
+ <tag-entry>, g\bge\ben\bne\ber\bri\bic\bc
+ <tag-message>, p\bpa\bag\bge\ber\br
+ <tag-pattern>, i\bin\bnd\bde\bex\bx
+ <tag-prefix>, g\bge\ben\bne\ber\bri\bic\bc
+ <tag-prefix-cond>, g\bge\ben\bne\ber\bri\bic\bc
+ <tag-thread>, T\bTh\bhr\bre\bea\bad\bde\bed\bd \b M\bMo\bod\bde\be, i\bin\bnd\bde\bex\bx
+ $text_flowed , $\b$t\bte\bex\bxt\bt_\b_f\bfl\blo\bow\bwe\bed\bd
+ $thorough_search , $\b$t\bth\bho\bor\bro\bou\bug\bgh\bh_\b_s\bse\bea\bar\brc\bch\bh
+ $thread_received , $\b$t\bth\bhr\bre\bea\bad\bd_\b_r\bre\bec\bce\bei\biv\bve\bed\bd
+ $tilde , $\b$t\bti\bil\bld\bde\be
+ $timeout, I\bIM\bMA\bAP\bP \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b), $\b$t\bti\bim\bme\beo\bou\but\bt
+ $tmpdir, T\bTe\bem\bmp\bpo\bor\bra\bar\bry\by \b F\bFi\bil\ble\bes\bs, $\b$t\btm\bmp\bpd\bdi\bir\br
+ $to_chars, S\bSt\bta\bat\btu\bus\bs \b F\bFl\bla\bag\bgs\bs
+ toggle, S\bSe\bet\btt\bti\bin\bng\bg \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ <toggle-mailboxes>, b\bbr\bro\bow\bws\bse\ber\br
+ <toggle-new>, i\bin\bnd\bde\bex\bx
+ <toggle-quoted>, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, p\bpa\bag\bge\ber\br
+ <toggle-subscribed>, b\bbr\bro\bow\bws\bse\ber\br
+ <toggle-unlink>, c\bco\bom\bmp\bpo\bos\bse\be
+ <toggle-write>, i\bin\bnd\bde\bex\bx
+ <top>, p\bpa\bag\bge\ber\br
+ <top-page>, g\bge\ben\bne\ber\bri\bic\bc
+ $to_chars , $\b$t\bto\bo_\b_c\bch\bha\bar\brs\bs
+ <transpose-chars>, e\bed\bdi\bit\bto\bor\br
+ $trash , $\b$t\btr\bra\bas\bsh\bh
+ $tunnel , $\b$t\btu\bun\bnn\bne\bel\bl
+
+U
+
+ $umask, T\bTe\bem\bmp\bpo\bor\bra\bar\bry\by \b F\bFi\bil\ble\bes\bs, $\b$u\bum\bma\bas\bsk\bk
+ unalias, D\bDe\bef\bfi\bin\bni\bin\bng\bg/\b/U\bUs\bsi\bin\bng\bg \b a\bal\bli\bia\bas\bse\bes\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ unalternates, A\bAl\blt\bte\ber\brn\bna\bat\bti\biv\bve\be \b a\bad\bdd\bdr\bre\bes\bss\bse\bes\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ unalternative_order, M\bMI\bIM\bME\bE \b M\bMu\bul\blt\bti\bip\bpa\bar\brt\bt/\b/A\bAl\blt\bte\ber\brn\bna\bat\bti\biv\bve\be, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn
+ C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ unattachments, A\bAt\btt\bta\bac\bch\bhm\bme\ben\bnt\bt \b S\bSe\bea\bar\brc\bch\bhi\bin\bng\bg \b a\ban\bnd\bd \b C\bCo\bou\bun\bnt\bti\bin\bng\bg
+ unauto_view, M\bMI\bIM\bME\bE \b A\bAu\but\bto\bov\bvi\bie\bew\bw, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ $uncollapse_jump , $\b$u\bun\bnc\bco\bol\bll\bla\bap\bps\bse\be_\b_j\bju\bum\bmp\bp
+ uncolor, U\bUs\bsi\bin\bng\bg \b c\bco\bol\blo\bor\br \b a\ban\bnd\bd \b m\bmo\bon\bno\bo \b v\bvi\bid\bde\beo\bo \b a\bat\btt\btr\bri\bib\bbu\but\bte\bes\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ <undelete-entry>, a\bat\btt\bta\bac\bch\bh, p\bpo\bos\bst\btp\bpo\bon\bne\be
+ <undelete-message>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ <undelete-pattern>, i\bin\bnd\bde\bex\bx
+ <undelete-subthread>, T\bTh\bhr\bre\bea\bad\bde\bed\bd \b M\bMo\bod\bde\be, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ <undelete-thread>, T\bTh\bhr\bre\bea\bad\bde\bed\bd \b M\bMo\bod\bde\be, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ unhdr_order, D\bDe\bef\bfi\bin\bni\bin\bng\bg \b t\bth\bhe\be \b o\bor\brd\bde\ber\br \b o\bof\bf \b h\bhe\bea\bad\bde\ber\brs\bs \b w\bwh\bhe\ben\bn \b v\bvi\bie\bew\bwi\bin\bng\bg \b m\bme\bes\bss\bsa\bag\bge\bes\bs,
+ C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ unhook, R\bRe\bem\bmo\bov\bvi\bin\bng\bg \b h\bho\boo\bok\bks\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ unignore, I\bIg\bgn\bno\bor\bri\bin\bng\bg \b (\b(w\bwe\bee\bed\bdi\bin\bng\bg)\b) \b u\bun\bnw\bwa\ban\bnt\bte\bed\bd \b m\bme\bes\bss\bsa\bag\bge\be \b h\bhe\bea\bad\bde\ber\brs\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn
+ C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+
+ unlists, M\bMa\bai\bil\bli\bin\bng\bg \b l\bli\bis\bst\bts\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ unmailboxes, D\bDe\bef\bfi\bin\bni\bin\bng\bg \b m\bma\bai\bil\blb\bbo\box\bxe\bes\bs \b w\bwh\bhi\bic\bch\bh \b r\bre\bec\bce\bei\biv\bve\be \b m\bma\bai\bil\bl
+ unmime_lookup, M\bMI\bIM\bME\bE \b L\bLo\boo\bok\bku\bup\bp, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ unmono, U\bUs\bsi\bin\bng\bg \b c\bco\bol\blo\bor\br \b a\ban\bnd\bd \b m\bmo\bon\bno\bo \b v\bvi\bid\bde\beo\bo \b a\bat\btt\btr\bri\bib\bbu\but\bte\bes\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ unmy_hdr, U\bUs\bse\ber\br \b d\bde\bef\bfi\bin\bne\bed\bd \b h\bhe\bea\bad\bde\ber\brs\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ unscore, M\bMe\bes\bss\bsa\bag\bge\be \b S\bSc\bco\bor\bri\bin\bng\bg, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ unset, S\bSe\bet\btt\bti\bin\bng\bg \b v\bva\bar\bri\bia\bab\bbl\ble\bes\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ unsubscribe, M\bMa\bai\bil\bli\bin\bng\bg \b l\bli\bis\bst\bts\bs, C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn \b C\bCo\bom\bmm\bma\ban\bnd\bds\bs, b\bbr\bro\bow\bws\bse\ber\br
+ <untag-pattern>, i\bin\bnd\bde\bex\bx
+ <upcase-word>, E\bEd\bdi\bit\bti\bin\bng\bg \b I\bIn\bnp\bpu\but\bt \b F\bFi\bie\bel\bld\bds\bs, e\bed\bdi\bit\bto\bor\br
+ $use_8bitmime, S\bSM\bMT\bTP\bP \b S\bSu\bup\bpp\bpo\bor\brt\bt \b (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
+ $use_8bitmime , $\b$u\bus\bse\be_\b_8\b8b\bbi\bit\btm\bmi\bim\bme\be
+ $use_domain , $\b$u\bus\bse\be_\b_d\bdo\bom\bma\bai\bin\bn
+ $use_envelope_from , $\b$u\bus\bse\be_\b_e\ben\bnv\bve\bel\blo\bop\bpe\be_\b_f\bfr\bro\bom\bm
+ $use_from , $\b$u\bus\bse\be_\b_f\bfr\bro\bom\bm
+ $use_idn , $\b$u\bus\bse\be_\b_i\bid\bdn\bn
+ $use_ipv6 , $\b$u\bus\bse\be_\b_i\bip\bpv\bv6\b6
+
+V
+
+ <verify-key>, p\bpg\bgp\bp
+ <view-attach>, a\bat\btt\bta\bac\bch\bh, c\bco\bom\bmp\bpo\bos\bse\be
+ <view-attachments>, i\bin\bnd\bde\bex\bx, p\bpa\bag\bge\ber\br
+ <view-file>, b\bbr\bro\bow\bws\bse\ber\br
+ <view-mailcap>, a\bat\btt\bta\bac\bch\bh
+ <view-name>, p\bpg\bgp\bp
+ <view-text>, a\bat\btt\bta\bac\bch\bh
+ $VISUAL, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs
+ $visual , $\b$v\bvi\bis\bsu\bua\bal\bl
+
+W
+
+ $wait_key, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, O\bOp\bpt\bti\bio\bon\bna\bal\bl \b F\bFi\bie\bel\bld\bds\bs
+ $wait_key , $\b$w\bwa\bai\bit\bt_\b_k\bke\bey\by
+ $weed, M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs \b F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs, $\b$w\bwe\bee\bed\bd
+ <what-key>, g\bge\ben\bne\ber\bri\bic\bc
+ $wrapmargin , $\b$w\bwr\bra\bap\bpm\bma\bar\brg\bgi\bin\bn
+ $wrap_search , $\b$w\bwr\bra\bap\bp_\b_s\bse\bea\bar\brc\bch\bh
+ <write-fcc>, C\bCo\bom\bmp\bpo\bos\bsi\bin\bng\bg \b n\bne\bew\bw \b m\bme\bes\bss\bsa\bag\bge\bes\bs, c\bco\bom\bmp\bpo\bos\bse\be
+ $write_bcc , $\b$w\bwr\bri\bit\bte\be_\b_b\bbc\bcc\bc
+ $write_inc , $\b$w\bwr\bri\bit\bte\be_\b_i\bin\bnc\bc
+
+X
+
+ $xterm_icon , $\b$x\bxt\bte\ber\brm\bm_\b_i\bic\bco\bon\bn
+ $xterm_leave , $\b$x\bxt\bte\ber\brm\bm_\b_l\ble\bea\bav\bve\be
+ $xterm_set_titles , $\b$x\bxt\bte\ber\brm\bm_\b_s\bse\bet\bt_\b_t\bti\bit\btl\ble\bes\bs
+ $xterm_title , $\b$x\bxt\bte\ber\brm\bm_\b_t\bti\bit\btl\ble\be
projects / apps / madmutt.git / commitdiff